Date: Tue, 22 May 2001 15:26:45 -0700 From: Doug Barton <DougB@DougBarton.net> To: Matt Dillon <dillon@earth.backplane.com> Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>, stable@FreeBSD.ORG Subject: Re: Continuing ahc problems - also cause fxp failure Message-ID: <3B0AE7A5.3DB34788@DougBarton.net> References: <200105220925.f4M9Paf00409@earth.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matt Dillon wrote:
>
> This is getting weirder and weirder.
>
> 4.2 or 4.3-RC
> AHC failure once or twice a month (as previously posted last month)
> FXP Ethernet (appeared to be) working perfectly
>
> RELENG_4 (After Justin's adaptec fix)
> FXP failure one week (old FXP driver)
> FXP failure the next week (old FXP driver)
> FXP *and* AHC failures tonight (new FXP driver)
>
> What I got tonight was basically a system lockup with the kernel
> generating console messages every few seconds from both the FXP
> and the AHC drivers. I *was* able to break into the debugger, but
> with ahc dead I couldn't generate a core. I think the system itself
> is fine and the problem is somewhere in the AHC or FXP drivers.
I think you have bad hardware. I've had ahc and fxp running on Intel ISP
2150's with various vintages of -stable, including recent 4.3-Stable at
work; and the same two drivers running -current on my workstation at home
for years... no problems like you describe.
Doug
--
I need someone really bad. Are you really bad?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B0AE7A5.3DB34788>