On 2018-12-02 22:12, Adam Thompson wrote: > I'm unsure if my test is valid, but I switched to i8254 (confirmed successful > via sysctl), and tset(1) continues to pause for an unnaturally long time. > But then I rebooted and re-tested the same sysctl vaules, and this time > tset(1) took 1sec, as expected. WTF... > > Well, putting that into sysctl.conf seems to be a reasonable workaround for > now. I also enabled timestepwarnings, and they are occurring, although I > don't yet know how often.
I understand why I got inconsistent results... I had two different hosts open in the two windows I was using. Thank goodness they were both just personal systems! I'll re-test tomorrow morning when I'm more awake! -Adam
