From owner-freebsd-questions Wed Jun 7 17:21:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 9C47837BE0A; Wed, 7 Jun 2000 17:21:46 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id F03392B2CF; Wed, 7 Jun 2000 19:21:45 -0500 (CDT) Date: Wed, 7 Jun 2000 17:21:45 -0700 From: Paul Saab To: Palle Girgensohn Cc: sthaug@nethelp.no, freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required Message-ID: <20000607172145.A72618@elvis.mu.org> References: <393EBF45.B67A6655@partitur.se> <2148.960414026@verdi.nethelp.no> <393EE388.411D6E56@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <393EE388.411D6E56@partitur.se>; from girgen@partitur.se on Thu, Jun 08, 2000 at 02:06:32AM +0200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Palle Girgensohn (girgen@partitur.se) wrote: > sthaug@nethelp.no wrote: > > > > > 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. > > Hi Steinar, > > No, I haven't considered that. I will, when upgrading to > fbsd-4. It seems that the sym driver is not available before > release-4.0. :( The sym driver is in 3.4-STABLE. -- Paul Saab Technical Yahoo paul@mu.org - ps@yahoo-inc.com - ps@freebsd.org Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message