Re: Lock order reversal in 5.2-CURRENT

On Tuesday 10 August 2004 03:40 pm, Terrence Koeman wrote:
> > -----Original Message-----
> > From: John Baldwin [mailto:jhb_at_FreeBSD.org]
> > Sent: Tuesday, August 10, 2004 21:35
> > To: freebsd-current_at_FreeBSD.org
> > Cc: Colin Percival; root_at_mediamonks.net
> > Subject: Re: Lock order reversal in 5.2-CURRENT
> >
> > On Tuesday 10 August 2004 02:45 pm, Colin Percival wrote:
> > > At 11:29 10/08/2004, Terrence Koeman wrote:
> > > >lock order reversal
> > > > 1st 0xc0645aa0 sched lock (sched lock) _at_
> > > > /usr/src/sys/vm/vm_zeroidle.c:156 2nd 0xc06748c0 sio (sio) _at_
> > > > /usr/src/sys/dev/sio/sio.c:3039
> > > >
> > > >This LOR is not on
> >
> > http://sources.zabbadoz.net/freebsd/lor.html, so I'm
> >
> > > >guessing this one locked up my system.
> > >
> > > This is LOR #013 on bzeeb's list.  There isn't any solution
> >
> > yet, but there
> >
> > > is a simple workaround: unplug the serial console.
> >
> > The real problem is that mi_switch panic'd:
> >
> > calltrap() at calltrap+0x5
> > --- trap 0xc, eip = 0xc04b3ed2, esp = 0xd4dd7c90, ebp = 0xd4dd7ce0 ---
> > mi_switch(1,0,c060d2be,9c,dbba0) at mi_switch+0x102
> >
> > Does the original poster have a debug kernel built?
>
> Yes I have, but I have no experience with the debugger. I'll be happy to
> carry out whatever's needed.

Just pull up gdb on the kernel.debug file in the kernel build directory and do 
'l *0xc04b3ed2'  (the value is the eip from above) to list the source line 
associated with the fault.

-- 
John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org