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

[Luka Renko]

Binary package hint: xserver-xorg-video-intel

I get regular (at least once per day) lockups. I am running Kubuntu, but not using composited desktop.

ACTHD: 0x0290cc28
EIR: 0x00000000
EMR: 0xffffff05
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x54300004
IPEIR: 0x00000000
INSTDONE: 0x808fffff
INSTDONE1: 0x9ffd193f
    busy: Row 0, EU 1
    busy: Row 0, EU 2
    busy: Row 0, EU 3
    busy: Row 1, EU 0
    busy: Row 1, EU 1
    busy: Row 1, EU 2
    busy: Row 1, EU 3
    busy: Setup Engine
    busy: Windowizer
    busy: CS
    busy: MASF
    busy: SVSM
    busy: QC
    busy: FL
    busy: SC
    busy: DG
    busy: SI
    busy: PL
    busy: WIZ

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic x86_64
Architecture: amd64
Chipset: gm45
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1440x900
 edid-base64: AP///////wAwrhRAAAAAACoSAQOAGhB46uWVk1ZPkCgoUFQAAAABAQEBAQEBAQEBAQEBAQEB8BygoFCEGjAYEDYABaMQAAAY8BygoFCEGjAYEDYABaMQAAAYAAAADwCVCjKVCjIZAQAwZABVAAAA/gBMVEQxMjFFUTNCCiAgAJM=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Fri Aug 13 21:32:09 2010
DumpSignature: aa0da95d
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 74705HG
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=/dev/mapper/plain-root ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcCwd: /
ProcEnviron:

RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu3
 libdrm2 2.4.21-1ubuntu2
 xserver-xorg-video-intel 2:2.12.0-1ubuntu3
SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup aa0da95d
UdevDb: Error: [Errno 2] No such file or directory
UserGroups:

dmi.bios.date: 03/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET63WW (3.13 )
dmi.board.name: 74705HG
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:bvr6DET63WW(3.13):bd03/10/2010:svnLENOVO:pn74705HG:pvrThinkPadX200s:rvnLENOVO:rn74705HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 74705HG
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO
glxinfo: Error: [Errno 2] No such file or directory
peripherals:

system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-14-generic

[bugbot (bugbot)]

Hey Luka,

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.