[arrandale] False GPU lockup render.IPEHR: 0x01800002
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash when i launch any graphical application
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-
ProcVersionSign
Uname: Linux 3.0.0-11-generic x86_64
.tmp.unity.
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Chipset: arrandale
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Tue Sep 20 21:01:05 2011
DistUpgraded: Log time: 2011-09-13 21:31:34.218345
DistroCodename: oneiric
DistroVariant: ubuntu
DuplicateSignature: [arrandale] GPU lockup render.IPEHR: 0x01800002 Ubuntu 11.10
ExecutablePath: /usr/share/
GraphicsCard:
Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fd10]
InterpreterPath: /usr/bin/python2.7
MachineType: TOSHIBA Satellite L655
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6+7ubuntu7
libdrm2 2.4.26-1ubuntu1
xserver-
SourcePackage: xserver-
Title: [arrandale] False GPU lockup render.IPEHR: 0x01800002
UpgradeStatus: Upgraded to oneiric on 2011-09-17 (4 days ago)
UserGroups:
dmi.bios.date: 11/11/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.90
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Satellite L655
dmi.product.
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.5.
version.ia32-libs: ia32-libs 20090808ubuntu22
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
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.