Clocksource tsc unstable leads to lockups

Thakn you for your report.

Can you perform a memory test?

Jon

Thank you for your report. Can you perform a memory test, and post back the results?

https://help.ubuntu.com/community/MemoryTest

Thank you again,

Jon

left a memtest running for a couple of hours, it did 3 passes with no errors

see picture:

I had the same problem. It appear after update from 2.6.28-6 on 2.6.28-8 kernel and upper.
Firstly I've think it's video driver related but with 2.6.28-6 kernel, on the same driver it's work very stable.
I find in kernel.log this lines:

kernel: [ 21.198429] Marking TSC unstable due to cpufreq changes
kernel: [ 23.588616] agpgart-nvidia 0000:00:00.0: AGP 3.0 bridge
kernel: [ 23.588633] agpgart-nvidia 0000:00:00.0: putting AGP V3 device into 8x mode
kernel: [ 23.588689] nvidia 0000:02:00.0: putting AGP V3 device into 8x mode
kernel: [ 31.732343] Clocksource tsc unstable (delta = -63230109 ns)

After adding notsc clocksource=acpi_pm to grub kernel boot parameters. It stop freezing.

Hope it's help somehow.

Pit.

CPU: AMD Sempron 2500+
Memory: 1Gb
MB: Asus A7N8 on nforce2
Video: Gigabyte GeForce 6200

And yes, before anyone asks, this is causing data loss, most likely cause the ext4 issues, but still.

i tried adding 'clocksource=acpi_pm' to the kernel boot parameters, and my computer still freezes.

Try also 'notsc' .

I can confirm this happens on 2 different PCs with Nvidia cards.

One is a Core 2 Duo with a 8600GT and the other is an Athlon 64 with an 6600LE.

The common factor is they both run amd64 Jaunty, all packages up-to-date.

I can confirm this, Jaunty 64bit, driver version 185.19-0ubuntu0 (not official, I know). My card is a GeForce 8400M GS, CPU is Core Duo; everything else is up-to-date.

Same problem on 32bit jaunty with a VGA compatible controller: nVidia Corporation G71 [GeForce 7300 GS] (rev 06) card.

Scrolling up and down the page quickly makes the screen blank temporarily, and eventually results in hard freeze and reboot and on odd occasions gnome will die and return me to the gdm login screen so a few problems probably all related to this bug though.

is there nothing we can do? i cannot leave my computer running jaunty for more then a day without coming back to see a frozen screen and my mouse/keyboard not responding. Each time it crashes there is nothing in any of the error logs, is there some way to turn debugging on so i can help get this bug fixed? I do not want to be stuck using intrepid when jaunty is better in most every way just because of some stupid kernel bug

Same problem here, jaunty amd64 with an nvidia card.

ditto. jaunty amd64 with an nvidia card. I have seen two different types of lock up. the first two times it locked up followed the same description as that mentioned above. Today, my display blacked out and all control was lost.

I can confirm this on Nvidiacard and ATI.

We can rule out this is because errors in hardware. Intrepid works fine on same hardware.

Other things it looks like we can rule out is brand of videocard and sort of filesystem, people are having freezes regardless of this.

This is the thread in the forums about this issue:
http://ubuntuforums.org/showthread.php?t=1135055

Same problem with this card:

01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]

x86 / EXT4

Rest of lspci
00:00.0 Host bridge: ATI Technologies Inc Device 5a31 (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:12.0 IDE interface: ATI Technologies Inc IXP SB400 Serial ATA Controller (rev 80)
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 82)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
03:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
03:06.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller
03:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
04:00.0 USB Controller: NEC Corporation USB (rev 43)
04:00.1 USB Controller: NEC Corporation USB (rev 43)
04:00.2 USB Controller: NEC Corporation USB 2.0 (rev 04)

The same here!!!
Random freezes for Ubuntu 9.04 64 bits. Sometimes after 23 hours on, sometimes in the boot. Sometimes selecting text on the web, sometimes watching a video... I can not find any regular behaivor.

I have been using Ubuntu since 6.10 and this is the first time something like this happens to me.

Mi logs don't show anything strange (syslog, messages, xorg.log, ...).
For example:

1rst freeze today (8:28 am):
May 1 07:40:01 borriquito /USR/SBIN/CRON[7110]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null)
May 1 08:28:05 borriquito syslogd 1.5.0#5ubuntu3: restart.

