[gm45] GPU lockup (IPEHR: 0x01820000)

[Chris Halse Rogers]

Binary package hint: xserver-xorg-video-intel

This lockup occurred during the investigation of bug #531069, when resuming my laptop in the docking station with the lid down and an external monitor plugged in via VGA.

The VGA monitor is never lit up, and the internal LVDS, once I open the lid, is up with the mouse pointer movable, but nothing else.

ACTHD: 0x08ea5014
EIR: 0x00000000
EMR: 0xffffff05
ESR: 0x00000000
PGTBL_ER: 0x00000000
IPEHR: 0x01820000
IPEIR: 0x00000000
INSTDONE: 0xffffffff
INSTDONE1: 0xbfffffff
    busy: CS

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.11.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-6.8-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic x86_64
Architecture: amd64
Chipset: gm45
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DisplayPort.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 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: connected
 enabled: enabled
 dpms: On
 modes: 1024x768 800x600 800x600 848x480 640x480
 edid-base64:
Date: Wed Jun 30 17:42:11 2010
DkmsStatus: Error: [Errno 2] No such file or directory
DumpSignature: f822dc02
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100622)
InterpreterPath: /usr/bin/python2.6
MachineType: LENOVO 7465CTO
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-6-generic root=/dev/sda2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup f822dc02
UserGroups:

dmi.bios.date: 03/10/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6DET63WW (3.13 )
dmi.board.name: 7465CTO
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:pn7465CTO:pvrThinkPadX200s:rvnLENOVO:rn7465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7465CTO
dmi.product.version: ThinkPad X200s
dmi.sys.vendor: LENOVO
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-6-generic

[Benoit des Ligneris (benoit-des-ligneris)]

Hello,

Same problem here. I went to suspend in RAM, no dock but an external monitor plugged via VGA.

When I opened the lid in a new emplacement :
* LVDS went on : mouse pointer is there but nothing else. I waited 5 minutes.
* VGA display : nothing displayed (disclaimer : it was another monitor as I moved from home to office)

I killed the XServer (ctrl + sys + K).

[bugbot (bugbot)]

Hey Chris,

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.