From owner-freebsd-amd64@FreeBSD.ORG Thu Jan 10 05:20:02 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CE0A16A41B for ; Thu, 10 Jan 2008 05:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 653B113C501 for ; Thu, 10 Jan 2008 05:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0A5K2mh024414 for ; Thu, 10 Jan 2008 05:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0A5K2hV024405; Thu, 10 Jan 2008 05:20:02 GMT (envelope-from gnats) Date: Thu, 10 Jan 2008 05:20:02 GMT Message-Id: <200801100520.m0A5K2hV024405@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Peter Wemm" Cc: Subject: Re: amd64/119516: panic: _mtx_lock_sleep: recursed on non-recursive mutex rtentry @ /usr/src/sys/net/route.c:1287 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Peter Wemm List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2008 05:20:02 -0000 The following reply was made to PR amd64/119516; it has been noted by GNATS. From: "Peter Wemm" To: "Niels Bakker" Cc: freebsd-gnats-submit@freebsd.org Subject: Re: amd64/119516: panic: _mtx_lock_sleep: recursed on non-recursive mutex rtentry @ /usr/src/sys/net/route.c:1287 Date: Wed, 9 Jan 2008 20:44:41 -0800 I think this is the same problem that I reported in kern/116172. I have a user-mode ipv6 tunnel using tun0. If I have active ssh sessions while I reboot, the tunnel driver is killed instantly at the first sigterm. The machine then panics with the same recursive mutex problems that you describe above as it tries to send the tcp resets from ssh/sshd while tun0 is being torn down and routes being destroyed. Sorry that's no help to you. But you're not alone. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5