2nd freeze today (9:15 am):
May 1 09:15:59 borriquito pulseaudio[4648]: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.
May 1 09:24:59 borriquito syslogd 1.5.0#5ubuntu3: restart.

As you see, diferent messages without any relation. The same messages appear in logs sometimes without causing freezing.

My hardware: Asus P5Q3 / 4 GB DDR3 RAM / Intel E8400 / GeForce 7300 GS / 1 TB + 250 GB disk

Maybe a hardware incompatibility???

If you need more information, please ask!!

People who are experiencing this, please attach information such as /var/log/Xorg.0.log, dmesg and lspci -vvnn output.

I put my Xorg.0.log, dmesd and lspci.

Thank you.

David.

In the last freeze I saw this in message's log:

May 6 20:05:31 borriquito kernel: [ 3455.085169] npviewer.bin[7060]: segfault at ff9bea2c ip 00000000ff9bea2c sp 00000000ffe7fa4c error 14

Is the first time I see something strange!!!

Hope it helps.

David.

Same issue here.

I have an onboard nvidia 8300 (rev 2)

Running the latest official jaunty nvidia drivers in jockey-gtk.

Running the latest default 64-bit kernel in Jaunty as well: 2.6.28-11.

My mouse will lock up after around 20 minutes with the nvidia 180 drivers.
My mouse locks up after about only 2 minutes with the nvidia 173 drivers.
I am currently testing not using the nvidia drivers for now--will report on results.

I should note that Intrepid worked flawlessly on this pc with the latest nvidia drivers, which leads to suspect this is a kernel issue.

Also, the only thing that appears to lock up is my mouse. My keyboard and background apps such as Banshee still work fine after the mouse lockup.

This is a brand new pc I built myself a few months ago.

Okay, I've uninstalled the nvidia drivers and I have a new record uptime of 32 minutes so far and no lockups.

It seems the culprit might be the nvidia drivers after all.

I am about to install the 2.6.30 kernel to see if it works with the nvidia drivers.

Same issue. Jaunty, Ubuntu Studio amd_64, 2.6.28-3-rt, fresh install (using old /home directory), Nvidia 7300 gt, gigabyte ds3l mb, core 2 duo e2160, 4gb ram. Succesfully updated.

RULED OUT:
No issues with 7.10 and an upgrade to 8.04. This issue is regardless of the Nvidia drivers. It happens even if uninstalled completely. One of my several fresh installs was greeted with a freeze even prior to attempting to install graphics drivers. I couldn't get the latest 180.51 driver to install at all, nor were attempts succesfull to go back to the 173 driver via Ubuntu's restricted driver package (no x after changing to 173 driver). Disabling screensaver has no effect.

SUSPICIOUS:
Issue seems to me to be related to network activity. To attempt any relatively heavy net traffic seems 100% fatal. I'll note also that my initial attempt at the fresh install was buggy in that DHCP detection made several failed attempts at auto configuration. Subsequent reinstallations went without a hiccup, however.

I haven't figured out how to install the 2.6.30 kernel, so haven't tested. I'm planning to go back to my Jaunty install and disable my network connection and see if I can run stable while doing some real work. If I'm up for 4 or 5 hrs. I'd be pretty satisfied that it's something with the network activity. I'll also get the logs that I should have in the first place before coming to Windows to file this report (I did try in Jaunty, but several hard resets later... :)

brntoki , first off, what logs are you going to report? i have not found any mention of any problems pertaining to this hard locking issue in any of the logs, kern.logm messages, etc. If you do find something that might be related, share it so i can check my logs

also, yeah it might be network. My wireless router (an apple airport), likes to...reset itself or disconnect everyone in the house for a few minutes before it allows us to reconnect. One time that jaunty froze, i just got the notify-osd popup that my network had disconnected, and it was at that moment that my computer froze.

Same here with a amd x2-4800+ and geforce 7300LE
The machine used to work with ubuntu 8.10, and now lots of freeze/crash since upgrade to jaunty.
Tried all ubuntu nvidia drivers, then nvidia 180.51, still crashing.
Currently trying kernel 2.6.29-020629-generic with nvidia v185.18.08, if this doesn't work I'll have to revert to 8.10

Polygon,

As posted by Åskar: "People who are experiencing this, please attach information such as /var/log/Xorg.0.log, dmesg and lspci -vvnn output."

