Hot buttered damn.  Break out the champagne and add another variant to the website.

NetBSD 1.4P (ALPHA) #10: Thu Dec  9 11:33:39 PST 1999
     mjacob@nobble:/usr/src/sys/arch/alpha/compile/ALPHA
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 = 468 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

*dances a little jig*

Oh, wait, I'm the only one in the world that has one.

Thanks, Matthew.  Thanks a huge ton.  +thanks for everyone else for the 1200-specific
code.
dhop

Matthew Jacob wrote:

> Well, at the very least my presumption about mailbox register 2 containing
> the ordinal bus where resets are detected even for 1040 f/w is wrong
> (ambiguous Qlogic documents- for dual channel controllers an async event
> like a bus reset has to say for which bus the reset happened- but I guess
> Qlogic pooched it and just didn't make this generally true for all hbas..)
> but that's pettifoggery..
>
> On Thu, 9 Dec 1999, David Hopper wrote:
>
> > I can't get to the error.  The boot process occurs normally, and the
> > error manifests itself only in userland.  I get a healthy dmesg, some
> > of which I've quoted below. Upon running a newfs, either from sysinst
> > or from a shell, the system slams a millisecond worth of debug (how do
> > I get to this?) to the screen and hard resets.
>
> Ow. I think this is very likely due to the bug in isp_netbsd.c that didn't
> get checked in until 12/5. I sent you (under separate email) a ALPHA
> kernel from this morning. See if that helps.
>
> >
> > 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...
> > 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...
> > de0: enabling 10baseT port
> > scsibus2: waiting 2 seconds for devices to settle...
> > isp1: SCSI bus 0 reset detected
> > 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: SCSI bus 2 reset detected
> > 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: SCSI bus 4 reset detected
> > 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
> > md0: internal 4650K image area
> > WARNING: can't figure what device matches "DVA 0 1000 0 0 0 8086 0002"
> > root on md0a dumps on md0b
> > root file system type:ffs
> > Terminal type? [vt100]
> >
> > The warning above refers to the floppy drive, which is probed as fd0 earlier in the
> > dmesg just fine.
> >
> > Thanks,
> > dhop