-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Thursday 2007-12-06 at 14:43 -0000, Neil Dawkins wrote:

Carlos,

I had a similar problem on one of my 10.3 servers.

I had to reset /sys/devices/system/clocksource/clocksource0/current_clocksource (in this case to jiffies).

To list available sources:

cat /sys/devices/system/clocksource/clocksource0/available_clocksource

I have seen that.

nimrodel:~ # cat 
/sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm pit jiffies tsc

nimrodel:~ # cat 
/sys/devices/system/clocksource/clocksource0/current_clocksource
acpi_pm

I didn't know I could change the clock. How, writing the desired one to the "current..." file?


Do you know of a link or file with documentation on each type of clock?



Before 10.3 I have not experienced this issue.

Same here... the problems started with 10.3. At least visible problems, any "time reset" message is bad.


I'll try brute force...

nimrodel:~ # echo tsc > 
/sys/devices/system/clocksource/clocksource0/current_clocksource
nimrodel:~ # cat 
/sys/devices/system/clocksource/clocksource0/current_clocksource
tsc


I'm not sure... I just updated the kernel tonight, and 45' after boot I see:

Dec  6 22:14:08 nimrodel kernel: Clocksource tsc unstable (delta = 65620380907 
ns)
Dec  6 22:51:06 nimrodel kernel: set_rtc_mmss: can't update from 0 to 51
Dec  6 22:51:09 nimrodel syslog-ng[3946]: last message repeated 2 times
Dec  6 22:51:09 nimrodel kernel: set_rtc_mmss: can't update from 1 to 51
Dec  6 22:51:35 nimrodel syslog-ng[3946]: last message repeated 22 times
Dec  6 22:51:36 nimrodel kernel: set_rtc_mmss: can't update from 1 to 51


Lots of those messages till 23:09:54, then they stopped. Maybe the 'tsc' clock is bad and it switches to 'acpi_pm'. Perhaps I'll have to try them all.


- -- Cheers,
       Carlos E. R.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFHWJx5tTMYHG2NR9URAs+NAKCYXeF3pc3xfpVwsFBLBoTooVvA/wCeOb7Q
w6+xIxtg70nensXuPARXyFc=
=TilF
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to