Unity crashes after being suspended for >48hrs

Bug #900308 reported by Steve Magoun
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned
xorg (Ubuntu)
Invalid
High
Bryce Harrington

Bug Description

After being suspended for a weekend (Friday pm to Monday am - about 60hrs) Unity/compiz (or X?) reliably crash upon resume, dropping me to the lightdm greeter. As a result whatever apps I had on my desktop are gone - it is as if I had restarted or logged out. Shorter periods of sleep work fine; the machine resumes normally after being suspended for 1hr.

I believe this is a regression that appeared a couple weeks after 11.10 (I regularly pull from oneiric-proposed) but I don't have an exact date.

I haven't found any indication of a crash in any system logs, and there is nothing in /var/crash/.
I do see this at the end of /var/log/Xorg.0.log.old:
[121316.041] ddxSigGiveUp: Closing log

In the attached logs, I put the machine to sleep on Dec 2 at 17:05 and woke it up on Dec 5 at 08:53.

To reproduce:
1) Suspend the machine
2) Unplug it so it's running on battery power
3) Don't touch the machine for a few days (Friday night-->Monday morning, for example)
4) Plug the machine back in and wake it up

Actual results:
1) After the screen comes on, I see the desktop background and a few flashing white rectangles that correspond to windows on the screen (same size/position).
2) X seems to crash/quit; I see a console with text (no screenshot available, sorry)
3) Light starts and I'm prompted to login

Expected results:
Machine resumes to the desktop

Hardware is a Macbook Pro 3,1 w/ NVidia graphics. OS is Ubuntu 11.10 AMD64. I upgraded to nvidia-current-updates 285.05.09-0ubuntu0.1, but that did not solve the problem.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.24.0-0ubuntu2b1
ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
Uname: Linux 3.0.0-14-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011
 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,imgjpeg,decor,snap,imgpng,place,dbus,session,mousepoll,regex,commands,vpswitch,wall,neg,move,gnomecompat,resize,imgsvg,resizeinfo,text,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,scaleaddon]
CompositorRunning: compiz
Date: Mon Dec 5 08:58:18 2011
DistUpgraded: Log time: 2011-09-02 09:45:42.465764
DistroCodename: oneiric
DistroVariant: ubuntu
DkmsStatus:
 nvidia-current, 280.13, 3.0.0-14-generic, x86_64: installed
 nvidia-current-updates, 285.05.09, 3.0.0-14-generic, x86_64: installed
 virtualbox, 4.1.2, 3.0.0-14-generic, x86_64: installed
DpkgLog:

GraphicsCard:
 nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Apple Computer Inc. Device [106b:00a0]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
JockeyStatus:
 xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use)
 xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Disabled, Not in use)
MachineType: Apple Inc. MacBookPro3,1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-14-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: Upgraded to oneiric on 2011-09-02 (93 days ago)
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 03/05/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP31.88Z.0070.B07.0803051658
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4238BC8
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-F4238BC8
dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
dmi.product.name: MacBookPro3,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
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-1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

Revision history for this message
Steve Magoun (smagoun) wrote :
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

Looking at the X logs, it looks like an Xorg issue to me, not a Unity or compiz issue. I might be wrong, though, I'll wait for someone from x-swat to look at this.

Changed in unity:
status: New → Invalid
affects: unity (Ubuntu) → xorg (Ubuntu)
Changed in unity:
status: Invalid → Incomplete
Changed in xorg (Ubuntu):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
Martin Pitt (pitti) wrote :

Indeed, the log says:

[ 96109.353] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 96109.353]
Backtrace:
[ 96109.358] 0: /usr/bin/X (xorg_backtrace+0x26) [0x460566]

I don't know what that means; Bryce, do you?

Changed in xorg (Ubuntu):
assignee: Canonical Desktop Team (canonical-desktop-team) → Bryce Harrington (bryce)
Revision history for this message
Chris Halse Rogers (raof) wrote :

