GPU freeze possibly caused by transparency effects? sandybridge-m-gt2 GPU lockup IPEHR: 0x41e80000 IPEHR: 0x0b140001

Bug #1159255 reported by markusj
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

The issue appeared since a few days and might be related to transparency/overlay effects used by gnome shell (or firefox for hw-accelerated rendering). The screen freezes except of mouse pointer movement, but the system still reacts on keystrokes.

Recent related updates:
03/19: linux-generic-lts-quantal:amd64 3.5.0.25.32 -> 3.5.0.26.33 (including image und headers)
03/08: xserver-common:amd64 2:1.11.4-0ubuntu10.11 -> 2:1.11.4-0ubuntu10.12 (common, xephyr, xorg-core)

Most propably the last kernel update caused this problem

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
ProcVersionSignature: Ubuntu 3.5.0-26.42~precise1-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Chipset: sandybridge-m-gt2+
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Mar 23 23:14:26 2013
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
DuplicateSignature: [sandybridge-m-gt2+] GPU lockup IPEHR: 0x41e80000 IPEHR: 0x0b140001 Ubuntu 12.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: Yes,
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21d1]
 NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21d1]
InterpreterPath: /usr/bin/python2.7
MachineType: LENOVO 4242PT2
MarkForUpload: True
ProcCmdline: /usr/bin/python /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-26-generic root=/dev/mapper/vgluks-root ro quiet noplymouth pcie_aspm=force acpi_irq_balance i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 i915.powersave=1 drm.vblankoffdelay=1 bootchart=disable
RelatedPackageVersions:
 xserver-xorg 1:7.6+12ubuntu2
 libdrm2 2.4.39-0ubuntu0.1
 xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
SourcePackage: xserver-xorg-video-intel
Title: [sandybridge-m-gt2+] GPU lockup IPEHR: 0x41e80000 IPEHR: 0x0b140001
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 12/05/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET61WW (1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4242PT2
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:bvr8AET61WW(1.41):bd12/05/2012:svnLENOVO:pn4242PT2:pvrThinkPadT520:rvnLENOVO:rn4242PT2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4242PT2
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.12-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu0.1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3

Revision history for this message
markusj (markusj) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Hans-Martin (hmm-heeg) wrote :

I experienced the same problem on an i3-2100 with 3.2.0-39. No detailed info available as I'm not near the machine.
Running the 3.2.0-38 kernel made the bug go away.

Revision history for this message
Chris Wilson (ickle) wrote :

TLB invalidate bug, fixed in raring, maybe one day backported to 3.5. By the way the bug is also present in 3.2.0-38.

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Fix Released
Revision history for this message
Ubu4u (bj7u6139zdyf2a6nz2ly74oec10f2lnela24rsgd389d0elot5a7jz6hawymvsdk8c4sd6srfzh4i-info-jjcftv6wldnzq84cskygyvhqqb9qwjfcq0yfnwzcca0ux8ircw2a3om624q2ycdp941uw5474gcdb) wrote :

This sounds related to the bug I'm experiencing:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1160151

At the moment, I am not able to use Ubuntu on the affected machine because of the continuous freezing.

The reason I decided to chime in here is because of the reference to the transparency issue: I am using Docky, which uses transparency effects, and I have found this bug to be easily reproducible when Docky is activated with a mouse hover-over.

I'm seeing a lot of recent posts on the /usr/share/apport/apport-gpu-error-intel.py issue on various forums on the Internet, including AskUbuntu, Ubuntu Forums, Ubuntu Answers, etc. - most within the past week.

Revision history for this message
markusj (markusj) wrote :

@Chris Wilson:

This bugreport is about precise (and maybe quantal), and there is no package out there which fixes this bug. Nice if the raring-kernel does not have this issue any more, but the affected versions have no working fix released! As far as i understand the bugtracker, the status you set is wrong/missleading.

Revision history for this message
Ubu4u (bj7u6139zdyf2a6nz2ly74oec10f2lnela24rsgd389d0elot5a7jz6hawymvsdk8c4sd6srfzh4i-info-jjcftv6wldnzq84cskygyvhqqb9qwjfcq0yfnwzcca0ux8ircw2a3om624q2ycdp941uw5474gcdb) wrote :

@Chris,

My setup is very similar to markusj's, and I am still having the issue. Unless you can explain otherwise, I would have to agree that you've incorrectly marked this bug as "Fixed Released," when in fact it has not been fixed in Ubuntu 12.04.

@Markusj,

Would it be possible for you to verify that using Docky for a little while, and especially while hovering the mouse over it, can recreate the GPU freeze.

I have opened a related bug here: https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1160151

Revision history for this message
markusj (markusj) wrote :

@Ubu4u: Yes, but this would not make any sense at all. The bug is known and there are already patches which fix the bug for raring. (See https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157649/comments/15). You better stop opening bugreports for packages which do not cause this bug. Docky is only a victim.

Use 3.5.0-25 (which works reliable) until a fixed kernel has been released.

Revision history for this message
Ubu4u (bj7u6139zdyf2a6nz2ly74oec10f2lnela24rsgd389d0elot5a7jz6hawymvsdk8c4sd6srfzh4i-info-jjcftv6wldnzq84cskygyvhqqb9qwjfcq0yfnwzcca0ux8ircw2a3om624q2ycdp941uw5474gcdb) wrote :

@markusj,
My apologies - as I explained to Chris, I'm very, very new to the bugtracking process, and to the linux kernel in general.

I've removed the tag to Docky from my original bug, and have marked my bug as a duplicate of #1157649. I've also just installed the 3.5.0-25 kernel with "sudo apt-get install linux-image-3.5.0-25-generic linux-headers-3.5.0-25-generic".

I've just tested a bit with the 3.5.0-25 kernel and the GPU crashes seem to have stopped!!!!!!!!

I have so many questions at this point, e.g.:

1) Was the 3.2.0-40 kernel version on my Ubuntu 12.04 LTS machine there because all the software for that version of Ubuntu has not been deemed compatible with it? Why was a newer version not used?

2) Now that I've changed my kernel, will I be receiving automatic software updates OK?

3) What is the best way to keep up to date on the fix for this issue? This is all very cool, I want to help out as much as possible.

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.