Date: Thu, 19 Feb 1998 11:08:31 -0600 From: Doug Ledford <dledford@dialnet.net> To: Patrick Michael Kane <modus@pr.es.to> Cc: aic7xxx Mailing List <AIC7xxx@FreeBSD.ORG> Subject: Re: lockups with 5.0.7 & 2.0.33 Message-ID: <34EC670F.5F7EBD32@dialnet.net> References: <19980218192458.33178@pr.es.to> <34EC2648.DC854610@dialnet.net> <19980219080045.60695@pr.es.to>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
--
Doug Ledford <dledford@dialnet.net>
Opinions expressed are my own, but
they should be everybody's.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34EC670F.5F7EBD32>