From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 18:02:49 2003 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 956B637B401 for ; Mon, 21 Apr 2003 18:02:49 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26A3943F75 for ; Mon, 21 Apr 2003 18:02:49 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from asmtp02.mac.com (asmtp02-qfe3 [10.13.10.66]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h3M12mGm001235 for ; Mon, 21 Apr 2003 18:02:48 -0700 (PDT) Received: from mac.com ([67.33.226.63]) by asmtp02.mac.com (Netscape Messaging Server 4.15) with ESMTP id HDQ08O00.T7X; Mon, 21 Apr 2003 18:02:48 -0700 Date: Mon, 21 Apr 2003 20:02:46 -0500 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: David Leimbach From: David Leimbach In-Reply-To: <6856864.1050949023709.JavaMail.leimy2k@mac.com> Message-Id: <2131886D-745E-11D7-962B-0003937E39E0@mac.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: FreeBSD-current@freebsd.org Subject: panic with SMP 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, 22 Apr 2003 01:02:49 -0000 This happens almost every other time I boot CURRENT SMP: AP CPU #1 Launched! panic: mutex Giant not owned at /usr/src/sys/vm/vm_page.c:774 cpuid = 1; lapic.id = 00000000 Debugger("panic") Stopped at Debugger+0x4e: xchgl %ebx, in_Debugger.0 I am going to update again tonight and see if there are any changes... This is from Sunday morning. Dave On Monday, April 21, 2003, at 01:17 PM, David Leimbach wrote: > Could there be a race condition in the vm? I have been seeing > problems right at the moment the > second CPU in my box is started at boot time. Its not every time > either. I believe the file was vm_allloc > and it fails an assertion involving the ownership of Giant. > > I can provide more details this evening but I have been noticing this > at least all weekend. > > - Dave > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"