From owner-freebsd-current Tue Mar 26 6:29:42 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 B65A337B400 for ; Tue, 26 Mar 2002 06:29:38 -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 g2QETIe7001229; Tue, 26 Mar 2002 15:29:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: David Malone Cc: Kyle Butt , freebsd-current@FreeBSD.ORG Subject: Re: Superfast clock on current. In-Reply-To: Your message of "Tue, 26 Mar 2002 10:04:55 GMT." <20020326100455.GA37656@walton.maths.tcd.ie> Date: Tue, 26 Mar 2002 15:29:17 +0100 Message-ID: <1228.1017152957@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 <20020326100455.GA37656@walton.maths.tcd.ie>, David Malone writes: >On Tue, Mar 26, 2002 at 09:59:29AM +0100, Poul-Henning Kamp wrote: >> This is an interesting machine: A K6 wiht ACPI, havn't seen that >> before. > >I had one of these machines and concluded that the ACPI time counter >was busted. I dunno if it is possible to sanity check the time >counter before using it? I just switched to using the TSC early in >boot and forgot about it. That is what I try to do, and I recently rewrote the code in current for that exact reason, so I'm very interested in seeing the diagnostic output (boot -v) from a -current kernel on these motherboards. -- 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