Date: Tue, 2 Sep 2008 16:13:57 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: John Baldwin <jhb@freebsd.org> Cc: Julian Elischer <julian@elischer.org>, FreeBSD current mailing list <current@freebsd.org> Subject: Re: rtentry panic with FIB Message-ID: <20080902161225.C65801@maildrop.int.zabbadoz.net> In-Reply-To: <200809021036.53908.jhb@freebsd.org> References: <200808291636.10656.jhb@FreeBSD.org> <48B86BB3.30705@elischer.org> <200809021036.53908.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Sep 2008, John Baldwin wrote: > 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. I had a look at the function and the locking looked strange (possibly because of the goto and label in the middle). Could you find the line number (surrounding code block) for: >>> rt_check_fib() at rt_check_fib+0x1ea /bz -- Bjoern A. Zeeb Stop bit received. Insert coin for new game.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080902161225.C65801>