From owner-freebsd-questions Thu Dec 7 6:43:39 2000 From owner-freebsd-questions@FreeBSD.ORG Thu Dec 7 06:43:35 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from xena.gsicomp.on.ca (cr677933-a.ktchnr1.on.wave.home.com [24.43.230.149]) by hub.freebsd.org (Postfix) with ESMTP id B906B37B401 for ; Thu, 7 Dec 2000 06:43:34 -0800 (PST) Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18]) by xena.gsicomp.on.ca (8.9.3/8.9.3) with SMTP id JAA64812; Thu, 7 Dec 2000 09:43:32 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <001901c0605c$9c32da50$1200a8c0@gsicomp.on.ca> From: "Matthew Emmerton" To: "Mike Galvez" , References: <20001207085336.A303@m.mail.virginia.edu> Subject: Re: failed to force tx and rx to idle state... dang Date: Thu, 7 Dec 2000 09:47:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I hope someone has some wisdom to share (other than not using cheap NICs). I have > a Netgear FA 310tx installed on my 4.0 FreeBSD box. It has worked fine for the > last couple of months but occasionally I get the following message: > > dc0: failed to force tx and rx to idle state > > Until I can get a better NIC, is there a way to restart/reset this hardware > without having to take the server down? Have you tried 'ifconfig dc0 down' followed by 'ifconfig dc0 up'? -- Matthew Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message