[gm45] GPU lockup (ESR: 0x00000001 IPEHR: 0x7b001c04)

[Taiten Peng]

Binary package hint: xserver-xorg-video-intel

gpu

ACTHD: 0x0298341c
EIR: 0x00000000
EMR: 0xffffff05
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x7b001c04
IPEIR: 0x00000000
INSTDONE: 0xafffffff
INSTDONE1: 0xbfffefe0
    busy: Row 0, EU 1
    busy: Row 0, EU 3
    busy: CS
    busy: DM
    busy: SF
    busy: CL
    busy: GS
    busy: VS0
    busy: VF

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu2
Uname: Linux 2.6.35-020635rc5-generic i686
Architecture: i386
Chipset: gm45
Date: Wed Jul 28 13:03:40 2010
DumpSignature: 2cf41343
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 7458PU9
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-020635rc5-generic root=UUID=1ca249c7-2e34-4ddd-ab62-eb5cac73a311 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup 2cf41343
UdevDb: Error: [Errno 2] No such file or directory
UserGroups:

dmi.bios.date: 03/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET42WW (2.06 )
dmi.board.name: 7458PU9
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6DET42WW(2.06):bd03/17/2009:svnLENOVO:pn7458PU9:pvrThinkPadX200:rvnLENOVO:rn7458PU9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7458PU9
dmi.product.version: ThinkPad X200
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-020635rc5-generic

[michael da cova (michael-dacova)]

while opening the laptop lid after a suspend got the crash

[bugbot (bugbot)]

Hey Taiten,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[bugbot (bugbot)]

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.