I have no idea if this will actually be at all helpful, but I can tell you that it removed the "clocksource tsc unstable" lines from dmesg for me.
1) First, I checked the output of: cat /sys/devices/system/clocksource/clocksource0/available_clocksource to see which clocksources I had available on my system. (Some people will have hpet, some will have acpi_pm, some will perhaps have neither.) I had hpet, so I used that in the next step. 2) As others have suggested, I added the clocksource=hpet option (those who have acpi_pm but not hpet may try acpi_pm here; YMMV) to my kernel boot line in GRUB. I'm not sure whether this helped anything; in my case, dmesg still contained "clocksource tsc unstable" lines, so I wasn't satisfied. 3) I then saw the suggestion (here: http://fixunix.com/kernel/351423-re- clocksource-tsc-always-unstable-2-6-25-kernels-config_no_hz-y-my- box.html) that adding the nohz=off option to the kernel boot line might fix the issue. The kernel's default tickless mode can apparently (see here: http://fedoraproject.org/wiki/Common_kernel_problems) sometimes mess with the kernel's timekeeping abilities. The nohz=off option in the kernel boot line turns tickless mode off. The last step makes it so that dmesg no longer outputs "clocksource tsc unstable lines" for me. I'll let you all know if this stops the system freezes, but it'll be hard to tell since they're so seemingly random. Anyone else who wants to try using this kernel boot option is welcome. :) -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
