From owner-freebsd-questions@FreeBSD.ORG Mon Dec 15 19:41:39 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C61A1065672 for ; Mon, 15 Dec 2008 19:41:39 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail4.sea5.speakeasy.net (mail4.sea5.speakeasy.net [69.17.117.6]) by mx1.freebsd.org (Postfix) with ESMTP id 66CB98FC20 for ; Mon, 15 Dec 2008 19:41:39 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 11866 invoked from network); 15 Dec 2008 19:41:38 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail4.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Dec 2008 19:41:38 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 05B1350826; Mon, 15 Dec 2008 14:41:37 -0500 (EST) To: Gennady Kudryashoff References: From: Lowell Gilbert Date: Mon, 15 Dec 2008 14:41:37 -0500 In-Reply-To: (Gennady Kudryashoff's message of "Mon\, 15 Dec 2008 10\:31\:16 +0300") Message-ID: <44y6yhns3y.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 7.1-RC1 rl0 watchdog timeout with custom kernel X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Dec 2008 19:41:39 -0000 Gennady Kudryashoff writes: > Hello, all! > > I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed. > There were no troubles with GENERIC kernel, but when I've compiled custom kernel, rl ethernet driver tells to the console a lot of errors: > > rl0: link state changed to UP > rl0: watchdog timeout > rl0: watchdog timeout > > Any mistake? The rl driver supports some really terrible hardware, so I'm far from convinced that your custom kernel is causing the problems. Perhaps you could check by switching back to a GENERIC kernel for a while. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/