Something wrong with (t)mscp scanning lately?

[Tom Ivar Helbekkmo <tih%hamartun.priv.no@localhost>]

Here's my 4000/700A with a TQK50 TMSCP controller, and a CMD CQD223 MSCP
SCSI controller with its TMSCP option disabled, running 5.1.1 from
January.  There's a single SCSI disk attached:

NetBSD 5.1.1 (GENERIC) #0: Thu Jan  5 02:17:53 UTC 2012
        
builds%b7.netbsd.org@localhost:/home/builds/ab/netbsd-5-1-1-RELEASE/vax/201201040549Z-obj/home/builds/ab/netbsd-5-1-1-RELEASE/src/sys/arch/vax/compile/GENERIC
VAX 4000/700A
total memory = 127 MB
avail memory = 121 MB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
cpu0 at mainbus0KA692, NVAX (ucode rev 2)
ze0 at mainbus0
ze0: hardware address 08:00:2b:2b:67:a6
shac at mainbus0 not configured
uba0 at mainbus0: Q22
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 4 model 14
mscpbus0: DMA burst size set to 4
mt0 at mscpbus0 drive 0: TK70
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 6 model 13
mscpbus1: DMA burst size set to 4
ra0 at mscpbus1 drive 0: RA90
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "mfpr" frequency 1000000 Hz quality 100
Kernelized RAIDframe activated
ra0: size 45322643 sectors
boot device: ra0
root on ra0a dumps on ra0b
root file system type: ffs

...and here she is, running current, cvs update done March 6th:

NetBSD 6.99.3 (GENERIC) #2: Mon Mar 12 14:39:25 CET 2012
        
root%athene.hamartun.priv.no@localhost:/usr/obj/sys/arch/vax/compile.vax/GENERIC
VAX 4000/700A
total memory = 127 MB
avail memory = 120 MB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
cpu0 at mainbus0KA692, NVAX (ucode rev 2)
ze0 at mainbus0
ze0: hardware address 08:00:2b:2b:67:a6
shac at mainbus0 not configured
uba0 at mainbus0: Q22
mtc0 at uba0 csr 174500 vec 774 ipl 17
mscpbus0 at mtc0: version 4 model 14
mscpbus0: DMA burst size set to 4
uda0 at uba0 csr 172150 vec 770 ipl 17
mscpbus1 at uda0: version 6 model 13
mscpbus1: DMA burst size set to 4
timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
timecounter: Timecounter "mfpr" frequency 1000000 Hz quality 100
mt0 at mscpbus0 drive 0: TK70
mt1 at mscpbus0 drive 0: TK70
ra0 at mscpbus1 drive 0: RA90
ra1 at mscpbus1 drive 0: RA90

Then, the kernel will hang there for a very long time, before continuing:

Kernelized RAIDframe activated
boot device: ra1
root on ra1a dumps on ra1b
root file system type: ffs

So, what could be causing it to see each device twice with the newer code?

-tih
-- 
"The market" is a bunch of 28-year-olds who don't know anything. --Paul Krugman