From owner-freebsd-questions Wed Jun 7 17: 6:54 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id C098E37B8EC; Wed, 7 Jun 2000 17:06:45 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (elbas.partitur.se [193.219.246.222]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id CAA14915; Thu, 8 Jun 2000 02:06:32 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <393EE388.411D6E56@partitur.se> Date: Thu, 08 Jun 2000 02:06:32 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: sthaug@nethelp.no Cc: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: fxp0: device timeout - reboot required References: <393EBF45.B67A6655@partitur.se> <2148.960414026@verdi.nethelp.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. :( Thanks for input anyway! Cheers, Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message