[i915gm] GPU lockup 24843869 (PGTBL_ER: 0x00000100)

[UndiFineD]

Binary package hint: xserver-xorg-video-intel

bootup

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae
Uname: Linux 2.6.31-14-generic-pae i686
Architecture: i386
Chipset: i915gm
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1024x600
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Thu Aug 26 18:07:33 2010
DkmsStatus:

DumpSignature: 24843869 (PGTBL_ER: 0x00000100)
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InterpreterPath: /usr/bin/python2.6
MachineType: ASUSTeK Computer INC. 900
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic-pae root=UUID=2a919a00-4402-48f6-9f73-235ae7907dee ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [i915gm] GPU lockup 24843869 (PGTBL_ER: 0x00000100)
UserGroups:

dmi.bios.date: 09/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 900
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0906:bd09/11/2008:svnASUSTeKComputerINC.:pn900:pvr0802:rvnASUSTeKComputerINC.:rn900:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 900
dmi.product.version: 0802
dmi.sys.vendor: ASUSTeK Computer INC.
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.31-14-generic-pae

[Robert Hooker (sarvatt)]

Is there a reason you are using the karmic kernel on maverick? Do you have this problem with the maverick kernel as well?

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.