Re: 2.6.10 and time drift
Valdis.Kletnieks_at_vt.edu
Date: 12/27/04
- Previous message: Srinivas Naga Vutukuri: "hi all"
- In reply to: Alexander Prokoshev: "2.6.10 and time drift"
- Next in thread: Gene Heskett: "Re: 2.6.10 and time drift"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Alexander Prokoshev <ap@insysnet.ru> Date: Mon, 27 Dec 2004 06:59:37 -0500
On Mon, 27 Dec 2004 14:28:25 +0300, Alexander Prokoshev said:
> after installation of 2.6.10 kernel I've noticed time drift, which
> (according to ntpdc's dmpeer command) is about 10-15 seconds per hour.
> Downgrade to 2.6.9 solves this problem. I can send any additional
> information which may be helpful.
For starters, the output of 'uname -a', the architecture/hardware you're
running on, and if your dmesg has any hints about which time source it's
using. On my Dell laptop, I see:
Dec 26 19:11:22 turing-police kernel: PID hash table entries: 1024 (order: 10, 16384 bytes)
Dec 26 19:11:22 turing-police kernel: Detected 1595.344 MHz processor.
Dec 26 19:11:22 turing-police kernel: Using pmtmr for high-res timesource
Dec 26 19:11:22 turing-police kernel: Console: colour dummy device 80x25
Dec 26 19:11:22 turing-police kernel: Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Dec 26 19:11:22 turing-police kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Most x86 systems should have a similar note of the timesource right
around that point of the dmesg.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- application/pgp-signature attachment: stored
- Previous message: Srinivas Naga Vutukuri: "hi all"
- In reply to: Alexander Prokoshev: "2.6.10 and time drift"
- Next in thread: Gene Heskett: "Re: 2.6.10 and time drift"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|