Re: panic: ffs_blkfree_cg: freeing free block

From: <deeptech71_at_gmail.com>
Date: Sat, 29 Oct 2011 01:34:30 +0200
With object files which were built using the original kernel
configuration file (no debugging symbols included):

#kgdb kernel /var/crash/vmcore.4
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 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-marcel-freebsd"...(no debugging
symbols found)...
Attempt to extract a component of a value that is not a structure pointer.
Attempt to extract a component of a value that is not a structure pointer.
#0  0xc0687d88 in doadump ()
(kgdb) bt
#0  0xc0687d88 in doadump ()
#1  0xc0688302 in kern_reboot ()
#2  0xc0688768 in panic ()
#3  0xc07f92bf in ffs_blkfree_cg ()
#4  0xc07f9417 in ffs_blkfree ()
#5  0xc0803259 in ffs_indirtrunc ()
#6  0xc08042e1 in ffs_truncate ()
#7  0xc083171c in ufs_inactive ()
#8  0xc0712718 in vinactive ()
#9  0xc0716e2a in vputx ()
#10 0xc071affb in kern_unlinkat ()
#11 0xc071b1a6 in kern_unlink ()
#12 0xc071b1ca in sys_unlink ()
#13 0xc089c954 in syscall ()
#14 0xc0887021 in Xint0x80_syscall ()
#15 0x00000033 in ?? ()
Previous frame inner to this frame (corrupt stack?)

wtf?

With object files which were built using a kernel configuration file
that had ``makeoptions DEBUG=-g'' inserted compared to the original
configuration file:

#kgdb kernel.debug /var/crash/vmcore.4
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 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-marcel-freebsd"...
Cannot access memory at address 0x0
(kgdb) bt
#0  0x00000000 in ?? ()

wtf?
Received on Fri Oct 28 2011 - 21:34:31 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:19 UTC