Re: NTP problem - Clock too fast for NTP to keep up?
From: James Wilkinson (james_at_westexe.demon.co.uk)
Date: 02/09/05
- Previous message: Markku Kolkka: "Re: updatedb"
- In reply to: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Next in thread: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Reply: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Reply: John DeDourek: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 9 Feb 2005 00:23:27 +0000 To: For users of Fedora Core releases <fedora-list@redhat.com>
jdow wrote:
> Also try booting with "noapic" and "nolapic" options. (I'd LOVE to
> know why the APIC screws up the ntp operations.)
I'm sure the kernel developers would, too.
But it's not that improbable, if you think about it.
The kernel measures the passage of time by counting timer ticks. A timer
works by sending interrupts to the CPU (which are received by the
kernel) every so often. And a Programmable Interrupt Controller (such as
the Advanced PIC, or APIC) is responsible for marshalling those
interrupts and sending them on.
James.
-- James Wilkinson | The camel has a single hump; Exeter Devon UK | The dromedary two; E-mail address: james | Or else the other way around. @westexe.demon.co.uk | I'm never sure. Are you? -- Ogden Nash -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
- Previous message: Markku Kolkka: "Re: updatedb"
- In reply to: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Next in thread: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Reply: jdow: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Reply: John DeDourek: "Re: NTP problem - Clock too fast for NTP to keep up?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|