-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

john stultz wrote:
> Hmm... Not sure if this is mis-calibration or just bad-interaction w/
> kthrt. Mind sending a dmesg to me?

dmesg attached

>>and 'pit' seems to produce errors (system will not switch from pit to
>>another clocksource anymore):

Odd.  This time, I got the errors when I switched from acpi_pm (which it
had defaulted to at bootup) to jiffies.  System has not locked at one
clocksource yet, though.

> Do the TOD patches have this issue by themselves, or is this only with
> kthrt? I know I had some issues with non-continuous clocksources (pit,
> jiffies) with the kthrt patch, where it wouldn't fall back to
> non-high-res when the clocksource stopped supporting it.

I only tried with kthrt because I ran into lots of conflicts when
applying the patches to more recent kernels otherwise.  I can try again
with 2.6.14-mm2 in order to test it out.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFDeQdNaI0dwg4A47wRAmPLAJsGeBvY/M7wc4UehisbcLDVxcYi7wCgoaZM
gEKYNqAsmtXrgKI7ePr8Whg=
=wjaI
-----END PGP SIGNATURE-----