[gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000001 IPEHR: 0x60020100

[Tim Penhey]

I am running the compiz and unity from the product strategy PPA. This is work that should shortly land in quantal.

ppa:unity-team/staging

Shortly after logging in (I'm guessing around 10 seconds, which is the delay before we construct the dash view inside unity), the GPU locks up.

This has happened every time I have logged in since upgrading to the latest compiz and unity. Restarting compiz makes no difference as it blocks immediately in the same place on restart.

The solution is to restart lightdm.

I have also had compiz crash about 10s after startup as well. I'm assuming the same root cause may be there. Ratio of crashes to lockups is about 2 to 1.

Sometimes it works.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
Uname: Linux 3.6.0-030600rc3-generic x86_64
ApportVersion: 2.5.1-0ubuntu3
Architecture: amd64
Chipset: gm45
Date: Thu Aug 30 10:44:08 2012
DistroCodename: quantal
DistroVariant: ubuntu
DuplicateSignature: [gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000001 IPEHR: 0x60020100 Ubuntu 12.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GpuHangFrequency: Several times a day
InterpreterPath: /usr/bin/python3.2mu
MachineType: Micro-Star International PR420
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-030600rc3-generic root=UUID=30f7166b-fe9e-4d50-81f8-9c0566868056 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu3
 libdrm2 2.4.38-0ubuntu2
 xserver-xorg-video-intel 2:2.20.3-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Title: [gm45] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000001 IPEHR: 0x60020100
UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
UpgradeStatus: Upgraded to quantal on 2012-08-03 (26 days ago)
UserGroups:

dmi.bios.date: 02/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-1432
dmi.board.vendor: Micro-Star International
dmi.board.version: Ver 1.000
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/13/2009:svnMicro-StarInternational:pnPR420:pvrVer1.000:rvnMicro-StarInternational:rnMS-1432:rvrVer1.000:cvnMicro-StarInternational:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: PR420
dmi.product.version: Ver 1.000
dmi.sys.vendor: Micro-Star International

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bryce Harrington (bryce)]

This is a common sporadic failure on gen4 chips. Upstream bug reports are:

https://bugs.freedesktop.org/show_bug.cgi?id=53379
https://bugs.freedesktop.org/show_bug.cgi?id=53385

For debugging work, there are some suggested avenues of analysis on the above bugs (e.g. git bisection between kernel 3.4 and 3.5).

Reported workaround is to switch from UXA to SNA in your xorg.conf; SNA is not yet considered broadly stable enough for us to turn on as the default, but has been heavily tested upstream.

[Timo Aaltonen (tjaalton)]

Tim: please test with sna turned on, put this in /etc/X11/xorg.conf:

Section "Device"
 Identifier "intel"
 driver "intel"
 Option "UseSna" "True"
EndSection

[Timo Aaltonen (tjaalton)]

sorry, should be 'Option "Accelmethod" "sna"' instead..

[Tim Penhey (thumper)]

On 20/09/12 21:43, Timo Aaltonen wrote:
> sorry, should be 'Option "Accelmethod" "sna"' instead..

This seems to have fixed it.

[Timo Aaltonen (tjaalton)]

thanks, I need to send this upstream now

[Bryce Harrington (bryce)]

@Timo, I spoke with ickle about this bug on 9/10 -- comment #3 includes two upstream bugs he pointed to that he felt were probably dupes of this. Those bugs list some git bisection searches that could be done to narrow down the regressing patch.

@thumper, yeah like I mentioned SNA should work as a workaround, but we will not be shipping SNA by default in quantal so I'd hesitate calling it a fix, unless you only need to get the one system up and running. If you do want to help get this fixed in general, then would you be willing to do the git bisection work on the kernel to help isolate what patch causes the failure?

[Timo Aaltonen (tjaalton)]

well, the current -intel version has plenty of pageflip fixes on it, so it would be time to test without SNA again to see if this was indeed pageflip related (as fdo 53385 suggested)

[Blümchen Blau (bluemchen-blau)]

Had the error-report strait after successfull boot.
Don't know, if this is connected with a problem I experience since Kernels 3.4.0-15 and higher: I need in average 3 boots until unity starts properly. Systems sticks at some point during boot after authentication of dm-crypt (showing various text-messages).
Usually (not always) starts then with Kernel 3.4.0-14.
Found no xorg.conf on my system.

[penalvch (penalvch)]

Tim Penhey, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xserver-xorg-video-intel REPLACE-WITH-BUG-NUMBER

Please note, given that the information from the prior release is already available, doing this on a release prior to the development one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Tim Penhey (thumper)]

I am currently running saucy, and on a different laptop. No longer experiencing this problem.

[penalvch (penalvch)]

Tim Penhey, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1043562/comments/12 regarding you are using different hardware and this is not reproducible on it. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.