Hi Andi, Providing that a) me switching from the forcedeth to the nvnet NIC module didn't somehow fix this, and b)clock=pmtmr does nothing on my system, then yes, nostc has fixed the problem. Oh, I could try removing noapic from the boot command and see if that has any influence. Will do that now. Can't switch back to forcedeth since it was causing me so many problems and I need to work :( Cheers, Jon Andi Kleen wrote:
On Friday 28 October 2005 11:45, Jonathan Brooks wrote:
Hi Andi,
Just that - nothing else. Machine is now keeping perfect time, and there are now no messages about lost ticks (at least not for the last 12 hours).
Ok so it is safe to say that notsc helped in your case? Or did you change other things too?
Last thing when I look at the output of dmesg I get the following (see 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.
-Andi
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon