Re: ffs_alloccg panics in 5.2 RC2

Following up on my earlier reported problems with
ffs_alloccg panics, I added debugging to my kernel,
and also enabled options INVARIANTS,
INVARIANT_SUPPORT, WITNESS, WITNESS_SKIPSPIN, and
DEBUG_VFS_LOCKS. After my last panic I now have a
512MB vmcore.0 file in /var/crash.

As mentioned before:
uname -a
FreeBSD mydomain.com 5.2-RC2 FreeBSD 5.2-RC2 #1: Wed
Jan  7 13:39:36 PST 2004    
root_at_mydomain.com:/mnt/tmp/src/sys/i386/compile/GENERIC
 i386

Now following what I think the FAQ is trying to say,
here is what I get when I use gdb:

gdb -k /usr/src/sys/i386/compile/GENERIC/kernel.debug
/var/crash/vmcore.0
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General
Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "i386-unknown-freebsd"...
/var/crash/vmcore.0: Unknown error: 0.
(kgdb) where
No stack.
(kgdb)

What now? Thanks.



__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus