Subject: Re: Failure to boot -current...
To: Johnny Billquist <bqt@update.uu.se>
From: Anders Hjalmarsson <hjalmar@hjalmar.to>
List: port-vax
Date: 01/13/2005 21:02:32
I see something similar:

NetBSD 2.99.12 (MV3100-1-$Revision: 1.2 $) #4: Tue Jan 11 23:26:21 UTC 2005
        hjalmar@simh-vax.hjalmar.to:/var/obj/vax/compile/MV3100-1

MicroVAX 3100
cpu: KA41/42
cpu: Enabling primary cache, no secondary cache present
total memory = 16264 KB
avail memory = 14052 KB
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: interrupt mask 8
le0 at vsbus0 csr 0x200e0000 vec 120 ipl 14 maskbit 5 buf 0x20d000-0x21cfff
le0: address 08:00:2b:15:a2:de
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 304 ipl 14 maskbit 6
dz0: 4 lines
si0 at vsbus0 csr 0x200c0080 vec 770 ipl 14 maskbit 1
si0: NCR5380, SCSI ID 6
scsibus0 at si0: 8 targets, 8 luns per target
si1 at vsbus0 csr 0x200c0180 vec 774 ipl 14 maskbit 0
si1: NCR5380, SCSI ID 6
scsibus1 at si1: 8 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 3 lun 0: <DEC, RZ23     (C) DEC, 0A18> disk fixed
sd0(si0:0:3:0):  Check Condition on CDB: 0x00 00 00 00 00 00
    SENSE KEY:  Not Ready
     ASC/ASCQ:  Logical Unit Not Ready, Cause Not Reportable

sd0: drive offline
sd0: async, 8-bit transfers
boot device: le0
root on le0
nfs_boot: trying DHCP/BOOTP
nfs_boot: DHCP next-server: 192.168.1.3
nfs_boot: my_name=mv3100-1.hjalmar.to
nfs_boot: my_domain=hjalmar.to
nfs_boot: my_addr=192.168.1.17
nfs_boot: my_mask=255.255.255.0
nfs_boot: gateway=192.168.1.1
root on 192.168.1.3:/exp/root/mv3100-1
root file system type: nfs
Clock has lost 2 day(s) - CHECK AND RESET THE DATE.


Then nothing more. I have not had time to debug it.
This is 2.99.12 from some days ago. I had thought that it might be
a disk-access which hanged it (you can see it has a bad disk) since
I tried an older kernel compiled for a different machine (and which
did not include the si driver) some days before (before updating sources)
And it worked ok.
I have not had time to compile a new kernel for another vax

One thing though, it reponds to pings so even after the last message so
it is not quite dead.

-hjalmar