Constant "false gpu hang" system alerts

[Star Man]

[Impact]
Apport hook is triggered for GPU lockups in the stable release, in cases where the system did not freeze. We no longer need bug reports about GPU lockups for quantal (or other stable releases), so can simply disable the hook.

[Test Case]
On Intel gfx hardware running quantal, wait until a GPU hang occurs.
The apport hook should not generate a .crash file in /var/crashes.
The apport hook should not trigger a display of the bug reporting dialogs in the current or subsequent sessions.

[Regression Risk]
The patch comments out a udev rule, so is very low risk of regression.

The side effect of this change is that GPU lockup bugs will no longer be collected for quantal. This is acceptable; we are mostly just interested in lockups in raring and newer at this point.

[Original Report]
My system:

I'm running Ubuntu 12.10 64-bit
My system is a Macbook4.1 Intel Core 2 Duo 2.4GHz / 2GB RAM / GMA X3100 with 144MB shared memory / Intel HDA audio.
The image I used for installing the system is Ubuntu 12.10 64-bit (AMD64) + MAC.

The issue:

Every time I log onto my session, a system program error dialog is displayed. (I'll try to translate as possible since my system is running in Spanish)

· "There's is a system program problem detected. Do you want to inform this now?"

I pick "Yes", and then I've got to enter my password. Then, another dialog appears displaying the following message:

· "We're sorry. Ubuntu 12.10 has experienced an internal error. If you continue to have problems, try to restart the system.
[marked checkbox] Send a bug report to help solve this issue."

[*] Picking "details" it shows a long list of components wich start with the lines "Executable path | /usr/share/apport/apport-gpu-error-intel.py"

Before I even pick the "continue" button, another system dialog pops up onscreen displaying the following message:

· "Apport has detected a possible GPU hang. Did your system recently lock up and/or require a hard reboot?"

Since neither of the two were needed, I pick "No". Then, the system pop up another dialog:

· "Your display manager log files may help developers diagnose the bug, but may contain sensitive information such as your hostname. Do you want to include these logs in your bug report?"

I pick "Yes". In the next Apport dialogue "Would you be willing to do additional debugging work?", I pick "Yes".

Several minutes later, nothing happens yet. No other system dialogued showed up. I never did any debugging work as I choose to do.

Meanwhile, the dialogue that displays the details of the internal error (in the line marked with [*] on this report), now has completed the list. It took more than two minutes to do. I mark the checkbox for "Send a bug report to help solve this issue", and then I pick "Continue".

Nothing else ever happened. I don't even know if the bug was reported.

This issue will happen again some time later, and so on, being really annoying.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Wed Oct 31 10:56:49 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: bcmwl, 5.100.82.112+bdcom, 3.5.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00a1]
   Subsystem: Apple Inc. Device [106b:00a1]
