Re: kern/68442: panic - acquiring duplicate lock of same type: "sleepq chain"

On Tuesday 29 June 2004 12:30 pm, Daniel Lang wrote:
> Hi,
>
> [ I removed PR-audit address and Bjoern, continue on -current ]
>
> John Baldwin wrote on Tue, Jun 29, 2004 at 12:00:12PM -0400:
> > > LOR2:
> > > [..]
> > > acquiring duplicate lock of same type: "sleepq chain"
> > >  1st Giant _at_ /usr/src/sys/kern/uipc_syscalls.c:1735
> > >  2nd sleepq chain _at_ /usr/src/sys/kern/subr_sleepqueue.c:223
> >
> > This message makes no sense at all as they aren't the same type.
>
> Well, I did not invent it :-/ I copy/pasted from the serial
> console of the machine.
>
> > > And here the panic message:
> > > [..]
> > > Fatal trap 12: page fault while in kernel mode
> > > cpuid = 1; apic id = 06
> > > fault virtual address   = 0x34
> > > fault code              = supervisor read, page not present
> > > instruction pointer     = 0x8:0xc053932b
> > > stack pointer           = 0x10:0xe53d8ab0
> > > frame pointer           = 0x10:0xe53d8ad4
> > > code segment            = base 0x0, limit 0xfffff, type 0x1b
> > >                         = DPL 0, pres 1, def32 1, gran 1
> > > processor eflags        = resume, IOPL = 0
> > > current process         = 2550 (cvsupd)
> > > [..]
> > >
> > > No ddb prompt, no crash-dump, no reboot. I need to go and
> > > reset the thing (now for the dozenth time :-/).
> >
> > Can you pop up gdb -k on the kernel.debug and do 'l *0xc053932b'
>
> Ahh, so stupid, I was close.
>
> Colin: I missed '-k', so forget my private reply.
>
> But however it is futile, since the -current gdb (6.1.1) does
> not allow -k. I've read on the list, that there is work in
> progress right now.

Ah, yes.  You can use addr2line to get the address.  Something like:

% addr2line -e kernel.debug -f 0xc053932b

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