Ubuntu
xserver-xorg-video-intel package

[i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100

Bug #816337 reported by Matthew Paul Thomas on 2011-07-26

This bug report is a duplicate of: Bug #828684: [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	xf86-video-intel	Confirmed	Medium	freedesktop-bugs #39962
	xserver-xorg-video-intel (Ubuntu)	Triaged	Low	Unassigned

Bug Description

Apport says:

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.0-3ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Chipset: i965gm
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Tue Jul 26 10:52:28 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
DuplicateSignature: [i965gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 Ubuntu 11.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Apple Computer Inc. Device [106b:00a1]
Subsystem: Apple Computer Inc. Device [106b:00a1]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64+mac (20110705.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Apple Inc. MacBook4,1
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic root=UUID=dd41ef42-12f2-42cb-80ce-fc52d9f2c3d0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
xserver-xorg 1:7.6+7ubuntu6
libdrm2 2.4.26-1ubuntu1
xserver-xorg-video-intel 2:2.15.0-3ubuntu2
SourcePackage: xserver-xorg-video-intel
Title: [i965gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB41.88Z.00C1.B00.0802091535
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F22788A9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788A9
dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
dmi.product.name: MacBook4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
peripherals:
/desktop/gnome/peripherals/mouse:
cursor_theme = DMZ-White
version.compiz: compiz 1:0.9.5.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11~1-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11~1-0ubuntu4
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.2-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.0-3ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

Tags:

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2011-07-26:

BootDmesg.txt Edit (57.4 KiB, text/plain; charset="utf-8")
BootLog.gz Edit (177 bytes, application/x-gzip)
CurrentDmesg.txt Edit (48.1 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (1.5 MiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (27.5 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (996 bytes, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (1.5 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (4.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (26.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (742 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (120.8 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (268.7 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (592 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (28.3 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (29.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.1 KiB, text/plain; charset="utf-8")
i915_error_state.txt Edit (673.5 KiB, text/plain; charset="utf-8")
locale.txt Edit (335 bytes, text/plain; charset="utf-8")
setxkbmap.txt Edit (238 bytes, text/plain; charset="utf-8")
xdpyinfo.txt Edit (9.7 KiB, text/plain; charset="utf-8")
xinput.txt Edit (852 bytes, text/plain; charset="utf-8")
xkbcomp.txt Edit (57.4 KiB, text/plain; charset="utf-8")

Bryce Harrington (bryce) on 2011-08-08

Changed in xserver-xorg-video-intel (Ubuntu):
importance:	Undecided → Low
status:	New → Triaged

Bryce Harrington (bryce) on 2011-08-09

summary:	- [i965gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 + [i965gm] Fake GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100
summary:	- [i965gm] Fake GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100 + [i965gm] False GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000100

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-08-09:

Matthew Paul Thomas - I've forwarded this bug upstream to http://bugs.freedesktop.org/show_bug.cgi?id=39962 - please subscribe yourself to this bug, in case they need further information or wish you to test something.

In general, these false gpu lockups aren't something we're terribly worried about; the only user-visible effect is the apport popup and we turn that off for release. However, it does hint at something being not quite right under the hood in how the system is loading up the kernel video driver; I've chatted with apw about this and we investigated a few ideas but the fact that it still is happening means those fixes weren't sufficient, so I'm forwarding it upstream to see if we can get some additional ideas or advice.

Theoretically we could probably suppress the error dialog, however this potentially could mask real bugs, so I'd prefer leaving apport as is and hope this issue gets sorted out eventually.

If you file additional bug reports on this same issue, please go ahead and dupe those reports to this report, which we'll use as the master for your issue.

Bug Watch Updater (bug-watch-updater) on 2011-08-09

Changed in xserver-xorg-video-intel:
importance:	Unknown → Medium
status:	Unknown → Confirmed

Revision history for this message

Matthew Paul Thomas (mpt) wrote on 2011-08-15:

Thanks. From now until six months after f.d.o #39962 is fixed, I'll assume all GPU lockup errors are duplicates of this one and will not report them (notwithstanding bug 732030 and 732725, which were apparently a separate problem).

Is bug 741653 a duplicate of this one as well?

Revision history for this message

Bryce Harrington (bryce) wrote on 2011-08-18:

Yes, I think all the bugs with EIR 0x00000010 and PGTBL_ER: 0x00000100 are the same bug. However, I've noticed some variation between one person and the next, so am hesistant to continue just duping them all together, as we don't have a complete understanding of the problem.

I'm perplexed by what might be causing it. It's not an X.org bug obviously since it occurs well before X.org ever comes into the picture, and it seems to not be a kernel bug exactly. It might be ubuntu-specific; I've never heard of reports about it from other distros, but I don't think other distros have as good of tools for capturing crash reports as us. It's not a bug in apport, it's a legitimate gpu lockup, just false. We thought it was something to do with how video drivers were being loaded, but andy rejiggered them so we only have one graphics driver at a time, which should have solved that, yet people still see it. I think it must have something to do with conflicts in the order or overlapping of kernel driver loading. It would be nice if someone with a real thorough knowledge of how kernel drivers are loaded during init could look into this problem, but admittedly it's a fairly minor issue since it's a false hang and since it won't appear in the actual release (since we turn off apport at that point).

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #828684, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags:

removed: need-duplicate-check