On Thursday 24 November 2005 17:01, Bernd Paysan wrote:
I have to set clock=pmtmr to get a sufficiently stable clock for ntp on four of the seven boards, but that may be due to having dual-core Athlons in them (TSC and clock stepping conflicts?).
To be a bit more precise: All of them have dual-cores inside, but three had an acceptable drift with default PIT/TSC timing (less than 500ppm). One even has comparable accuracy to the pmtmr ones. They all sync to a single local ntp stratum 2 server, which has a HPET based timing (a dual-opteron server). That's the only board I've ever seen in years where I can't use PIT/TSC (on four out of seven!). There are several other Linux PCs in the office, and two at home, and all work fine with PIT/TSC, except the dual-Opteron system (running SuSE 9.3), which needs the HPET timer, since the TSC based timekeeping doesn't work with different CPUs having different speeds. -- Bernd Paysan "If you want it done right, you have to do it yourself" http://www.jwdt.com/~paysan/