Re: PSA: Clock drift and pkgin
John Klos <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
> Did anyone actually report results running on a 4000/60? Personally, I've > been running on a 4000/90, where time is not working well. But that one would > be depending on the ICR. But I haven't checked if it actually do have a > proper ICR. Does anyone know? 4000/60: [ 1.000003] timecounter: Timecounter "diagtimer" frequency 1000000 Hz quality 100 kern.timecounter.choice = clockinterrupt(q=0, f=100 Hz) diagtimer(q=100, f=1000000 Hz) dummy(q=-1000000, f=1000000 Hz) That comes straight from: counter = *(volatile u_int *)&ka46_cpu->vc_diagtimu; which is u_short vc_diagtimu; /* 1a - usecond timer KA46 */ Over the course of a week, time on the 4000/60 is off by 1.13 to 1.15 seconds when the system is loaded, and by about .25 seconds when it's idle, per day. I imagine that's due to thermals. John