Re: panic: ffs_blkfree: freeing free block

2007/10/16, Eric Anderson <anderson@xxxxxxxxxxx>:

Pieter de Goeje wrote:
On Sunday 14 October 2007, Eric Anderson wrote:
Pieter de Goeje wrote:
On Saturday 13 October 2007, Rolf Witt wrote:
Backtrace from crash tonight (after portsnap cron):
<snip>

# uname -a
FreeBSD peanuts.homenet.local 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE
#121: Thu Oct 11 16:29:05 CEST 2007
rowi@xxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/PEANUTS i386

Sources from Builddate.

Rowi
Eric sent me this patch:
http://www.googlebit.com/freebsd/patches/ffs_softdep.c-patch
which seems to be working great so far. I am still testing it, but I
think it fixed the problem.
To apply, cd /usr/src; patch < /path/to/patch and then rebuild the
kernel.

Cheers,
Pieter de Goeje
It doesn't actually 'fix' the problem, but I think it helps identify
it.
I'm not 100% certain if this is the right fix our not, but so far
feedback has been good when running with this patch.

Can somebody confirm that this patch is ok?

Eric
Can you elaborate on what this patch exactly does / what the problem is?

Pieter


I think the problem is that blocks are being put in the worklist twice,
but I'm not certain why yet. The patch reduces the chance of this
happening by more often removing the block from the worklist instead of
leaving it on. I think actually the patch is hiding the real issue more
than anything, which is why I said it isn't fixing the problem, but
because of the reports I've seen, I think we're sniffing in the right
area. I'll be looking more into this soon, when I get another few
minutes of free time and my debugger..

I actually seem to be getting the panic more often with the patch (i.e.
twice in just 30 minutes with the patch, about twice per day without the
patch), while doing the same things as usual. The panic usually happens when
I'm compiling or linking. Is that strange?
Arjan
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: [OT] Q: what would you choose for a VCS today
    ... FreeBSD as base that would allow better teams cooperation and easy code ... control fly out the window from, say, the 42nd floor. ... If you think you need a vendor branch, take a look at mercurial patch ... Patch queues are quite powerful, and even though you end up versioning ...
    (freebsd-hackers)
  • RE: For the love of God, is it even possible to make the Atheros ath.patch & updated HALactually
    ... > # mv ath_hal_20051212 ath ... in hopes that maybe the patch was FINALLY ... This FreeBSD installation is sitting here doing ... To June/July 2005 madwifi was very unstable, after merging cvs BSD tree of ...
    (freebsd-current)
  • Re: panic: ffs_blkfree: freeing free block
    ... Pieter de Goeje wrote: ... FreeBSD peanuts.homenet.local 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE ... feedback has been good when running with this patch. ...
    (freebsd-current)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:28.resolv
    ... > There's no patch for these, and in the case of the embedded ... >>FreeBSD only: NO ... In a few instances in the resolver code, ... >>can spoof DNS messages) may produce a specially crafted DNS message ...
    (FreeBSD-Security)
  • Re: FreeBSD 6.0 compat with DL320 G4
    ... The patch I created makes the broadcom chip work without panicing ... FreeBSD 6.0 compat with DL320 G4 ... this server also has bge interfaces and had no ...
    (freebsd-questions)