| 1 |
Things to check: |
| 2 |
are you using speedfreq or cpufreq? - if the kernel timing sets itself |
| 3 |
when throtting is in effect, it may not be right when running fast |
| 4 |
|
| 5 |
batterystat applets can cause problems with blocking in /proc - this |
| 6 |
usually causes a loss in time, and I have not seen it with recent |
| 7 |
kernels. |
| 8 |
|
| 9 |
BillK |
| 10 |
|
| 11 |
On Wed, 2005-12-14 at 11:30 +0000, Noah J Norris wrote: |
| 12 |
> my hardware clock stays correct but the software clock is like going 20x fast |
| 13 |
> im on a laptop and using noapic the problem goes away but leads to other |
| 14 |
> problems like network problems happing like errors with internal ethernet |
| 15 |
> card and ndiswrapper stops working . the processer is amd64 running as x86 |
| 16 |
> (32bit mode) i get apic errors and lost tick errors . if i leave this on |
| 17 |
> for a couple hours it becomes days ahead can anyone shead some light on |
| 18 |
> this ? kernel being used is 2.6.14-r2 i believe |
| 19 |
> |
| 20 |
> |
| 21 |
> thanks |
| 22 |
> |
| 23 |
> 'hwclock --hctosys' works to set the time back to what the hardware clock says |
| 24 |
> |
| 25 |
> -- |
| 26 |
> life is linux |
| 27 |
> linux is life |
| 28 |
-- |
| 29 |
William Kenworthy <billk@×××××××××.au> |
| 30 |
Home! |
| 31 |
-- |
| 32 |
gentoo-user@g.o mailing list |
Archives