Date: Sun, 12 Sep 2004 17:26:40 +0000 From: Kris Kennaway <kris@FreeBSD.org> To: Anish Mistry <mistry.7@osu.edu> Cc: freebsd-questions@freebsd.org Subject: Re: 4.10 panic: ffs_alloccg: map corrupted Message-ID: <20040912172640.GA92737@hub.freebsd.org> In-Reply-To: <200409121318.10404.mistry.7@osu.edu> References: <200409121318.10404.mistry.7@osu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 12, 2004 at 01:18:02PM -0400, Anish Mistry wrote: > I'm running 4.10 on my main desktop and I've been getting a weird FFS pan= ic,=20 > and just finally got a dump of it. >=20 > IdlePTD at physical address 0x008af000 > initial pcb at physical address 0x002eb960 > panicstr: lockmgr: locking against myself > panic messages: > --- > panic: ffs_alloccg: map corrupted >=20 > syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself > Uptime: 13h52m35s >=20 > dumping to dev #ad/0x20001, offset 230592 > dump ata0: resetting devices .. done >=20 > See the attached file for the rest of the dump and the backtrace. Try booting to single user mode and run fsck -f on all your filesystems. if it find errors, keep running fsck -f until it stops reporting them. Sometimes fsck can fail to repair all of the corruption and you'll get runtime panics. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040912172640.GA92737>