[i965gm] GPU lockup (IPEHR: 0x01820000) on playing with water effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-intel (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: xserver-
Got this just after playing with the water effect. Did notice that during it that it started to freeze slightly.
Then the crash report came up just after it finished.
ACTHD: 0x0637a014
EIR: 0x00000000
EMR: 0xffffffcd
ESR: 0x00000000
PGTBL_ER: 0x00000000
IPEHR: 0x01820000
IPEIR: 0x00000000
INSTDONE: 0xffe5fafd
INSTDONE1: 0x000fffff
busy: Projection and LOD
busy: Bypass FIFO
busy: Color calculator
busy: Command Processor
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-
ProcVersionSign
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Chipset: i965gm
DRM.card0.LVDS.1:
status: connected
enabled: enabled
dpms: On
modes: 1280x800
edid-base64: AP/////
DRM.card0.VGA.1:
status: disconnected
enabled: disabled
dpms: On
modes:
edid-base64:
Date: Tue Sep 7 13:32:38 2010
DumpSignature: 9090b3b1
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
MachineType: Acer Aspire 5315
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
SourcePackage: xserver-
Title: [i965gm] GPU lockup 9090b3b1
UserGroups:
dmi.bios.date: 11/10/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.45
dmi.board.
dmi.board.name: Acadia
dmi.board.vendor: Acer
dmi.board.version: V1.45
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5315
dmi.product.
dmi.sys.vendor: Acer
glxinfo: Error: [Errno 2] No such file or directory
system:
distro: Ubuntu
codename: maverick
architecture: i686
kernel: 2.6.35-19-generic
description: | updated |
summary: |
- [i965gm] GPU lockup 9090b3b1 + [i965gm] GPU lockup (IPEHR: 0x01820000) on playing with water effect |
Hey Jonathan,
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.