From owner-freebsd-current Sat Sep 14 3: 4:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06CD837B400 for ; Sat, 14 Sep 2002 03:04:16 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4883F43E42 for ; Sat, 14 Sep 2002 03:04:15 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.3/8.12.2) with ESMTP id g8EA3hB9016205; Sat, 14 Sep 2002 12:03:44 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Julian Elischer Cc: Terry Lambert , Mark Murray , FreeBSD current users Subject: Re: A riddle in -current In-Reply-To: Your message of "Sat, 14 Sep 2002 02:46:55 PDT." Date: Sat, 14 Sep 2002 12:03:42 +0200 Message-ID: <16204.1031997822@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 , Ju lian Elischer writes: >the only difference I've found so far is teh following differnce in the >dmesg output: >21,22c21 >< Timecounter "ACPI-safe" frequency 3579545 Hz >< unknown: I/O range not supported >--- >> Timecounter "ACPI-fast" frequency 3579545 Hz You can test the difference this makes by timing for (i = 0; i < 1000000; i++) gettimeofday(&tv, NULL) ACPI-safe means that the hardware doesn't act like a properly implemented binary counter (!) whereas ACPI-fast has not given any signs of having trouble during the boot-time probing. -- 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