GPU HANG: ecode 6:0:0x85eefffc

[Haggai Eran]

I am using an i3 2100 system with an "Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)".

I'm getting these errors after suspend, with the screen showing a little garbled (text appearing in the wrong color or disappearing).

[27409.858424] [drm] GPU HANG: ecode 6:0:0x85eefffc, in chrome [9550], reason: Ring hung, action: reset
[27409.858425] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[27409.858426] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[27409.858427] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[27409.858428] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[27409.858428] [drm] GPU crash dump saved to /sys/class/drm/card0/error
---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: haggai 8000 F.... pulseaudio
 /dev/snd/controlC0: haggai 8000 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ab5f4eed-4f9d-4097-8a15-cd7bc60070fa
InstallationDate: Installed on 2013-01-31 (1200 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic root=UUID=35dc6554-8a90-49e3-852a-4ae844b92802 ro rootflags=subvol=@ quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-05-06 (10 days ago)
UserGroups: adm cdrom debian-transmission dip docker libvirtd lpadmin lxd plugdev sambashare sudo vboxusers wireshark
_MarkForUpload: True
dmi.bios.date: 12/04/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67BL
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10189-207
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-207:cvn:ct3:cvr:

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1582075

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Haggai Eran (haggai-eran)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety

[Haggai Eran (haggai-eran)]

The issue started after upgrading from 14.04 to 16.04. Previously I believe I used 01.org drivers on top of the 14.04 kernel, and I don't remember if it worked out of the box or not.

I'll try the mainline kernel.

[Haggai Eran (haggai-eran)]

Hi, I've tested kernel 4.6.0-040600-generic and it doesn't have this problem.

[penalvch (penalvch)]

Haggai Eran, the next step is to fully reverse commit bisect from kernel 4.4 to 4.6 in order to identify the last bad commit, followed immediately by the first good one. Once this good commit has been identified, it may be reviewed for backporting. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

After the fix commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Haggai Eran (haggai-eran)]

I tried to do a bisect but I think it went bad at some point.

In any case, I see (#1580114) that the i915 driver was backported from 4.6-rc7 in 4.4.0-24. I'm currently testing 4.4.0-28, but so far it haven't shown this error.

[Haggai Eran (haggai-eran)]

It took a while but the problem reproduced itself even on 4.4.0-28.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]