I read another similar bug and there some guys got it fixed like that: into /boot/grub/menu.lst on kernel line they added "clocksource=tsc". I tried that too, system was super slow on boot. So the other line was "clocksource=hpet". I am now running with that hpet line, had wireless activity, switched wireless off and did some tests. Almost 24 hours without crash. So far so good.
grep -i tsc /var/log/messages shows nothing grep -i hpet /var/log/messages shows nothing PS. Frequency scaling also is working. -- 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
