[ubuntu] Freeze in Jaunty

[TheHimself]

I have Ubuntu Netbook remix on a Lenovo laptop and experience frequent freezes. I'm using ext3. I've included the part of log file for one of the freezes. It includes the messages from when I woke up the computer until I forced it shut down. The freeze happened at 13:12. Can this reveal the source of the problem?

Oct 14 13:09:26 rez-laptop kernel: [ 6495.737452] PM: Syncing filesystems ... done.
Oct 14 13:09:27 rez-laptop kernel: [ 6495.755655] Freezing user space processes ... (elapsed 0.00 seconds) done.
Oct 14 13:09:27 rez-laptop kernel: [ 6495.757076] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
Oct 14 13:09:27 rez-laptop kernel: [ 6495.757268] Suspending console(s) (use no_console_suspend to debug)
Oct 14 13:09:27 rez-laptop kernel: [ 6495.757907] pci 0000:00:02.0: PCI INT A disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.345216] sd 2:0:0:0: [sda] Synchronizing SCSI cache
Oct 14 13:09:27 rez-laptop kernel: [ 6496.345505] sd 2:0:0:0: [sda] Stopping disk
Oct 14 13:09:27 rez-laptop kernel: [ 6496.896611] wl 0000:05:00.0: PCI INT A disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.912743] ata_piix 0000:00:1f.2: PCI INT B disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.928457] ata_piix 0000:00:1f.1: PCI INT B disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.928613] ehci_hcd 0000:00:1d.7: PCI INT A disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.944235] uhci_hcd 0000:00:1d.3: PCI INT D disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.944296] uhci_hcd 0000:00:1d.2: PCI INT C disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.944354] uhci_hcd 0000:00:1d.1: PCI INT B disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.944411] uhci_hcd 0000:00:1d.0: PCI INT A disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.960177] HDA Intel 0000:00:1b.0: PCI INT A disabled
Oct 14 13:09:27 rez-laptop kernel: [ 6496.976333] PM: suspend devices took 1.220 seconds
Oct 14 13:09:27 rez-laptop kernel: [ 6496.976393] ACPI: Preparing to enter system sleep state S3
Oct 14 13:09:27 rez-laptop kernel: [ 6497.011915] Disabling non-boot CPUs ...
Oct 14 13:09:27 rez-laptop kernel: [ 6497.116064] CPU 1 is now offline
Oct 14 13:09:27 rez-laptop kernel: [ 6497.116075] SMP alternatives: switching to UP code
Oct 14 13:09:27 rez-laptop kernel: [ 6497.438314] CPU1 is down
Oct 14 13:09:27 rez-laptop kernel: [ 6497.438419] Extended CMOS year: 2000
Oct 14 13:09:27 rez-laptop kernel: [ 6497.438419] Extended CMOS year: 2000
Oct 14 13:09:27 rez-laptop kernel: [ 6497.438419] Enabling non-boot CPUs ...
Oct 14 13:09:27 rez-laptop kernel: [ 6497.438419] SMP alternatives: switching to SMP code
Oct 14 13:09:27 rez-laptop kernel: [ 6497.756877] Booting processor 1 APIC 0x1 ip 0x6000
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] Initializing CPU#1
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] Calibrating delay using timer specific routine.. 3192.02 BogoMIPS (lpj=6384046)
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] CPU: L1 I cache: 32K, L1 D cache: 24K
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] CPU: L2 cache: 512K
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] CPU: Physical Processor ID: 0
Oct 14 13:09:27 rez-laptop kernel: [ 6497.437155] CPU: Processor Core ID: 0
Oct 14 13:09:27 rez-laptop kernel: [ 6497.844282] CPU1: Intel(R) Atom(TM) CPU N270 @ 1.60GHz stepping 02
Oct 14 13:09:27 rez-laptop kernel: [ 6497.857038] CPU1 is up
Oct 14 13:09:27 rez-laptop kernel: [ 6497.857043] ACPI: Waking up from system sleep state S3
Oct 14 13:09:27 rez-laptop kernel: [ 6498.172291] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
Oct 14 13:09:27 rez-laptop kernel: [ 6498.172819] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Oct 14 13:09:27 rez-laptop kernel: [ 6498.172891] usb usb2: root hub lost power or was reset
Oct 14 13:09:27 rez-laptop kernel: [ 6498.172916] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Oct 14 13:09:27 rez-laptop kernel: [ 6498.172984] usb usb3: root hub lost power or was reset
Oct 14 13:09:27 rez-laptop kernel: [ 6498.173008] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
Oct 14 13:09:27 rez-laptop kernel: [ 6498.173118] usb usb4: root hub lost power or was reset
Oct 14 13:09:27 rez-laptop kernel: [ 6498.173145] uhci_hcd 0000:00:1d.3: PCI INT D -> GSI 16 (level, low) -> IRQ 16
Oct 14 13:09:27 rez-laptop kernel: [ 6498.173213] usb usb5: root hub lost power or was reset
Oct 14 13:09:27 rez-laptop kernel: [ 6498.188161] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
Oct 14 13:09:27 rez-laptop kernel: [ 6498.188510] ata_piix 0000:00:1f.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Oct 14 13:09:27 rez-laptop kernel: [ 6498.204254] ata_piix 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
Oct 14 13:09:27 rez-laptop kernel: [ 6498.220611] wl 0000:05:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Oct 14 13:09:27 rez-laptop kernel: [ 6498.220838] sd 2:0:0:0: [sda] Starting disk
Oct 14 13:09:27 rez-laptop kernel: [ 6499.401067] ata3.00: configured for UDMA/133
Oct 14 13:09:27 rez-laptop kernel: [ 6499.421476] sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors: (160 GB/149 GiB)
Oct 14 13:09:27 rez-laptop kernel: [ 6499.421583] sd 2:0:0:0: [sda] Write Protect is off
Oct 14 13:09:27 rez-laptop kernel: [ 6499.421725] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 14 13:09:27 rez-laptop kernel: [ 6499.688187] usb 1-3: reset high speed USB device using ehci_hcd and address 2
Oct 14 13:09:27 rez-laptop kernel: [ 6500.076139] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Oct 14 13:09:27 rez-laptop kernel: [ 6500.232169] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 14 13:09:27 rez-laptop kernel: [ 6500.233534] PM: resume devices took 2.340 seconds
Oct 14 13:09:27 rez-laptop kernel: [ 6500.233603] Restarting tasks ... <6>synaptics was reset on resume, see synaptics_resume_reset if you have trouble on resume
Oct 14 13:09:27 rez-laptop kernel: [ 6500.398417] done.
Oct 14 13:09:27 rez-laptop kernel: [ 6500.941067] ACPI: EC: missing confirmations, switch off interrupt mode.
Oct 14 13:09:28 rez-laptop kernel: [ 6501.316842] ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 14 13:09:29 rez-laptop kernel: [ 6502.969836] tg3: eth0: Link is up at 100 Mbps, full duplex.
Oct 14 13:09:29 rez-laptop kernel: [ 6502.969846] tg3: eth0: Flow control is on for TX and on for RX.
Oct 14 13:09:29 rez-laptop kernel: [ 6502.978738] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Oct 14 13:13:50 rez-laptop kernel: [ 6763.292134] CE: hpet increasing min_delta_ns to 22500 nsec
Oct 14 13:14:16 rez-laptop kernel: [ 6789.538913] tg3: eth0: Link is down.
Oct 14 13:14:31 rez-laptop kernel: [ 6804.344625] usb 1-3: USB disconnect, address 2
Oct 14 13:14:40 rez-laptop kernel: [ 6813.300186] usb 1-3: new high speed USB device using ehci_hcd and address 4
Oct 14 13:14:40 rez-laptop kernel: [ 6813.615937] usb 1-3: configuration #1 chosen from 1 choice
Oct 14 13:14:40 rez-laptop kernel: [ 6813.617790] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (5986:0241)
Oct 14 13:14:40 rez-laptop kernel: [ 6813.619364] input: Lenovo EasyCamera as /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/input/input10
Oct 14 13:15:28 rez-laptop kernel: [ 6861.556754] tg3: eth0: Link is up at 100 Mbps, full duplex.
Oct 14 13:15:28 rez-laptop kernel: [ 6861.556767] tg3: eth0: Flow control is on for TX and on for RX.
Oct 14 13:21:08 rez-laptop syslogd 1.5.0#5ubuntu3: restart.

