[Bug 99192] New: GPU HANG: ecode 5:-1:0x00000000, reason: Kicking stuck wait on render ring
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Dec 23 11:37:06 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=99192
Bug ID: 99192
Summary: GPU HANG: ecode 5:-1:0x00000000, reason: Kicking stuck
wait on render ring
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: antonio.galea at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Resuming after a suspend, the LCD of my laptop stays blank.
Xorg.0.log reports this error:
[ 532.718] (EE) intel(0): failed to set mode: Invalid argument [22]
[ 548.734] (EE) intel(0): failed to set mode: Invalid argument [22]
If I stop gdm3 and try to restart it, the screen is still blank, but now dmesg
reports a fault:
[ 724.908116] [drm:drm_framebuffer_remove [drm]] *ERROR* failed to reset crtc
ffffa06e30e5d000 when fb was deleted
[ 724.908214] [drm:drm_plane_force_disable [drm]] *ERROR* failed to disable
plane with busy fb
Software installed:
Laptop: HP 630 Notebook PC
GPU: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
[8086:0046]
OS: Debian 8.6
Packages:
linux-image-4.8.0-0.bpo.2-amd64 4.8.11-1~bpo8+1
xserver-xorg 1:7.7+7
xserver-xorg-video-intel 2:2.99.917+git20161105-1~bpo8+1
libdrm2 2.4.73-1~bpo8+1
libdrm-intel 2.4.73-1~bpo8+1
Antonio
--
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/20161223/d630c521/attachment.html>
More information about the intel-gfx-bugs
mailing list