[i965gm] GPU lockup fe13e3d7 (IPEHR: 0x79050003) adjust compiz water plugin settings

[John O'Dwyer]

Binary package hint: xserver-xorg-video-intel

When playing with water effects in Compiz (shift + F9) I received the following error: apport-gpu-error-intel.py

I am running 10.10 but have had similar problems with 10.04 - see the following bug that is now closed: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/533342

It was suggested that I ssh into the locked up system to access the logs but I fail to see how to reproduce the error remotely when it is only produced by using desktop effects.

---
PCI ID: 0x2a02
EIR: 0x00000000
  PGTBL_ER: 0x00000000
  INSTPM: 0x00000000
  IPEIR: 0x00000000
  IPEHR: 0x79050003
  INSTDONE: 0xffe5fafd
    busy: Projection and LOD
    busy: Bypass FIFO
    busy: Color calculator
    busy: Command Processor
  ACTHD: 0x08b3b1f4
  INSTPS: 0x8001e022
  INSTDONE1: 0x000ffffc
    busy: VS0 CS
    busy: VF CS
---

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.25-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Chipset: i965gm
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800
 edid-base64: AP///////wAyDAEDAAAAAAARAQOAIRV4CrNAmVlTjSclUFQAAAABAQEBAQEBAQEBAQEBAQEBfh0A6FAgIDBAMDYAS88QAAAZfh0A6FAgIDBAMDYAS88QAAAAAAAA/gBOVTc2M4AxNTRXMDEKAAAA/gAkMj1FaIun/wEBCiAgAJs=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Thu Aug 26 19:38:55 2010
DumpSignature: fe13e3d7
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Inspiron 1525
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=5ba43d73-91a9-4762-98e6-064e3c2f39e0 ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [i965gm] GPU lockup fe13e3d7
UserGroups:

dmi.bios.date: 03/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-19-generic

[bugbot (bugbot)]

Hey John,

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.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.