Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#55945 - [mesa] GPU hangs ecode 6:0:0x85fffffc

Attached to Project: Arch Linux
Opened by Christian Rebischke (Shibumi) - Tuesday, 10 October 2017, 23:02 GMT
Last edited by Laurent Carlier (lordheavy) - Wednesday, 25 October 2017, 04:24 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Laurent Carlier (lordheavy)
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


The GPU hangs in games like 0ad and spring-RTS-engine based games. Sometimes the hang is over after a few minutes. But most of the time the whole system just stucks and is impossible to reset. No kernel panic. Nothing. Just a stucked screen. Even sysrq doesn't help to reboot the machine safely. This behaviour does only occur in games. desktop with i3 + chromium and other applications works fine.

Journal-Logs: (see the upstream-report for a GPU crash dump)
[drm] GPU HANG: ecode 6:0:0x85fffffc, in pyrogenesis [24779], reason: Hang on rcs0, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[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
drm/i915: Resetting chip after gpu hang

This task depends upon

Closed by  Laurent Carlier (lordheavy)
Wednesday, 25 October 2017, 04:24 GMT
Reason for closing:  Fixed
Comment by Christian Rebischke (Shibumi) - Wednesday, 11 October 2017, 17:37 GMT
I've added a apitrace from such a GPU hang to the upstream-report.
Comment by Christian Rebischke (Shibumi) - Tuesday, 24 October 2017, 23:12 GMT
This bug is not an issue anymore. Since round about a week it's working as expected, although the mesa version hasn't changed. So I guess it was another packages fault. However everything working fine now.
Comment by Laurent Carlier (lordheavy) - Wednesday, 25 October 2017, 04:23 GMT
Thanks for the report, now closing