From owner-freebsd-stable  Tue May 22 15:27: 5 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55])
	by hub.freebsd.org (Postfix) with ESMTP id 52BDF37B422
	for <stable@FreeBSD.ORG>; Tue, 22 May 2001 15:27:02 -0700 (PDT)
	(envelope-from DougB@DougBarton.net)
Received: from DougBarton.net (master [10.0.0.2])
	by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA98424;
	Tue, 22 May 2001 15:26:45 -0700 (PDT)
	(envelope-from DougB@DougBarton.net)
Message-ID: <3B0AE7A5.3DB34788@DougBarton.net>
Date: Tue, 22 May 2001 15:26:45 -0700
From: Doug Barton <DougB@DougBarton.net>
Organization: Triborough Bridge & Tunnel Authority
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
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
References: <200105220925.f4M9Paf00409@earth.backplane.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

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