Am Mo 31.10.2005 11:27 schrieb Jonathan Brooks <jonathan.brooks@human-anatomy.oxford.ac.uk>:
Hi Andi, Mark,
Can confirm that if I remove the nostc argument to the boot command, I do start to see the following in the output from dmesg:
warning: many lost ticks. Your time source seems to be instable or some driver is hogging interupts rip acpi_processor_idle+0x12f/0x37f [processor]
So as you suspected the only thing that seems to make a difference is nostc. Though I wonder if the error message is use dependent, I left the machine running over the weekend, and didn't gain too much time on the clock, and only had the one warning with dmesg. Still wish I knew what on earth was going on :)
You actually used notsc, not nostc, right? Just double checking because you consistently misspelled it. -Andi