Date: Fri, 13 Feb 2004 13:35:53 -0500 (EST) From: Andre Guibert de Bruet <andy@siliconlandmark.com> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: current@freebsd.org Subject: Re: panic in 11th Feb current Message-ID: <20040213133320.F34361@alpha.siliconlandmark.com> In-Reply-To: <20040213112153.GA14493@stud.fit.vutbr.cz> References: <20040213094957.GA8898@stud.fit.vutbr.cz> <20040213112153.GA14493@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 13 Feb 2004, Divacky Roman wrote:
> > Source from the 11th indicates that this line number to points to a
> > vm_map_lock_read() call inside vm_map_lookup() which would be called on a
> > page fault.
>
> seems so
>
> > > stray iqr 9
> > > _mtx_lock_sleep: recursed on non-recursive mutex
> > > kern_mutex.c:436
> >
> > Ouch.
> >
> > > I have kernel dump which I can provide (but my kernel is not -g
> > > compiled)
> >
> > Run an "nm /boot/kernel/kernel |sort" and report the function names and
> > addresses of the functions just above and below the eip (0xc05babdc).
> >
> > Regards,
>
> is this enough?
>
> c05bab60 T _vm_map_unlock
> c05babc0 T _vm_map_lock_read
^^^^^^^^^^^^^^^^^
> c05bac50 T _vm_map_unlock_read
That EIP reflects the panic in vm_map_lock_read(). Was there another EIP
that was displayed on your screen for the the first fault?
Regards,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040213133320.F34361>