lockups with 5.0.7 & 2.0.33

[Patrick Michael Kane]

On Thu, Feb 19, 1998 at 11:08:31AM -0600, Doug Ledford wrote:
> Patrick Michael Kane wrote:
> > Hmmm.  I'll try this.
> 
> Let me know if it makes a difference.
> 
> > > > Oddly enough, the system seemed to work fine under a slackware
> > > > installation that was recently replaced with redhat 5.0.
> > >
> > > Older, slower version of the driver, less likely to max out bus transfer
> > > speeds I would guess :)
> > 
> > Nope.  The old install was running 2.0.33, as well.  That's what is baffling
> > me. If it is indeed a hardware problem, why didn't it manifest itself under
> > the previous install?
> 
> Well, a slackware 2.0.33 kernel != a RedHat 2.0.33 kernel :) Most
> distributors have either a mixture of their own patches, or specific config
> options they en/disable.  Possibly a difference in those config options
> could be part of it.  Of course, that isn't an answer if you use your own
> home grown kernel.
> 
> BTW, when you say lock-up, are you able to do things like switch VTs at all
> <ALT-Fx key stuff> or is the machine locked hard as in no interrupts what so
> ever?

No interrupts ever.

The machine is in Italy and I'm in San Francisco, so I will most likely not
be able to get the L2 settings toyed with until early next week.  I'll let
you know if that helps.  I'm also going to try to swap out for a
BusLogic/Mylex card and see if the problem still manifests itself.

-- 
Patrick Michael Kane
<modus at pr.es.to>

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