4.10 panic: ffs_alloccg: map corrupted
I'm running 4.10 on my main desktop and I've been getting a weird FFS panic, and just finally got a dump of it. IdlePTD at physical address 0x008af000 initial pcb at physical address 0x002eb960 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself Uptime: 13h52m35s dumping to dev #ad/0x20001, offset 230592 dump ata0: resetting devices .. done See the attached file for the rest of the dump and the backtrace. -- Anish Mistry pgprX0kRpRv60.pgp Description: signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 panic: ffs_alloccg: map corrupted
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 panic, and just finally got a dump of it. IdlePTD at physical address 0x008af000 initial pcb at physical address 0x002eb960 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself Uptime: 13h52m35s dumping to dev #ad/0x20001, offset 230592 dump ata0: resetting devices .. done 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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 panic: ffs_alloccg: map corrupted
On Sunday 12 September 2004 01:26 pm, you wrote: 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 panic, and just finally got a dump of it. IdlePTD at physical address 0x008af000 initial pcb at physical address 0x002eb960 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself Uptime: 13h52m35s dumping to dev #ad/0x20001, offset 230592 dump ata0: resetting devices .. done 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. Just did that and fsck didn't report any errors. -- Anish Mistry pgp56fuXAyuYk.pgp Description: signature
Re: 4.10 panic: ffs_alloccg: map corrupted
Tell us about your hard drive and the way you have attacked them to the cable. Regards S. On Sun, 12 Sep 2004 13:18:02 -0400, Anish Mistry [EMAIL PROTECTED] wrote: I'm running 4.10 on my main desktop and I've been getting a weird FFS panic, and just finally got a dump of it. IdlePTD at physical address 0x008af000 initial pcb at physical address 0x002eb960 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself Uptime: 13h52m35s dumping to dev #ad/0x20001, offset 230592 dump ata0: resetting devices .. done See the attached file for the rest of the dump and the backtrace. -- Anish Mistry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.10 panic: ffs_alloccg: map corrupted
On Sunday 12 September 2004 02:13 pm, Subhro wrote: Tell us about your hard drive and the way you have attacked them to the cable. The dmesg is attached. They are connected using a 80 pin cable. The long end (blue terminator) is connected to the first ide spot on the motherboard. ad0: 38166MB WDC WD400AB-00CMB0 is the master and jumpered as the master. It is connected to the primary end of the cable. ad1: 9541MB WDC WD100BA is the slave and is jumpered as the slave. It is connected to the secondary spot, between the board and the master. Regards S. On Sun, 12 Sep 2004 13:18:02 -0400, Anish Mistry [EMAIL PROTECTED] wrote: I'm running 4.10 on my main desktop and I've been getting a weird FFS panic, and just finally got a dump of it. IdlePTD at physical address 0x008af000 initial pcb at physical address 0x002eb960 panicstr: lockmgr: locking against myself panic messages: --- panic: ffs_alloccg: map corrupted syncing disks... 71 9 4 4 4 4 4 4 4 panic: lockmgr: locking against myself Uptime: 13h52m35s dumping to dev #ad/0x20001, offset 230592 dump ata0: resetting devices .. done See the attached file for the rest of the dump and the backtrace. -- Anish Mistry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Anish Mistry pgpWMcnhEpSVN.pgp Description: signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