I can't make heads or tails of these logs myself. I've had my Jaunty on for close to 4 hrs with the networking disabled. I haven't been able to do much work, but the screensaver has been active the entire time. I'm going to go do some work on it in another 30. min or so. We'll see, but so far so good.

Also note: This has been with the Nvidia 180.44 driver. Again, I'm sure that it has nothing to do with the graphics drivers. It was freezing with or without.

SYMPTOM:

After some network activity via wlan0 I experience a total system freeze, mouse does not move. ALT+SysReq+R-E-I-S-U-B has no effect. Rebooting does not help, than I will experience the freeze again within minutes.

SHORT-TERM-RESOLUTION:

Boot into MS-Vista, reboot again to Jaunty. System will work again for 4-24hours.

SUSPICION:

I am not a developer, but is it possible that by booting to Vista some fancy registers of the hardware will be reset? As I can link the problems to WLAN activity, I think the freeze is connected to either general network activity or the WLAN driver.

I attached the output from lspci. I will also attach Xorg.0.log and dmesg.

Hope I can help,
Marc

I mark this one as confirmed instead of incomplete as the memorytest that was requested has been done, we also have people who posted their /var/log/Xorg.0.log, dmesg and lspci -vvnn outputs.

My computer ran most of the day without freezing after disabling the network connection. I re-enabled it in order to submit my logs and it froze up before I could get into this page. I'm sure it has to do with the networking somehow. Maybe a static IP would be my next test.

is everyone here using a wireless card that has an atheros chipset? (and therefore is using the ath5k driver)?

No, Dell Inspiron 1545 w/ Intel Wifi-Link 5100AGN ("iwlagn" driver).

No, I don't use wireless.

I don't use wireless.
The problems is not the wireless or the graphics. I think the problem is a hardware managing.
My new computer freeze with 9.04 64 bits and with 8.10 32 bits.
My hardware is:
- Asus P5Q3
- Chipset: P45
- RAM: DDR3 1333MHz
- CPU: Intel Pentium Dual Core 2 E8400
- Hard Disk: Seagate 1 TB
- Hard Disk: Seagate 250 GB
- Graphics: Geforce 7300 GS

David.

Same problem on my workstation.
I run Kunbutun from 6.04 to 9.4 and now it's freeze under 20min each time.
While I play kids game (supertux) or on internet with java/flash game too.

Hardware
AMD Athlon(tm) XP 3200+
Asus A7N8 on nforce2
GeForce 6600 GT

Software
Linux vonloschz 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
NVRM version: NVIDIA UNIX x86 Kernel Module 180.44 Mon Mar 23 14:59:10 PST 2009
GCC version: gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)

@Chem.Imbalance:

 Do you have this problem with a Toshiba laptop?

I'd like to report that after three days from upgrading to kernel 2.69.30 and nVidia Drivers 185.18.14 from the X-updates ppa, I have ceased to experience kernel panics.

@ alcCapone

No, its on a desktop I built. Asus mobo and nvidia onboard graphics.

On Thu, Jul 16, 2009 at 10:14 AM, mercutio22 <email address hidden> wrote:

> I'd like to report that after three days from upgrading to kernel
> 2.69.30 and nVidia Drivers 185.18.14 from the X-updates ppa, I have
> ceased to experience kernel panics.
>
> --
> Clocksource tsc unstable leads to lockups in Ubuntu Jaunty
> https://bugs.launchpad.net/bugs/355155
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: Triaged
>
> Bug description:
> Ever since i installed jaunty, randomly my computer would just freeze, and
> even a alt+f1 or a alt+sysrq+reisub would not do anything, so i assume its a
> kernel problem. This just happened right now, and i had to restart my
> computer, so i ran 'ubuntu-bug linux' the second i restarted. Maybe it will
> provide some insight to the problem?
>
> ProblemType: Bug
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> MachineType: System manufacturer P5Q-PRO
> NonfreeKernelModules: nvidia
> Package: linux-image-2.6.28-11-generic 2.6.28-11.40
> ProcCmdLine: root=UUID=d9574ed9-a697-45be-b773-ad8a81d79b6b ro quiet splash
> vga=792
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.28-11.40-generic
> SourcePackage: linux
>

My freezing has been solved.

Check my above post for details.

My freezing has been solved.

Check my above post for details.

Good luck all.

Disabling multicore support does not solve my problem. I've changed it yesterday and it worked w/o freeze. Today after wakeup from hibernation, I got a freeze while logging in.

