From owner-freebsd-current@FreeBSD.ORG Wed Jul 12 22:57:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 ABAD416A4DE for ; Wed, 12 Jul 2006 22:57:18 +0000 (UTC) (envelope-from goto@snowy.to) Received: from mail.snowy.to (mail.snowy.to [219.166.73.149]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F9CD43D4C for ; Wed, 12 Jul 2006 22:57:16 +0000 (GMT) (envelope-from goto@snowy.to) Received: (qmail 77711 invoked from network); 13 Jul 2006 07:57:15 +0900 Received: from unknown (HELO snowy.to) (0.0.0.0) by 0.0.0.0 with SMTP; 13 Jul 2006 07:57:15 +0900 Date: Thu, 13 Jul 2006 07:57:14 +0900 (JST) Message-Id: <20060713.075714.41630956.goto@snowy.to> To: wpaul@FreeBSD.ORG From: Yoshikazu GOTO In-Reply-To: <20060712194701.6AFF516A4DE@hub.freebsd.org> References: <20060712.101453.74755604.goto@snowy.to> <20060712194701.6AFF516A4DE@hub.freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, imp@bsdimp.com Subject: Re: if_re does not work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 12 Jul 2006 22:57:18 -0000 Hi, In Message-ID: <20060712194701.6AFF516A4DE@hub.freebsd.org> wpaul@FreeBSD.ORG (Bill Paul) wrote : > > > > You can try the following patch. It just papers over the problem... > > > > Thank you for your reply and patch. > > > > I tried it, but I caught error messages as follows: > > > > ---- start ---- > > << boot sequence (dhclient on em0) >> > > re0: link state changed to DOWN > > panic: mutex re0 not owned at /usr/src/sys/kern/kern_mutex.c:405 > > cpuid = 0 > > KDB: enter: panic > > [thread pid 414 tid 100054 ] > > Stopped at kdb_enter+0x2b: nop > > db> > > ---- end ---- > > At this point, you should have typed 'bt' at the debugger prompt > and obtained a backtrace so we can see where in the driver code > the problem is occuring. > > Sadly, you did not, so the problem remains a mystery. When "db>" was printed, I can't input any key. The least I could do was to push my power switch. Goto. -=-=-=- // Yoshikazu GOTO // E-mail: goto@snowy.to -=-=-=- \e