| Summary: | GPU Hang Triage (GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Andrew Pikul <ajpikul> | ||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
| Severity: | normal | ||||||
| Priority: | medium | CC: | intel-gfx-bugs | ||||
| Version: | unspecified | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
Semaphores are now disabled on gen6; use i915.semaphores=0 in the meantime. *** This bug has been marked as a duplicate of bug 54226 *** Closing as dup closed too. |
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.
Created attachment 138898 [details] What I was told to attach by dmesg [drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue [231430.174287] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [231430.174287] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [231430.174288] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [231430.174289] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [231430.174290] [drm] GPU crash dump saved to /sys/class/drm/card0/error [232408.242876] kworker/dying (16698) used greatest stack depth: 10936 bytes left I saw this on another thread: can you reproduce issue with "drm.debug=0xe" in your boot command line and then attached your dmesg. So I'll do that too, but it's an "I don't know how to reproduce it but I know it'll happen again" type thing.