From owner-freebsd-current@FreeBSD.ORG  Fri Sep 28 14:37:26 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 06B1916A420;
	Fri, 28 Sep 2007 14:37:26 +0000 (UTC)
	(envelope-from cb@severious.net)
Received: from ion.gank.org (ion.gank.org [69.55.238.164])
	by mx1.freebsd.org (Postfix) with ESMTP id E2C3713C468;
	Fri, 28 Sep 2007 14:37:25 +0000 (UTC)
	(envelope-from cb@severious.net)
Received: by ion.gank.org (Postfix, from userid 1001)
	id 70FC810F4E; Fri, 28 Sep 2007 09:37:25 -0500 (CDT)
Date: Fri, 28 Sep 2007 09:37:25 -0500
From: Craig Boston <cb@severious.net>
To: Francois Ranchin <fyr@fyrou.net>, Scott Long <scottl@samsco.org>,
	Darren Reed <darrenr@freebsd.org>, freebsd-current@freebsd.org,
	Larry Rosenman <ler@lerctr.org>
Message-ID: <20070928143725.GB52277@nowhere>
References: <46F7D7A4.5090007@samsco.org> <20070928133452.GA52277@nowhere>
	<20070928142419.GA59916@fyrou.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070928142419.GA59916@fyrou.net>
User-Agent: Mutt/1.4.2.2i
Cc: 
Subject: Re: panic: kmem_malloc(131072): kmem_map too small (AMD64)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Sep 2007 14:37:26 -0000

On Fri, Sep 28, 2007 at 04:24:19PM +0200, Francois Ranchin wrote:
> Perhaps these two (2 weeks old) : arc.c 1.11 and/or zfs_vfsops.c v1.12

Pretty sure those aren't the root of the problem.  I had already tried
falling back to a build from before those two changes went in, and while
it does take longer to panic it still does eventually.

Craig