Subject: Re: problems with KZPCM-DA card
To: Michael L. Hitch <mhitch@lightning.msu.montana.edu>
From: Rumi Szabolcs <rumi_ml@rtfm.hu>
List: port-alpha
Date: 07/08/2004 01:32:55
Hello!

I have now compiled a custom SMP kernel including Michael L. Hitch's patch
for the machine having the KZPCM-DA and here is what I got:

-----8<-------------------------------------------------------------------

NetBSD 2.0_BETA (CUSTOM) #0: Thu Jul  8 01:06:03 CEST 2004
        root@iceberg.ipn.dynaweb.hu:/usr/src/sys/arch/alpha/compile/CUSTOM
DIGITAL Server 7000 Model 7305 6533A 5/533 4MB, 531MHz, s/n PY84800391
8192 byte page size, 2 processors.
total memory = 512 MB
(2064 KB reserved for PROM, 509 MB used by NetBSD)
avail memory = 495 MB
mainbus0 (root)
cpu0 at mainbus0: ID 0 (primary), 21164A-2
cpu0: Architecture extensions: 1<BWX>
cpu1 at mainbus0: ID 1, 21164A-2
cpu1: Architecture extensions: 1<BWX>
mcbus0 at mainbus0: 4MB BCache
mcmem0 at mcbus0 mid 1: Memory
mcpcia0 at mcbus0 mid 5: PCI Bridge
mcpcia0: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2
pci0 at mcpcia0 bus 0
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
siop0 at pci0 dev 1 function 0: Symbios Logic 53c810 (fast scsi)
siop0: interrupting at kn300 irq 36
scsibus0 at siop0: 8 targets, 8 luns per target
ppb0 at pci0 dev 2 function 0: Digital Equipment DECchip 21152 PCI-PCI Bridge (rev. 0x02)
pci1 at ppb0 bus 2
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
esiop0 at pci1 dev 0 function 0: Symbios Logic 53c875 (ultra-wide scsi)
esiop0: using on-board RAM
esiop0: interrupting at kn300 irq 40
scsibus1 at esiop0: 16 targets, 8 luns per target
esiop1 at pci1 dev 1 function 0: Symbios Logic 53c875 (ultra-wide scsi)
esiop1: using on-board RAM
esiop1: interrupting at kn300 irq 41
scsibus2 at esiop1: 16 targets, 8 luns per target
tlp0 at pci1 dev 2 function 0: DECchip 21140A Ethernet, pass 2.2
tlp0: interrupting at kn300 irq 42
tlp0: Ethernet address 00:06:2b:00:0b:ac
nsphy0 at tlp0 phy 5: DP83840 10/100 media interface, rev. 1
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
mcpcia1 at mcbus0 mid 4: PCI Bridge
mcpcia1: Horse Revision 3, Left Handed Saddle Revision 3, CAP Revision 2
pci2 at mcpcia1 bus 0
pci2: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pceb0 at pci2 dev 1 function 0: Intel 82375EB/SB PCI-EISA Bridge (PCEB) (rev. 0x15)
vga0 at pci2 dev 2 function 0: S3 Trio32/64 (rev. 0x54)
wsdisplay0 at vga0 (kbdmux ignored): console (80x25, vt100 emulation)
eisa0 at pceb0
isa0 at pceb0
lpt0 at isa0 port 0x3bc-0x3bf irq 7
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 (mux ignored): console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 (mux ignored)
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
mcclock0 at isa0 port 0x70-0x71: mc146818 or compatible
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
Kernelized RAIDframe activated
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
scsibus2: waiting 2 seconds for devices to settle...
cd0 at scsibus0 target 5 lun 0: <DEC, RRD46   (C) DEC, 1337> cdrom removable
cd0: sync (100.00ns offset 8), 8-bit (10.000MB/s) transfers
sd0 at scsibus1 target 0 lun 0: <QUANTUM, VIKING II 4.5SCA, 5520> disk fixed
sd0: 4095 MB, 5899 cyl, 10 head, 142 sec, 512 bytes/sect x 8388315 sectors
sd0: sync (50.00ns offset 16), 16-bit (40.000MB/s) transfers, tagged queueing
root on sd0a dumps on sd0b
root file system type: ffs
stray kn300 irq 42
wsdisplay0: screen 1 added (80x25, vt100 emulation)
wsdisplay0: screen 2 added (80x25, vt100 emulation)
wsdisplay0: screen 3 added (80x25, vt100 emulation)
wsdisplay0: screen 4 added (80x25, vt100 emulation)

-----8<------------------------------------------------------------------

Generally, the system boots and seems to work properly, although I haven't
tested it under heavy load yet.

There is that "stray kn300 irq 42" message which is the tulip NIC on the
KZPCM-DA, well, that network interface actually does seem to work: I have
pingflooded it rather heavily and I could not induce any packet loss, nor
any more stray irq messages. Comments?

Regards,

Szabolcs Rumi