| Summary: | GPU HANG: ecode -1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Vasil Kolev <vasil> | ||||
| 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: |
|
||||||
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 109147 [details] /sys/class/drm/card0/error Got this in dmesg: [52085.917318] [drm] GPU HANG: ecode -1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue [52085.917324] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [52085.917325] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [52085.917326] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [52085.917326] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [52085.917337] [drm] GPU crash dump saved to /sys/class/drm/card0/error This is on debian jessie, this is the output of uname -a: Linux nymphadora 3.16-3-amd64 #1 SMP Debian 3.16.5-1 (2014-10-10) x86_64 GNU/Linux Is this the proper place for this bug, or debian's bug tracker?