[Wazzag]

I have stumbled on a fix for my system freezing

When it freezes I plug a USB device in (bluetooth or just a drive) and presto! back to normal

I have been searching for a fix for this for a long while and have tried a few of the magic fixes to no avail, Jaunty still freezes randomly but at least now I can 'un-freeze' it without a re-boot

[pveurshout]

Originally Posted by Wazzag I have stumbled on a fix for my system freezing When it freezes I plug a USB device in (bluetooth or just a drive) and presto! back to normal I have been searching for a fix for this for a long while and have tried a few of the magic fixes to no avail, Jaunty still freezes randomly but at least now I can 'un-freeze' it without a re-boot

Extraordinary problems require uncommon solutions, I guess I'm gonna remember that one, thanks. My system hasn't frozen since I disabled hpet in the boot options, though, so I hope it won't be necessary.

[Wazzag]

Originally Posted by pveurshout Extraordinary problems require uncommon solutions, I guess I'm gonna remember that one, thanks.

Hehe
yeah it's extraordinary alright

I tried it out of pure frustration, no keyboard, no mouse, so I thought I'd just plug something in to see what happened
And it worked!!!!

I get a freeze on average about once a week I guess, I might go a couple of weeks then get frozen twice in a day (sometimes), sometimes it fixes itself if I just leave it alone for 5-10 minutes, other times it just stays frozen, I did leave it one evening, it was frozen for about four hours before I went to bed, the next day it was fine (fixed itself)

