Bug 99890 - [IVB] GPU hang: (ecode 7:0:0x85fffffa, in Xorg [1617], reason: Hang on render ring, action: reset) after wakeup from S3 sleep
Summary: [IVB] GPU hang: (ecode 7:0:0x85fffffa, in Xorg [1617], reason: Hang on render...
Status: CLOSED WORKSFORME
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: 2017-02-21 16:16 UTC by Felix E.
Modified: 2017-06-28 14:32 UTC (History)
1 user (show)

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

Attachments
Output from /sys/class/drm/card0/error (65.24 KB, application/x-bzip)
2017-02-21 16:16 UTC, Felix E. 		no flags Details
Full dmesg (19.52 KB, application/x-bzip)
2017-02-21 16:19 UTC, Felix E. 		no flags Details
View All

Description Felix E. 2017-02-21 16:16:25 UTC 
Created attachment 129798 [details]
Output from /sys/class/drm/card0/error

Hey Guys!
In the last 2 months I have been getting about 3 "GPU Hangs", every time after I resumed my laptop (Lenovo B590, more details down below) from S3 energy save mode.

Until now I just ignored them, but this may help some people (I hope ^^).

Error message (dmesg):
[ 3414.728202] [drm] GPU HANG: ecode 7:0:0x85fffffa, in Xorg [1617], reason: Hang on render ring, action: reset
[ 3414.728203] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 3414.728204] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 3414.728204] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 3414.728205] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 3414.728205] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 3414.728242] drm/i915: Resetting chip after gpu hang
[ 3424.775906] drm/i915: Resetting chip after gpu hang

System:
Lenovo B590
CPU: Intel Core i3-3110M @2.4Ghz
GPU: Intel HD4000 (Ubuntu says "Intel® Ivybridge Mobile")

Ubuntu 16.10
Kernel: 4.4.0-45-generic
X.Org X Server 1.18.4 (2016-07-19) (Package: xorg-server 2:1.18.4-1ubuntu6.1)
X Protocol Version 11, Revision 0
pixman: 0.33.6

Latest Intel divers via "Intel Graphics Update Tool for Linux OS" (newest version from 01.org)
Comment 1 Felix E. 2017-02-21 16:19:41 UTC 
Created attachment 129799 [details]
Full dmesg
Comment 2 Elizabeth 2017-06-27 21:07:43 UTC 
Hello Felix,
Sorry for the delay, is this bug still valid? Can you reproduce it with the last kernel update? Could you please update dmesg with drm.debug=0xe parameter on bug? Thank you.
Comment 3 Felix E. 2017-06-27 22:12:43 UTC 
Hi Elizabeth!

I am afraid that I am not able to reproduce this issue, nor help with its resolution anymore.
Since the bug report some things changed: now I am using the current kernel (4.8.0-57-generic) and the "git" version of the Intel OpenSource drivers and I do not exactly know which of both made the hangs disappear.

For reference: this is the Ubuntu 16.10 PPA with my current drivers:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/

Thanks for your time.

Felix

P.S.: Which status should I choose? "Resolved - WORKSFORME" or "Resolved - Invalid"?
Comment 4 Elizabeth 2017-06-28 14:32:51 UTC 
(In reply to Felix E. from comment #3)
> Hi Elizabeth!
> 
> I am afraid that I am not able to reproduce this issue, nor help with its
> resolution anymore.
> Since the bug report some things changed: now I am using the current kernel
> (4.8.0-57-generic) and the "git" version of the Intel OpenSource drivers and
> I do not exactly know which of both made the hangs disappear.
> 
> For reference: this is the Ubuntu 16.10 PPA with my current drivers:
> https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers/
> 
> Thanks for your time.
> 
> Felix
> 
> P.S.: Which status should I choose? "Resolved - WORKSFORME" or "Resolved -
> Invalid"?

Hello Felix,
WORKSFORME is okay, thanks for your time.

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.