Bug 92194 - [HSW][drm] stuck on render ring
Summary: [HSW][drm] stuck on render ring
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-30 13:27 UTC by Hallo32
Modified: 2016-11-15 11:36 UTC (History)
4 users (show)

See Also:
i915 platform: HSW
i915 features: GPU hang


Attachments
/sys/class/drm/card0/error (60 bytes, text/plain)
2015-09-30 13:27 UTC, Hallo32
no flags Details

Description Hallo32 2015-09-30 13:27:02 UTC
Created attachment 118537 [details]
/sys/class/drm/card0/error

Steps to reproduce: ssh -X to another and run meld. Happens 2 out 2 times.

uname -m: x86_64
uname -r: 3.13.0-65-generic
Linux distribution: Xubuntu 14.04 (up to date)
Machine or mother board model: Acer 3820TG
Display connector: internal Display. VGA not used.

demsg:
Sep 30 14:52:54 Acer3820 kernel: [  125.849261] [drm] stuck on render ring
Sep 30 14:52:54 Acer3820 kernel: [  125.849334] [drm] GPU crash dump saved to /sys/class/drm/card0/error
Sep 30 14:52:54 Acer3820 kernel: [  125.849336] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Sep 30 14:52:54 Acer3820 kernel: [  125.849338] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Sep 30 14:52:54 Acer3820 kernel: [  125.849340] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Sep 30 14:52:54 Acer3820 kernel: [  125.849341] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Sep 30 14:52:54 Acer3820 kernel: [  125.854354] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x31cf000 ctx 0) at 0x31cf314
Sep 30 14:53:00 Acer3820 kernel: [  131.882771] [drm] stuck on render ring
Sep 30 14:53:06 Acer3820 kernel: [  137.868387] [drm] stuck on render ring
Sep 30 14:53:12 Acer3820 kernel: [  143.877963] [drm] stuck on render ring
Sep 30 14:53:18 Acer3820 kernel: [  149.875577] [drm] stuck on render ring
Sep 30 14:53:24 Acer3820 kernel: [  155.873140] [drm] stuck on render ring
Sep 30 14:53:30 Acer3820 kernel: [  161.846731] [drm] stuck on render ring
Sep 30 14:53:36 Acer3820 kernel: [  167.868279] [drm] stuck on render ring
Sep 30 14:53:42 Acer3820 kernel: [  173.865919] [drm] stuck on render ring
Sep 30 14:53:50 Acer3820 kernel: [  181.838718] [drm] stuck on render ring
Sep 30 14:53:56 Acer3820 kernel: [  187.848239] [drm] stuck on render ring
Sep 30 14:54:02 Acer3820 kernel: [  193.833857] [drm] stuck on render ring
Sep 30 14:54:08 Acer3820 kernel: [  199.831456] [drm] stuck on render ring
Sep 30 14:54:14 Acer3820 kernel: [  205.841002] [drm] stuck on render ring
Sep 30 14:54:20 Acer3820 kernel: [  211.838621] [drm] stuck on render ring
Sep 30 14:54:26 Acer3820 kernel: [  217.848174] [drm] stuck on render ring
Sep 30 14:54:32 Acer3820 kernel: [  223.833779] [drm] stuck on render ring
Sep 30 14:54:38 Acer3820 kernel: [  229.843349] [drm] stuck on render ring
Comment 1 yann 2016-09-27 13:26:16 UTC
We seem to have neglected the bug a bit, apologies.

Your gpu crash dump doesn't contain any error state.

There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring. In this case, please attach kernel log & gpu crash dump
Comment 2 yann 2016-11-15 11:36:19 UTC
(In reply to yann from comment #1)
> We seem to have neglected the bug a bit, apologies.
> 
> Your gpu crash dump doesn't contain any error state.
> 
> There were improvements pushed in kernel and Mesa that will benefit to your
> system, so please re-test with latest kernel & Mesa to see if this issue is
> still occurring. In this case, please attach kernel log & gpu crash dump

Timeout. Assuming that it is fixed by now. If this is not the case, please re-test with latest kernel & Mesa (12-13) to see if this issue is still occurring since there were improvements pushed in kernel and Mesa that will benefit to your system.


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.