From owner-freebsd-questions Thu Dec 7 5:49:11 2000 From owner-freebsd-questions@FreeBSD.ORG Thu Dec 7 05:49:09 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from humpty.finadmin.virginia.edu (humpty.finadmin.Virginia.EDU [128.143.87.245]) by hub.freebsd.org (Postfix) with ESMTP id 44E6037B400 for ; Thu, 7 Dec 2000 05:49:09 -0800 (PST) Received: (from mrg8n@localhost) by humpty.finadmin.virginia.edu (8.9.3/8.9.3) id IAA00419 for questions@freebsd.org; Thu, 7 Dec 2000 08:53:36 -0500 (EST) (envelope-from mrg8n) Date: Thu, 7 Dec 2000 08:53:36 -0500 From: Mike Galvez To: questions@freebsd.org Subject: dc0: failed to force tx and rx to idle state... dang Message-ID: <20001207085336.A303@m.mail.virginia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD Sender: mrg8n@virginia.edu 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 This message will appear on the console every now and then but yesterday and today, I get this message and the NIC just quits, or seems to. ifconfig dc0 shows it to be up and you can ping it from the console but its not sending packets over the lan. Until I can get a better NIC, is there a way to restart/reset this hardware without having to take the server down? Thanks -- Michael Galvez Computer Systems Sr. Engineer Office: 804-982-2975 Financial Analysis E-Mail: mrg8n@virginia.edu University of Virginia Messenger Mail: Carruthers Hall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message