From owner-freebsd-current Mon Jul 15 8:49:21 2002 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 F33D237B400 for ; Mon, 15 Jul 2002 08:49:16 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D00443E58 for ; Mon, 15 Jul 2002 08:49:16 -0700 (PDT) (envelope-from qhwt@myrealbox.com) Received: from localhost qhwt@smtp-send.myrealbox.com [61.195.119.87] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.9 $ on Novell NetWare; Mon, 15 Jul 2002 09:49:15 -0600 Date: Tue, 16 Jul 2002 00:49:24 +0900 From: qhwt To: current@FreeBSD.ORG Subject: Re: panic at boot in ffs_valloc Message-ID: <20020715154923.GA1480.qhwt@myrealbox.com> References: <20020703213021.H59537-100000@skaarup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020703213021.H59537-100000@skaarup.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. On Wed, Jul 03, 2002 at 09:36:24PM +0200, Rasmus Skaarup wrote: > > I'm also suddenly having a panics - every 5 minutes actually, since my > latest cvsup a few hours ago. They seem to be related to some ufs > and ffs calls.. > > I'm not able to read my core dumps for some reason (gdb says "kernel > symbol 'cpuhead' not found.") and I don't have the time to scratch a > backtrace down by hand just now. > > The panicstring is: "bremfree: bp 0xc77e8670 not locked" > > Sincerely, > Rasmus Skaasrup > > On Wed, 3 Jul 2002, Andrew R. Reiter wrote: > > > :I cvsup'd and built world+kernel a few hours ago and was happy to see > > :KDE working again, but I got a spontaneous reboot while trying to track > > :down a segfault in a mozilla build component. I "boot -v"'ed and as > > :soon as the login prompt came up I hit a panic. I'm guessing the > > :backgorund fsck had something to do with it. I'll hand-copy the trace > > :here; any debugging info needed while my box is stuck at the debugger, > > :lemme know: > > > > > > I don't have the output to show people since I was trying to reproduce but > > couldnt, but i got essentially the same panic, but it came only from a > > syscall to open() that called ufs_create() -> ufs_makeinode -> > > ffs_valloc() -> panic. > > > > I can try and reproduce (tho, mine occured when just running cscope) and > > get a dump. same here, and I can reproduce the panic by: $ cd /tmp $ for i in `jot 300 1`; do touch $i; done this panics when $i reaches around 128 on my machine. However, the next one doesn't: $ mkdir /tmp/foo $ cd /tmp/foo $ for i in `jot 300 1`; do touch $i; done I have a 256Mbytes of swap-backed /tmp configured in /etc/rc.local as follows: $ cat /etc/rc.local mdmfs -p 1777 -s 256M md0 /tmp According to a post on an anonymous BBS in Japan, malloc-backed /tmp doesn't seem to trigger the panic. Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message