[OpenAFS-devel] linux 2.6.11.4 and bogus 'setting clock back'

[Troy Benjegerdes]

What could be causing this?

afs: setting clock back 10 seconds (of 1111023402, via 147.155.137.11 in
cell scl.ameslab.gov); clock is still fast.
afs: setting clock back 10 seconds (of 1111023423, via 147.155.137.11 in
cell scl.ameslab.gov); clock is still fast.
Losing some ticks... checking if CPU frequency changed.
afs: setting clock back 10 seconds (of 1111023423, via 147.155.137.11 in
cell scl.ameslab.gov); clock is still fast.
afs: setting clock back 10 seconds (of 1111023503, via 147.155.137.11 in
cell scl.ameslab.gov); clock is still fast.
afs: setting clock back 10 seconds (of 1111023833, via 147.155.137.11 in
cell scl.ameslab.gov); clock is still fast.
afs: file server 147.155.137.11 in cell scl.ameslab.gov is back up
(multi-homedaddress; other same-host interfaces may still be down)
afs: file server 147.155.137.11 in cell scl.ameslab.gov is back up
(multi-homedaddress; other same-host interfaces may still be down)
afs: setting clock ahead 53 seconds (via 147.155.137.11 in cell
scl.ameslab.gov).
afs: setting clock ahead 53 seconds (via 147.155.137.11 in cell
scl.ameslab.gov).


The clock was maybe 30 seconds off, but that 1111023503 number looks
overly large. Eventually, it figures out what the right time its. What I
don't understand is why it's perfectly happing with one server
(147.155.137.10), but not the other.

This was immediately after booting a 2.6.11.4 kernel and loading the afs
module.

The machine is a dual opteron, booted via network, with nfs-root
filesystem, so I started afsd manually with 'afsd -memcache'