kern/68442: panic - acquiring duplicate lock of same type:
dl at leo.org
Tue Jun 29 09:30:46 PDT 2004
[ 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 @ /usr/src/sys/kern/uipc_syscalls.c:1735
> > 2nd sleepq chain @ /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.
I can copy the kernel image to a machine with a older -current
which has working gdb -k. However I do not have the exact
source tree there. I will see if I can check it out though.
I'll get back to you, if I can come up with a line number
that could make sense. Not sure how sensitive it is to
have the "exact" source-tree.
Thanks so far,
IRCnet: Mr-Spock - May His Shadow fall upon thee -
Daniel Lang * dl at leo.org * +49 89 289 18532 * http://www.leo.org/~dl/
More information about the freebsd-current