[Bug 101991] [drm] GPU HANG: ecode 9:0:0xeede0199, in chrome [6476], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Aug 30 19:15:46 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=101991
Thiago Macieira <thiago at kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Assignee|intel-gfx-bugs at lists.freede |thiago at kde.org
|sktop.org |
--- Comment #7 from Thiago Macieira <thiago at kde.org> ---
Created attachment 133892
--> https://bugs.freedesktop.org/attachment.cgi?id=133892&action=edit
card0_error
Another error state, this time the GPU hang happened immediately after resume
from hibernation. There was an earlier hang a few days ago, but I didn't
capture the log -- I mistook the blank screen for a failed resume, as opposed
to a GPU hang.
The i915_error_state file came up empty, but it's likely I made a mistake
capturing it or because the FS didn't sync properly when rebooting. Don't read
too much into that.
dmesg:
[256003.269843] [drm] GPU HANG: ecode 9:0:0x8ad3e08a, in kmail [3457], reason:
Hang on rcs, action: reset
[256003.269845] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[256003.269846] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[256003.269846] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[256003.269847] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[256003.269848] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[256003.269899] drm/i915: Resetting chip after gpu hang
[256003.977305] [drm:gen8_reset_engines [i915]] *ERROR* rcs: reset request
timeout
[256003.977319] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -5
$ uname -a
Linux tjmaciei-mobl1 4.12.8-1-default #1 SMP PREEMPT Thu Aug 17 05:30:12 UTC
2017 (4d7933a) x86_64 x86_64 x86_64 GNU/Linux
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact 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/20170830/54765a3b/attachment.html>
More information about the intel-gfx-bugs
mailing list