[Bug 98355] New: [SNB][drm] GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck wait on render ring, action: continue
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Oct 20 11:31:42 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=98355
Bug ID: 98355
Summary: [SNB][drm] GPU HANG: ecode 6:-1:0x00000000, reason:
Kicking stuck wait on render ring, action: continue
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: mariusz.libera at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
i915 platform: SNB
i915 features: GPU hang
Created attachment 127422
--> https://bugs.freedesktop.org/attachment.cgi?id=127422&action=edit
cat /sys/class/drm/card0/error | bzip2 > error.bz2
After resuming from suspend instead of KDE's lockscreen I was greeted only by
my wallpaper and mouse cursor (responsive). I switched to another tty (it
worked, I could log in) and back and this time it was only black screen, after
another tty switch xserver crashed. After that I was able to start another X
session.
This is what happened this time, but honestly I can't use my laptop for 2 days
without experiencing, at best, freezing of my desktop for a few seconds or, at
worst, forcing me to reboot using sysrq. I can't reliably reproduce it, seems
to happen at random, and may not always be a "GPU Hang", I also saw messages
like:
WARNING: CPU: 0 PID: 500 at drivers/gpu/drm/i915/intel_display.c:3857
intel_atomic_commit+0x1459/0x1460 [i915]
Removing stuck page flip
followed by a backtrace, but was too lazy to report.
Archlinux x86_64
Kernel 4.8.2
Mesa 12.0.3
Xserver 1.18.4
--
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20161020/ecbd772e/attachment.html>
More information about the intel-gfx-bugs
mailing list