[Bug 226495] GPU freeze on Sandy Bridge system

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226495

            Bug ID: 226495
           Summary: GPU freeze on Sandy Bridge system
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: rkoberman at gmail.com

Since the last MESA update, my ThinkPad T520 with Sandy Bridge graphics has
been freezing intermittently. It has done so four times with nothing obvious in
common, so it is quite infrequent. Running standard DRM, not drm-next. (I plan
to try that shortly.) 

I have not been able to get the system to recover except to ssh in from my
phone and kill xinit. I can then restart MATE and all is well again.

I log the following:
Mar  9 08:20:12 rogue kernel: error: [drm:pid1599:__gen6_gt_force_wake_get]
*ERROR* Timed out waiting for forcewake to ack request.
Mar  9 08:20:12 rogue kernel: error: [drm:pid1599:__gen6_gt_wait_for_thread_c0]
*ERROR* GT thread status wait timed out
Mar  9 08:20:12 rogue kernel: error: [drm:pid1599:gen6_gt_check_fifodbg]
*ERROR* MMIO read or write has been dropped 3
Mar  9 08:21:12 rogue kernel: error: [drm:pid12:i915_hangcheck_hung] *ERROR*
Hangcheck timer elapsed... GPU hung
Mar  9 08:21:12 rogue kernel: info: [drm] capturing error event; look for more
information in sysctl hw.dri.0.info.i915_error_state

I have a copy of the contents of hw.dri.0.info.i915_error_state from after the
restart of mate, though I have no idea if it remains valid after the restart of
X and mate. I will attach the text.

These errors (except the last two lines) do occur from time to time, but the
recovery is usually quick, often too quickly to be noticed and other times
causing a brief pause. I believe these happened on older DRM versions, but
without the freezes.

I have a copy of the contents of hw.dri.0.info.i915_error_state from after the
restart of mate, though I have no idea if it remains valid a

The system is running 11-STABLE:
FreeBSD rogue 11.1-STABLE FreeBSD 11.1-STABLE #0 r330560: Wed Mar  7 09:09:42
PST 2018     root at rogue:/usr/obj/usr/src/sys/GENERIC.4BSD  amd64


info: [drm] Initialized drm 1.1.0 20060810
CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz (2491.96-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206a7  Family=0x6  Model=0x2a  Stepping=7
 
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,$
 
Features2=0x1fbae3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,C$
  AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  XSAVE Features=0x1<XSAVEOPT>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics

-- 
You are receiving this mail because:
You are the assignee for the bug.