Re: I/O bus reset to fix CMD MSCP controllers (and probably others)

[Hans Rosenfeld <hans%netbsd.org@localhost>]

On Mon, Mar 31, 2025 at 06:47:16PM +0200, Johnny Billquist wrote:
> Do we know which model of VAX and which model of CMD controller this
> is?

Robert has a VAX 4000/200 (KA660) with a CMD CQD-223/M. George reported
the same issues on a VAX 4000/500A (KA681) with a CMD CQD-223/TM.

I got mine in a uVAX 3500, but I never tried NetBSD on that system, and
even if I did it would probably have just worked as that was around
NetBSD 1.6 / 2.0 time. It did fail to boot 4.3BSD, though, which is why
I replaced it with a Emulex UC07 in that system.


> It do seem we should expect a transition to step 1 within 100ms after a
> reset, and could do a second reset much faster (than 10s).

Yes.

> I don't agree that skipping this retrying in udaattach() is correct. Just
> because udamatch() was successful don't mean we can't have a fail to reset
> for some weird reason, at which point it should be retried at least once.

Sure. I was just saying that it apparently never caused a problem so
far, so I'm not too inclined to change it. :)

> And I can tell that I'm running with a CMD controller in my 11/93 and
> booting 2.11BSD just fine. Which means it goes through both of those
> initializations fine.

I have one in my 11/73, and yes, it works fine there.


Hans


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown