Desktop becomes completely unresponsive

[Seth Forshee]

I'm finding that occasionally as I'm using my desktop it becomes completely unresponsive. Often this seems to be random, and these random freezes are happening several times a day. The only reliable way I've been able to reproduce it is by closing and opening the lid (which isn't triggering a suspend due to bug 933710). When in this state the mouse pointer moves but otherwise the screen is not updated at all. If I switch to a VT and back the desktop isn't even redrawn, only the mouse pointer.

I've looked through the logs and can't find any crash reports when this happens. X is still running when in this state.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
Date: Wed Feb 22 09:33:40 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
---
.tmp.unity.support.test.0:

ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CompizPlugins: [core,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
CompositorRunning: compiz
DistUpgraded: Fresh install
DistroCodename: precise
DistroRelease: Ubuntu 12.04
DistroVariant: ubuntu
DkmsStatus:
 apple-bl-gmux, 0.4, 3.0.0-16-generic, x86_64: installed
 apple-bl-gmux, 0.4, 3.2.0-14-generic, x86_64: installed
 apple-bl-gmux, 0.4, 3.2.0-15-generic, x86_64: installed
 apple-bl-gmux, 0.4, 3.2.0-16-generic, x86_64: installed
 apple-bl-gmux, 0.4, 3.2.0-17-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:00ea]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208)
MachineType: Apple Inc. MacBookAir4,1
Package: xorg 1:7.6+10ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=f4af0efe-df4b-4d74-8995-7081cf79889c ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Tags: precise precise precise ubuntu compiz-0.9 precise ubuntu compiz-0.9
Uname: Linux 3.2.0-17-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 10/14/2011
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA41.88Z.0077.B0E.1110141154
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C08A6BB70A942AC2
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir4,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C08A6BB70A942AC2
dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0E.1110141154:bd10/14/2011:svnAppleInc.:pnMacBookAir4,1:pvr1.0:rvnAppleInc.:rnMac-C08A6BB70A942AC2:rvrMacBookAir4,1:cvnAppleInc.:ct10:cvrMac-C08A6BB70A942AC2:
dmi.product.name: MacBookAir4,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Omer Akram (om26er)]

which GPU do you use? its probably better to use ubuntu-bug unity command for such type of reports and make sure you select the option to send complete logs about your system.

[Seth Forshee (sforshee)]

This machine has intel graphics.

$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09)

[Seth Forshee (sforshee)]

I've determined that this is pretty reliably reproducible when using chromium by loading google+ and rapidly scrolling up and down using the touchpad. I'm not sure whether or not it's specifically tied to chromium however. I also saw it earlier when scrolling through a spreadsheet in Calc, although I haven't been able to reproduce it and I did have chromium open at the time.

[Seth Forshee (sforshee)]

After upgrading this morning I haven't been able to reproduce the problem whereas I could produce it reliably before. I'm going to keep testing, but if I haven't been able to reproduce it by the end of the day I'll close out the bug.

For reference, here's the list of packages that were upgraded.

  libc-bin:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libgl1-mesa-dri:amd64 (8.0.1-0ubuntu1, 8.0.1-0ubuntu2)
  libgl1-mesa-glx:amd64 (8.0.1-0ubuntu1, 8.0.1-0ubuntu2)
  libglapi-mesa:amd64 (8.0.1-0ubuntu1, 8.0.1-0ubuntu2)
  libc6-i386:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libxatracker1:amd64 (8.0.1-0ubuntu1, 8.0.1-0ubuntu2)
  libc6-dev:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libglu1-mesa:amd64 (8.0.1-0ubuntu1, 8.0.1-0ubuntu2)
  libc-dev-bin:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libc6:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libc6:i386 (2.15-0ubuntu2, 2.15-0ubuntu3)
  libc6-dev-i386:amd64 (2.15-0ubuntu2, 2.15-0ubuntu3)
  python-wadllib:amd64 (1.3.0-0ubuntu2, 1.3.0-1)

[Seth Forshee (sforshee)]

Just got this twice more, both times while using chromium. It doesn't happen when closing and opening the lid anymore, but it's still not fixed.

[Seth Forshee (sforshee)]

I spoke too soon. The desktop is once again hanging when I close and reopen the lid, although not every time.

I experimented a little with the last hang, and I found that killing compiz (by sending it SIGKILL) got my desktop back to a functional state.

[Seth Forshee (sforshee)]

I've attached to compiz a few times using gdb when I get in this state, and the state of the threads always seems to be the same. Here's the output from one of the sessions, in case it's helpful.

