Date: Sat, 15 Mar 2003 11:56:42 -0500
From: Craig Rodrigues [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Sat, Mar 15, 2003 at 03:51:09PM +, David Malone wrote:
On Fri, Mar 14, 2003 at 11:14:51PM -0800, [EMAIL PROTECTED] wrote:
Has anyone ever seen this? My clock is running double
In message [EMAIL PROTECTED], Kevin Oberman writes:
kern.timecounter.hardware=TSC
Can someone explain why TSC is preferred to i8254 (or why not)?
Cheaper access better resolution.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
On Tue, Mar 18, 2003 at 07:23:48PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kevin Oberman writes:
kern.timecounter.hardware=TSC
Can someone explain why TSC is preferred to i8254 (or why not)?
Cheaper access better resolution.
Which brings me to the question if
In message [EMAIL PROTECTED], Wilko Bulte writes:
On Tue, Mar 18, 2003 at 07:23:48PM +0100, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Kevin Oberman writes:
kern.timecounter.hardware=TSC
Can someone explain why TSC is preferred to i8254 (or why not)?
Cheaper access better
On Fri, Mar 14, 2003 at 11:14:51PM -0800, [EMAIL PROTECTED] wrote:
Has anyone ever seen this? My clock is running double time, that is,
each second it advances two seconds. Needless to say, ntpd can't sync
up with any servers.
This has been reported several times (searching the mailinglist
On Fri, Mar 14, 2003 at 11:14:51PM -0800, [EMAIL PROTECTED] wrote:
Has anyone ever seen this? My clock is running double time, that is,
each second it advances two seconds. Needless to say, ntpd can't sync
up with any servers.
You almost certainly have a motherboard with bad ACPI (probably
On Sat, Mar 15, 2003 at 03:51:09PM +, David Malone wrote:
On Fri, Mar 14, 2003 at 11:14:51PM -0800, [EMAIL PROTECTED] wrote:
Has anyone ever seen this? My clock is running double time, that is,
each second it advances two seconds. Needless to say, ntpd can't sync
up with any servers.
Has anyone ever seen this? My clock is running double time, that is,
each second it advances two seconds. Needless to say, ntpd can't sync
up with any servers.
-Seth
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
