Current on 86x0

[Johnny Billquist <bqt%softjar.se@localhost>]

Seems like the recent problems with device detection have been fixed, 
and a current build boots. This is nice.
So, here is how my simulated 8650 appears right now:

============

sim> boot rq/r5:8
Loading boot code from vmb.exe

>> NetBSD/vax boot [1.11 Mon Apr 27 08:07:57 UTC 2009] <<
>> Press any key to abort autoboot 5
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
2674084+172684 [212768+204148]=0x31cfc8
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013
    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.99.18 (Puff) #5: Fri Mar 29 04:10:49 CET 2013
        root%GW.SoftJAR.SE@localhost:/usr/obj/sys/arch/vax/compile/Puff
VAX 8650
total memory = 65532 KB
avail memory = 59700 KB
mainbus0 (root)
cpu0 at mainbus0: KA865, S/N 1234, Rev. G, manufactured in simh.
cpu0: no FPA
cpu0: Physical memory layout:
cpu0: Memory slot 0 (@0x00000000): 64 Mbytes.
cpu0: I/O adapter 0 (@0x20000000): 32 Mbytes.
cpu0: Unused address space: 928 Mbytes.
abus0 at mainbus0
sbi1 at abus0: SBIA Rev. 0, base address 0x20000000
uba1 at sbi1 tr3: DW780
dz1 at uba1 csr 160100 vec 304 ipl 15
mtc0 at uba1 csr 174500 vec 774 ipl 15
mscpbus0 at mtc0: version 5 model tu81
mscpbus0: DMA burst size set to 4
uda0 at uba1 csr 172150 vec 770 ipl 15
mscpbus1 at uda0: version 3 model uda50a
mscpbus1: DMA burst size set to 4
de0 at uba1 csr 174510 vec 120 ipl 15: delua, hardware address 
aa:00:04:01:04:16
mt0 at mscpbus0 drive 0: TU81
mt1 at mscpbus0 drive 1: TU81
mt2 at mscpbus0 drive 2: TU81
mt3 at mscpbus0 drive 3: TU81
ra0 at mscpbus1 drive 0: RA82
ra1 at mscpbus1 drive 1: RA82
ra2 at mscpbus1 drive 2: RA82
racd0 at mscpbus1 drive 3: RRD40
ra0: size 16007168 sectors
ra1: no disk label: size 16007168 sectors
ra2: no disk label: size 16007168 sectors
racd0: size 1331200 sectors
boot device: ra0
root on ra0a dumps on ra0b
root file system type: ffs
Fri Mar 29 04:39:22 GMT 2013
swapctl: adding /dev/ra0b as swap device at priority 0
Starting file system checks:
/dev/rra0a: file system is clean; not checking
/dev/rra0d: file system is clean; not checking
/dev/rra0e: file system is clean; not checking
/dev/rra0f: file system is clean; not checking
Setting tty flags.
Setting sysctl variables:
kern.no_sa_support: 1 -> 1
ddb.onpanic: 1 -> 0
Starting network.
Hostname: Puff.BQTnet.SE
NIS domainname: BQTnet.SE
IPv6 mode: host
Configuring network interfaces: de0.
Adding interface aliases:.
add net default: gateway 10.0.1.1
Building databases: dev, utmp, utmpx done
Starting syslogd.
Setting date via ntp.
Checking for core dump...
savecore: no core dump
Mounting all filesystems...
Clearing temporary files.
Creating a.out runtime link editor directory cache.
Checking quotas: done.
Setting securelevel: kern.securelevel: 0 -> 1
Starting virecover.
Starting local daemons:.
Updating motd.
Starting ntpd.
Starting sshd.
postfix/postfix-script: starting the Postfix mail system
Starting inetd.
Starting cron.
Fri Mar 29 04:39:56 CET 2013

NetBSD/vax (Puff.BQTnet.SE) (console)

login:

==========


There are a couple of problems right now, that I have not even started 
looking at, but maybe someone already have an idea.
The system does not boot if I configure more than 64 Mbyte of memory. If 
I configure more, it fails to detect my disk controller, and fails to 
come past the initial setup. It asks for the root device, but since it 
didn't even detect the controller, of course no possible answer can be 
given.
With NetBSD 5.0, the same problem existed, but the limit then was 128 
Mbyte. Anything more than that, and failure.
But now it is 64 Mbyte. I think I've also tested the 11/780 emulation, 
with the same issue. However, it do work just fine with a 3900, which 
I've ran with 512 Mbyte without problems.
(Actually booting the same image.)
Anyone who might know what that is about?

(And of course, if anyone even tries this, they need to fix the boot 
block, and then I think there is still some problems with console I/O in 
NetBSD with the original code in combination with simh.)

Also, yes, the output here is from a load of code that is not checked 
into NetBSD at this time. I'll try and send things in once it's more in 
order. A lot of it only makes sense on a real 86x0, since simh does not 
emulate the full console system, but the partial emulation is nice as it 
is. Unfortunately, some of my code is just on a real 8650, which is in 
bits right now because it had to be moved around some.

        Johnny