[arrandale] GPU lockup d49b2ae1(IPEHR: 0x02000000)

[Jone Marius Vignes]

Binary package hint: xserver-xorg-video-intel

apport seems to be reporting this continuosly

---
ACTHD: 0x0d06c724
EIR: 0x00000000
EMR: 0xffffff3f
ESR: 0x00000001
PGTBL_ER: 0x00000000
IPEHR: 0x02000000
IPEIR: 0x00000000
INSTDONE: 0x000fa17e
INSTDONE1: 0x9f15fc2e
    busy: Row 0, EU 0
    busy: Row 0, EU 1
    busy: Row 0, EU 2
    busy: Row 0, EU 3
    busy: Row 1, EU 0
    busy: Row 1, EU 1
    busy: Row 1, EU 2
    busy: Row 1, EU 3
    busy: Row 2, EU 0
    busy: Row 2, EU 1
    busy: Row 2, EU 2
    busy: Row 2, EU 3
    busy: Row 0 MA
    busy: Row 2 MA
    busy: Row 0 ISC
    busy: Row 1 ISC
    busy: Row 2 ISC
    busy: TD
    busy: CS
    busy: MASF
    busy: MT
    busy: RC
    busy: DAP
    busy: MT idle
    busy: SVSM
    busy: SI
    busy: SO
    busy: PL
    busy: WIZ
    busy: SF
    busy: VF
Ringbuffer: Reminder: head pointer is GPU read, tail pointer is CPU write
ringbuffer at 0x00000000:
---

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu4
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
Architecture: i386
Chipset: arrandale
DRM.card0.DisplayPort.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.HDMI_Type_A.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768
 edid-base64: AP///////wAGrywyAAAAAAATAQOAHRB4ChWFl1hTiiYlUFQAAAABAQEBAQEBAQEBAQEBAQEBJhtWZFAAFjAwIDYAJaQQAAAYAAAADwAAAAAAAAAAAAAAAAAgAAAA/gBBVU8KICAgICAgICAgAAAA/gBCMTMzWFcwMyBWMiAKAEk=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: On
 modes:
 edid-base64:
Date: Wed Sep 22 22:32:30 2010
DumpSignature: d49b2ae1
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
Lsusb:
 Bus 002 Device 003: ID 04f2:b1d8 Chicony Electronics Co., Ltd
 Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 3820T
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic-pae root=UUID=7813a027-28e0-43de-97c5-330bb77a7470 ro acpi_osi=Linux quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

SourcePackage: xserver-xorg-video-intel
Title: [arrandale] GPU lockup d49b2ae1
UserGroups:

dmi.bios.date: 05/04/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.13
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Aspire 3820T
dmi.board.vendor: Acer
dmi.board.version: V1.13
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.13
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.13:bd05/04/2010:svnAcer:pnAspire3820T:pvrV1.13:rvnAcer:rnAspire3820T:rvrV1.13:cvnAcer:ct10:cvrV1.13:
dmi.product.name: Aspire 3820T
dmi.product.version: V1.13
dmi.sys.vendor: Acer
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic-pae

[bugbot (bugbot)]

Hey Jone,

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.