So my brain figured the thing just needed a poke, can't poke it with the keyboard, can't poke it with the mouse, what else is there.......USB!!!

And it worked!

I have frozen about six times since then, every time plugging something into USB has kicked it into gear

I know it's not a proper fix, but it has worked every time (so far)

[billharris]

Just an update: I've tried disabling hpet and switching to the 2.6.31 kernel on Jaunty, but I still get freezes multiple times a day. I tried the USB idea, and it did not help me. (I do sometimes see that I can provoke a seemingly frozen Jaunty by right-clicking on Firefox in the bottom panel, and that lets me do a little bit until it freezes again; the second time almost always requires a reboot. Perhaps the USB trick is in the same category.)

Has anyone got any multi-day experience with Karmic who has experienced the freezing problem with Jaunty? I grabbed a daily build of the beta last week, and it seemed to work okay as a Live CD, but I only ran it for a short while. I'm hopeful that the released Karmic will fix the freezes. If it doesn't, I'll probably switch back to Debian.

[Dougga]

I'm seeing the same thing.

Ubuntu 9.04 fully patched
Linux tc 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/

I get perpetual freezes which is driving me nuts. I'm too busy to spend too much time on this, I'll be moving off 9.04 to the 8.04 LTS and Win9 if that fails.

From my experience the freezes come from two different sources.
1. The Alt-Tab application switcher
2. Evolution

In the #1 case where I suspect Alt-Tab as the culprit, the UI locks up completely with no mouse movement. I can access the machine using ssh from another machine and force a reboot. Requesting a restart to GDM has no effect.

In case #2 which I suspect Evolution problem, the mouse appears to move across the screen but cannot interact with anything shown on the screen. I've had some success killing the evolution task from a terminal session - but only occasionally does this work.

I'll have to add that 9.04 is not ready for prime time (for professionals who value their time) and the suggestion of launching a new version suggests that these releases are essentially only betas and will not be much more unless something significant changes in the release or testing model. I have no real experience with LTS so I'll be looking to this next to evaluate. I may have a look at Suse as well. Their's is a business model that is based on enterprise productivity.

Thanks for everyones input.

