[Bug 76792] New: Fedora 20, i5 2500K HD 3000 GPU hang
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Mar 30 05:56:03 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=76792
Priority: medium
Bug ID: 76792
CC: intel-gfx-bugs at lists.freedesktop.org
Assignee: intel-gfx-bugs at lists.freedesktop.org
Summary: Fedora 20, i5 2500K HD 3000 GPU hang
QA Contact: intel-gfx-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: aaron.riekenberg at gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: DRM/Intel
Product: DRI
Created attachment 96615
--> https://bugs.freedesktop.org/attachment.cgi?id=96615&action=edit
Copy of /sys/class/drm/card0/error
I'm running up to date Fedora 20 (3.13.7-200.fc20.x86_64 kernel) with Gnome 3
on a Core i5 2500K (HD 3000 graphics). I'm running the latest version of
Google Chrome (33.0.1750.152). I frequently see GPU hangs in Chrome,
particularly when using Google maps.
Output from dmesg when playing with Google maps in Chrome:
[ 8201.552198] [drm] stuck on render ring
[ 8201.552204] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 8201.552205] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 8201.552207] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 8201.552208] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 8201.552209] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 8201.554807] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo
(0x959c000 ctx 3) at 0x959f7ec
Output from /sys/class/drm/card0/error is attached.
--
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/20140330/3a1598f1/attachment.html>
More information about the intel-gfx-bugs
mailing list