pre10 on a 2940u2w still shows BRKADRINT

[Doug Ledford]

Robert G. Brown wrote:

> Could such a problem survive power down?  What you describe certainly is
> consistent with my early experiences with a "working" pre7 driver, but
> only if I booted NT at least one time first (presumably it wrote
> everything and set all the parity bits?).  However, I would have
> expected that a COMPLETE power down (where I pull the plug in back and
> hit the power button one more time to drain the capacitors in the
> attempted ATX startup surge) would have reset everything to ground
> zero...

Yes, that should reset things to ground zero.

> Your problem reproducing it may be statistical.  Right now the odds of
> it occurring are first order estimate of 1/8, but by machine, not by
> bootup or powerdown.  You might try booting your system a bunch of times
> with pre3-pre7 -- it is quite possible that something in pre3 or pre4 is
> "toxic" enough that it corrupts the right places in a way that survives
> between boots (somehow).  Is there any chance that one of these drivers
> could have overwritten the Adaptec BIOS in any way or part (this may be
> a dumb question -- I don't really know how the BIOS flash works in the
> first place -- but if it is a matter of writing to the wrong part of the
> address space it seems possible which is why I ask).

No, I don't think it would effect the BIOS.  But, the bug I found that
enabled me to remove the FAILDIS flag from SEQCTL would worry me some. 
After all, the point was that the driver was writing to the cards registers
without pausing the sequencer first.  This is strictly required and when we
did it without the FAILDIS bit set, the sequencer let us know.  It's
possible this could have something to do with it.

-- 

 Doug Ledford  <dledford at dialnet.net>
  Opinions expressed are my own, but
     they should be everybody's.

To Unsubscribe: send mail to majordomo at FreeBSD.org
with "unsubscribe freebsd-aic7xxx" in the body of the message