Diskless MicroVAX II boot crash in simh current

Josh Moyer <[email protected]>
Newsgroups gmane.os.netbsd.ports.vax
Message-ID <DS7PR07MB75581DE3D3FD38A47DCEBD7EAC9FA@DS7PR07MB7558.namprd07.prod.outlook.com>
Hello port-vax,
Was trying to netboot a KA630 in simh (to troubleshoot my severe clock drift, which I am starting to suspect is due to a missing TOY clock battery (or perhaps the network.)  simh sources pulled on the 24th, but when boot tries to load the kernel it immediately crashes with stray interrupts:

MicroVAX II (KA630) simulator V4.0-0 Current        git commit id: ee34e295+uncommitted-changes
./rasterloopzero.ini-24> at xq eth4
%SIM-INFO: Eth: opened OS device \Device\NPF_{1DE511AE-7F45-4459-BDEF-722560611452} - NODOMAIN.NET
sim> boot


◄

KA630-A.V1.3

Performing normal system tests.

  5..4..3..

Tests completed.


>>> boot xqa0

  2..1..0..


>> NetBSD/vax boot [1.12 (Sun Nov  5 18:30:08 UTC 2023)] <<
>> Press any key to abort autoboot 5
Press '?' for help
> boot -s
Trying BOOTP
Using IP address: 10.9.10.24
myip:  (10.9.10.24)
root addr=10.9.10.192 path=/Data/Code/vax/NetBSD-10.0_RC1/rasterloop-10.0_RC1
stray interrupt: vector 0x18, ipl 31
stray interrupt: vector 0x18, ipl 31
stray interrupt: vector 0x18, ipl 31
...

simh config is as follows, with twiddled options commented out:

load -r ka630.bin
SET WTC TIME=STD
set cpu 16m
;set cpu idle=netbsd
;SET CPU CONHALT
att nvr rasterloopzero.nvr
SET XQ TYPE=DEQNA
;SET XQ TYPE=DELQA
SET XQ MAC=08-00-2B-04-AC-8F
;set xq poll=0
at xq eth4

Any suggestions?  Since my real KA630 boots fine with this config, should I follow-up with the simh team?

Thanks and kind regards,

    _____    
   | * * |   Josh Moyer (he/him) <[email protected]>
   |*(*)*|   http://jmoyer.nodomain.net/
    \ - /    http://www.nodomain.net/
     \//     
             Love, Responsibility, Justice
             Liebe, Verantwortung, Gerechtigkeit
             
             Please don't eat the animals.
             Thanks.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.