From owner-freebsd-hardware  Wed Jun  7 14:40:38 2000
Delivered-To: freebsd-hardware@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by hub.freebsd.org (Postfix) with SMTP id A321D37B8BE
	for <freebsd-hardware@freebsd.org>; Wed,  7 Jun 2000 14:40:32 -0700 (PDT)
	(envelope-from sthaug@nethelp.no)
Received: (qmail 2150 invoked by uid 1001); 7 Jun 2000 21:40:26 +0000 (GMT)
To: girgen@partitur.se
Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org
Subject: Re: fxp0: device timeout - reboot required
From: sthaug@nethelp.no
In-Reply-To: Your message of "Wed, 07 Jun 2000 23:31:49 +0200"
References: <393EBF45.B67A6655@partitur.se>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Wed, 07 Jun 2000 23:40:26 +0200
Message-ID: <2148.960414026@verdi.nethelp.no>
Sender: owner-freebsd-hardware@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I've seen it happen twice in a weeks time on our server, that
> has always been rock stable before:
> 
> fxp0: device timeout   (many many times, repeated in syslog)
> 
> The machine does not answer to ping.

I see you're using the fxp driver in combination with the ncr driver.
Have you considered using the sym driver instead? That has cured a
number of stability problems for us.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


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