@Chem.Imbalance: I'm happy for you but I don't see an IRQ conflict on my side
[code]>cat /proc/interrupts
           CPU0
  0: 630296 IO-APIC-edge timer
  1: 468 IO-APIC-edge i8042
  8: 1 IO-APIC-edge rtc0
  9: 1 IO-APIC-fasteoi acpi
 12: 2125 IO-APIC-edge i8042
 14: 4517 IO-APIC-edge ata_piix
 15: 0 IO-APIC-edge ata_piix
 16: 1238 IO-APIC-fasteoi nvidia
 17: 1294 IO-APIC-fasteoi nvidia
 18: 0 IO-APIC-fasteoi mmc0
 19: 2 IO-APIC-fasteoi ohci1394
 20: 20 IO-APIC-fasteoi ehci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb5
 21: 50303 IO-APIC-fasteoi uhci_hcd:usb4, uhci_hcd:usb6, HDA Intel
 22: 2 IO-APIC-fasteoi ehci_hcd:usb1, uhci_hcd:usb7
2296: 4 PCI-MSI-edge eth0
2297: 26213 PCI-MSI-edge iwlagn
2298: 81562 PCI-MSI-edge ahci
NMI: 0 Non-maskable interrupts
LOC: 330170 Local timer interrupts
RES: 0 Rescheduling interrupts
CAL: 0 Function call interrupts
TLB: 0 TLB shootdowns
SPU: 0 Spurious interrupts
ERR: 0
MIS: 0
>lsusb
Bus 002 Device 003: ID 05a9:2640 OmniVision Technologies, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046d:c251 Logitech, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub[/code]

I did not yet a kernel upgrade:
Linux clawfinger 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC 2009 x86_64 GNU/Linux

Btw. I never had freezes with 32bit version of Ubuntu Jaunty (used since alpha 4).

Today I was watching the processes with top on terminal. In the gnome session a terminal was open and I was recursively deleting a file structure. Suddenly I got:
iwlagn: Microcode SW error detexted. Restarting 0x2000000

and afterwards repeating errors:
BUG: soft lockup - CPU#0 stock for 61s! [gnome-power-man:3663]
BUG: soft lockup - CPU#1 stock for 61s! [rm:4180]g

No freezes for a week since I started booting with maxcpus=1, though that, naturally, isn't a solution, but only more of a "fix until this gets resolved".

Also, I'd like to share the info that the last time I had this sort of uptime, was during a period of a severely degraded internet connection. Some workers had damaged the outside cable, resulting in a severely unstable connection, but more interestingly, it made my adsl router connect at only 3Mbps, and during that period (10 days), I didn't have a single freeze. When the connections was restored to the usual 20/2, I had a freeze a couple of hours later. Longest uptime with full internet connection and without booting with maxcpus=1 is usually around 2½ days...

This probable causality with network might also explain why I have never been able to capture anything useful with netconsole, when the freezes happen...

@Fjodor: Are you connected by cable or wireless? Perhaps this does also matter, as I could see a "iwlagn: Microcode SW error detected. Restarting 0x2000000" while I had my last freeze. I would also wonder what this error message means.
Btw. my connection is only 5Mbps.

Hello together,

i wold like to renew my say:
ever since i changed to maxcpu=1 i work without freezes.
Yesterday i tried to start without it. 2 Minutes after my login i got a freeze.
So far, i will stay with maxcpus=1 until i have time to install another distribution (maybe Gentoo).
Since i bought 4cores to work with them, and at this moment i can't

