[i965gm] One time only GPU lockup (IPEHR: 0x14000000) - Black screen

[Mark Shuttleworth]

Binary package hint: xserver-xorg-video-intel

No idea what triggered this, hard black screen, ctrl-alt-del rebooted.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Chipset: i965gm
CompositorRunning: compiz
DRM.card0.HDMI.A.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAwZAYjNjYzNy0RAQOAHRJ4Cof1lFdPjCcnUFQAAAABAQEBAQEBAQEBAQEBAQEBKhwAqFAgHjAQMCIAH7QQAAAYAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBSUDc3NKMxMzNFV0REAAAA/gAIDBAUKFB/2AEBCiAgAMI=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Apr 11 20:29:19 2011
DistUpgraded: Log time: 2010-07-25 15:41:02.611860
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-8-generic, i686: installed
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0209]
   Subsystem: Dell Device [1028:0209]
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100201)
InterpreterPath: /usr/bin/python2.7
MachineType: Dell Inc. XPS M1330
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=c4c39ed1-eb48-484a-8729-0600466a83a0 ro quiet splash vt.handoff=7
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=c4c39ed1-eb48-484a-8729-0600466a83a0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.6+4ubuntu3
 libdrm2 2.4.23-1ubuntu6
 xserver-xorg-video-intel 2:2.14.0-4ubuntu6
SourcePackage: xserver-xorg-video-intel
Title: [i965gm] GPU lockup
UpgradeStatus: Upgraded to natty on 2010-07-25 (260 days ago)
UserGroups:

dmi.bios.date: 12/26/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0N6705
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0N6705:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: XPS M1330
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.4+bzr20110411-0ubuntu1
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

[Bryce Harrington (bryce)]

It appears you've been running natty for some time now; I gather this is the first time you've encountered this GPU lockup? (It's a code I don't recognize, so I'm wondering if it is a recent regression). If you've seen it before this report, do you know about when you first saw it?

Can you post your /var/log/dpkg.log?

[mfmj_linux (fek-asis)]

Yes, this is the first time.

[Bryce Harrington (bryce)]

mfmj, thanks. It looks like 165 packages were ugpraded on the 12th, and I will assume one of those packages are what brought this regression. Excluding packages which have little to do with graphics leaves this list of suspects:

2011-04-12 10:28:46 upgrade libglu1-mesa 7.10.1-0ubuntu3 7.10.2-0ubuntu1
2011-04-12 10:28:47 upgrade compiz-core 1:0.9.4+bzr20110407-0ubuntu2 1:0.9.4+bzr20110411-0ubuntu1
2011-04-12 10:28:48 upgrade unity 3.8.4-0ubuntu1 3.8.6-0ubuntu1
2011-04-12 10:28:49 upgrade libnux-0.9-0 0.9.40-0ubuntu1 0.9.42-0ubuntu1
2011-04-12 10:28:51 upgrade libnux-0.9-common 0.9.40-0ubuntu1 0.9.42-0ubuntu1
2011-04-12 10:28:53 upgrade unity-common 3.8.4-0ubuntu1 3.8.6-0ubuntu1
2011-04-12 10:28:54 upgrade nux-tools 0.9.40-0ubuntu1 0.9.42-0ubuntu1
2011-04-12 10:28:55 upgrade compiz 1:0.9.4+bzr20110407-0ubuntu2 1:0.9.4+bzr20110411-0ubuntu1
2011-04-12 10:29:12 upgrade grub-pc 1.99~rc1-8ubuntu2 1.99~rc1-12ubuntu1
2011-04-12 10:29:13 upgrade grub-common 1.99~rc1-8ubuntu2 1.99~rc1-12ubuntu1
2011-04-12 10:29:15 upgrade libegl1-mesa-drivers 7.10.1-0ubuntu3 7.10.2-0ubuntu1
2011-04-12 10:29:16 upgrade libegl1-mesa 7.10.1-0ubuntu3 7.10.2-0ubuntu1
2011-04-12 10:30:11 upgrade xserver-common 2:1.10.0-0ubuntu3 2:1.10.0.902-1ubuntu1
2011-04-12 10:30:12 upgrade xserver-xorg-core 2:1.10.0-0ubuntu3 2:1.10.0.902-1ubuntu1
2011-04-12 10:30:15 upgrade xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6 1:0.0.16+git20110107+b795ca6e-0ubuntu7
2011-04-12 13:59:20 upgrade xserver-xorg-video-intel 2:2.14.0-4ubuntu6 2:2.14.0-4ubuntu7
2011-04-12 21:27:23 upgrade grub-gfxpayload-lists 0.1 0.2

compiz: The change here involves changes to error handling after making an X call (XQueryTree).

mesa: This updates to a new upstream bugfix release 7.10.2. This pulls in several dozen changes, a number of which affect Intel.

xserver: This updates to a new upstream bugfix beta 10.0.902. Most of the fixes are for input issues or memory leaks.

intel: This is a small one-line change for texture caching, to fix an issue particular to KDE.

The mesa update seems like the most likely suspect, but any of the four could be plausible candidates.

mfmj, are you able to reproduce this lockup, or has it happened just the one time? If you are able to reproduce it, we may be able to narrow down the package that causes the regression. Let me know and I can provide additional directions.

[mfmj_linux (fek-asis)]

until now, its only happen once..
if it happen again..
I will inform to you..

[Bryce Harrington (bryce)]

Hmm, alright given the timing my suspicion would be a regression introduced by either the xserver or mesa updates that occurred shortly prior to this might have led to the freeze, but given that it seems to have happened only once, it'll be very hard to narrow in on an actual suspect.

Still, I've received a handful of other i965 gpu freeze regression reports similar to this one. Except for #760054, the error codes vary a bit so they're not perfect dupes. All hard to reproduce or one-time-only, so debugging this lockup could be quite hard.

I think what I'm going to do for now is dupe these bug reports together and forward a bug report upstream on the chance that they recognize the issue.