From owner-freebsd-hackers  Sat Dec  6 06:55:37 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA23295
          for hackers-outgoing; Sat, 6 Dec 1997 06:55:37 -0800 (PST)
          (envelope-from owner-freebsd-hackers)
Received: from elvis.vnet.net (elvis.vnet.net [166.82.1.5])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA23284
          for <freebsd-hackers@FreeBSD.ORG>; Sat, 6 Dec 1997 06:55:32 -0800 (PST)
          (envelope-from rivers@dignus.com)
Received: from ponds.dignus.com (ponds.vnet.net [166.82.177.48])
          by elvis.vnet.net (8.8.8/8.8.4) with ESMTP
	  id JAA18581; Sat, 6 Dec 1997 09:55:20 -0500 (EST)
Received: from lakes.dignus.com (lakes [10.0.0.3])
	by ponds.dignus.com (8.8.5/8.8.5) with ESMTP id KAA25505;
	Sat, 6 Dec 1997 10:15:15 -0500 (EST)
Received: (from rivers@localhost) by lakes.dignus.com (8.8.7/8.6.9) id KAA15170; Sat, 6 Dec 1997 10:01:06 -0500 (EST)
Date: Sat, 6 Dec 1997 10:01:06 -0500 (EST)
From: Thomas David Rivers <rivers@dignus.com>
Message-Id: <199712061501.KAA15170@lakes.dignus.com>
To: ivt@gamma.ru, nectar@NECTAR.COM
Subject: Re: panic: blkfree: freeling free block/frag
Cc: freebsd-hackers@FreeBSD.ORG
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Is there a FreeBSD-INN list or something similar?  There oughter be.  I'd
> subscribe.
> 
> Jacques Vidrine <n@nectar.com>
> 
> On Fri, 5 Dec 1997, Igor Timkin wrote:
> 
> > Every 4-8 days my news server (~10 full incoming feeds, ~50
> > outgoing feeds) crash:
> > panic: blkfree: freeing free block
> > or
> > panic: blkfree: freeing free frag
> > 
> > I have a P6-200 rinning on a ASUS P65UP5+C-P6ND (BIOS rev. 2.05),
> > with 512M ECC of RAM (with David Greenman patch).
> > news spool is 6x4G Barracuda (ST15150W) CCD across two 2940UW.

 This is very reminiscent of my "Daily panic"s which I used to get
on a full news server.  I never saw the "freeing free frag" but I
frequently saw the "freeing free block" panic.  Do you also get
"dup alloc" panics?

 Anyway, suffice it to say that we've been bird-dogging this problem
for quite some time (since 2.1 came out.)  It has been a bear to track
down.  And, unfortunately, I lost my news feed; so I don't get it
every day.  [Although, I can reproduce a problem that is suspiciously
similar on a stand-alone 386.] The more info we can get, the better.

	- Dave Rivers -