[i945gm] GPU lockup 2cd82a5a (ESR: 0x00000001 IPEHR: 0x02000011)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
No information.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.38-4-generic i686
Architecture: i386
Chipset: i945gm
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1280x800
edid-base64: AP/////
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: Off
modes:
edid-base64:
Date: Fri Feb 18 17:16:03 2011
DistUpgraded: Yes, recently upgraded Log time: 2011-02-16 14:50:33.644126
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
virtualbox-ose, 4.0.2, 2.6.38-3-generic, i686: installed
virtualbox-ose, 4.0.2, 2.6.38-4-generic, i686: installed
DumpSignature: 2cd82a5a (ESR: 0x00000001 IPEHR: 0x02000011)
ExecutablePath: /usr/share/
GraphicsCard:
Subsystem: Uniwill Computer Corp Device [1584:9917]
Subsystem: Uniwill Computer Corp Device [1584:9917]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
MachineType: Standard L41II3
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
ProcKernelCmdLine_: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.6~3ubuntu5
libdrm2 2.4.23-1ubuntu3
xserver-
Renderer: Unknown
SourcePackage: xserver-
Title: [i945gm] GPU lockup 2cd82a5a (ESR: 0x00000001 IPEHR: 0x02000011)
UserGroups:
dmi.bios.date: 10/16/2007
dmi.bios.vendor: Standard
dmi.bios.version: 2.01.CCE
dmi.board.name: L41II3
dmi.board.vendor: Standard
dmi.chassis.type: 10
dmi.chassis.vendor: Standard
dmi.modalias: dmi:bvnStandard
dmi.product.name: L41II3
dmi.sys.vendor: Standard
version.compiz: compiz 1:0.9.2.
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.
version.
version.
version.
version.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.