[Bug 105397] [drm] GPU HANG: ecode 7:1:0xf4ebffff, in Xorg [1731], reason: No progress on bcs0, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Mar 8 17:13:01 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105397
--- Comment #2 from Giuseppe Bilotta <giuseppe.bilotta at gmail.com> ---
I don't know if this is relevant, but the GPU reset repeatedly in a relatively
short time. This is the dmesg output from the first reset to the paraview
segfault:
[Mar 8 12:21] [drm] GPU HANG: ecode 7:1:0xf4ebffff, in Xorg [1731], reason: No
progress on bcs0, action: reset
[ +0.000004] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ +0.000002] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ +0.000001] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ +0.000002] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ +0.000002] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ +0.000038] i915 0000:00:02.0: Resetting chip after gpu hang
[ +8.086583] i915 0000:00:02.0: Resetting chip after gpu hang
[ +7.935792] i915 0000:00:02.0: Resetting chip after gpu hang
[Mar 8 12:22] i915 0000:00:02.0: Resetting chip after gpu hang
[ +7.935842] i915 0000:00:02.0: Resetting chip after gpu hang
[ +8.063832] i915 0000:00:02.0: Resetting chip after gpu hang
[Mar 8 12:24] paraview[13787]: segfault at 5572c408d160 ip 00005572c408d160 sp
00007fff7cefda78 error 15
Is it possible that the crash dump got overwritten during the reset?
--
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/20180308/e769507d/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list