~Doug

[Hated On Mostly]

Originally Posted by Dougga I'm seeing the same thing. Ubuntu 9.04 fully patched Linux tc 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/ I get perpetual freezes which is driving me nuts. I'm too busy to spend too much time on this, I'll be moving off 9.04 to the 8.04 LTS and Win9 if that fails. From my experience the freezes come from two different sources. 1. The Alt-Tab application switcher 2. Evolution In the #1 case where I suspect Alt-Tab as the culprit, the UI locks up completely with no mouse movement. I can access the machine using ssh from another machine and force a reboot. Requesting a restart to GDM has no effect. In case #2 which I suspect Evolution problem, the mouse appears to move across the screen but cannot interact with anything shown on the screen. I've had some success killing the evolution task from a terminal session - but only occasionally does this work. I'll have to add that 9.04 is not ready for prime time (for professionals who value their time) and the suggestion of launching a new version suggests that these releases are essentially only betas and will not be much more unless something significant changes in the release or testing model. I have no real experience with LTS so I'll be looking to this next to evaluate. I may have a look at Suse as well. Their's is a business model that is based on enterprise productivity. Thanks for everyones input. ~Doug

openSUSE is a good choice. I tested both of them out very recently as well as Fedora due to Jaunty's instability. They don't exhibit the same problems that Ubuntu does and are much more stable. Their alpha, beta, and release candidates are much more stable than Ubuntu's as well.

The next version of openSUSE (11.2) will be released November 12, 2009. The next version of Fedora (12) will be released November 17, 2009. I would go with openSUSE over Fedora as it is easier to use.

Ubuntu has very unique bugs that other Linux distributions don't have. I am going to give the official Karmic Koala a try, but if I have problems I am switching permanently. I want a stable machine, not a machine that I am constantly looking up how to workaround bugs for it.

[Dougga]

Excellent post. thanks

I believe I'll follow the identical path to system and emotional stability. I'm looking forward to the extra time in my days.

Looking into this specific bug I found evidence that it existed when Jaunty was originally launched back in '07.

Here is an excerpt from the release notes under "known Issues" [one of my favorite terms in systems parlance].

[QUOTE]
Display freezes with Intel graphics cards

Users of various Intel video chipsets reported freezes under various conditions (e. g. a few minutes after suspend on the i945, see 339091). In many cases, switching off desktop effects in System → Preferences → Appearance was reported to help.

If it still happens without desktop effects, you can add Option "DRI" "off" to the Device section of /etc/X11/xorg.conf, as described above. This will disable 3D acceleration and desktop effects, but makes suspend work reliably again and also avoid many types of crashes.

These freezes happen particularly often on the i965 chips (359392). For that reason, desktop effects were disabled by default on this chipset in the final release. They will be re-enabled in a 9.04 Update once the problem has been fixed.
[QUOTE]

More hints to things I can disable or remove to get my machines to work as designed.

Here are the details of my graphics subsystems:

00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. Device 8295
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0
Capabilities: [e0] Vendor Specific Information <?>
Kernel driver in use: agpgart-intel
Kernel modules: intel-agp

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 8276
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 2299
Region 0: Memory at fdd00000 (32-bit, non-prefetchable) [size=1M]
Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at cc00 [size=8]
Capabilities: [90] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable+
Address: fee0300c Data: 41a1
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
Subsystem: ASUSTeK Computer Inc. Device 8276
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at fde00000 (32-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[Hated On Mostly]

Originally Posted by Dougga Excellent post. thanks I believe I'll follow the identical path to system and emotional stability. I'm looking forward to the extra time in my days. Looking into this specific bug I found evidence that it existed when Jaunty was originally launched back in '07.

There is nothing wrong with wanting a stable system that you don't have to fight with even if you are more than capable of doing so. I use my computer to get work done and have fun, not to fix problems with the system itself. Not to mention, most of these critical bugs on Ubuntu have no workarounds as this thread demonstrates!

[MKe2]

I must say 8.04 is rock-stable. Since I installed it I haven't had anything remotely to a crash.