Bug 82665 - [drm] stuck on render ring
Summary: [drm] stuck on render ring
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ian Romanick
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-15 14:43 UTC by cs_gon
Modified: 2017-02-10 22:38 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (2.28 MB, text/plain)
2014-08-15 14:43 UTC, cs_gon
Details

Description cs_gon 2014-08-15 14:43:16 UTC
Created attachment 104680 [details]
/sys/class/drm/card0/error

This happened on a Lenovo X220, using Ubuntu Precise, with LTS-Trusty Kernel (3.13.0-30) and LTS-Saucy Xorg stack:

Jul 10 09:20:52 c462301 kernel: [264250.203026] [drm] stuck on render ring
Jul 10 09:20:52 c462301 kernel: [264250.203030] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Jul 10 09:20:52 c462301 kernel: [264250.203031] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Jul 10 09:20:52 c462301 kernel: [264250.203033] [drm] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Jul 10 09:20:52 c462301 kernel: [264250.203033] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Jul 10 09:20:52 c462301 kernel: [264250.203034] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Jul 10 09:20:52 c462301 kernel: [264250.212691] [drm:i915_set_reset_status] ERROR render ring hung inside bo (0x13df4000 ctx 1) at 0x13df41d8
Comment 1 Chris Wilson 2014-08-20 05:57:33 UTC
This is a very old stack. Please test using upstream when filing upstream bug reports.
Comment 2 cs_gon 2014-08-20 11:16:26 UTC
I only did what the kernel messages told me to do. :-)

We are in the process of bringing the LTS-Trusty Xorg Stack in production. But we are managing over 10000 Linux desktops, so this takes some time (a lot of testing, etc.)

Sadly, we currently don't know how to reproduce the issue, so it's difficult to test if newer Xorg/Mesa versions would fix the problem. It seems to happen sporadically about 1-2 times per week for some users (assuming this is the same issue, might be other root causes too, of course), and in this specific case, according to the user, it caused a freeze of 1-2 minutes. 

If I can provide any information that would help to resolve this, or to find out, if this is a known bug (and might be fixed in newer Xorg/Mesa versions), I would gladly do so.
Comment 3 Annie 2017-02-10 22:38:32 UTC
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.


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.