InstallationDate: Installed on 2012-10-24 (6 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64+mac (20121017.3)
MachineType: Apple Inc. MacBook4,1
MarkForUpload: True
PlymouthDebug: Error: [Errno 13] Permiso denegado: '/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f1d1b864-6064-4edb-b90e-e7da9ffb7419 ro plymouth:debug splash quiet drm.debug=0xe
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/09/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MB41.88Z.00C1.B00.0802091535
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F22788A9
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F22788A9
dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9:
dmi.product.name: MacBook4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.8.4-0ubuntu3
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

[Launchpad Janitor (janitor)]

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

[Matt Richardson (m-richardson-1990)]

I am experiecing this problem too.

I am running Ubuntu 12.10 32bit on a HP Compaq Presario CQ71
Pentium(R) Dual-Core CPU T4200 @ 2.00GHz × 2
4gb ram
Mobile Intel® GM45 Express Chipset x86/MMX/SSE2

I will post the full output next time the error appears

[0x14 (powerxaxvi50)]

same here.
running on Ubuntu 12.10 32bit
cpu B980 @ intel HD 2000

[Jeremy Sutherland (jsutherland74)]

Same here. Any Fix yet?

[Simo (s-benyoussef)]

Same issue and it is getting frustrating ...

[Patrick Xarles Hayes (pxhayes)]

I'm having the same problem on a ThinkPad T420 Type 4180-A22 running Ubuntu 12.10 64 bit.

I don't, however, get these errors when I'm running KDE instead of Gnome.

[Bryce Harrington (bryce)]

Applied the same change as done in 2.5.1 for precise (see bug #997470).

Leaving a raring task open as a reminder that this needs disabled when raring releases as well.

[Launchpad Janitor (janitor)]

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

[Humberto Ferreira da Luz Jr. (hfluz-jr)]

Same happening to me for the last few days. I hope we can receive the fix through updates soon.

[mx80 (rzach)]

This has just started happening to me today after I updated software.
Linux maggie 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:18:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
on an Asus UX31E notebook.

[Chris Halse Rogers (raof)]

Hello Star, or anyone else affected,

Accepted xdiagnose into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xdiagnose/3.2.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Steven Van Maldeghem (steven-vanmaldeghem)]

I have the same issue using Ubuntu 12.10 and working on a Thinkpad (not sure which type).

Some way to dissable this alert would be great.

[dnelub (dnelub)]

Hi

I am also one those who are affected from the bug. I downloaded xdiagnose given in #12 but unfortunately installation gave an error:

Traceback (most recent call last):
  File "setup.py", line 28, in <module>
    import DistUtilsExtra.auto
ImportError: No module named DistUtilsExtra.auto

[dnelub (dnelub)]

Hi again

I have enabled proposed-repository and installation is done successfullly but the problem is still there. Thing is that it doesnt seem that it is a false alert. After receiving several errors, the computer is getting warmer and the fun runs faster. Freankly speaking I am afraid of the bug.

[jqf (jquinnford)]

I was getting these errors all the time. Not sure if there's a real underlying bug here (as noted by dnelub -- this may be something outside of xdiagnose that is very real -- and xdiagnose just seems to create the annoying xdiagnose alerts -- which this fix appears to be for).

I just wanted to disable the irritating popups that kept showing up.

Here's a fix that's worked for me on my Lenovo Ideapad U300s (fingers crossed -- 1 day without xdiagnose alerts) and is incredibly simple:

1 - In terminal, type: sudo xdiagnose

2 - uncheck EVERYTHING in the xdiagnose window

3 - restart the computer

I also did the following -- and I'm not sure whether it did something in addition to the items above - so I'm disclosing it just to be safe:

1 - In Software Center search for "xdiagnose"

2- Select it when you find it, and click on "More Info"

3 - In Add-ons, uncheck the box next to "Tools for debugging the intel graphics driver (intel-gpu-tools)"

4 - restart the computer.

The reason I'm skeptical that the Software Center change did anything is that if I re-open the Software Center after boot, the "Tools for debugging the intel graphics driver (intel-gpu-tools)" is checked once again -- so it looks like it can't actually be disabled.

Let me know if it works for you.

[paulf (paulf-linux-launchpad)]

Since i have installed the latest kernel via updates i am having this problem continuously. The kernel version is 3.5.0-26-generic.

if i have taken the time to report this then many more out there are being hit who dont read launchpad bugs for solutions.

[Jean-Philippe Roberge (jproberge)]

I'm also having this problem since I last updated the kernel. This is very very annoying and I was having a hard time working on my laptop.

But then I tried jqf's patch (I call it a patch since it doesn't fix the problem at its source IMAO) and everything is fine since then.

So thanks a lot jqf for sharing your fix, it completely saved my life (I'm writing a thesis, and it's due for next week:) )

jqf's fix working for me until now.

[Teelka (teelka)]

