Bug 99204 - [ILK] GPU HANG: ecode 5:1:0x01000000, reason: Ring hung, action: reset / stuck on bsd ring
Summary: [ILK] GPU HANG: ecode 5:1:0x01000000, reason: Ring hung, action: reset / stuc...
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: 2016-12-26 23:24 UTC by Hallo32
Modified: 2017-03-04 10:01 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (90.50 KB, application/x-bzip)
2016-12-26 23:24 UTC, Hallo32
no flags Details

Description Hallo32 2016-12-26 23:24:13 UTC
Created attachment 128665 [details]
/sys/class/drm/card0/error

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

dmesg:
[13059.548196] [drm] stuck on bsd ring
[13059.551649] [drm] GPU HANG: ecode 5:1:0x01000000, reason: Ring hung, action: reset
[13059.551653] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[13059.551654] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[13059.551656] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[13059.551658] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[13059.551660] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[13059.555062] drm/i915: Resetting chip after gpu hang

Feel free to request any missing information.
Comment 1 yann 2017-01-20 17:24:44 UTC
Hallo32@gmx.net, please update your kernel with latest on and confirm whether or not you are reproducing the issue
Comment 2 Hallo32 2017-01-22 11:14:13 UTC
Yann, I have updated to kernel 4.8 which is at the moment the latest supported kernel and I will monitor dmesg for further error messages related to this topic.

The system is used as productive system and this is the point why I would prefer official supported kernels.

As how stable should I expect the driver in combination with a kaby lake c/gpu?
Comment 3 yann 2017-01-23 10:20:24 UTC
(In reply to Hallo32 from comment #2)
> Yann, I have updated to kernel 4.8 which is at the moment the latest
> supported kernel and I will monitor dmesg for further error messages related
> to this topic.
Thanks Hallo32

> 
> The system is used as productive system and this is the point why I would
> prefer official supported kernels.
> 
I understand, this is fair

> As how stable should I expect the driver in combination with a kaby lake
> c/gpu?

It depends on your usage, config ... but this is pretty stable as far as I noticed and there were many improvements pushed up-stream. My recommendation will be to use also Modesetting/Glamor rather than SNA.
Comment 4 Ricardo 2017-03-03 16:55:21 UTC
Hallo32 after your update have you seen the hung still? The bug will remain open a bit longer waiting for your response. However if no activity is done this will be closed

if the hang still reoccurs after updating the kernel please make sure "drm.debug=0xe" in your boot command line and then attached your dmesg.
Comment 5 Hallo32 2017-03-03 20:23:12 UTC
Hi Ricardo,

I didn't see the hung after the update again.

So I conclude, that the bug has been fixed through the update.
Comment 6 yann 2017-03-04 10:01:17 UTC
(In reply to Hallo32 from comment #5)
> Hi Ricardo,
> 
> I didn't see the hung after the update again.
> 
> So I conclude, that the bug has been fixed through the update.

Thanks Hallo32 for this confirmation.


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.