From owner-freebsd-current Tue Mar 26 23:43:16 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 90B1337B422 for ; Tue, 26 Mar 2002 23:43:08 -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 g2R7gne7014007; Wed, 27 Mar 2002 08:42:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: Kyle Butt , freebsd-current@FreeBSD.ORG Subject: Re: Superfast clock on current. In-Reply-To: Your message of "27 Mar 2002 00:45:56 +0100." Date: Wed, 27 Mar 2002 08:42:49 +0100 Message-ID: <14006.1017214969@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 , Dag-Erling Smorgrav writes: >Kyle Butt writes: >> My system clock is running twice as fast as it should be, >> but it doesn't affect timing functions. Ex: >> [...] >> Has anyone else experienced this problem? > >I'm seeing the exact same problem on, guess what... Can I get one of you to collect a hund-thousand samples of the ACPI timer for me ? You need to find the exact I/O port it lives on, and then run the following program and send me the uuencoded stdout ? #include #include #define PORT 0x1008 #define N 100000 uint32_t h[N]; main() { FILE *f; f = fopen("/dev/io", "r"); memset(h, 0, sizeof h); insl(PORT, h, N); write (1, h, sizeof h); } -- 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