From owner-freebsd-current@FreeBSD.ORG Tue Sep 2 15:34:59 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EC82106582D; Tue, 2 Sep 2008 15:34:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id E50488FC2C; Tue, 2 Sep 2008 15:34:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m82FYMYe015249; Tue, 2 Sep 2008 11:34:51 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Julian Elischer Date: Tue, 2 Sep 2008 10:36:53 -0400 User-Agent: KMail/1.9.7 References: <200808291636.10656.jhb@FreeBSD.org> <48B86BB3.30705@elischer.org> In-Reply-To: <48B86BB3.30705@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200809021036.53908.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Tue, 02 Sep 2008 11:34:51 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8140/Tue Sep 2 11:02:13 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: current@freebsd.org Subject: Re: rtentry panic with FIB 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: Tue, 02 Sep 2008 15:34:59 -0000 On Friday 29 August 2008 05:35:47 pm Julian Elischer wrote: > John Baldwin wrote: > > Unfortunately it hung trying to dump, so all I have is the stack trace from > > DDB. This is recent HEAD running stress2 > > > > panic: _mtx_lock_sleep: recursed on non-recursive mutex rtentry @ ../../1 > > > > do you know what lock it was talking about? All I have is what I included in the original e-mail. So it's an "rtentry" mutex, but that's all I know. You can try running the 'udp' test from stress2 locally perhaps to see if you can trigger it. -- John Baldwin