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 :)
Langsdorf, Mark wrote:
Last thing when I look at the output of dmesg I get the
below), I am slightly worried, since I have read somewhere that the kernel needs to be patched to include a more recent version of powernow-k8. Is this error expected, or should I patch?
Known problem, but harmless. Just ignore for now. Some future update kernel will likely fix it.
I can submit a patch, but I'm not sure what to do.
The code loops through NR_CPUS and ignores the ones that are not online: if (!cpu_online(i)) continue;
This code used to work, but the hotplug changes broke it. What's the correct code now to check if a cpu isn't available?
-Mark Langsdorf AMD, Inc.