Bug 96776 - dell inspiron with intel N3700 [drm] GPU HANG: ecode 8:0:0xab2ffff9, in X [3026], reason: Engine(s) hung, action: reset
Summary: dell inspiron with intel N3700 [drm] GPU HANG: ecode 8:0:0xab2ffff9, in X [30...
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: 2016-07-01 22:14 UTC by Jeffery Miller
Modified: 2017-07-24 22:41 UTC (History)
1 user (show)

See Also:
i915 platform: BSW/CHT
i915 features: GPU hang

Attachments
dmesg.out with nightly kernel and drm.debug=14 (141.05 KB, text/plain)
2016-07-01 22:14 UTC, Jeffery Miller 		no flags Details
Content of /sys/class/drm/card0/error (52.57 KB, application/gzip)
2016-07-01 22:15 UTC, Jeffery Miller 		no flags Details
lspci of the machine (11.69 KB, text/plain)
2016-07-01 22:16 UTC, Jeffery Miller 		no flags Details
dmidecode of the machine (13.35 KB, text/plain)
2016-07-01 22:16 UTC, Jeffery Miller 		no flags Details
View All

Description Jeffery Miller 2016-07-01 22:14:41 UTC 
Created attachment 124851 [details]
dmesg.out with nightly kernel and drm.debug=14

The gpu hangs early on in kernels 4.4.14 and drm-nightly commit 6044ca70fbf0d53ec083fa82f893faa144cf99cc.

This is on a Dell Inspiron 11-3157 2-in-1 with a Pentium N3700.
I am using the built screen on the machine.

This particular machine is a chromiumos build with X and Chromium starting. I have had similar issues with Fedora attempts in the past on this machine.

I built the latest drm-nightly kernel today with `drm.debug=14` option and attached the output.


Some lines in the log are as followed and I am attaching the dmesg.out:

```
[   18.758852] [drm] stuck on render ring
[   18.765824] [drm] GPU HANG: ecode 8:0:0xab2ffff9, in X [3026], reason: Engine(s) hung, action: reset
[   18.765839] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   18.765847] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   18.765854] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   18.765861] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   18.765869] [drm] GPU crash dump saved to /sys/class/drm/card0/error
```
Comment 1 Jeffery Miller 2016-07-01 22:15:53 UTC 
Created attachment 124852 [details]
Content of /sys/class/drm/card0/error

This is the contents of the error file for the nightly repro case.
Comment 2 Jeffery Miller 2016-07-01 22:16:18 UTC 
Created attachment 124853 [details]
lspci of the machine
Comment 3 Jeffery Miller 2016-07-01 22:16:33 UTC 
Created attachment 124854 [details]
dmidecode of the machine
Comment 4 Jeffery Miller 2016-07-01 22:18:49 UTC 
This isn't a regression as far as I know. I have tried a 4.0.5 kernel in the past and it didn't work as well.
Comment 5 Jeffery Miller 2016-07-01 22:19:09 UTC 
I can provide more details and other information as requested.
Comment 6 Chris Wilson 2016-07-01 22:39:05 UTC 
The ddx is too old.
Comment 7 Jeffery Miller 2016-07-07 23:53:56 UTC 
Updating the ddx worked.
Comment 8 Jeffery Miller 2016-07-08 13:54:21 UTC 
The issue was no longer present after upgrading the ddx.

I was at these commits:

xf86-video-intel at 26f8ab5429a554801641415f0ab3b2d68cea1d00
drm-intel at 6044ca70fbf0d53ec083fa82f893faa144cf99cc

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.