Date: Mon, 20 Nov 2006 13:26:46 -0500 From: John Baldwin <jhb@freebsd.org> To: "Rong-en Fan" <grafan@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: panic in _mtx_lock_sleep() from unp_gc() (Was: LOR (intr table and sio) and instability) Message-ID: <200611201326.47309.jhb@freebsd.org> In-Reply-To: <6eb82e0611171708i1c29963dj4037f651f7294147@mail.gmail.com> References: <6eb82e0611171708i1c29963dj4037f651f7294147@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 17 November 2006 20:08, Rong-en Fan wrote: > > This is a bug we just ran into at work. It's not currently fixed in FreeBSD. > > Once we have a known good fix it'll make it into FreeBSD. > > You mean doadump and no core reported by savecore or the panic I > encountered? Anyway, this box just panic with the same backtrace again. > Console ddb backtrace and kgdb output are attached below. I will keep > this core available. The unp_gc() panic. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611201326.47309.jhb>