Re: PSA: Clock drift and pkgin

On Sun, 2023-12-24 09:22:33 +0100, Jan-Benedict Glaw <[email protected]> wrote:
> On Sat, 2023-12-23 12:49:16 +0100, Jan-Benedict Glaw <[email protected]> wrote:
> > After swapping terminators and cables, the conclusion is that one of
> > the system's SCSI cable's plug doesn't make proper contact to the
> > cable. Using a different plug on the same cable (which isn't at the
> > "perfect" location though) makes it work.
> > 
> > So I'm now prepared with a 4000/60 :)
> 
> With the HDD image I used on the /90, that 4000/60 is running since
> some hours. No network connection, no ntpd. The image is a few months
> old, but for finding a misbehaving clock or lost interrupts, that
> should be good enough.
> 
>   While running idle (~ 3 h), I didn't notice loss of time. Maybe a
> second? But no more. (And that's over 9k6 serial...)

Running for another day, my /60 lost about 3.5 seconds in a whole day
while running GCC in a loop. No further "timecounter went backwards"
except the initial one were reported.

MfG, JBG

--

-----BEGIN PGP SIGNATURE-----

iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZYqKXQAKCRAdvV51g5nh
u0o5AJ4+j2ehM5+Kj/iXpCkaFUZ/jpQikQCfV8jgp1RLzcFVafSdPKrM4kfnm6A=
=WXTL
-----END PGP SIGNATURE-----