From owner-freebsd-current@FreeBSD.ORG  Wed Jul 12 19:47:01 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 618)
	id 6AFF516A4DE; Wed, 12 Jul 2006 19:47:01 +0000 (UTC)
In-Reply-To: <20060712.101453.74755604.goto@snowy.to> from Yoshikazu GOTO at
	"Jul 12, 2006 10:14:53 am"
To: goto@snowy.to (Yoshikazu GOTO)
Date: Wed, 12 Jul 2006 19:47:01 +0000 (GMT)
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20060712194701.6AFF516A4DE@hub.freebsd.org>
From: wpaul@FreeBSD.ORG (Bill Paul)
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2006 19:47:01 -0000


> > 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.

-Bill

--
=============================================================================
-Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
                 wpaul@windriver.com | Wind River Systems
=============================================================================
              <adamw> you're just BEGGING to face the moose
=============================================================================