From owner-freebsd-smp  Sat Mar 16  5:20:38 2002
Delivered-To: freebsd-smp@freebsd.org
Received: from web21107.mail.yahoo.com (web21107.mail.yahoo.com [216.136.227.109])
	by hub.freebsd.org (Postfix) with SMTP id 52B6137B405
	for <smp@freebsd.org>; Sat, 16 Mar 2002 05:20:31 -0800 (PST)
Message-ID: <20020316132031.97750.qmail@web21107.mail.yahoo.com>
Received: from [62.254.0.5] by web21107.mail.yahoo.com via HTTP; Sat, 16 Mar 2002 05:20:31 PST
Date: Sat, 16 Mar 2002 05:20:31 -0800 (PST)
From: Hiten Pandya <hitmaster2k@yahoo.com>
Reply-To: hiten@uk.FreeBSD.org
Subject: Re: -current lock warning...
To: Poul-Henning Kamp <phk@freebsd.org>, current@freebsd.org,
	smp@freebsd.org
In-Reply-To: <35758.1016270542@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-smp.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-smp>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-smp>
X-Loop: FreeBSD.org

--- Poul-Henning Kamp <phk@freebsd.org> wrote:
> I get this one on every single boot.  We're not shipping the snapshot
> with that in place, right ?
> 
> real memory  = 268423168 (262132K bytes)
> avail memory = 257003520 (250980K bytes)
> acquiring duplicate lock of same type: "thrd_sleep"
>  1st @ ../../../vm/vm_map.c:2288
>  2nd @ ../../../vm/vm_kern.c:172
> Debugger("witness_lock")
> Stopped at      Debugger+0x40:  xorl    %eax,%eax
> db> trace
> Debugger(c02e9ace) at Debugger+0x40
> witness_lock(c038afe4,8,c02f8440,ac,c038afb4) at witness_lock+0x546
> _sx_xlock(c038afe4,c02f8440,ac,bfc00000,c0435c5c) at _sx_xlock+0xa1
> _vm_map_lock(c038afb4,c02f8440,ac,c034a840,1) at _vm_map_lock+0x16
> kmem_alloc(c038afb4,3000,c0e41a00,0,c02fa434) at kmem_alloc+0x41
> _zget(c0e41a00,bfc00000,0,c0435cd0,c0281769) at _zget+0xfa
> zalloc(c0e41a00,c034a840,1,c02f8630,a7) at zalloc+0x3b
> vmspace_alloc(0,bfc00000,c035c940,c02f8630,8f0) at vmspace_alloc+0x2d
> vmspace_fork(c035c940,cbb9ad24,c0331f84,cbb9ab00,c0331d60) at
> vmspace_fork+0x4d
> vm_forkproc(c0332080,cbb9ab00,cbb9ac00,20014) at vm_forkproc+0xc6
> fork1(c0332080,20014,c0332130) at fork1+0xd58
> create_init(0,432c00,432000,0,c012368c) at create_init+0x17
> mi_startup() at mi_startup+0x90
> begin() at begin+0x43
> db> 

I haven't seen this.  I built a kernel today, and I have a dual processor
machine.  Are you using any special kernel options, such as VFS_BIO_DEBUG
or something, or am I talking nuts? :)

Regards,

  -- Hiten

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - live college hoops coverage
http://sports.yahoo.com/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message