From owner-freebsd-hackers  Thu Feb 25 15:41: 2 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 54CAD14E8E
	for <freebsd-hackers@FreeBSD.ORG>; Thu, 25 Feb 1999 15:40:57 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id PAA09708;
	Thu, 25 Feb 1999 15:40:39 -0800 (PST)
	(envelope-from dillon)
Date: Thu, 25 Feb 1999 15:40:39 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199902252340.PAA09708@apollo.backplane.com>
To: Julian Elischer <julian@whistle.com>,
	Luoqi Chen <luoqi@watermarkgroup.com>, dfr@nlsystems.com,
	freebsd-hackers@FreeBSD.ORG, mjacob@feral.com
Subject: Re: Panic in FFS/4.0 as of yesterday - update
References: <Pine.BSF.3.95.990225134720.11039F-100000@current1.whistle.com> 
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:    The patch I've supplied has one bug in it that came up... While building
:    the world one of my 'ranlib's got stuck in 'newbuf' even after plenty of
:    buffers were freed up.  I think it's a simple missing wakeup... when
:    I spiked the load the ranlib got going again ( too bad, I was trying to
:    gdb -k the running system and the gdb command unstuck the ranlib! ).

    Fragmentation in the buffer_map, even though it is *twice* the size of
    maxbufspace, can cause map allocations to fail due to fragmentation.

    Joy.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message