From owner-freebsd-current Mon Apr 1 1:24: 8 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 2473037B41B for ; Mon, 1 Apr 2002 01:24:05 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g319Nc4F003055; Mon, 1 Apr 2002 11:23:38 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Kyle Butt Cc: David Malone , freebsd-current@FreeBSD.ORG Subject: Re: Superfast clock on current. In-Reply-To: Your message of "Mon, 01 Apr 2002 02:23:16 PDT." <87bsd3kc1n.wl@kylebutt.dorms.usu.edu> Date: Mon, 01 Apr 2002 11:23:38 +0200 Message-ID: <3054.1017653018@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <87bsd3kc1n.wl@kylebutt.dorms.usu.edu>, Kyle Butt writes: >> I've stared at the data file and I'll be damned if I can find anything >> which would case the clock to double its speed :-( > >Perhaps something else is causing the clock to run twice as fast? >Maybe two things that are working properly are both incrementing >the clock? Well, obviously something causes it, but I have no idea what at this moment. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message