gm45 GPU lockup ESR: 0x00000001 IPEHR: 0x61010004
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
crash
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xserver-
ProcVersionSign
Uname: Linux 3.0-3-generic i686
NonfreeKernelMo
Architecture: i386
Chipset: gm45
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Sun Jul 10 12:43:54 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
DkmsStatus:
bcmwl, 5.100.82.38+bdcom, 3.0-3-generic, i686: installed
bcmwl, 5.100.82.38+bdcom, 3.0-2-generic, i686: installed
bcmwl, 5.100.82.38+bdcom, 3.0-1-generic, i686: installed
DuplicateSignature: (ESR: 0x00000001 IPEHR: 0x61010004)
ExecutablePath: /usr/share/
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:1526]
Subsystem: Hewlett-Packard Company Device [103c:1526]
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6+7ubuntu1
libdrm2 2.4.26-1ubuntu1
xserver-
Renderer: Unknown
SourcePackage: xserver-
Title: [gm45] GPU lockup (ESR: 0x00000001 IPEHR: 0x61010004)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/07/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PVI Ver. F.08
dmi.board.name: 1526
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.0D
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.4+
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
tags: | removed: need-duplicate-check |
Hi Vadim, are you able to reproduce this bug with current oneiric by playing Civ4 through Wine?
I'm asking because there were recently a variety of problems with the new /run directory around the time you experienced this bug, so just want to make sure we're ruling that out as a possible cause.