From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 04:41:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1748B16A50F for ; Fri, 10 Dec 2004 04:41:38 +0000 (GMT) Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com [204.228.228.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id A957E43D5A for ; Fri, 10 Dec 2004 04:41:37 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 85027 invoked by uid 89); 10 Dec 2004 04:40:43 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 10 Dec 2004 04:40:43 -0000 Received: from 63.231.165.87 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Thu, 9 Dec 2004 21:40:43 -0700 (MST) Message-ID: <54799.63.231.165.87.1102653643.squirrel@63.231.165.87> Date: Thu, 9 Dec 2004 21:40:43 -0700 (MST) From: "Ryan Sommers" To: current@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: dc(4) oddity X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 04:41:38 -0000 Since about two days ago a box had been spewing: dc0: watchdog timeout every 10-15 seconds. Network connectivity was nonexistant. I tried down/uping the device, reboots, network plug, anything I could think of. Nothing helped. And this box has been running since FreeBSD 6.0-CURRENT #6: Tue Sep 28 16:48:13 CDT 2004 without problems. Not constantly, it goes up in the morning and down at night. Switch lights were active the during the whole 'scrolling timeout' period. I was about ready to call it a bad network card when all of a sudden I switched the KVM back over to it and I see dc0: failed to force tx and rx to idle state as the last message on the console. No scrolling watchdog timeouts. Interesting I thought. I down'ed the interface and brought it back up and tried pinging the router. Success. So, after about 36 hours of watchdog timeouts it came back to life. Any idea what this might be? -- Ryan Sommers ryans@gamersimpact.com