From owner-freebsd-current@FreeBSD.ORG  Fri Feb 13 10:35:57 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 378D316A4CE
	for <current@freebsd.org>; Fri, 13 Feb 2004 10:35:57 -0800 (PST)
Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com
	[209.69.98.4])	by mx1.FreeBSD.org (Postfix) with ESMTP id F055743D1D
	for <current@freebsd.org>; Fri, 13 Feb 2004 10:35:56 -0800 (PST)
	(envelope-from andy@siliconlandmark.com)
Received: from alpha.siliconlandmark.com (localhost [127.0.0.1])
	i1DIZsZV051583;	Fri, 13 Feb 2004 13:35:54 -0500 (EST)
	(envelope-from andy@siliconlandmark.com)
Received: from localhost (andy@localhost)i1DIZrs5051580;
	Fri, 13 Feb 2004 13:35:54 -0500 (EST)
	(envelope-from andy@siliconlandmark.com)
X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing
	-bs
Date: Fri, 13 Feb 2004 13:35:53 -0500 (EST)
From: Andre Guibert de Bruet <andy@siliconlandmark.com>
To: Divacky Roman <xdivac02@stud.fit.vutbr.cz>
In-Reply-To: <20040213112153.GA14493@stud.fit.vutbr.cz>
Message-ID: <20040213133320.F34361@alpha.siliconlandmark.com>
References: <20040213094957.GA8898@stud.fit.vutbr.cz>
	<20040213112153.GA14493@stud.fit.vutbr.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
cc: current@freebsd.org
Subject: Re: panic in 11th Feb current
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Feb 2004 18:35:57 -0000


On Fri, 13 Feb 2004, Divacky Roman wrote:

> > Source from the 11th indicates that this line number to points to a
> > vm_map_lock_read() call inside vm_map_lookup() which would be called on a
> > page fault.
>
> seems so
>
> > > stray iqr 9
> > > _mtx_lock_sleep: recursed on non-recursive mutex
> > > kern_mutex.c:436
> >
> > Ouch.
> >
> > > I have kernel dump which I can provide (but my kernel is not -g
> > > compiled)
> >
> > Run an "nm /boot/kernel/kernel |sort" and report the function names and
> > addresses of the functions just above and below the eip (0xc05babdc).
> >
> > Regards,
>
> is this enough?
>
> c05bab60 T _vm_map_unlock
> c05babc0 T _vm_map_lock_read
             ^^^^^^^^^^^^^^^^^
> c05bac50 T _vm_map_unlock_read

That EIP reflects the panic in vm_map_lock_read(). Was there another EIP
that was displayed on your screen for the the first fault?

Regards,

> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/    >