Bug 84936 - [ILK] stuck on render ring (3.13)
Summary: [ILK] stuck on render ring (3.13)
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-12 15:02 UTC by stephan
Modified: 2017-07-24 22:51 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (1.46 MB, text/plain)
2014-10-12 15:02 UTC, stephan
no flags Details
full dmesg output (61.30 KB, text/plain)
2014-10-12 15:03 UTC, stephan
no flags Details

Description stephan 2014-10-12 15:02:41 UTC
Created attachment 107741 [details]
/sys/class/drm/card0/error

X stopped responding to mouse and keyboard.

Partial dmesg output:

[11759.532741] [drm] stuck on render ring
[11759.532812] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[11759.532815] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[11759.532817] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[11759.532819] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[11759.532825] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[11759.535807] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xf64a000 ctx 0) at 0xf64bec4
[11765.544030] [drm] stuck on render ring
[11771.519331] [drm] stuck on render ring
[11777.518648] [drm] stuck on render ring

Full dmesg output and contents of /sys/class/drm/card0/error are attached.

Possibly relevant version information:

libdrm-intel1:amd64	2.4.52-1
libdrm-intel1:i386	2.4.52-1
libdrm2:amd64	2.4.52-1
libdrm2:i386	2.4.52-1
xorg	1:7.7+1ubuntu8
xserver-xorg-core	2:1.15.1-0ubuntu2
xserver-xorg-video-intel	2:2.99.910-0ubuntu1

I'd be happy to give more information if necessary.
Comment 1 stephan 2014-10-12 15:03:14 UTC
Created attachment 107742 [details]
full dmesg output
Comment 2 Paulo Zanoni 2014-10-13 18:20:09 UTC
Hi

Can you reliably reproduce this? If yes, how?

I see you're using Kernel 3.13. Are you able to test a newer Kernel and confirm if the bug still happens?

I see you're using Ubuntu. You could try to download a Kernel from its development version, or one of its many PPAs, or you could even try the drm-intel-nightly branch from http://cgit.freedesktop.org/drm-intel/log/?h=drm-intel-nightly directly.

Thanks,
Paulo
Comment 3 stephan 2014-10-13 18:46:44 UTC
(In reply to Paulo Zanoni from comment #2)
> Can you reliably reproduce this?

No, it only happened once. I'll add a comment if it should happen again.
Thanks,
--Stephan
Comment 4 Rodrigo Vivi 2014-10-15 20:31:31 UTC
Feel free to reopen if you still face this issue with more recent kernel.
In this case, please try to collect and attach updated logs and gpu error state.


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.