I had the same problem, disabling the messages helped (as I was told in this German forum --> http://forum.ubuntuusers.de/topic/staendige-fehlermeldung-von-ubunut-12-10-intel/). Not sure if my netbook is kinda slower, but if thats the case, it's not much. Hopefully it's "just" the messages and nothing else!

[danpo (danpo)]

I can confirm the same problem on a ThinkPad X220i. Most of the time the error appears just randomly, however the system sometimes hangs for a couple of seconds... Will try -proposed package and let you know whether it worked.

[danpo (danpo)]

Ok, so I got an error again even with xdiagnose/quantal-proposed. Will try the workaround suggested above, although I'm afraid that disabling error messages is just not what you would typically want to do to solve an error.

[dnelub (dnelub)]

Hi again,

I am not sure the problem is because of xdiagnose but something is clear that xdiagnose makes things worse because the computer is getting warmer if I want to report problem. As far as I see, xdiagnose intervene the process whenever there is a problem in GPU. That is why I am simply ignoring the error. However, it is not a real solution because computer keeps hanging.

[ismir (scheinbar)]

same here - only error message, but all works
using thingpad edge E520(intel sandybridge mobile), ubuntu 12.10
(xdiagnose found nothing or i m too stupid to use it)

[Crz (flgcrz)]

Same bug here will try some of the proposed solutions.

[Star Man (starman-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

Hello guys. I just installed the proposed update: sorry but the bug is still present.

[breckenr (keith-breckenridge)]

I have the same issue, but only on one of my pcs -- an HP / Compaq 6200 running 12.10 in 32bit. I'll disable the automatic gpu alerts. I hope that's all it is.

[Sleet Storm (tsehai3)]

Also affected by this after latest kernel update.The update also included something about the perl-library, was a pretty big one.
Had several freezes needing hard reboot since my laptop didn't react anymore .

I'm using Ubuntu 12.10 64bit.

[nldquy (nguyenledinhquy-yahoo)]

Confirmed

Ubuntu 12.10 64bit
CPU Intel Corei7 2600
RAM Kingmax 4x4GB DDRIII

[norbi (ndiazromero)]

  Hi, same problema... I tried solution of #16 but the PC keeps hanging.

                                                                                                           Thanks

[Bryce Harrington (bryce)]

If anyone is still seeing this and wants to comment here, please provide:

  /lib/udev/rules.d/40-xdiagnose.rules

and

 apt-cache policy xdiagnose

[Bryce Harrington (bryce)]

I have booted quantal on an intel box, and after enabling proposed and installing xdiagnose 3.2.3 can verify the udev rule is commented out as intended, with no other misbehaviors. (I don't reproduce the false gpu lockups so can't verify that aspect of the bug.)

[Launchpad Janitor (janitor)]

This bug was fixed in the package xdiagnose - 3.4.4

---------------
xdiagnose (3.4.4) raring; urgency=low

  * debian/xdiagnose.udev: Disable gpu apport hook for raring release
    (LP: #1073626)
  * apport/apport-gpu-error-intel.py:
    - Bail if not on a devel release (LP: #1071278)
    - Skip over failure accessing apt cache (LP: #1103061)
 -- Bryce Harrington <email address hidden> Mon, 01 Apr 2013 18:54:09 -0700

[Brian Murray (brian-murray)]

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package xdiagnose - 3.2.3

---------------
xdiagnose (3.2.3) quantal-proposed; urgency=low

  * xdiagnose.udev: Disable GPU apport hook from being triggered by udev.
    This should only be enabled during the development period. Apport is
    disabled after release, but it appears the hook still gets triggered
    under certain circumstances.
    (LP: #1073626)
 -- Bryce Harrington <email address hidden> Thu, 14 Feb 2013 12:38:26 -0800

[Sleet Storm (tsehai3)]

Where do I find this update please? Full name would be good too. Still xdiagnose-3.2.3?

[Sleet Storm (tsehai3)]

I would really appreciate an answer. What am I supposed to do now?

[dragonmago (dragonmago)]

Ok, I am a victim of this infamous bug and it's getting really frustrating. Apport just keeps spamming error messages and report requests -until eventually, a real freeze occurs.

For reference, here are the requested files:

--40-xdiagnose.rules

# do not edit this file, it will be overwritten on update

# Jesse Barnes on <email address hidden>:
# You'll get three events, one when the error is detected, one before the
# reset and one after. Each has a different environment variable set; the
# initial error has ERROR=1, the pre-reset event has RESET=1 and the
# post-reset event has ERROR=0.

# disable GPU hang hook for release
# SUBSYSTEM=="drm", ACTION=="change", ENV{RESET}=="1", RUN+="/usr/share/apport/apport-gpu-error-intel.py"

xdiagnose:
  Installed: 3.2.3
  Candidate: 3.2.3
  Version table:
 *** 3.2.3 0
        500 http://archive.ubuntu.com/ubuntu/ quantal-updates/main amd64 Packages
        500 http://archive.ubuntu.com/ubuntu/ quantal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     3.2 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages

For lack of a better idea at this time, I've upgraded the upgrades from Stable to Proposed -thus installing a cornucopia of things it seems I'll never need, however, I haven't had another event in the last 10 minutes or so. I'll keep you posted.

[Bryce Harrington (bryce)]

On Wed, Apr 03, 2013 at 11:01:58PM -0000, dragonmago wrote:
> Ok, I am a victim of this infamous bug and it's getting really
> frustrating. Apport just keeps spamming error messages and report
> requests -until eventually, a real freeze occurs.

Even after applying this change, if you still have stuff in /var/crash/
apport will bug you to file those. So do `sudo rm /var/crash/*.crash`
to clear it out.

You don't need to install everything from proposed, only xdiagnose.
Make sure to reboot after installing it, because the udev rules need to
be re-read. Or, if you don't want to reboot, run
`sudo service udev restart`.

And note this change is only disabling the gpu lockup apport detector.
That's the one that pops up after you reboot from a system hang, that
says "Did your system recently lockup and require a hard reboot?"

If the popups you're seeing do *not* say that, and /var/crash is empty,
then you have some different problem with apport.

[dragonmago (dragonmago)]

Well, I've worked the whole morning without interruption. It seems like the problem has been solved.

Thanks Mr. Harrington, it seems like Ubuntu is being run as a tight ship.

[akaxa_82 (akaxa-82)]

executablepath /usr/share/apport/apport-gpu-error-intel.py

[Blair Zajac (blair)]

I'm running quantal and just started getting GPU hangs on 3.5.0-26 and 3.5.0-27, the last good kernel is 3.5.0-25 which doesn't cause GPU hangs.

Aside from the bug in apport itself, doesn't ubuntu want to know when there are GPU hangs with newer kernels on stable releases?