From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 16:30:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A5A016A4CE; Tue, 29 Jun 2004 16:30:46 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E497C43D48; Tue, 29 Jun 2004 16:30:45 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Tue, 29 Jun 2004 18:30:28 +0200 From: Daniel Lang To: John Baldwin Message-ID: <20040629163028.GM75577@atrbg11.informatik.tu-muenchen.de> References: <20040628202434.GA73213@atrbg11.informatik.tu-muenchen.de> <20040629153921.GE75577@atrbg11.informatik.tu-muenchen.de> <200406291200.12030.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406291200.12030.jhb@FreeBSD.org> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: freebsd-current@FreeBSD.org Subject: Re: kern/68442: panic - acquiring duplicate lock of same type: "sleepq chain" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2004 16:30:46 -0000 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 @ /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, Daniel -- IRCnet: Mr-Spock - May His Shadow fall upon thee - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/