Bug 93668 - [ILK] kernel: [drm] GPU HANG message after waking up from hibernation
Summary: [ILK] kernel: [drm] GPU HANG message after waking up from hibernation
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-01-11 16:11 UTC by Mikhail Morfikov
Modified: 2017-03-16 13:24 UTC (History)
1 user (show)

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

Attachments
GPU crash dump (1.32 MB, text/plain)
2016-01-11 16:11 UTC, Mikhail Morfikov 		no flags Details
View All

Description Mikhail Morfikov 2016-01-11 16:11:08 UTC 
Created attachment 120956 [details]
GPU crash dump

I'm getting the following log each time the machine is waking up from hibernation:

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

It says to send the message here, so there it is.

I'm using debian sid, and I have the following options set in the i915 module:

options i915 lvds_downclock=1 fastboot=1
Comment 1 cprigent 2016-03-04 15:08:53 UTC 
PCI ID: 0x0046
Code name Arrandale which contains 45 nm Intel HD Graphics (Ironlake) controller
Comment 2 yann 2017-03-16 13:16:56 UTC 
(In reply to cprigent from comment #1)
> PCI ID: 0x0046
> Code name Arrandale which contains 45 nm Intel HD Graphics (Ironlake)
> controller

We seem to have neglected the bug a bit, apologies.

ukwt@ya.ru, since There were improvements pushed in kernel that will benefit to your system, so please re-test with latest kernel and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.
Comment 3 Mikhail Morfikov 2017-03-16 13:21:49 UTC 
I think this bug is gone.
Comment 4 yann 2017-03-16 13:24:13 UTC 
(In reply to Mikhail Morfikov from comment #3)
> I think this bug is gone.

thanks Mikhail

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.