Date: Wed, 27 Mar 2002 08:42:49 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Dag-Erling Smorgrav <des@ofug.org> Cc: Kyle Butt <kylebutt@myrealbox.com>, freebsd-current@FreeBSD.ORG Subject: Re: Superfast clock on current. Message-ID: <14006.1017214969@critter.freebsd.dk> In-Reply-To: Your message of "27 Mar 2002 00:45:56 %2B0100." <xzp8z8edhaj.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <xzp8z8edhaj.fsf@flood.ping.uio.no>, Dag-Erling Smorgrav writes:
>Kyle Butt <kylebutt@myrealbox.com> 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 <stdio.h>
#include <machine/cpufunc.h>
#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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14006.1017214969>