(gdb) info threads
  Id Target Id Frame
  4 Thread 0x7f7679af3700 (LWP 8136) "gmain" 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
  3 Thread 0x7f7663301700 (LWP 8183) "dconf worker" 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
  2 Thread 0x7f7662b00700 (LWP 8184) "gdbus" 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
* 1 Thread 0x7f767ec02780 (LWP 8135) "compiz" 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f767be78862 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007f767be79d5f in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007f767be79f7b in xcb_wait_for_reply () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4 0x00007f767d973fed in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007f767d96a4e6 in XQueryTree () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6 0x00007f766ac558dd in GestureEngine::FindCompWindow(unsigned long) () from /usr/lib/compiz/libunityshell.so
#7 0x00007f766ac55a21 in GestureEngine::OnTouchStart(GeisAdapter::_GeisTouchData*) () from /usr/lib/compiz/libunityshell.so
#8 0x00007f766ac54ae7 in GeisAdapter::GestureStart(void*, unsigned int, unsigned int, unsigned long, GeisGestureAttr*) () from /usr/lib/compiz/libunityshell.so
#9 0x00007f766a5a9ded in ?? () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
#10 0x00007f766a5aa996 in ?? () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
#11 0x00007f766a5a4ee6 in ?? () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
#12 0x00007f766a5aa5ec in geis_event_dispatch () from /usr/lib/x86_64-linux-gnu/libutouch-geis.so.1
#13 0x00007f766ac52920 in GeisAdapter::OnWatchIn(_GIOChannel*, GIOCondition, void*) () from /usr/lib/compiz/libunityshell.so
#14 0x00007f767c7dbdda in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007f767c7dc1a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007f767c7dc59a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x000000000040299e in main ()
(gdb) thread 2
[Switching to thread 2 (Thread 0x7f7662b00700 (LWP 8184))]
#0 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x00007f767df6bd93 in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x00007f767c7dc136 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f767c7dc59a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f7678818446 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x00007f767c7fd7d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f767dc71e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6 0x00007f767df7774d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x0000000000000000 in ?? ()
(gdb) thread 3
[Switching to thread 3 (Thread 0x7f7663301700 (LWP 8183))]
#0 0x00007f767df6bd93 i...

[Steven Keys (steevven1)]

Is this a Sandy Bridge processor? If so, this may be related to RC6 being turned on by default recently in the Ubuntu 12.04 kernel update. This issue has been discussed a lot here over time: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/818830

To test whether it is RC6-related, first determine if your processor is a Sandy Bridge one by running "cat /proc/cpuinfo | grep "model name" | head -1" and looking up that processor model number in Google.

If it is Sandy Bridge, pass the kernel parameter "i915.i915_enable_rc6=0" on boot and see if you can reproduce the bug. If you can't, please report your experience by adding your machine to the tests being done here: https://wiki.ubuntu.com/Kernel/PowerManagementRC6

Thanks.

[Steven Keys (steevven1)]

Just to clarify: If your bug disappears when you pass that kernel parameter (and you haven't updated your kernel since you filed this bug), it means that RC6 is the culprit. If the bug persists, it means RC6 is not the culprit. Please report which is the case, both here and at the wiki.

If your processor is not Sandy Bridge, then nothing I said is relevant to you.

[Seth Forshee (sforshee)]

It is sandy bridge, but I see no evidence that it's RC6 related. I've had RC6 enabled on this machine since December and only just recently started seeing it. If I disable RC6 now I can reproduce it, and if I go back to earlier kernels (as far back as 3.2.0-3.9 from early December) I can reproduce it with RC6 disabled. So I'm fairly certain this is _not_ related to RC6.

I am getting the idea that this could somehow related to intel graphics though, given my inability to reproduce this on a radeon system. I'm going to explore that a bit more today.

[Seth Forshee (sforshee)]

I've been trying some different things today, and I found that if I downgrade mesa to 7.11-0ubuntu4 I've so far been unable to reproduce the issue. The problem has been elusive at times before though, so it's not definite, but I've gone back and forth between mesa versions a number of times and I've been able to consistently reproduce the issue with the newer mesa but not the older. I'm going to go ahead and add a mesa task at this point to see if we can get anywhere.

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

apport information

[Seth Forshee (sforshee)]

I'm seeing a similar hang sometimes when coming out of S3 as well. This just happened a few minutes ago. The compiz stacktrace this time was identical to the one above. I'm attaching .xsession-errors, which I note has a lot of "failed to get previous touch value" warnings along with some others. Xorg.0.log also had a number of "unable to find touch point 1" messages.