From owner-freebsd-stable Sat Nov 16 09:20:39 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA08554 for stable-outgoing; Sat, 16 Nov 1996 09:20:39 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA08541 for ; Sat, 16 Nov 1996 09:20:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA11191; Sat, 16 Nov 1996 12:20:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Sat, 16 Nov 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id HAA10853; Sat, 16 Nov 1996 07:51:48 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id HAA26583; Sat, 16 Nov 1996 07:53:24 -0500 (EST) Date: Sat, 16 Nov 1996 07:53:24 -0500 (EST) From: Thomas David Rivers Message-Id: <199611161253.HAA26583@lakes.water.net> To: gpalmer@freebsd.org, ponds!freebsd.org!freebsd-stable Subject: Re: panic: ffs_valloc: dup alloc Cc: ponds!freebsd.org!freebsd-hackers Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Hi > > Our mail box just died with: > > root@mail:/var/crash> gdb -k kernel vmcore.2 > GDB is free software and you are welcome to distribute copies of it > under certain conditions; type "show copying" to see the conditions. > There is absolutely no warranty for GDB; type "show warranty" for details. > GDB 4.13 (i386-unknown-freebsd), > Copyright 1994 Free Software Foundation, Inc... > IdlePTD 1d5000 > current pcb at 1abd64 > panic: ffs_valloc: dup alloc > #0 boot (howto=260) at ../../i386/i386/machdep.c:912 > 912 } else { > (kgdb) bt Welcome to the club :-) This is the panic that I have had for several months, which is duplicated almost every night. Rest assured that several people are investigating this at this time... I believe it has something to do with the inode allocation bits in ffs_valloc(). Others believe some race conditions in vnode allocation are to blaim, etc... David Greene is investigating other avenues. It seems to me that we are closing in on the issue, if only by eliminating everything else :-) - Dave Rivers - p.s. I've moved this from freebsd-bugs to freebsd-hackers, where we have been discussing the problem for some time.