panic in 11th Feb current

[Andre Guibert de Bruet]

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/    >