'ello all!
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 floppy. So I told the loader to boot
from my root partition on my HDD instead. This produced some error
messages about filesystems not being properly dismounted (not sure if
that is true...), but booted anyway. Now, every boot from the HDD
produces the panics.
After being up for a few minutes, the machine panics saying (all
messages hand-transcribed):
dev=ad0s1e, block=33336, 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 missing out the values inside the ()'s as thats a lot of
writing - but I'll report back anything that the developers need to know) :
Debugger(...)
panic(...)
ffs_blkfree(...)
indir_trunc(...)
handle_workitem_freeblocks(...)
process_worklist_item(...)
softdep_process_worklist(...)
sched_sync(...)
fork_exit(...)
fork_trampoline(...)
If anybody needs more information then please let me know, as I said I
have it panic-ing reliably.
I guess that booting single-user and then fsck-ing might well fix the
problem, but I wanted to take the opportunity to report what is one of
the very few panics I've had in many years of FreeBSD usage. And I'm
planning to install RC2 on this machine anyway.
Thanks!
Andrew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
- Re: "panic: ffs_blkfree" in recent JPSNAP Andrew Boothman
- Re: "panic: ffs_blkfree" in recent JPSNAP Giorgos Keramidas