[sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7a000002

Bug #906269 reported by Daniel Holbach
84
This bug affects 18 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Incomplete
High
Unassigned

Bug Description

Not quite sure what happened.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Chipset: sandybridge-m-gt2+
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Dec 19 12:48:01 2011
DistUpgraded: Log time: 2011-12-02 10:42:12.615728
DistroCodename: precise
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7a000002 Ubuntu 12.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExecutableTimestamp: 1323941303
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110817)
InterpreterPath: /usr/bin/python2.7
MachineType: LENOVO 429149G
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcCwd: /
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-5-generic root=UUID=51ab960b-a2da-4841-98ce-c017f0582971 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.6+7ubuntu7
 libdrm2 2.4.27-1ubuntu1
 xserver-xorg-video-intel 2:2.15.901-1ubuntu4
SourcePackage: xserver-xorg-video-intel
Title: [sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x7a000002
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to precise on 2011-12-02 (17 days ago)
UserGroups:

dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
version.ia32-libs: ia32-libs 20090808ubuntu32
version.libdrm2: libdrm2 2.4.27-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.10.4-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1

Revision history for this message
Daniel Holbach (dholbach) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Onlyodin (ubuntu-xsnet) wrote :

By enabling "MapsGL" in Google Maps, I seem to get this error reoccurring.

Revision history for this message
PeterKolloch (pkolloch) wrote :

Like described in comment #3, the bug seems to be reproducable by enabling mapsgl in google maps.

As long as that browser window is open, bug reporting windows seem to pop up again and again (after dealing with them).

Revision history for this message
Alan Goodman (zgzx6-alan-kecso) wrote :

Not quite sure what caused this. But the error reporter pops up repeatedly (I counted 15 times this time) which could be a bug in itself?!

Revision history for this message
Doug Morgan (doug-morgan) wrote :

I'm also having this issue, if there is anything I can do to help to diagnose/fix it (debug output, etc) please let me know!

Revision history for this message
Henrik Jacobsson (henrikj) wrote :

I get this a lot to suddenly, not a nice impression for a new stable release. I've been using Precise since alpha-times and only experiencing this now - regression?
Using 12.04 64-bit on Dell Latitude E6420 (core i7 snb)

Revision history for this message
kriztof (krzysztof-arendt) wrote :

In my case the bug started occuring after installing the "Ryzom" game from the Ubuntu Software Center. The game crashed, so I deinstalled it, but the bug remained. It pops up several times a day.

Revision history for this message
Grafosecondo (alafauci) wrote :

+1 after Google maps GPL was activated. It keeps showing up.

tags: added: precise
Revision history for this message
David Overcash (funnylookinhat) wrote :

Ryzom is what I installed to make this start as well - now the crash reports show up any time I start up the computer. The only way I've found to get rid of them is a fresh install ( obviously works ) - reporting the error seems to crash and just tries to report it again.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Please try a 3.4 mainline kernel from here:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/

if it fixes the bug, then this is a dupe of bug 966631

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
importance: Undecided → High
Revision history for this message
David Overcash (funnylookinhat) wrote :

That fixes it for me!

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Could you also try the kernel in precise-proposed, it has the commit from the other bug included.

Revision history for this message
David Overcash (funnylookinhat) wrote :

Just tested 3.2.0-25-generic from precise-proposed and it worked as well.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

had a chat with dholbach who said that the bug happened to him only occasionally and not anymore since some time, so I'll just mark this as a dupe of the other bug since that's what other folks here have hit.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.