[gm45] GPU lockup 02d3352c (EIR: 0x00000010)

[Marek Tyburec]

Binary package hint: xserver-xorg-video-intel

Bug happened just by turning-on my hp620 notebook.

[ 21.740308] input: HP WMI hotkeys as /devices/virtual/input/input5
[ 21.833288] render error detected, EIR: 0x00000010
[ 21.833293] IPEIR: 0x00000000
[ 21.833295] IPEHR: 0x00000000
[ 21.833296] INSTDONE: 0xfffffffe
[ 21.833298] INSTPS: 0x00000000
[ 21.833299] INSTDONE1: 0xffffffff
[ 21.833301] ACTHD: 0x00000000
[ 21.833303] page table error
[ 21.833305] PGTBL_ER: 0x00000001
[ 21.833307] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
Uname: Linux 2.6.38-1-generic x86_64
Architecture: amd64
Chipset: gm45
CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins'
CompositorRunning: compiz
DRM.card0.DP.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DP.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
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: 1366x768
 edid-base64: AP///////wAlzAcAAAAAAAATAQOAIhN4CsiFnldUmyYSUFQAAAABAQEBAQEBAQEBAQEBAQEBEhtWZlAAEzAZETMAWMIQAAAZAAAAAAAAAAAAAAAAAAAAAAAAAAAA/gBJTkxEaXNwbGF5CiAgAAAA/ABCVDE1NkdXMDEAVi4zAKI=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Jan 31 21:30:21 2011
DistUpgraded: Yes, recently upgraded Log time: 2010-12-03 08:08:22.908006
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:

DumpSignature: 02d3352c (EIR: 0x00000010)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Subsystem: Hewlett-Packard Company Device [103c:1526]
   Subsystem: Hewlett-Packard Company Device [103c:1526]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
LocalLibraries: /usr/local/lib/libz.so.1.2.5
MachineType: Hewlett-Packard HP 620
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=a0ad7778-8d27-40c2-8f6f-6ff75321f37c ro quiet splash vt.handoff=7
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=a0ad7778-8d27-40c2-8f6f-6ff75321f37c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu8
 libdrm2 2.4.23-1ubuntu3
 xserver-xorg-video-intel 2:2.14.0-1ubuntu2
Renderer: Hardware acceleration
SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup 02d3352c (EIR: 0x00000010)
UnitySupportTest:

UserGroups:

dmi.bios.date: 02/25/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVI Ver. F.00
dmi.board.name: 1526
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.0D
dmi.chassis.asset.tag: CNU0203BP0
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PVIVer.F.00:bd02/25/2010:svnHewlett-Packard:pnHP620:pvrF.00:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP 620
dmi.product.version: F.00
dmi.sys.vendor: Hewlett-Packard
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10-1ubuntu1
version.xserver-xorg: xserver-xorg 1:7.5+6ubuntu8
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.13.2+git20110124.fadee040-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu1

[Bryce Harrington (bryce)]

Aside from the apport popup with the error message, did you notice any other kernel or X misbehaviors/lockups associated with this?

Might be this is just a false positive, like #711275 and others that have recently been reported.

[Bryce Harrington (bryce)]

I'll go ahead and make that assumption. The trace seems to match bug 711275 and we're getting a spate of dupe reports about it.