Ubuntu
linux package

System locks up (and often restarts) on (and since upgrade to) Maverick

Bug #660982 reported by messi
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This did not happen with 10.04 (Lucid), upto latest provided kernel version, only since upgrade to 10.10 (Maverick), from RC to current.
Most often, this happens when starting synaptic right after boot/login (I could reproduce it several times trying to remove VirtualBox), but will inevitably happen after a few hours uptime. Couldn't (yet) reproduce on a text console (using aptitude).
Before the system freezes, it will typically exhibit slow response to mouse and keyboard events for a few seconds (up to minutes), eventually the mouse cursor will grind to a halt, no flashing caps; often the system will auto-restart after a few seconds of lockup (so couldn't validate if I can still reach it via network).
I tried with the "current" mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ (linux-headers-2.6.36-999 maverick), seems to happen not as often with it and the "slowness before restart" doesn't happen, the system suddenly restarts, so the problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.34
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bm 1814 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfbff4000 irq 50'
   Mixer name : 'Realtek ALC889A'
   Components : 'HDA:10ec0885,1458a002,00100101'
   Controls : 38
   Simple ctrls : 21
CurrentDmesg:
 [ 26.070214] eth0: no IPv6 routers present
 [ 29.672904] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Date: Fri Oct 15 07:33:40 2010
Frequency: Once a day.
HibernationDevice: RESUME=UUID=14d5aeb0-9fb1-4ca5-850d-6190cdcd9ddd
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. EX58-UD4P
ProcCmdLine: root=UUID=de4f347f-0adf-461c-8a9e-bb093c4039f4 ro quiet splash
ProcEnviron:
 LANGUAGE=de_AT:de
 LANG=de_AT.utf8
 SHELL=/bin/zsh
RelatedPackageVersions: linux-firmware 1.38
RfKill:

SourcePackage: linux
WpaSupplicantLog:

dmi.bios.date: 03/31/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F7
dmi.board.name: EX58-UD4P
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:bvnAwardSoftwareInternational,Inc.:bvrF7:bd03/31/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX58-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX58-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: EX58-UD4P
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
messi (bmesserer) wrote :
Revision history for this message
messi (bmesserer) wrote :

Regarding frequency: This happens multiple times a day, more or less every few hours, sometimes only minutes

Revision history for this message
Headless Platter (headlessplatter) wrote :

I am also experiencing periodic hard lock-ups after upgrading from Lucid to Maverick. There is no response to any mouse or key combinations. It occurs after about 4-10 hours. I have not seen it auto-restart--it's always a hard lock-up for me. Once, the hdd light was permanently on, but usually it is off. It seems to occur less frequently if I log out and leave it on the login screen, but it occurred once while sitting on the login screen. It occurs even if I am not using the machine (although I am running Apache and some other daemons). I will attach my "lshw" hardware profile.

Revision history for this message
messi (bmesserer) wrote :

Can I do something to help diagnosing this bug? Because in its current state, the PC is completely unusable - when doing "real work" it crashes more or less every few minutes, I never reach an hour uptime.

Revision history for this message
Headless Platter (headlessplatter) wrote :

Hmm, it sounds like mine is a different issue. My machine is usable for a few hours at a time. I just have to reboot two or three times per day. I checked, and mine is definitely not reachable via network when it's locked up. So, I suppose I need to go open another bug for myself.

Revision history for this message
messi (bmesserer) wrote :

I retested with a 2.6.32 kernel - although the remaining one from lucid (2.6.32-25) was in the boot menu, I couldn't boot it because it was missing linux-kernel-headers, so I couldn't build the nvidia module.
So I installed one from the mainline repository, 2.6.32-0206322411 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.24-lucid/ uploaded 2010-10-02.
As soon as I use this one, the system is completely stable again, the crash doesn't happen.

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
messi (bmesserer) wrote :

Seems ro be resolved with 2.6.37+ kernel
Installed 2.6.37-02063702.201102250905 from mainline builds (https://wiki.ubuntu.com/Kernel/MainlineBuilds) and tested for a few weeks - no more freezes experienced. Since I expected to no more need a 2.6.32 kernel then, I dared to upgrade to Ubuntu 11.04 with 2.6.38, freezes seem to be gone too (crossing fingers).
As far as I'm concerned, this bug can be closed.

kind regards,

Messi

Revision history for this message
penalvch (penalvch) wrote :

messi, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.