Created attachment 118746 [details] output of /sys/class/drm/card0/error I have an old pentium D (4GB) desktop with an intel 3000 gfx chipset. It is old, but after upgrading to debian jessie, i've had some pretty regular issues. Upon waking from screensaver for an extended period, something happening in chrome or a more major operation in a cad program (openSCAD, freecad or cura), the GFX support drops out and I can't open the cad programs again without a reboot. Chrome will still work fine. From my research, a lot of people have similar issues in Ubuntu and are using intel-based GFX, so it may just be a problem with the driver. Here is the dmesg output following a failed SCAD render. [ 1667.804027] [drm] stuck on render ring [ 1667.807191] [drm] GPU HANG: ecode 0:0x8644f8fe, in chrome [1403], reason: Ring hung, action: reset [ 1667.807195] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1667.807197] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1667.807200] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1667.807202] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1667.807204] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1667.808643] [drm:i915_reset] *ERROR* Failed to reset chip: -19 I've also attached a copy of the /sys/class/drm/card0/error info to this message. Thanks so much for working on this.
Is this still an issue with current kernels and mesa?
There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa (or at least with update your debian) to see if this issue is still occurring. In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang). Kernel: 3.16.0-4-amd64 Platform: Q963/Q965 (pci id: 0x2992) Mesa: [Please confirm your mesa version] From this error dump, hung is happening in render ring batch with active head at 0x0f90ee5c, with 0x79010003 (3DSTATE_CONSTANT_COLOR) as IPEHR. Batch extract (around 0x0f90ee5c): 0x0f90ee40: 0x78010004: 3DSTATE_BINDING_TABLE_POINTERS 0x0f90ee44: 0x00006300: VS binding table 0x0f90ee48: 0x00000000: GS binding table 0x0f90ee4c: 0x00000000: Clip binding table 0x0f90ee50: 0x00000000: SF binding table 0x0f90ee54: 0x000062e0: WM binding table 0x0f90ee58: 0x79010003: 3DSTATE_CONSTANT_COLOR 0x0f90ee5c: 0x00000000: dword 1 0x0f90ee60: 0x00000000: dword 2 0x0f90ee64: 0x00000000: dword 3 0x0f90ee68: 0x00000000: dword 4 0x0f90ee6c: 0x78000005: 3DSTATE_PIPELINED_POINTERS 0x0f90ee70: 0x0f914220: VS state 0x0f90ee74: 0x00000000: GS state 0x0f90ee78: 0x0f9141c1: Clip state 0x0f90ee7c: 0x0f914240: SF state 0x0f90ee80: 0x0f914260: WM state 0x0f90ee84: 0x0f914380: CC state
Dear Reporter, This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested. Thank you.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.