[Bug 106333] New: GPU HANG: ecode 9:1:0xfefffffe, in Xorg [600], reason: Hang on bcs0, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue May 1 12:36:27 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=106333
Bug ID: 106333
Summary: GPU HANG: ecode 9:1:0xfefffffe, in Xorg [600], reason:
Hang on bcs0, action: reset
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: udo at hypervisor.org
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 139245
--> https://bugs.freedesktop.org/attachment.cgi?id=139245&action=edit
GPU crash dump
With Linux-4.16.6 on a Lenovo X1 laptop (Skylake GT2 [HD Graphics 520]) I just
hit the following:
[ 24.801885] [drm] GPU HANG: ecode 9:1:0xfefffffe, in Xorg [600], reason:
Hang on bcs0, action: reset
[ 24.801886] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 24.801886] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 24.801886] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 24.801887] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 24.801887] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 24.801927] i915 0000:00:02.0: Resetting bcs0 after gpu hang
[ 27.868430] asynchronous wait on fence i915:clflush:0 timed out
[ 27.868450] asynchronous wait on fence i915:Xorg[600]/0:3 timed out
[ 32.796660] i915 0000:00:02.0: Resetting chip after gpu hang
[ 32.796739] i915 0000:00:02.0: GPU recovery failed
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180501/aa91d503/attachment.html>
More information about the intel-gfx-bugs
mailing list