Okay, here's the dmesg, DEBUG kernel with verbosity.

NetBSD 1.4P (TERRAN) #0: Sat Dec 11 15:08:58 PST 1999
    bard@terran.globalesi.com:/usr/src/sys/arch/alpha/compile/TERRAN
AlphaServer 4X00 5/533 4MB, 531MHz
8192 byte page size, 2 processors.
total memory = 512 MB
(2064 KB reserved for PROM, 509 MB used by NetBSD)
avail memory = 470 MB
using 3276 buffers containing 26208 KB of memory
mainbus0 (root)
cpu0 at mainbus0: ID 0 (primary), 21164A-2 (pass 2)
cpu0: VAX FP support, IEEE FP support, Primary Eligible
cpu1 at mainbus0: ID 1, 21164A-2 (pass 2)
cpu1: VAX FP support, IEEE FP support
mcbus0 at mainbus0
mcmem0 at mcbus0 mid 1: Memory
mcpcia0 at mcbus0 mid 5: PCI Bridge
mcpcia0: Horse Revision 3, Left Handed Saddle Revision 0, CAP Revision 2
pci0 at mcpcia0 bus 0
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
ncr0 at pci0 dev 1 function 0: ncr 53c810 fast10 scsi
ncr0: interrupting at kn300 irq 36
ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo
ncr0: single-ended, open drain IRQ driver
ncr0: restart (scsi reset).
scsibus0 at ncr0: 8 targets, 8 luns per target
isp0 at pci0 dev 2 function 0
Qlogic ISP Driver, NetBSD (pci) Platform Version 0.997 Core Version 1.11
isp0: interrupting at kn300 irq 40
isp0: Ultra Mode Capable
isp0: Board Revision 1040B, loaded F/W Revision 7.65.0
isp0: Last F/W revision was 5.57.1
isp0: 124 max I/O commands supported
isp0: driver initiated bus reset of bus 0
scsibus1 at isp0: 16 targets, 8 luns per target
mcpcia1 at mcbus0 mid 4: PCI Bridge
mcpcia1: Horse Revision 3, Left Handed Saddle Revision 0, CAP Revision 2
pci1 at mcpcia1 bus 0
pci1: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pceb0 at pci1 dev 1 function 0: Intel 82375EB/SB PCI-EISA Bridge (PCEB) (rev.
0x15)
vga0 at pci1 dev 2 function 0: S3 Trio32/64 (rev. 0x54)
wsdisplay0 at vga0: console (80x25, vt100 emulation)
de0 at pci1 dev 3 function 0
de0: interrupting at kn300 irq 12
de0: 21140A [10-100Mb/s] pass 2.2
de0: address 00:40:05:41:a4:0e
isp1 at pci1 dev 4 function 0
isp1: interrupting at kn300 irq 16
isp1: Ultra Mode Capable
isp1: Board Revision 1040B, loaded F/W Revision 7.65.0
isp1: Last F/W revision was 5.57.1
isp1: 124 max I/O commands supported
isp1: driver initiated bus reset of bus 0
scsibus2 at isp1: 16 targets, 8 luns per target
eisa0 at pceb0
isa0 at pceb0
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0
lpt0 at isa0 port 0x3bc-0x3bf irq 7
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
isabeep0 at pcppi0
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
mcbus0 mid 2: CPU 4MB BCache
scsibus0: waiting 2 seconds for devices to settle...
de0: enabling 100baseTX port
cd0 at scsibus0 targ 5 lun 0: <DEC, RRD46   (C) DEC, 1337> SCSI2 5/cdrom
removable
probe(ncr0:5:1): 10.0 MB/s (100 ns, offset 8)
scsibus1: waiting 2 seconds for devices to settle...
scsibus2: waiting 2 seconds for devices to settle...
isp1: Bus 0 Target 0 Async Mode
sd0 at scsibus2 targ 0 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct
fixed
sd0: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
isp1: Bus 0 Target 2 Async Mode
sd1 at scsibus2 targ 2 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct
fixed
sd1: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
isp1: Bus 0 Target 4 Async Mode
sd2 at scsibus2 targ 4 lun 0: <DEC, RZ1CB-CA (C) DEC, LYJ0> SCSI2 0/direct
fixed
sd2: 4091 MB, 3708 cyl, 20 head, 113 sec, 512 bytes/sect x 8380080 sectors
raidattach: Asked for 4 units
Kernelized RAIDframe activated
WARNING: can't figure what device matches "SCSI 0 4 0 0 0 6000 10201077"
root on sd0a dumps on sd0b
isp1: channel 0 target 0 can do SYNC xfers
isp1: channel 0 target 0 can do WIDE xfers
isp1: channel 0 target 0 can do TAGGED xfers
isp1: Bus 0 Target 0 at 20MHz Max Offset 8, 16 bit wide, Tagged Queueing
Enabled
isp1: Bus 0 Target 0 at 20MHz Max Offset 8, 16 bit wide, Tagged Queueing
Enabled
isp1: Bus 0 Target 0 at 20MHz Max Offset 8, 16 bit wide, Tagged Queueing
Enabled
readclock: 99/12/11/23/16/49=>944954209 (944953931)
init: copying out path `/sbin/init' 11

Now the messages after 'raidctl -C /etc/raidcfg raid0':

Dec 11 15:23:30 terran /netbsd: RAIDFRAME: protectedSectors is 64
Dec 11 15:23:30 terran /netbsd: isp1: channel 0 target 2 can do SYNC xfers
Dec 11 15:23:30 terran /netbsd: isp1: channel 0 target 2 can do WIDE xfers
Dec 11 15:23:30 terran /netbsd: isp1: channel 0 target 2 can do TAGGED xfers
Dec 11 15:23:30 terran /netbsd: isp1: Bus 0 Target 2 at 20MHz Max Offset 8, 16
bit wide, Tagged Queueing Enabled
Dec 11 15:23:30 terran /netbsd: sd1: no disk label
Dec 11 15:24:58 terran /netbsd: isp1: command for target 2 lun 0 was aborted
Dec 11 15:24:58 terran /netbsd: stray kn300 irq 8
Dec 11 15:25:28 terran /netbsd: isp1: command for target 2 lun 0 was aborted
Dec 11 15:25:28 terran /netbsd: stray kn300 irq 8

Could this be related to the recent changes to mcpcia.c to recognise the <3
PCI busses in the 1200 variant?  Is there cruft left over elsewhere from the
kn300 define that hasn't been updated?  (Armchair troubleshooting by a
nonprogrammer, there :)

TVMIA,
dhop

Matthew Jacob wrote:

> That is very very strange. I have no idea.
>
> It's strange on two counts- one that it goes to the empty controller. And,
> second, that you get this aborted command.
>
> This looks more like a misdirected interrupt (kn300) than a Qlogic
> problem. Can you build a DEBUG kernel and publish the full boot messages?
>
> You know, it's too bad that Jason nuked the messages I used to have in the
> kernel- the stray interrupts could then be specifically bound to a
> specific bus and PCI slot.
>
> On Mon, 13 Dec 1999, David Hopper wrote:
>
> > I have two Qlogic 1040B's:  an isp0 with three Seagate 4-gig drives, and
> > an isp1 that isn't hooked up to anything.  The system is on the first
> > disk, sd0a, on isp0, and I'm trying to stripe the remaining two disks at
> > sd1a and sd2a, again, all three disks on isp0.  I get the following
> > errors when I run raidctl -C /etc/raidcfg raid0:
> >
> > isp1: command for target 4 lun 0 was aborted
> > stray kn300 irq 8
> > [...]
> > ad infinitum: the process continues to attempt the RAID creation,
> > failing each time on the empty controller.  Why is it hitting this
> > controller??
> >
> > Here's my /etc/raidcfg:
> >
> > START disks
> > /dev/sd1a
> > /dev/sd2a
> >
> > START layout
> > 32 1 1 0
> >
> > START queue
> > fifo 100
> >
> > I'm using the platform .997, Core 1.11 Qlogic driver from the 12/11/99
> > sources, and a hand-rolled kernel with the DEC_KN300 and RAID defines.
> >
> > Any thoughts?
> > dhop
> >
> >
> >
> >