[i945gm] GPU lockup (ESR: 0x00000010 PGTBL_ER: 0x00000102)

Bug #753014 reported by sipple
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Incomplete
High
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

this occurred on login on ubuntu 11.04 beta1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-xorg-video-intel 2:2.14.0-4ubuntu6
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Chipset: i945gm
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CurrentDmesg:
 [ 22.690927] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 23.981534] ppdev: user-space parallel port driver
DRM.card0.DVI.D.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///////wAGEF+cAAAAAAgQAQOAHRJ4Ci8wl1hTiyklUFQAAAABAQEBAQEBAQEBAQEBAQEBvBsAoFAgFzAwIDYAHrMQAAAYAAAAAQAGECAAAAAAAAAAAAogAAAA/gBMUDEzM1dYMS1UTEExAAAA/gBDb2xvciBMQ0QKICAgAMI=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Wed Apr 6 18:24:59 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DuplicateSignature: (ESR: 0x00000010 PGTBL_ER: 0x00000102)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:7270]
   Subsystem: Intel Corporation Device [8086:7270]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
InterpreterPath: /usr/bin/python2.7
MachineType: Apple Inc. MacBook2,1
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=0274f19d-7c52-46e5-bc03-a6564f9628c4 ro quiet splash vt.handoff=7
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=0274f19d-7c52-46e5-bc03-a6564f9628c4 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
Renderer: Unknown
SourcePackage: xserver-xorg-video-intel
Title: [i945gm] GPU lockup (ESR: 0x00000010 PGTBL_ER: 0x00000102)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 06/27/07
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB21.88Z.00A5.B07.0706270922
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4208CAA
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4208CAA
dmi.modalias: dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA:
dmi.product.name: MacBook2,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.4+bzr20110406-0ubuntu1
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
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-0ubuntu6

Revision history for this message
sipple (sipple) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #738066. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: removed: need-duplicate-check
tags: added: regression-retracer
Revision history for this message
Bryce Harrington (bryce) wrote :

Did it actually freeze the system (graphics stop updating, but mouse still moves)?

Does the freeze occur every time you log in? Only sometimes? Just once?

Did you upgrade to natty recently? If so, did you experience freezes in maverick?

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Incomplete
Revision history for this message
sipple (sipple) wrote :

I get the notification of the crash on every login at least 3 times. It sometimes locks up randomly, the graphics stop updating and the mouse still moves. It is a fresh install of natty. I did not experience lockups in maverick

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → High
status: Incomplete → Confirmed
Revision history for this message
Bryce Harrington (bryce) wrote :

Hmm, ok this particular one looks like a "no symptom" gpu lockup, which is basically a dupe to 752940 and 767475 and similar bugs. It is caused by a conflict with the vesafb kernel module. You can use the xdiagnose utility to disable that module (or do it manually by blacklisting and/or modifying grub if you prefer the technical route), which should suppress that error.

You may also be experiencing a real gpu lockup as a separate bug. There is a commonly experienced lockup bug in natty which is particular to i945, for which I have a fix in my PPA:

https://launchpad.net/~bryce/+archive/fig

My hypothesis is that between disabling vesafb and installing this PPA, your gpu lockup error popups and freezes should either go away entirely or be much, much less frequent. Please let me know what you find, so we can proceed with a permanent fix.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
sipple (sipple) wrote :

First, I installed the fix from your PPA first and then rebooted and still got a crash
Then I disabled the vesafb kernel module using xdigagnose and rebooted and the error did not pop up this time

Hope this helps

Revision history for this message
Bryce Harrington (bryce) wrote :

Yeah that basically confirms it as the vesafb conflict, thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.