Machines with ACPI timecounters will now print 10 lines at boot when
the timer is tested.

If you are lucky you will see ten times something like:
        ACPI timer looks GOOD min = 3, max = 3, width = 1
That means that you have well implemented ACPI timer.

If you are unlucky, one, several or all 10 lines will be marked as

Please send me an email with these 10 lines and the output of
"pciconf -l -v" for your machine.  I'm am interested in reports
both from good and bad machines.

If your machine starts to mysteriously hang after this commit, try
to increase the 15 to 31 in this line:

        } while (u1 > u2 || u2 > u3 || (u3 - u1) > 15);

Hopefully this commit fixes the "timecounter backwards" problem
with broken ACPI timers, if not, let me know.



In message <[EMAIL PROTECTED]>, Poul-Henning Kamp 
>phk         2002/02/25 01:51:18 PST
>  Modified files:
>    sys/dev/acpica       acpi_timer.c 
>  Log:
>  Add a new test_counter() function which tries to determine the width of
>  the inter-value histogram for 2000 samples.  If the width is 3 or less
>  for 10 consequtive samples, we trust the counter to be good, otherwise
>  we use the *_safe() method.
>  This method may be too strict, but the worst which can happen is that
>  we take the performance hit of the *_safe() method when we should not.
>  Make the *_safe() method more discriminating by mandating that the three
>  samples do not span more than 15 ticks on the counter.
>  Disable the PCI-ident based probing as a means to recognize good
>  counters.
>  Inspiration from:       dillon and msmith
>  Revision  Changes    Path
>  1.14      +46 -17    src/sys/dev/acpica/acpi_timer.c

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

Reply via email to