I've noticed some problems with 1.6ZG for the VAX.  I've been running
1.6ZG GENERIC on a VS4000/VLC (KA48) for around two days now without
problems.  However, When I try to run the same kernel and binaries on
either my MicroVAX 3100/20e (KA41) or my VAXstation 3100/M76 (KA43),
the kernel panics in the following manner just as it begins the
filesystem checks
during boot up:


>>> b dka500


-DKA500
>> NetBSD/vax boot [1.11 Wed Dec 10 05:41:59 EST 2003] <<
>> Press any key to abort autoboot 0
nfs_open: must mount first.
open netbsd.vax: Device not configured
> boot netbsd
1716624+242976 [165568+129762]=0x226a90
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003
    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 1.6ZG (GENERIC) #4: Wed Dec 10 06:31:00 EST 2003

root@duh:/u0/work/netbsd-current/src/sys/arch/vax/compile/obj/GENERIC

VAXstation 3100/m76
cpu: KA43
primary cache status: 1a<HIT,REFRESH,ENABLE>
secondary cache status: ffe1<TPE,DPE,MISS,ENABLE>
total memory = 32636 KB
avail memory = 27232 KB
using 433 buffers containing 1732 KB of memory
sysctl_createv: sysctl_create(console_device) returned 17
mainbus0 (root)
vsbus0 at mainbus0
vsbus0: interrupt mask 8
le0 at vsbus0 csr 0x200e0000 vec 120 ipl 14 maskbit 5 buf
0x28573000-0x28582fff
le0: address 08:00:2b:1e:59:c3
le0: 32 receive buffers, 8 transmit buffers
dz0 at vsbus0 csr 0x200a0000 vec 304 ipl 14 maskbit 6
dz0: 4 lines
lkkbd0 at dz0
wskbd0 at lkkbd0 (mux ignored)
lkms0 at dz0
wsmouse0 at lkms0 (mux ignored)
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
smg0 at vsbus0 csr 0x200f0000 vec 104 ipl 14 maskbit 3
wsdisplay0 at smg0 (kbdmux ignored)
wsdisplay0: screen 0-7 added (128x57, vt100 emulation)
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 1 lun 0: <MICROP, 4221-09 1128RVAV, RVAV> disk fixed
sd0: 1955 MB, 4049 cyl, 9 head, 109 sec, 512 bytes/sect x 4004219 sectors
sd0: async, 8-bit transfers
cd0 at scsibus0 target 4 lun 0: <SONY, CD-ROM CDU-8003A, 1.9a> cdrom removable
cd0: async, 8-bit transfers
sd1 at scsibus0 target 5 lun 0: <SEAGATE, ST32171N, 0360> disk fixed
sd1: 2061 MB, 5168 cyl, 5 head, 163 sec, 512 bytes/sect x 4222640 sectors
sd1: async, 8-bit transfers
boot device: sd1
root on sd1a dumps on sd1b
root file system type: ffs
Thu Dec 11 04:38:46 UTC 2003
swapctl: adding /dev/sd1b as swap device at priority 0
Starting file system checks:
panic: lockmgr: no context
Stopped at      netbsd:lockmgr+0x66:    movab   lwp0, r2
db>

It also happens if I boot up into single user mode and manually invoke
fsck on /dev/rsd1a.

-brian.