From owner-freebsd-current@FreeBSD.ORG  Tue Mar 10 13:13:51 2009
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 EFC7510656CE
	for <freebsd-current@freebsd.org>; Tue, 10 Mar 2009 13:13:51 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42])
	by mx1.freebsd.org (Postfix) with ESMTP id 9AE948FC20
	for <freebsd-current@freebsd.org>; Tue, 10 Mar 2009 13:13:51 +0000 (UTC)
	(envelope-from jhb@freebsd.org)
Received: from server.baldwin.cx (pool-98-109-39-197.nwrknj.fios.verizon.net
	[98.109.39.197])
	by cyrus.watson.org (Postfix) with ESMTPSA id 4274F46B09;
	Tue, 10 Mar 2009 09:13:51 -0400 (EDT)
Received: from localhost (john@localhost [127.0.0.1]) (authenticated bits=0)
	by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id n2ADDdl2026220;
	Tue, 10 Mar 2009 09:13:45 -0400 (EDT) (envelope-from jhb@freebsd.org)
From: John Baldwin <jhb@freebsd.org>
To: freebsd-current@freebsd.org
Date: Tue, 10 Mar 2009 09:13:11 -0400
User-Agent: KMail/1.9.7
References: <alpine.BSF.2.00.0903101222470.1591@kushnir1.kiev.ua>
In-Reply-To: <alpine.BSF.2.00.0903101222470.1591@kushnir1.kiev.ua>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200903100913.12233.jhb@freebsd.org>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]);
	Tue, 10 Mar 2009 09:13:45 -0400 (EDT)
X-Virus-Scanned: ClamAV 0.94.2/9084/Tue Mar 10 03:11:13 2009 on
	server.baldwin.cx
X-Virus-Status: Clean
X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 
	autolearn=ham version=3.1.3
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx
Cc: 
Subject: Re: LOR and sysctl(vfs.bufspace...) failed: Cannot allocate memory
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: Tue, 10 Mar 2009 13:13:54 -0000

On Tuesday 10 March 2009 6:44:38 am Vladimir Kushnir wrote:
> Since the last buildworld/buildkernel I'm getting this kind of things:
> ~> top
> top: sysctl(vfs.bufspace...) failed: Cannot allocate memory

I'll fix this.

> and so on. This is with both custom kernel and GENERIC under 
> amd64-CURRENT:
> 
>   ~> uname -a
> FreeBSD kushnir1.kiev.ua 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Mar 10 
> 11:35:34
>   EET 2009     root@kushnir1.kiev.ua:/usr/obj/usr/src/sys/GENERIC  amd64
> 
> Besides, there was a LOR (dmesg output attached).

The LOR is not a true deadlock possibility, you can ignore it.

-- 
John Baldwin