Bug 82839 - [drm] stuck on render ring
Summary: [drm] stuck on render ring
Status: CLOSED DUPLICATE of bug 77104
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Paulo Zanoni
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-20 05:21 UTC by redwoz
Modified: 2017-07-24 22:51 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments
/sys/class/drm/card0/error (2.23 MB, text/plain)
2014-08-20 07:14 UTC, redwoz 		no flags Details
View All

Description redwoz 2014-08-20 05:21:41 UTC 
below errors shown after desktop (but not mouse pointer) freezes for 10 seconds then seems to unfreeze. often have chromium open and have been doing things in quick succession. happens most days.

[55024.663145] [drm] stuck on render ring
[55024.663150] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[55024.663150] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[55024.663151] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[55024.663152] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[55024.663152] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

crash dump mentioned above is empty; hardware config:

- Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
- Z77X-UD3H, BIOS F17 08/22/2012
- 3 
- Ubuntu 14.04 x64 3.13.0-34-generic #60
- Chromium 36.0.1985.125 Ubuntu 14.04 (283153)

cheers
Comment 1 Chris Wilson 2014-08-20 05:58:49 UTC 
/sys/class/drm/card0/error is not empty, try again. Hint: ls lies.
Comment 2 redwoz 2014-08-20 07:14:40 UTC 
Created attachment 104942 [details]
/sys/class/drm/card0/error
Comment 3 Chris Wilson 2014-08-20 17:24:44 UTC 

*** This bug has been marked as a duplicate of bug 77104 ***

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.