In message <[EMAIL PROTECTED]>, Dag-Erling Smorgrav writes: >Kyle Butt <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] | 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message