[Simh] NetBSD 5.1 on MicoVAX 3900 boot error
I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH
v 4.0 Beta. Install went fine w/o any problems. I'm attaching the session
file and here's the netbsd-boot file:
load -r ..\..\..\..\bin\ka655x.bin
set cpu 64m
; SET CPU IDLE=NETBSD
set tto 7b
; AT DZ
set rq0 ra92
at rq0 netbsd.dsk
at xq0 eth0
boot cpu
; At the VMB prompt, type boot dua0:
F:\SIMH\swkit\DEC\VAX\NetBSD_5.1>..\..\..\..\bin\vax.exe netbsd-boot
MicroVAX 3900 simulator V4.0-0 Betagit commit id: bce72b2b
Npcap version 0.86, based on libpcap version 1.8.1
Eth: opened OS device \Device\NPF_{48115EAA-67A9-465C-A70A-0D6F755C255F} -
my-tap
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua0:
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
>> NetBSD/vax boot [1.11 Sat Nov 6 19:40:01 UTC 2010] <<
>> Press any key to abort autoboot 0
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
2403628+308444 [194288+184371]=0x2f2c58
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008, 2009, 2010
The NetBSD Foundation, Inc. All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
NetBSD 5.1 (GENERIC) #0: Sat Nov 6 19:48:36 UTC 2010
bui...@b8.netbsd.org:/home/builds/ab/netbsd-5-1-RELEASE/vax/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/vax/compile/GENERIC
MicroVAX 3800/3900
total memory = 65468 KB
avail memory = 60312 KB
mainbus0 (root)
cpu0 at mainbus0: KA655, CVAX microcode rev 6 Firmware rev 83
lance at mainbus0 not configured
uba0 at mainbus0: Q22
dz1 at uba0 csr 160100 vec 304 ipl 17
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 5 model 3
mscpbus0: DMA burst size set to 4
mt0 at mscpbus0 drive 0: TK50
mt1 at mscpbus0 drive 1: TK50
mt2 at mscpbus0 drive 2: TK50
mt3 at mscpbus0 drive 3: TK50
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 3 model 3
mscpbus1: DMA burst size set to 4
ra0 at mscpbus1 drive 0: RA92
ra1 at mscpbus1 drive 1: RD54
ra2 at mscpbus1 drive 2: RD54
rx0 at mscpbus1 drive 3: RX50
qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc 801feeb5
addr 1c
Stopped in pid 0.1 (system) at netbsd:upcallret: function "upcallret()",
e
ntry-mask 0x7c0
remqhi *0x4ac(r0), r6
db>___
Simh mailing list
Simh@trailing-edge.com
http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: > I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH v > 4.0 Beta. Install went fine w/o any problems. I'm attaching the session file > and > here's the netbsd-boot file: > > > load -r ..\..\..\..\bin\ka655x.bin > set cpu 64m > ; SET CPU IDLE=NETBSD > set tto 7b > ; AT DZ > set rq0 ra92 > at rq0 netbsd.dsk > at xq0 eth0 > boot cpu > > ; At the VMB prompt, type boot dua0: > I vaguely recall that there was at least one NetBSD version that was just broken and hadn't been tested on any VAX (real or simulated) before it was 'released'. I suggest you: 1) try the same with simh 3.9 2) try a later NetBSD release. If you're seeing a problem which persists across several NetBSD releases, and/or exists in the 4.0 code but not the 3.9 code, please open an issue at https://github.com/simh/simh/issues Have Fun. - Mark Pizzolato ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Mon, 17 Apr 2017, Mark Pizzolato wrote: Date: Mon, 17 Apr 2017 10:37:49 -0700 From: Mark Pizzolato To: "peter...@sdf.org" , "simh@trailing-edge.com" Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH v 4.0 Beta. Install went fine w/o any problems. I'm attaching the session file and here's the netbsd-boot file: load -r ..\..\..\..\bin\ka655x.bin set cpu 64m ; SET CPU IDLE=NETBSD set tto 7b ; AT DZ set rq0 ra92 at rq0 netbsd.dsk at xq0 eth0 boot cpu ; At the VMB prompt, type boot dua0: I vaguely recall that there was at least one NetBSD version that was just broken and hadn't been tested on any VAX (real or simulated) before it was 'released'. I suggest you: 1) try the same with simh 3.9 2) try a later NetBSD release. If you're seeing a problem which persists across several NetBSD releases, and/or exists in the 4.0 code but not the 3.9 code, please open an issue at https://github.com/simh/simh/issues Have Fun. - Mark Pizzolato Thanks for the tips and info. I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't work on earlier versions of SIMH which require WinPcap. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. -- Peter Conrad Cumminsky - peter...@sdf.lonestar.org My Freeshell Web - http://petercon.freeshell.org/ My Gopher - gopher://sdf.lonestar.org/users/petercon SDF Public Access UNIX System - http://sdf.lonestar.org ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Tuesday, April 18, 2017 at 8:57 AM, Peter Conrad Cumminsky wrote: > On Mon, 17 Apr 2017, Mark Pizzolato wrote: > > > On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: > >> I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of > SIMH v > >> 4.0 Beta. Install went fine w/o any problems. I'm attaching the session > >> file > and > >> here's the netbsd-boot file: > >> > >> > >> load -r ..\..\..\..\bin\ka655x.bin > >> set cpu 64m > >> ; SET CPU IDLE=NETBSD > >> set tto 7b > >> ; AT DZ > >> set rq0 ra92 > >> at rq0 netbsd.dsk > >> at xq0 eth0 > >> boot cpu > >> > >> ; At the VMB prompt, type boot dua0: > >> > > > > I vaguely recall that there was at least one NetBSD version that was just > broken and hadn't been tested on any VAX (real or simulated) before it was > 'released'. > > > > I suggest you: > > 1) try the same with simh 3.9 > > 2) try a later NetBSD release. > > > > If you're seeing a problem which persists across several NetBSD releases, > and/or exists in the 4.0 code but not the 3.9 code, please open an issue at > https://github.com/simh/simh/issues > > > > Have Fun. > > > > - Mark Pizzolato > > > > Thanks for the tips and info. > > I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and > 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old > NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. > > I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit > and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't > work on earlier versions of SIMH which require WinPcap. You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. > I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did > run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a > laptop I have to Win7 in the future and may try that. Until then I'll play > with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
You can get a pre-built Windows 32b 3.9 executable without Ethernet (and therefore, without needing WinPCap) here: http://simh.trailing-edge.com/sources/simhv39-0-exe.zip. It should run fine under W10. See if it will boot NetBSD 5.1. /Bob Supnik On 4/18/2017 3:53 PM, simh-requ...@trailing-edge.com wrote: You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
Should one want winpcap in Windows 10, all one needs is: http://www.win10pcap.org/ -Mark On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik wrote: > You can get a pre-built Windows 32b 3.9 executable without Ethernet (and > therefore, without needing WinPCap) here: http://simh.trailing-edge.com/ > sources/simhv39-0-exe.zip. It should run fine under W10. See if it will > boot NetBSD 5.1. > > /Bob Supnik > > > On 4/18/2017 3:53 PM, simh-requ...@trailing-edge.com wrote: > >> You shouldn't need WinPCAP merely to test if the CD image is bootable. >> The point of the boot test exercise is to help determine if the problem is >> in NetBSD or due to recent changes to simh. If changes to simh are at >> fault, I'll track it down and fix the problem. >> >> I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did >>> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a >>> laptop I have to Win7 in the future and may try that. Until then I'll >>> play >>> with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. >>> >> The boot test I'm suggesting will be far less work than setting up another >> system. >> >> Let me know. >> >> - Mark >> > > ___ > Simh mailing list > Simh@trailing-edge.com > http://mailman.trailing-edge.com/mailman/listinfo/simh > ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
Actually, the latest simh ‘supported’ WinPcap is npcap. Npcap is part of the nmap project and directly shares the latest libpcap code. Npcap has a BSD license like the original WinPcap did. Win10pcap is a GPL package and is untested and unsupported for use with simh Ethernet devices. Npcap is available from: https://github.com/nmap/npcap/releases From: Simh [mailto:simh-boun...@trailing-edge.com] On Behalf Of Mark Abene Sent: Tuesday, April 18, 2017 3:07 PM To: Bob Supnik Cc: simh@trailing-edge.com Subject: Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error Should one want winpcap in Windows 10, all one needs is: http://www.win10pcap.org/ -Mark On Tue, Apr 18, 2017 at 1:08 PM, Bob Supnik mailto:b...@supnik.org>> wrote: You can get a pre-built Windows 32b 3.9 executable without Ethernet (and therefore, without needing WinPCap) here: http://simh.trailing-edge.com/sources/simhv39-0-exe.zip. It should run fine under W10. See if it will boot NetBSD 5.1. /Bob Supnik On 4/18/2017 3:53 PM, simh-requ...@trailing-edge.com<mailto:simh-requ...@trailing-edge.com> wrote: You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark ___ Simh mailing list Simh@trailing-edge.com<mailto:Simh@trailing-edge.com> http://mailman.trailing-edge.com/mailman/listinfo/simh ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Tue, 18 Apr 2017, Mark Pizzolato wrote: Date: Tue, 18 Apr 2017 11:52:35 -0700 From: Mark Pizzolato To: Peter Conrad Cumminsky Cc: "simh@trailing-edge.com" Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Tuesday, April 18, 2017 at 8:57 AM, Peter Conrad Cumminsky wrote: On Mon, 17 Apr 2017, Mark Pizzolato wrote: On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH v 4.0 Beta. Install went fine w/o any problems. I'm attaching the session file and here's the netbsd-boot file: load -r ..\..\..\..\bin\ka655x.bin set cpu 64m ; SET CPU IDLE=NETBSD set tto 7b ; AT DZ set rq0 ra92 at rq0 netbsd.dsk at xq0 eth0 boot cpu ; At the VMB prompt, type boot dua0: I vaguely recall that there was at least one NetBSD version that was just broken and hadn't been tested on any VAX (real or simulated) before it was 'released'. I suggest you: 1) try the same with simh 3.9 2) try a later NetBSD release. If you're seeing a problem which persists across several NetBSD releases, and/or exists in the 4.0 code but not the 3.9 code, please open an issue at https://github.com/simh/simh/issues Have Fun. - Mark Pizzolato Thanks for the tips and info. I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't work on earlier versions of SIMH which require WinPcap. You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark As I mentioned in my OP the NetBSD 5.x iso's installation works fine - no problems with cd-rom boot. The first boot of the installed NetBSD 5.x Segv's as per the original file attachment in my OP. I installed the SIMH 3.9 vax.exe and ka655x.bin in a seperate directory and ran the installed NetBSD 5.1. It booted w/o the Segv (and did not give me the WinPCAP error since I used the sans-network version of SIMH 3.9). While it doesn't help me to run it without a network I hope this helps you find the problem. Again, installation from CD works fine - first boot Segv's. Thanks for your assistance. -- Peter Conrad Cumminsky - peter...@sdf.lonestar.org My Freeshell Web - http://petercon.freeshell.org/ My Gopher - gopher://sdf.lonestar.org/users/petercon SDF Public Access UNIX System - http://sdf.lonestar.org ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Thu, 20 Apr 2017, Mark Pizzolato wrote: Date: Thu, 20 Apr 2017 23:47:16 -0700 From: Mark Pizzolato To: Peter Conrad Cumminsky Cc: Mark Pizzolato Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Thursday, April 20, 2017 at 4:57 AM, Peter Conrad Cumminsky wrote: On Wed, 19 Apr 2017, Mark Pizzolato wrote: Date: Wed, 19 Apr 2017 14:23:20 -0700 From: Mark Pizzolato To: Peter Conrad Cumminsky Cc: Mark Pizzolato Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error Hi Peter, On Wednesday, April 19, 2017 at 5:45 AM, Peter Conrad Cumminsky wrote: On Tue, 18 Apr 2017, Mark Pizzolato wrote: Date: Tue, 18 Apr 2017 11:52:35 -0700 From: Mark Pizzolato To: Peter Conrad Cumminsky Cc: "simh@trailing-edge.com" Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Tuesday, April 18, 2017 at 8:57 AM, Peter Conrad Cumminsky wrote: On Mon, 17 Apr 2017, Mark Pizzolato wrote: On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH v 4.0 Beta. Install went fine w/o any problems. I'm attaching the session file and here's the netbsd-boot file: load -r ..\..\..\..\bin\ka655x.bin set cpu 64m ; SET CPU IDLE=NETBSD set tto 7b ; AT DZ set rq0 ra92 at rq0 netbsd.dsk at xq0 eth0 boot cpu ; At the VMB prompt, type boot dua0: I vaguely recall that there was at least one NetBSD version that was just broken and hadn't been tested on any VAX (real or simulated) before it was 'released'. I suggest you: 1) try the same with simh 3.9 2) try a later NetBSD release. If you're seeing a problem which persists across several NetBSD releases, and/or exists in the 4.0 code but not the 3.9 code, please open an issue at https://github.com/simh/simh/issues Have Fun. - Mark Pizzolato Thanks for the tips and info. I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't work on earlier versions of SIMH which require WinPcap. You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark As I mentioned in my OP the NetBSD 5.x iso's installation works fine - no problems with cd-rom boot. The first boot of the installed NetBSD 5.x Segv's as per the original file attachment in my OP. I installed the SIMH 3.9 vax.exe and ka655x.bin in a seperate directory and ran the installed NetBSD 5.1. It booted w/o the Segv (and did not give me the WinPCAP error since I used the sans-network version of SIMH 3.9). While it doesn't help me to run it without a network I hope this helps you find the problem. Again, installation from CD works fine - first boot Segv's. Can you zip the installed disk image and provide it somewhere I can pick it up (Google Drive maybe)? Thanks. - Mark Here you go: https://www.dropbox.com/s/bbyrncu54z5qwcf/netbsd.zip?dl=0 Thanks. Using that, I've tracked the SEGV back to the instruction which is actually faulting. The panic message and the initial kernel debug have nothing to do with the instruction which actually is failing. The address being referenced is indeed not valid, so how/why it gets to this point is the next question Is there some way you might have (or I might find) a link map for the kernel that is being booted? Knowing what module it is occurring in would give me a clue as to where to look next... Thanks again. - Mark That is way beyond my level of expertise, I'm afraid. All I can offer is that the install image is the official release of NetBSD 5.1 from the NetBSD archives. Pretty much the default installation options and no kernel "tuning". -- Peter Conrad Cumminsky - peter...@sdf.lonestar.org My Freeshell Web - http://petercon.freeshell.org/ My Gopher - gopher://sdf.lonestar.org/users/petercon SDF Public Access UNIX System - http://sdf.lonestar.org ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Wednesday, April 19, 2017 at 5:45 AM, Peter Conrad Cumminsky wrote: > On Tue, 18 Apr 2017, Mark Pizzolato wrote: > > On Tuesday, April 18, 2017 at 8:57 AM, Peter Conrad Cumminsky wrote: > >> On Mon, 17 Apr 2017, Mark Pizzolato wrote: > >> > >>> On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: > I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of > >> SIMH v > 4.0 Beta. Install went fine w/o any problems. I'm attaching the session > file > >> and > here's the netbsd-boot file: > > > load -r ..\..\..\..\bin\ka655x.bin > set cpu 64m > ; SET CPU IDLE=NETBSD > set tto 7b > ; AT DZ > set rq0 ra92 > at rq0 netbsd.dsk > at xq0 eth0 > boot cpu > > ; At the VMB prompt, type boot dua0: > > >>> > >>> I vaguely recall that there was at least one NetBSD version that was just > >> broken and hadn't been tested on any VAX (real or simulated) before it was > >> 'released'. > >>> > >>> I suggest you: > >>> 1) try the same with simh 3.9 > >>> 2) try a later NetBSD release. > >>> > >>> If you're seeing a problem which persists across several NetBSD releases, > >> and/or exists in the 4.0 code but not the 3.9 code, please open an issue at > >> https://github.com/simh/simh/issues > >>> > >>> Have Fun. > >>> > >>> - Mark Pizzolato > >>> > >> > >> Thanks for the tips and info. > >> > >> I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and > >> 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old > >> NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. > >> > >> I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit > >> and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't > >> work on earlier versions of SIMH which require WinPcap. > > > > You shouldn't need WinPCAP merely to test if the CD image is bootable. > > The point of the boot test exercise is to help determine if the problem is > > in NetBSD or due to recent changes to simh. If changes to simh are at > > fault, I'll track it down and fix the problem. > > > >> I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did > >> run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade > a > >> laptop I have to Win7 in the future and may try that. Until then I'll play > >> with OpenBSD which doesn't seem to have any problems with SIMH 4.0 > beta. > > > > The boot test I'm suggesting will be far less work than setting up another > > system. > > > > Let me know. > > > > - Mark > > > > > > As I mentioned in my OP the NetBSD 5.x iso's installation works fine - no > problems with cd-rom boot. The first boot of the installed NetBSD 5.x Segv's > as per the original file attachment in my OP. > > I installed the SIMH 3.9 vax.exe and ka655x.bin in a seperate directory > and ran the installed NetBSD 5.1. It booted w/o the Segv (and did not give > me the WinPCAP error since I used the sans-network version of SIMH 3.9). > > While it doesn't help me to run it without a network I hope this helps you > find the problem. Again, installation from CD works fine - first boot > Segv's. OK. So, the difference in boot output on the simh v3.x version is: rx0 at mscpbus1 drive 3: RX50 qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address 08:00:2b:23:52:2f while on the failing simh v4.x version it is: rx0 at mscpbus1 drive 3: RX50 qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc 801feeb5 addr 1c Stopped in pid 0.1 (system) at netbsd:upcallret: function "upcallret()", e... As it turns out, on both versions of simh, the XQ device defaults to emulating a DELQA-PLUS (aka DELQA-T). Some changes were made in the XQ device simulation over time which now allows the NetBSD driver to detect the device as an DELQA-T instead of merely a DEQNA and it now is using the qt driver instead of the qe driver. The NetBSD qt driver seems to have some sort of bug and/or incompatibility with the DELQA-T device simulation which is demonstrated as the crash you see. If your configuration file has "SET XQ TYPE=DELQA" the boot output will be: rx0 at mscpbus1 drive 3: RX50 qt !Turbo qe0 at uba0 csr 174440 vec 764 ipl 17: delqa, hardware address 08:00:2b:23:52:2f and the system will boot successfully. It would be interesting to see what the boot output looks like on the subsequence NetBSD 6.x versions... - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
Den 2017-04-21 kl. 19:14, skrev Mark Pizzolato: OK. So, the difference in boot output on the simh v3.x version is: rx0 at mscpbus1 drive 3: RX50 qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address 08:00:2b:23:52:2f while on the failing simh v4.x version it is: rx0 at mscpbus1 drive 3: RX50 qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc 801feeb5 addr 1c Stopped in pid 0.1 (system) at netbsd:upcallret: function "upcallret()", e... As it turns out, on both versions of simh, the XQ device defaults to emulating a DELQA-PLUS (aka DELQA-T). Some changes were made in the XQ device simulation over time which now allows the NetBSD driver to detect the device as an DELQA-T instead of merely a DEQNA and it now is using the qt driver instead of the qe driver. The NetBSD qt driver seems to have some sort of bug and/or incompatibility with the DELQA-T device simulation which is demonstrated as the crash you see. Note that the delqa-t driver comes from 2.11BSD. If it fails with NetBSD but not 2BSD I may have introduced some bug when porting it over. It do work very well on real hardware though. -- Ragge ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Friday, April 21, 2017 at 10:57 AM, Anders Magnusson wrote: > Den 2017-04-21 kl. 19:14, skrev Mark Pizzolato: > > > > OK. So, the difference in boot output on the simh v3.x version is: > > > > rx0 at mscpbus1 drive 3: RX50 > > qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address > 08:00:2b:23:52:2f > > > > while on the failing simh v4.x version it is: > > > > rx0 at mscpbus1 drive 3: RX50 > > qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc > 801feeb5 addr 1c > > Stopped in pid 0.1 (system) at netbsd:upcallret: function > "upcallret()", e... > > > > As it turns out, on both versions of simh, the XQ device defaults to > emulating a DELQA-PLUS > > (aka DELQA-T). Some changes were made in the XQ device simulation over > time which now > > allows the NetBSD driver to detect the device as an DELQA-T instead of > merely a DEQNA and > > it now is using the qt driver instead of the qe driver. The NetBSD qt > > driver > seems to have > > some sort of bug and/or incompatibility with the DELQA-T device simulation > which is > > demonstrated as the crash you see. > > > Note that the delqa-t driver comes from 2.11BSD. If it fails with > NetBSD but not 2BSD I may have > introduced some bug when porting it over. It do work very well on real > hardware though. That is why I asked about what driver ends up getting used in later NetBSD versions. If it is the qt driver, then I'm not worried about fixing anything. If it is not the qt driver, then there is something to fix to get the device probe happy... - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Fri, 21 Apr 2017, Mark Pizzolato wrote: Date: Fri, 21 Apr 2017 10:14:29 -0700 From: Mark Pizzolato To: Peter Conrad Cumminsky Cc: "simh@trailing-edge.com" Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Wednesday, April 19, 2017 at 5:45 AM, Peter Conrad Cumminsky wrote: On Tue, 18 Apr 2017, Mark Pizzolato wrote: On Tuesday, April 18, 2017 at 8:57 AM, Peter Conrad Cumminsky wrote: On Mon, 17 Apr 2017, Mark Pizzolato wrote: On Monday, April 17, 2017 at 10:28 AM, peter...@sdf.org wrote: I'm getting a Segv error on boot of NetBSD 5.1 on the VAX emulator of SIMH v 4.0 Beta. Install went fine w/o any problems. I'm attaching the session file and here's the netbsd-boot file: load -r ..\..\..\..\bin\ka655x.bin set cpu 64m ; SET CPU IDLE=NETBSD set tto 7b ; AT DZ set rq0 ra92 at rq0 netbsd.dsk at xq0 eth0 boot cpu ; At the VMB prompt, type boot dua0: I vaguely recall that there was at least one NetBSD version that was just broken and hadn't been tested on any VAX (real or simulated) before it was 'released'. I suggest you: 1) try the same with simh 3.9 2) try a later NetBSD release. If you're seeing a problem which persists across several NetBSD releases, and/or exists in the 4.0 code but not the 3.9 code, please open an issue at https://github.com/simh/simh/issues Have Fun. - Mark Pizzolato Thanks for the tips and info. I've tried all versions of NetBSD 5.x (5.0.2, 5.1, 5.1.5, 5.2 and 5.2.3) that I can find on SIMH 4.0 beta and they all Segv. I have an old NetBSD 3 that boots and I tried NetBSD 6.0.4 and that also boots. I am not able to run earlier versions of SIMH as I'm on Windows 10 64-bit and WinPCAP does not run on W10. I use NPcap on W10 and that doesn't work on earlier versions of SIMH which require WinPcap. You shouldn't need WinPCAP merely to test if the CD image is bootable. The point of the boot test exercise is to help determine if the problem is in NetBSD or due to recent changes to simh. If changes to simh are at fault, I'll track it down and fix the problem. I specifically want to run a 5.x version of NetBSD. I'm pretty sure it did run on SIMH 3.8-1 on Windows 7 before the upgrade. I need to downgrade a laptop I have to Win7 in the future and may try that. Until then I'll play with OpenBSD which doesn't seem to have any problems with SIMH 4.0 beta. The boot test I'm suggesting will be far less work than setting up another system. Let me know. - Mark As I mentioned in my OP the NetBSD 5.x iso's installation works fine - no problems with cd-rom boot. The first boot of the installed NetBSD 5.x Segv's as per the original file attachment in my OP. I installed the SIMH 3.9 vax.exe and ka655x.bin in a seperate directory and ran the installed NetBSD 5.1. It booted w/o the Segv (and did not give me the WinPCAP error since I used the sans-network version of SIMH 3.9). While it doesn't help me to run it without a network I hope this helps you find the problem. Again, installation from CD works fine - first boot Segv's. OK. So, the difference in boot output on the simh v3.x version is: rx0 at mscpbus1 drive 3: RX50 qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address 08:00:2b:23:52:2f while on the failing simh v4.x version it is: rx0 at mscpbus1 drive 3: RX50 qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc 801feeb5 addr 1c Stopped in pid 0.1 (system) at netbsd:upcallret: function "upcallret()", e... As it turns out, on both versions of simh, the XQ device defaults to emulating a DELQA-PLUS (aka DELQA-T). Some changes were made in the XQ device simulation over time which now allows the NetBSD driver to detect the device as an DELQA-T instead of merely a DEQNA and it now is using the qt driver instead of the qe driver. The NetBSD qt driver seems to have some sort of bug and/or incompatibility with the DELQA-T device simulation which is demonstrated as the crash you see. If your configuration file has "SET XQ TYPE=DELQA" the boot output will be: rx0 at mscpbus1 drive 3: RX50 qt !Turbo qe0 at uba0 csr 174440 vec 764 ipl 17: delqa, hardware address 08:00:2b:23:52:2f and the system will boot successfully. It would be interesting to see what the boot output looks like on the subsequence NetBSD 6.x versions... - Mark YES, that works!!! NetBSD 5.1 now boots. Thanks for the info. -- Peter Conrad Cumminsky - peter...@sdf.lonestar.org My Freeshell Web - http://petercon.freeshell.org/ My Gopher - gopher://sdf.lonestar.org/users/petercon SDF Public Access UNIX System - http://sdf.lonestar.org ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Fri, 21 Apr 2017, Mark Pizzolato wrote: Date: Fri, 21 Apr 2017 17:42:05 -0700 From: Mark Pizzolato To: Anders Magnusson , Peter Conrad Cumminsky Cc: "simh@trailing-edge.com" Subject: RE: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error On Friday, April 21, 2017 at 10:57 AM, Anders Magnusson wrote: Den 2017-04-21 kl. 19:14, skrev Mark Pizzolato: OK. So, the difference in boot output on the simh v3.x version is: rx0 at mscpbus1 drive 3: RX50 qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address 08:00:2b:23:52:2f while on the failing simh v4.x version it is: rx0 at mscpbus1 drive 3: RX50 qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: pc 801feeb5 addr 1c Stopped in pid 0.1 (system) at netbsd:upcallret: function "upcallret()", e... As it turns out, on both versions of simh, the XQ device defaults to emulating a DELQA-PLUS (aka DELQA-T). Some changes were made in the XQ device simulation over time which now allows the NetBSD driver to detect the device as an DELQA-T instead of merely a DEQNA and it now is using the qt driver instead of the qe driver. The NetBSD qt driver seems to have some sort of bug and/or incompatibility with the DELQA-T device simulation which is demonstrated as the crash you see. Note that the delqa-t driver comes from 2.11BSD. If it fails with NetBSD but not 2BSD I may have introduced some bug when porting it over. It do work very well on real hardware though. That is why I asked about what driver ends up getting used in later NetBSD versions. If it is the qt driver, then I'm not worried about fixing anything. If it is not the qt driver, then there is something to fix to get the device probe happy... - Mark OK, here's my init file for NetBSD 6.1.5 (SET XQ TYPE=DELQA commented out): . set cpu 256M set cpu idle=netbsd at nvr vax.nvr set rq0 rauser=5000 at rq0 netbsd.dsk ; SET XQ TYPE=DELQA ; at xq nat:tcp=:10.0.2.15:22 ; set console telnet=2223 boot cpu and here's the output from the boot: ... F:\SIMH\swkit\DEC\VAX\NetBSD-6.1.5>..\..\..\..\bin\vax.exe netbsd-boot MicroVAX 3900 simulator V4.0-0 Betagit commit id: bce72b2b NVR: buffering file in memory Loading boot code from internal ka655x.bin KA655X-B V5.3, VMB 2.7 Performing normal system tests. 40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25.. 24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09.. 08..07..06..05..04..03.. Tests completed. boot dua0 (BOOT/R5:0 DUA0 2.. -DUA0 1..0.. NetBSD/vax boot [1.11] << Press any key to abort autoboot 0 nfs_open: must mount first. open netbsd.vax: Device not configured boot netbsd 2591168+174136 [211456+201165]=0x3081e8 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 6.1.5 (GENERIC) MicroVAX 3800/3900 total memory = 255 MB avail memory = 243 MB mainbus0 (root) cpu0 at mainbus0: KA655, CVAX microcode rev 6 Firmware rev 83 lance at mainbus0 not configured uba0 at mainbus0: Q22 dz1 at uba0 csr 160100 vec 304 ipl 17 mtc0 at uba0 csr 174500 vec 774 ipl 17 mscpbus0 at mtc0: version 5 model 3 mscpbus0: DMA burst size set to 4 uda0 at uba0 csr 172150 vec 770 ipl 17 mscpbus1 at uda0: version 3 model 3 mscpbus1: DMA burst size set to 4 qt0 at uba0 csr 174440 vec 764 ipl 17 qt0: delqa-plus in Turbo mode, hardware address 08:00:2b:d3:52:d9 rlc0 at uba0 csr 174400 vec 160 ipl 17 rl0 at rlc0 drive 0: RL01, drive not loaded rl1 at rlc0 drive 1: RL01, drive not loaded rl2 at rlc0 drive 2: RL01, drive not loaded rl3 at rlc0 drive 3: RL01, drive not loaded ts0 at uba0 csr 172520 vec 224 ipl 17: TS11 ts0: rev 0, extended features disabled, transport offline mt0 at mscpbus0 drive 0: TK50 mt1 at mscpbus0 drive 1: TK50 mt2 at mscpbus0 drive 2: TK50 mt3 at mscpbus0 drive 3: TK50 ra0 at mscpbus1 drive 0: RA82 ra1 at mscpbus1 drive 1: RD54 ra2 at mscpbus1 drive 2: RD54 rx0 at mscpbus1 drive 3: RX50 ra0: size 977 sectors ra1: attempt to bring on line failed: unit offline (not mounted) (code 3, subcode 1) ra2: attempt to bring on line failed: unit offline (not mounted) (code 3, subcode 1) rx0: attempt to bring on line failed: unit offline (not mounted) (code 3, subcode 1) boot device: ra0 root on ra0a dumps on ra0b root file system type: ffs WARNING: clock lost 160 days WARNING: using filesystem time WARNING: CHECK AND RESET THE DATE! Mon Sep 29 19:37:07 UTC 2014 Starting root file system check: /dev/rra0a: file system is clean; not checking swapctl: setting dump device to /dev/ra0b swapctl: adding /dev/ra0b as swap devi
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Saturday, April 22, 2017 at 8:27 AM, Peter Conrad Cumminsky wrote: > On Fri, 21 Apr 2017, Mark Pizzolato wrote: > > > On Friday, April 21, 2017 at 10:57 AM, Anders Magnusson wrote: > >> Den 2017-04-21 kl. 19:14, skrev Mark Pizzolato: > >>> > >>> OK. So, the difference in boot output on the simh v3.x version is: > >>> > >>> rx0 at mscpbus1 drive 3: RX50 > >>> qe0 at uba0 csr 174440 vec 764 ipl 17: deqna, hardware address > >> 08:00:2b:23:52:2f > >>> > >>> while on the failing simh v4.x version it is: > >>> > >>> rx0 at mscpbus1 drive 3: RX50 > >>> qt0 at uba0 csr 174440 vec 764 ipl 17panic: Segv in kernel mode: > >>> pc > >> 801feeb5 addr 1c > >>> Stopped in pid 0.1 (system) at netbsd:upcallret: function > >> "upcallret()", e... > >>> > >>> As it turns out, on both versions of simh, the XQ device defaults to > >> emulating a DELQA-PLUS > >>> (aka DELQA-T). Some changes were made in the XQ device simulation > over > >> time which now > >>> allows the NetBSD driver to detect the device as an DELQA-T instead of > >> merely a DEQNA and > >>> it now is using the qt driver instead of the qe driver. The NetBSD qt > >>> driver > >> seems to have > >>> some sort of bug and/or incompatibility with the DELQA-T device > simulation > >> which is > >>> demonstrated as the crash you see. > >>> > >> Note that the delqa-t driver comes from 2.11BSD. If it fails with > >> NetBSD but not 2BSD I may have > >> introduced some bug when porting it over. It do work very well on real > >> hardware though. > > > > That is why I asked about what driver ends up getting used in later NetBSD > > versions. > > If it is the qt driver, then I'm not worried about fixing anything. If it > > is not > > the qt > > driver, then there is something to fix to get the device probe happy... > > > > - Mark > > > > > > OK, here's my init file for NetBSD 6.1.5 (SET XQ TYPE=DELQA commented > out): > > . > set cpu 256M > set cpu idle=netbsd > at nvr vax.nvr > > set rq0 rauser=5000 > at rq0 netbsd.dsk > > ; SET XQ TYPE=DELQA > ; at xq nat:tcp=:10.0.2.15:22 > ; set console telnet=2223 > > boot cpu > > > and here's the output from the boot: > > ... > > F:\SIMH\swkit\DEC\VAX\NetBSD-6.1.5>..\..\..\..\bin\vax.exe netbsd-boot > > MicroVAX 3900 simulator V4.0-0 Betagit commit id: bce72b2b > NVR: buffering file in memory > Loading boot code from internal ka655x.bin > > [...] > qt0 at uba0 csr 174440 vec 764 ipl 17 > qt0: delqa-plus in Turbo mode, hardware address 08:00:2b:d3:52:d9 [...] Thanks for checking this Peter. Meanwhile, since NetBSD 6.1.5 works, and NetBSD 5.x.x doesn't, these questions arise: 1) What is different in that driver between those NetBSD versions? 2) Why were these differences introduced? 3) Are you sure the qt driver NetBSD 5.x.x truly worked on real hardware? 4) If so, can we test that today (with real hardware)? Thoughts? Thanks. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
Den 2017-04-22 kl. 18:01, skrev Mark Pizzolato: [...] qt0 at uba0 csr 174440 vec 764 ipl 17 qt0: delqa-plus in Turbo mode, hardware address 08:00:2b:d3:52:d9 [...] Thanks for checking this Peter. Meanwhile, since NetBSD 6.1.5 works, and NetBSD 5.x.x doesn't, these questions arise: 1) What is different in that driver between those NetBSD versions? I looked at the CVS logs and no bugfixes to the qt code. 2) Why were these differences introduced? 3) Are you sure the qt driver NetBSD 5.x.x truly worked on real hardware? I have had a 3900 using qt since loong time ago, running NetBSD 5 at last. Not around for me anymore though. 4) If so, can we test that today (with real hardware)? I might have a MV2 to test on, but not in the near future, so hopefully someone else on this list can try? -- Ragge ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Saturday, April 22, 2017 at 12:55 PM, Anders Magnusson wrote: > Den 2017-04-22 kl. 18:01, skrev Mark Pizzolato: > > [...] > >> qt0 at uba0 csr 174440 vec 764 ipl 17 > >> qt0: delqa-plus in Turbo mode, hardware address 08:00:2b:d3:52:d9 > > [...] > > > > Thanks for checking this Peter. > > > > Meanwhile, since NetBSD 6.1.5 works, and NetBSD 5.x.x doesn't, these > > questions arise: > > 1) What is different in that driver between those NetBSD versions? > I looked at the CVS logs and no bugfixes to the qt code. That is VERY strange. Simh v3.9 detects the DELQA-PLUS (DELQA-T) as a DEQNA/DELQA and not as the turbo case. So it uses qe vs qt. The 4.x simulation has some better emulation of the support which allows the different devices to be detected. BOTH NetBSD 5.x and NetBSD 6.x detect it as a turbo DELQA, 5.x crashes. I'm going to look at what both 5.x and 6.x do during their device probes to see if there is a difference. If all of the ways the device is being probed are the same, then the problem will lie somewhere else. > > 2) Why were these differences introduced? > > 3) Are you sure the qt driver NetBSD 5.x.x truly worked on real > > hardware? > I have had a 3900 using qt since loong time ago, running NetBSD 5 at last. > Not around for me anymore though. > > 4) If so, can we test that today (with real hardware)? > > > I might have a MV2 to test on, but not in the near future, so hopefully > someone else on this list can try? That would be useful... Thanks. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
Re: [Simh] NetBSD 5.1 on MicoVAX 3900 boot error
On Saturday, April 22, 2017 at 12:55 PM, Anders Magnusson wrote: > Den 2017-04-22 kl. 18:01, skrev Mark Pizzolato: > > [...] > >> qt0 at uba0 csr 174440 vec 764 ipl 17 > >> qt0: delqa-plus in Turbo mode, hardware address 08:00:2b:d3:52:d9 > > [...] > > > > Thanks for checking this Peter. > > > > Meanwhile, since NetBSD 6.1.5 works, and NetBSD 5.x.x doesn't, these > > questions arise: > > 1) What is different in that driver between those NetBSD versions? > I looked at the CVS logs and no bugfixes to the qt code. It might still be worth explicitly comparing the qt code between these NetBSD versions. I compared (from the simulator's point of view) the sequence of interactions with the simh XQ device done by qt on both NetBSD 5.x and 6.x and they are identical up to the point where 5.x crashes. > > 2) Why were these differences introduced? > > 3) Are you sure the qt driver NetBSD 5.x.x truly worked on real > > hardware? > I have had a 3900 using qt since loong time ago, running NetBSD 5 at last. > Not around for me anymore though. It would seem to me that this could be debugged on the simulator along with code, link map and knowledge about what else is really going on if the driver code is actually unchanged between NetBSD 5.x and NetBSD 6.x. - Mark ___ Simh mailing list Simh@trailing-edge.com http://mailman.trailing-edge.com/mailman/listinfo/simh
