Periodic lockups or crashes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
I've been using 12.04 beta since beta 1 and this problem has existed.
Essentially what happens is (normally) I'll be scrolling through a webpage and one of 3 things will happen. Either my current session exits, locks up entirely, or just locks up the UI allowing the mouse to still move. This happens on any desktop environment, whether it is Ubuntu 2D, Gnome classic, Gnome shell, Ubuntu unity, etc. It seems worse with gnome shell, where it almost always completely locks up. It seems most stable under gnome classic.
Last time it locked up I sshed into the machine to see if I could figure out what happened. Xorg was at 100% CPU and not responding besides the mouse. Video playback froze, UI non responsive.
This seems to be an architecture related problem and others seem to be having the same problem. See http://
I've been checking dmesg and syslogs to see if I could figure out what might be causing the lockups/crashes. dmesg returned a few bits of information that may be helpful
init: lightdm main process (1536) terminated with status 1
eclipse[4532]: segfault at 18 ip 00007f558e70d30e sp 00007fffd0fcb8f0 error in libgdk-
init: failsafe-x main process (6661) terminated with status 1
I had killed the main xorg process, causing the last messaged in dmesg.
Hopefully this will be helpful for someone.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: None
Date: Sun Apr 8 02:01:52 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingI
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120325)
MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: Fh3
dmi.board.name: X58A-UD3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: X58A-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.ia32-libs: ia32-libs 20090808ubuntu35
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
version.
tags: | added: regression |
Changed in xorg (Ubuntu): | |
importance: | Undecided → High |
Hi Matthew,
Dang, that sounds really annoying.
I've reviewed the log files you attached, but none show indications of server crashes or GPU freezes, that would indicate an X.org bug.
Thanks for the link to UF but we don't review forum discussions due to time constraints; if there's anything pertinent from those threads please re-summarize here for is.
The lightdm termination message is normal. lightdm terminates when it hands control over to the user session.
The failsafe-x termination likewise is probably innocuous.
The eclipse segfault in libgdk-x11 looks interesting; I don't know what that is. If that is always present when you see this bug, it may be a very strong clue.
In general, high Xorg CPU is usually caused not by X but by a client program or service, that is out of control and simply making too many X requests (X does not throttle clients).
You've ruled out display managers, which is a good start. When you booted into Gnome classic, was that with or without effects? If it was with effects, try without, as that will rule out compiz as the culprit.
Try booting into a guest session; that will help indicate if the problem is something in your user settings.
Try booting a beta1 or beta2 liveUSB image. If the problem reproduces on that, then that rules out something you've installed. If it doesn't reproduce, check if you've installed any services or secondary tools that could be causing it.
The typical procedure for debugging high X cpu issues is to ssh into the sick machine and start killing processes. Given the eclipse crash in libgdk-x11, I'd look for any remaining eclipse processes or anything related to gdk-x11; this could include gnome services for instance. The program 'xrestop' might give some ideas for other apps to try killing (it reports resource memory usage, not processor usage, so your perpetrator may not necessarily show up there at all.)