From owner-freebsd-questions@FreeBSD.ORG Fri Sep 26 06:22:51 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA78016A4B3 for ; Fri, 26 Sep 2003 06:22:51 -0700 (PDT) Received: from anon.securenym.net (anon.securenym.net [209.113.101.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 076BB43F3F for ; Fri, 26 Sep 2003 06:22:51 -0700 (PDT) (envelope-from dincht@securenym.net) Received: (from root@localhost) by anon.securenym.net (8.11.7/8.11.7) id h8QDH9816572 for freebsd-questions@freebsd.org.filtered; Fri, 26 Sep 2003 08:17:09 -0500 (CDT) Message-Id: <200309261317.h8QDH9816572@anon.securenym.net> X-Securenym: dincht From: "C. Ulrich" To: freebsd-questions@freebsd.org Content-Type: text/plain Organization: The Peter Jennings Fan Club Mime-Version: 1.0 Date: Fri, 26 Sep 2003 09:15:03 -0400 Content-Transfer-Encoding: 7bit Subject: preventing "watchdog timeout" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Sep 2003 13:22:51 -0000 If I boot FreeBSD 5.1-RELEASE with no cable attached to the NIC, I get a slew of "dc0: watchdog timeout" errors. Sometimes, I want to boot and run the system without being physically connected to the network. Is there any way to get rid of the timeout errors short of disabling networking all together? C. Ulrich -- http://bityard.net