[Bug 88894] New: System suddenly crashed to blank screen
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Jan 31 21:39:11 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=88894
Bug ID: 88894
Summary: System suddenly crashed to blank screen
Product: DRI
Version: XOrg git
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: john.eure at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 113010
--> https://bugs.freedesktop.org/attachment.cgi?id=113010&action=edit
GPU crash dump
My laptop's screen suddenly went blank, and the laptop became unresponsive. I
could not switch to a virtual console, or if I could, it was not able to
display the login prompt on the screen. Eventually, I stopped waiting and held
down the power button to reboot my laptop. This worked normally. After the
reboot, I looked in my syslog, and it told me to:
"Please file a _new_ bug report on bugs.freedesktop.org against DRI ->
DRM/Intel", and include the GPU crash dump at "/sys/class/drm/card0/error".
Unfortunately, when I read the GPU crash dump file, it just says "no error
state collected".
In case it's useful, the output of "uname -a" is:
Linux artemis 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
And the first bit of the syslog output after the crash, trimmed of headers, is:
Watchdog[16595]: segfault at 0 ip 00007f38da33f428 sp 00007f38ca9c8520 error 6
in libcontent.so[7f38d9a88000+1244000]
Watchdog[16909]: segfault at 0 ip 00007f6a47856428 sp 00007f6a37edf520 error 6
in libcontent.so[7f6a46f9f000+1244000]
[drm] stuck on render ring
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including
userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org 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:i915_set_reset_status] *ERROR* render ring hung inside bo (0x3175000 ctx
0) at 0x3176594
[drm] GMBUS [i915 gmbus vga] timed out, falling back to bit banging on pin 2
[drm:i915_reset] *ERROR* Failed to reset chip.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150201/c512c94b/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list