:-((

Andreas

I have only one core (AMD Athlon 64 3200+) and I had several freezes (about 3 or 4 a day).
Since I disabled the frequency variation of my CPU ("Cool & Quiet" option of my mother bord (ASUS A8N-SLI Deluxe)), on the 26th of june, I had only 3 freezes.

While having these freezes, does anybody run simple backup? I did a new installation and I could work 2 days very well without any freeze (converting videos, looking movies, using transmission, ...). Today I've enabled again simple backup to do my backups in regular intervals. While running the initial backup, my system freezed up again. I've disabled simple backup again and so far no more freezes.

A side information: I do my backups on another hard disk and not over the network.

This is also happening to me in debian squeeze, and it MIGHT be in arch linux now (got a freeze, but im not sure if its consistant, might of been just a random freeze)

and so far most of the freezes occur under heavy load, such as ripping a dvd in handbrake for me.

I found a realy good solution for my Bug, so you may look if this helps you too.

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/353502

So i found out that for me installing the newest nvidia-driver solved a lot of my Problems
since then i do not have any freezes. I am working with all off my 4 cores now, i have enabled Compiz, I am able to show Videos.

Even my Sound-Driver does Work now relaiably. (ever once in a while it worked after a new boot, most time there was even no chip found)

In the last Month i did try these drivers several times, but without success. But now i tried them again because i read about it in bug 353502

So if you happen to have nvidia-graphics, try it out

Andreas Kielkopf

Hi,

since I read your above message, I am using the 185.18.14 NVIDIA driver (since the 28th of july) and the "Cool & Quiet" option of my mother board is enabled (frequency variation enable for my AMD Athlon 64 3200+) and I just have a freeze this morning.

Hi:

I have had the same or similar experience to most others in this bug report. My machine started freezing randomly a few weeks back after years of reliable service. I tried lots of things and eventually determined that it was a heat problem. The CPU fan was full of dust and the temps were pretty high. I blew out the dust and the temp went right down, but the random freezes remained. That machine was an Asus P5B Deluxe, Dual Core, 6GB RAM, NVidia 6600 on Jaunty. On close inspection, I could see the graphics riser was slightly warped and discoloured, so I assumed it had heated to the point that it had damaged the MB and that was what was causing the random freezes,
I got a new MB, CPU, RAM (Asus M3N, AM2, 4GB RAM, on-board NVidia 8200) and re-installed Jaunty. It worked fine for about 1 day and then the random freezes happened again. I tried all the suggestions on this and other posts such as installing the 185 driver, except the 2.6.30 kernel, but still it froze more and more.
I am now running 8.04 with very limited graphics. I can at least work, but would like to use jaunty if possible. I hope someone can find a cure for this ill. The conspiracy theorist in me suspects an M$ mole planted in the kernel team several years ago who has finally made their move :)

Paul

Based on various recommendations here and in other forums, I installed 9.04 again and installed the 2.6.29 kernel. The system ran with the 180 driver fine for about 2 hours, then froze again. That fix didn't therefore work for me. I might try it in combination with the 185 driver, but there are only so many hours I can work without a working computer.

I'm thinking that the network has something to do with this, I had freezes time to time, then, due to some issues with my ISP I lost internet for 11 days... where I had no freezes. Now that internet is back, I get the occasional freeze

Sound/flash now appear to be the killers for me. My machine has now been running overnight and through the morning and seems happy enough. I had a freeze yesterday with a scim-launcher segfault while I was listening to music and then clicked on a heavy flash site. That was the experience I had before, although I also had a few npviewer.bin segfaults which I assume are related. It has now been up 17 hours and I have been able to work for the early part of the day. However, I have not used any sound or looked at flash heavy sites, or indeed used Skype. Those things seem to accelerate the crash. I read in one of these posts that they cause rapid memory leaks. Throughout all of this I have had heavy network activity through updates and various downloads, so I'm not sure the network is the problem for me.

I upgraded my AMD K6-3 400 with 380Mb RAM from server 8.04 LTS to Jaunty, and had been experiencing the hangs about once a day, but then with increasing regularity, to the point at which it hung about 4 times in the space of a couple of hours.

Based on suggestions earlier in this thread, I added the boot parameters "noapic nolapic acpi=off" on Monday afternoon, and I've not had a problem since.

I tried "noapic nolapic acpi=off" and it does not work: my Jaunty still freeze.

Would anyone of you happen to know how to restrict the lowest C-state of the processor? I ran into a similar problem on freebsd, where the lapic uses ticks on c-states lower than C1, causing temporary or permanent hard-freezes. Setting the lowest c-state to C1 fixed the problem. Under freebsd you set a sysctl (hw.acpi.cpi.cx_lowest=C1).

I'm not sure how this is done on Linux, but if someone does, please try to set the lowest C-state to C1 and see if that helps.

Would anyone of you happen to know how to restrict the lowest C-state of the processor? I ran into a similar problem on freebsd, where the lapic loses ticks on c-states lower than C1, causing temporary or permanent hard-freezes. Setting the lowest c-state to C1 fixed the problem. Under freebsd you set a sysctl (hw.acpi.cpi.cx_lowest=C1).

I'm not sure how this is done on Linux, but if someone does, please try to set the lowest C-state to C1 and see if that helps.

This bug isn't getting attention because it's a hodgepodge of unrelated bugs and symptoms being reported by people.

Everybody who has a freezing problem, report a new bug (yes, really). Post the usual sets of logs to your own bugs, and don't jump to conclusions. This will result in the triagers being able to clearly see who has what symptoms, and allow the developers to focus their attention.

Polygon, could you report a fresh bug, reattaching the log files and pulling any useful details together there? I have some tests and directions for you to follow, but I'm not willing to start a wild goose chase on this report. :)

@Manoj Iyer, if you don't object, I'm going to mark this invalid and scatter everyone off to their own bug reports. There are too many people who've latched on to this report with issues that aren't obviously related. The lack of duplicate bugs (an action performed by triagers) combined with the trivially unrelated bug statements by others above is strong evidence of this.

@ Carey Underwood
This may have turned into a hodgepodge but, in my opinion as a non-techy, there is something fundamentally wrong for so many people to be having similar issues. I've had to turn off multiple cpu support to get 100% stability which is not a satisfactory solution. It may help if someone could suggest to all affected some form of test (or tests) which may be useful in trying to pin down what is causing the problem; a problem that only seems to have surfaced with Jaunty. My, and many others systems, were perfectly stable with Hardy and Intrepid.

As a matter of interest, the latest official kernel upgrade to 2.6.28-15-generic and nVidia 180.44 seems to have brought better stability. I can now use both cpu cores without the system freezing every 20 minutes although the occasional freeze still happens.

At KeithR and everybody else:

It really looks like this bug report is actually a multiple-cause, similar-symptom report, which leads to mixed comments. This makes it impossible for the devs to track all the possible causes, as those have to be pinpointed and fixed one by one. I am too for everybody opening their own bug report. Having multiple bugs mixed in the same report is useless for the developers. It is actually more useful to mark multiple bugs as duplicates of one another; this way, different causes would still be tracked separately.

For instance, my crash-like problem turned out to be an multiple-minutes freeze but my system eventually came back always. I solved it by using 2.6.29 from mainline. So far, I haven't seen any comments of somebody experiencing the exact same-cause symptom.

KeithR, that may be true, but it does absolutely nothing to help us
fix the issues. The _only_ thing we can do is to split out the bugs,
and fix them one at a time. Bug reports are not a forum for users to
help each other out, they are intended to help the developers keep
things organized so they can _fix_ them.

I don't know where is the new bug so I post here. I hope it will help:
Just before my computer freezed, it wrote those 2 lines in /var/log/messages:

Sep 18 18:29:48 hostname kernel: [ 136.088162] Marking TSC unstable due to cpufreq changes
Sep 18 18:29:48 hostname kernel: [ 136.588023] Clocksource tsc unstable (delta = -251978895 ns)

I have an AMD Athlon 64 3200+ on an ASUS A8N-SLI Deluxe Mother board and the "Cool and quiet" (which permit the frequency of the CPU change) is enabled.

> I don't know where is the new bug so I post here.

Pierre Lejeune, please file a new bug report by running "ubuntu-bug
linux" from a terminal, and following the prompts.

I'm sorry that I changed the status to "Confirmed" - I didn't think that I had such user rights. But, maybe it should stay so, because I can definitely confirm, that:

1) this issue does relate to the network activity, and only to the outgoing one;
2) it goes away compeletely with acpi=off, which in its turn may break something else (in my case, Asterisk server)
3) it still exists in Karmic, 2.6.31-14

I have similar issues but now that I have grub2 (damn damn) I cannot set the acpi and other options (in a easy way).
Someone pointed out the atheros wirelss chipset as possible problem and I can only partially confirm since I have one myself. The problem only shows up when I use Firefox, not using the wlan. Also, rebooting in winxp and then coming back to 6.10 (with default kernel - whatever version it is) makes the trick. Finally, I have disabled the cpufreq applet to no avail.

-I'll post my own bug :-D

from Pit.
"After adding notsc clocksource=acpi_pm to grub kernel boot parameters. It stop freezing."

This worked for me too.

996 $ cat /proc/cmdline
root=UUID=55e3a787-1620-4311-a5fe-14dc6237dfb6 ro quiet splash notsc clocksource=acpi_pm

I'm still getting freezes despite adding the above mentioned arguments to kernel command line. Most recently, it was 3 freezes in 2 days. That's really bad. Quite annoying; and needless to mention data loss!

reset status invalid per the description. If you are affected by a similar issue, please file a new bug.

Thanks!

~JFo