[Bug 83141] New: Chrome gives occasional gpu hang with "ring hung" for drm with Intel graphics
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Sun Aug 24 11:14:59 PDT 2014
https://bugzilla.kernel.org/show_bug.cgi?id=83141
Bug ID: 83141
Summary: Chrome gives occasional gpu hang with "ring hung" for
drm with Intel graphics
Product: Drivers
Version: 2.5
Kernel Version: 3.16.1-1-ARCH
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - Intel)
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: mike.cloaked at gmail.com
CC: intel-gfx-bugs at lists.freedesktop.org
Regression: No
Created attachment 147931
--> https://bugzilla.kernel.org/attachment.cgi?id=147931&action=edit
Systemd journal showing the kernel [drm] hang
Running chrome in kde occasionally chrome hangs after updates the past day or
two, and no further mouse input can be made. Can killall chrome to recover.
Running google-chrome 36.0.1985.143-1 in kde version 4.14.0-1 with latest
kernel linux 3.16.1-1
The journal contains the following lines:
Aug 24 10:01:33 home1 kernel: [drm] stuck on render ring
Aug 24 10:01:33 home1 kernel: [drm] GPU HANG: ecode 0:0xf5f7fffe, in chrome
[11355], reason: Ring
hung, action: reset
Aug 24 10:01:33 home1 kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack
, including userspace.
Aug 24 10:01:33 home1 kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org agains
t DRI -> DRM/Intel
Aug 24 10:01:33 home1 kernel: [drm] drm/i915 developers can then reassign to
the right component
if it's not a kernel issue.
Aug 24 10:01:33 home1 kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so pleas
e always attach it.
Aug 24 10:01:33 home1 kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Aug 24 10:01:35 home1 kernel: [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp
off
xf86-video-intel 2.99.914-4
kdebase-workspace 4.11.11-2
mesa 10.2.6-1
libdrm 2.4.56-1
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the intel-gfx-bugs
mailing list