| Summary: | after Kernel Update to 3.15.6-40.2.gfdb2dde i915 G850 GPU HANG: ecode 0:0xf4e9fffe, in Xorg [698], reason: Ring hung, action: reset | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | f.st | ||||||||||
| Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | intel-gfx-bugs | ||||||||||
| Version: | XOrg git | ||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
f.st
2014-07-24 10:11:19 UTC
Created attachment 103395 [details]
enabling Option Tearfree and SNA
Trying booting now with i915.semaphores=1 linux /boot/vmlinuz-3.15.6-40.gfdb2dde-desktop root=UUID=fc2823aa-e3b-4fd4-8111-aa16ef2538de resume=/dev/disk/by-id/ata-OCZ-VERTEX4_OCZ-CPQ92H5W3DKY9T58-part2 splash=silent quiet showopts i915.semaphores=1 booting with i915.semaphores=1 doesn't solve the problem trying change from SNA to UXA now "/sys/class/drm/card0/error" dump file is always 0-length so now upload possible 2014-07-24T12:32:42.914130+02:00 peacy kernel: [ 837.937346] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue 2014-07-24T12:32:42.914143+02:00 peacy kernel: [ 837.937354] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. 2014-07-24T12:32:42.914144+02:00 peacy kernel: [ 837.937356] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel 2014-07-24T12:32:42.914145+02:00 peacy kernel: [ 837.937357] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. 2014-07-24T12:32:42.914145+02:00 peacy kernel: [ 837.937358] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. 2014-07-24T12:32:42.914146+02:00 peacy kernel: [ 837.937360] [drm] GPU crash dump saved to /sys/class/drm/card0/error 2014-07-24T12:40:26.910209+02:00 peacy kernel: [ 1302.056521] [drm] stuck on render ring 2014-07-24T12:40:26.910221+02:00 peacy kernel: [ 1302.056529] [drm] stuck on blitter ring 2014-07-24T12:40:26.910222+02:00 peacy kernel: [ 1302.057067] [drm] GPU HANG: ecode 0:0xf4e9fffe, in Xorg [680], reason: Ring hung, action: reset 2014-07-24T12:40:26.910725+02:00 peacy kernel: [ 1302.057269] [drm:i915_context_is_banned] *ERROR* gpu hanging too fast, banning! 2014-07-24T12:40:28.910542+02:00 peacy kernel: [ 1304.057239] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off Created attachment 103396 [details]
/var/log/messages
(In reply to comment #3) > booting with i915.semaphores=1 doesn't solve the problem No, i915.semaphores=0 would. Well that's a guess since you didn't follow: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error please see above, the mentioned dump is empty (0-length) UXA seems more stable, but slow and tearing. I'll try SNA and i915.semaphores=0 now. in the short time now, it seems, that SNA/Tearfree and i915.semaphores=0 resolved the problem. I'll get back to you in case the problem occurs again. Thank you, Chris ! Frank Just cat /sys/class/drm/card0/error - it's a virtual file so its size is always reported as zero but it does have content! OK done that : peacy:~ # cat /sys/class/drm/card0/error no error state collected I'll do it again immediately after the error ... wait Created attachment 103399 [details]
cat /sys/class/drm/card0/error >/tmp/dumpfile
Created attachment 103400 [details]
current messages
Hi Chris, now I was successful collection the dump. Thank you Frank As expected it is the semaphore hang. *** This bug has been marked as a duplicate of bug 54226 *** |
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.