Bug 76792 - Fedora 20, i5 2500K HD 3000 GPU hang
Summary: Fedora 20, i5 2500K HD 3000 GPU hang
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-30 12:56 UTC by Aaron Riekenberg
Modified: 2014-03-30 13:56 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Copy of /sys/class/drm/card0/error (340.10 KB, text/plain)
2014-03-30 12:56 UTC, Aaron Riekenberg
Details
Copy of /sys/class/drm/card0/error (2.23 MB, text/plain)
2014-03-30 12:57 UTC, Aaron Riekenberg
Details

Description Aaron Riekenberg 2014-03-30 12:56:03 UTC
Created attachment 96615 [details]
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.
Comment 1 Aaron Riekenberg 2014-03-30 12:57:57 UTC
Created attachment 96616 [details]
Copy of /sys/class/drm/card0/error
Comment 2 Chris Wilson 2014-03-30 13:56:13 UTC
This should already be fixed in the latest releases of 10.0 or 10.1.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.