This doesn't look like an X issue to me - that EQ overflow indicates that something blocked the Xserver process for long enough for its internal event queue to fill up; this can take much less than a second for a touchpad driver like synaptics. Given that the EQ overflow seems to have occurred many hours before the problem I don't think it's related.

The final line, “[121316.041] ddxSigGiveUp: Closing log” indicates that the X server shut down as expected; this looks like something has asked the server to shutdown, and it's complied.

Revision history for this message
Rick Spencer (rick-rickspencer3) wrote :

Setting back to new and subscribing Dx. Could you please take another look baesd on the Desktop Team's analysis?

Changed in unity:
status: Incomplete → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Magoun (smagoun) wrote :

Reproduced this again. Here is a video taken while resuming the system after being asleep for a weekend:
http://ubuntuone.com/7DTQgFyE49FT6r4AHrEr2r

I saw the same "ddxSigGiveUp: Closing log" signature in Xorg.0.log.old. I haven't found any other indication of a crash on the system.

(Sorry the video is upside-down, that is bug 697756)

Revision history for this message
Bryce Harrington (bryce) wrote :

"ddxSigGiveUp: Closing log" is just the normal "X is done running and is closing now" message, not an error, just X being jargonny.

The ubuntuone video you linked to just says "Could not locate object". Would be better to just attach it to the bug report.

If X was crashing there would be a stacktrace shown in the Xorg.0.log; if the GPU locked up it would show in dmesg. Not seeing any indication of either in the logs.

There are other reasons why X can terminate, such as if your system runs out of memory and the kernel kills it. Particularly since this happens on resume I would probably look closer at kernel failures. E.g. check your /var/log/kern.log or /var/log/syslog at the time of the failure to see if it gives a relevant error message.

Revision history for this message
Bryce Harrington (bryce) wrote :

Could you attach your /var/log/kern.log and /var/log/syslog after a crash? I can take a deeper look for you.

Bryce Harrington (bryce)
Changed in xorg (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Tomás Cohen Arazi (tomascohen) wrote :

It happens really often to me, and I see:

compiz[2686]: segfault at 10 ip 00007f1d60b08a23 sp 00007fff50cfa560 error 4 in libgdk-3.so.0.200.0[7f1d60acb000+77000]

in kern.log

Jan 17 19:55:58 luna gnome-session[2603]: Gdk-WARNING: The program 'gnome-session' received an X Window System error.#012This probably reflects a bug in the program.#012The error was 'XI_BadDevice (invalid Device parameter)'.#012 (Details: serial 529 error_code 149 request_code 141 minor_code 48)#012 (Note to programmers: normally, X errors are reported asynchronously;#012 that is, you will receive the error a while after causing it.#012 To debug your program, run it with the --sync command line#012 option to change this behavior. You can then get a meaningful#012 backtrace from your debugger if you break on the gdk_x_error() function.)#012
Jan 17 19:55:58 luna kernel: [49057.361005] compiz[2686]: segfault at 10 ip 00007f1d60b08a23 sp 00007fff50cfa560 error 4 in libgdk-3.so.0.200.0[7f1d60acb000+77000]

in syslog

Revision history for this message
Sebastien Bacher (seb128) wrote :

The XI_BadDevice error from comment #10 should be fixed in precise with the current gtk version

Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

With fresh versions of GTK, X and Compiz / Unity in Precise, this bug might get fixed, can someone confirm that?

Bryce Harrington (bryce)
Changed in xorg (Ubuntu):
status: Incomplete → Opinion
status: Opinion → New
status: New → Incomplete
status: Incomplete → Confirmed
Revision history for this message
Steve Magoun (smagoun) wrote :

I tried this (once) with 12.04 alpha 2 and could not reproduce the problem.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Omer Akram (om26er) wrote :

closed the issue as its not an issue in Precise. Thanks

Changed in unity:
status: New → Invalid
Changed in unity (Ubuntu):
status: Confirmed → Invalid
Changed in xorg (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.