Clock Error
Ken Wellsch <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
I have been running my own build release on simh, as I am sure others may be doing, after seeing such encouraging news that the VAX port may finally be self-hostable again. The build has not yet completed but is well along: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 6963 sim312 1 145 10 199M 150M CPU0 0 110.6H 100.00% vax I am now onto my 5th day running on the "classic" version of simh: VAX simulator V3.12-4 to which I added the small code fragment from open-simh for NEWBSD IDLE. I did not add a network device and learned the hard way that you can't just leave the default time after the install because some of the build config fails when sanity checking the timestamps on files created. So I set the system time from my watch (which is accurate to the second). I just checked the date on the build box and compared it with another system. My desktop: Tue Dec 19 07:59:09 EST 2023 The Build: Tue Dec 19 07:59:04 EST 2023 I am running a cross-compiled copy of 10.99.10 with the last GCC patch applied: NetBSD nb10sim312 10.99.10 NetBSD 10.99.10 (GENERIC) #1: Mon Dec 11 09:17:31 EST 2023 netbsd@z440:/home/netbsd/obj/sys/arch/vax/compile/GENERIC vax So for what it is worth, it appears I am loosing about one second per day, on a 100% loaded simh session, after nearly five days running.