= /usr
panic: ffs_blkfree: freeing free frag
cpuid = 1
KDB: enter: panic
[ thread pid 19 tid 100054 ]
Stopped at kdb_enter+0x92: [I2]addl r14=0xffe1e628,gp ;;
db
bt
Tracing pid 19 tid 100054 td 0xe00011105880
kdb_enter(0xe4783670, 0xe4783670, 0xe439bb40
.
if not:
--
dev=/dev/ad1s1e, block=1, fs=\Archiv\2
panic=ffs_blkfree: freeing free block
Debugger(panic)
Stopped at Debugger x0x4d xchgl %ebx, in Debugger.0
db
-
someone knows about that?
oh, hardware:
\dev\ad1 is a mxtor 120GB S-AtA drive conected to an
Silicon Image Sil3112(a) SAtA
On 2002-12-22 03:13, Andrew Boothman [EMAIL PROTECTED] wrote:
My 5.0-CURRENT-20021215-JPSNAP system is reliably panic-ing and
dropping into the debugger a few minutes after booting.
I was in the process of trying to boot 5.0-RC2's installation
floppies, and the boot failed due to a faulty
-transcribed):
dev=ad0s1e, block=6, fs=/tmp
panic: ffs_blkfree: freeing free block
Debugger(panic)
Stopped at Debugger+0x54: xchgl %ebx, in_Debugger()
Unfortunately I don't (yet) know the first thing about how to debug
something like this, so for the hell of it I typed trace and got the
following (I'm
Reading symbols from kernel.debug.7...done.
(kgdb) exec-file kernel.7
(kgdb) core-file vmcore.7
panic: from debugger
panic messages:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
Uptime: 50s
Dumping 123 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112
---
#0
PROTECTED]
Subject: Re: panic: ffs_blkfree: freeing free block
X-ASK-Info: Confirmed by User
I introduced a bug to snapshots on 11/30/02 which did not get fixed=20
until 12/15/02 which caused background fsck to (silently) fail to fix
certain filesystem problems. If you ran background fsck
On Wed, Dec 18, 2002 at 08:00:19AM -0800, Kirk McKusick wrote:
I corrected a botched patch last night. Make sure that you are running
with version 1.56 2002/12/18 07:19:41 of ufs/ffs/ffs_snapshot.c.
Kirk McKusick
=-=-=-=-=
nebula# ident /usr/src/sys/ufs/ffs/ffs_snapshot.c
By hard shutdown I assume you mean hitting the reset button while
the machine is busily running along? If so, my test machine passes
that test. I'll keep plugging away at it though in the hopes of
getting it to fail.
Kirk McKusick
Yes, that's what I meant. My main box is a laptop
I have managed to panic my system on a hard reboot and now believe
that I have found the problem on which you are faulting. I have
checked in a fix to the head of the tree (sys/ufs/ffs/ffs_snapshot.c
version 1.57). Let me know if it fixes your problem.
Kirk McKusick
To Unsubscribe: send
On Wed, Dec 18, 2002 at 11:50:42AM -0800, Kirk McKusick wrote:
I have managed to panic my system on a hard reboot and now believe
that I have found the problem on which you are faulting. I have
checked in a fix to the head of the tree (sys/ufs/ffs/ffs_snapshot.c
version 1.57). Let me know if
Date: Mon, 16 Dec 2002 22:42:07 -0600
From: Dan Nelson [EMAIL PROTECTED]
To: Aurelien Nephtali [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: panic: ffs_blkfree: freeing free block
In the last episode (Dec 16), Aurelien Nephtali said:
Hi,
I got a panic today which occured
debugger
panic messages:
---
dev = ad0s1f, block = 1088, fs = /tmp
panic: ffs_blkfree: freeing free block
panic: from debugger
Uptime: 50s
Dumping 123 MB
ata0: resetting devices ..
done
16 32 48 64 80 96 112
---
#0 doadump () at ../../../kern/kern_shutdown.c:232
232 dumping
: page fault
panic messages:
---
panic: ffs_blkfree: freeing free block
cpuid = 1; lapic.id =
boot() called on cpu#1
Uptime: 1m24s
pfs_vncache_unload(): 1 entries remaining
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id =
fault virtual address = 0x18
fault
:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
[...]
#0 dumpsys () at ../../../kern/kern_shutdown.c:479
#1 0xc01baf11 in boot (howto=260) at ../../../kern/kern_shutdown.c:322
#2 0xc01bb32a in panic (fmt=0xc02ba51e bremfree: bp %p not locked)
at ../../../kern
Hi,
-current as of Aug 16, ~2pm CEST:
---snip---
IdlePTD 4812800
initial pcb at 305f60
panicstr: bremfree: bp 0xc69e0748 not locked
panic messages:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
[...]
#0 dumpsys () at ../../../kern/kern_shutdown.c:479
#1 0xc01baf11 in boot
space ID is 0xc000, which I don't recognize. What process was
running?
---snip---
IdlePTD 4812800
initial pcb at 305f60
panicstr: bremfree: bp 0xc69e0748 not locked
panic messages:
---
panic: ffs_blkfree: freeing free block
panic: from debugger
[...]
#0 dumpsys () at ../../../kern
:
dev=0x2fb0e, block = 9432, fs = /usr
panic: ffs_blkfree: freeing free block
Debugger("panic")
Stopped at Debugger+0x37: movl $0, in Debugger
trace:
Debugger()
panic()
ffs_blkfree()
ffs_truncate()
ufs_inactive()
ufs_vnoperate()
vput()
unlink()
syscall()
Xint0x80_syscall()
IIRC t
17 matches
Mail list logo
