hardware clock = 6:53 pm software clock = 11:01 pm .... hardware clock is correct but the software is already 4 hours fast after a day it gets days ahead
using cpu freq but have no driver loaded for changing the cpu speed so currently uses default speed all the time at 2.5ghz On Wednesday 14 December 2005 11:01 pm, William Kenworthy wrote: > Things to check: > are you using speedfreq or cpufreq? - if the kernel timing sets itself > when throtting is in effect, it may not be right when running fast > > batterystat applets can cause problems with blocking in /proc - this > usually causes a loss in time, and I have not seen it with recent > kernels. > > BillK > > On Wed, 2005-12-14 at 11:30 +0000, Noah J Norris wrote: > > my hardware clock stays correct but the software clock is like going 20x > > fast im on a laptop and using noapic the problem goes away but leads to > > other problems like network problems happing like errors with internal > > ethernet card and ndiswrapper stops working . the processer is amd64 > > running as x86 (32bit mode) i get apic errors and lost tick errors . if > > i leave this on for a couple hours it becomes days ahead can anyone shead > > some light on this ? kernel being used is 2.6.14-r2 i believe > > > > > > thanks > > > > 'hwclock --hctosys' works to set the time back to what the hardware clock > > says > > > > -- > > life is linux > > linux is life > > -- > William Kenworthy <[EMAIL PROTECTED]> > Home! -- life is linux linux is life -- gentoo-user@gentoo.org mailing list