panic in rt_check_fib()

John Baldwin jhb at freebsd.org
Sat Sep 13 15:20:32 UTC 2008


On Saturday 13 September 2008 10:15:38 am Robert Watson wrote:
> On Sat, 13 Sep 2008, Robert Watson wrote:
> > On Fri, 5 Sep 2008, Giorgos Keramidas wrote:
> >> A kernel that I built last night to test Ed's "packet mode" for ptys
> >> included all the changes up to 182743 panics with:
> >
> > I had an identical panic on 7-STABLE last night:
> >
> > db> bt
> > Tracing pid 782 tid 100091 td 0xc4496440
> > kdb_enter_why(c0b25ea1,c0b25ea1,c0b24c19,e6772978,0,...) at
> > kdb_enter_why+0x3a
> > panic(c0b24c19,c0b32d59,c0b32d7a,633,c436c9b0,...) at panic+0x12c
> > _mtx_lock_sleep(c436ddf4,c4496440,0,c0b32d7a,633,...) at
> > _mtx_lock_sleep+0x4a
> > _mtx_lock_flags(c436ddf4,0,c0b32d7a,633,c436ca14,...) at
> > _mtx_lock_flags+0xd1
>
> This is actually from i386/machine/pcpu.h, line 194:
>
> static __inline struct thread *
> __curthread(void)
> {
>          struct thread *td;
>
>          __asm __volatile("movl %%fs:0,%0" : "=r" (td));
>          return (td);
> }

No, there is no "panic" message there.  Check the actual "panic" string, it's 
recursing on a non-recursable mutex.  I.e. it's trying to lock the same 
rtentry twice for some reason.

-- 
John Baldwin


More information about the freebsd-current mailing list