[arrandale] GPU lockup render.IPEHR: 0x01800002 - Resume from standby (dpms?)

[Patrik Lundquist]

Might have been provoked by resuming from standby but it didn't happen immediately as far as I can tell.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1
Uname: Linux 3.0.0-8-generic x86_64
Architecture: amd64
Chipset: arrandale
Date: Thu Aug 18 18:32:40 2011
DistroCodename: oneiric
DistroVariant: ubuntu
DuplicateSignature: [arrandale] GPU lockup render.IPEHR: 0x01800002 Ubuntu 11.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP EliteBook 2540p
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-8-generic root=UUID=acb02f8e-c511-420f-b440-6a163c8a8bec ro quiet splash pcie_aspm=force vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.6+7ubuntu6
 libdrm2 2.4.26-1ubuntu1
 xserver-xorg-video-intel 2:2.15.901-1ubuntu2
SourcePackage: xserver-xorg-video-intel
Title: [arrandale] GPU lockup render.IPEHR: 0x01800002
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to oneiric on 2011-08-12 (8 days ago)
UserGroups:

dmi.bios.date: 03/09/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CSU Ver. F.09
dmi.board.name: 7008
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 38.32
dmi.chassis.asset.tag: CZC0245P86
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CSUVer.F.09:bd03/09/2011:svnHewlett-Packard:pnHPEliteBook2540p:pvr:rvnHewlett-Packard:rn7008:rvrKBCVersion38.32:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 2540p
dmi.sys.vendor: Hewlett-Packard

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #825177, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.