From owner-freebsd-stable@FreeBSD.ORG  Thu Oct  9 21:34:49 2003
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id AE90516A4B3; Thu,  9 Oct 2003 21:34:49 -0700 (PDT)
Received: from relay.macomnet.ru (relay.macomnet.ru [195.128.64.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 217E743FBD; Thu,  9 Oct 2003 21:34:48 -0700 (PDT)
	(envelope-from maxim@macomnet.ru)
Received: from news1.macomnet.ru (ifm4m5h7@news1.macomnet.ru [195.128.64.14])
	by relay.macomnet.ru (8.12.10/8.12.10) with ESMTP id h9A4YkDt18452302;
	Fri, 10 Oct 2003 08:34:46 +0400 (MSD)
Date: Fri, 10 Oct 2003 08:34:46 +0400 (MSD)
From: Maxim Konovalov <maxim@macomnet.ru>
To: Mike Tancsa <mike@sentex.net>
In-Reply-To: <6.0.0.22.0.20031009202308.0879ec30@209.112.4.2>
Message-ID: <20031010083335.I11216@news1.macomnet.ru>
References: <20031010001355.GA93439@freebsdmall.com>
 <6.0.0.22.0.20031009202308.0879ec30@209.112.4.2>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: stable@freebsd.org
Subject: Re: [Peter_Losher@isc.org: More freebsd.isc.org issues...]
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Oct 2003 04:34:49 -0000

On Thu, 9 Oct 2003, 20:39-0400, Mike Tancsa wrote:
[...]
> The only other issue that comes to mind is tegge made a patch to allow
> maxim@macomnet.ru do a make -j64 work on a low RAM situation.  But that
> corrected panics, not lockups.

silby has already committed it.

[...]