From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 21:12:10 2006 Return-Path: X-Original-To: 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 2CA1616A420 for ; Wed, 5 Apr 2006 21:12:10 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8902F43D7F for ; Wed, 5 Apr 2006 21:11:54 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 21A1E53B0; Wed, 5 Apr 2006 16:11:54 -0500 (CDT) Date: Wed, 5 Apr 2006 16:11:54 -0500 To: Albert Shih Message-ID: <20060405211154.GA30089@soaustin.net> References: <20060405200341.GD14126@math.jussieu.fr> <20060405200727.GA28371@xor.obsecurity.org> <20060405201500.GE14126@math.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20060405201500.GE14126@math.jussieu.fr> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: freebsd-stable@freebsd.org, Kris Kennaway Subject: Re: Disappointed X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2006 21:12:10 -0000 On Wed, Apr 05, 2006 at 10:15:00PM +0200, Albert Shih wrote: > Le 05/04/2006 à 16:07:27-0400, Kris Kennaway a écrit > > On Wed, Apr 05, 2006 at 10:03:41PM +0200, Albert Shih wrote: > > > Hi all > > > > > > I'm disappointed by the stablity of FreeBSD 6-stable (I known it's > > > developpement branche). > > > > You forgot to provide pointers to your PRs. > > Well... I don't have one because I can't reproduce it. I think what kris is trying to say is that if we don't know what the problem is, there's no way that we can solve it. This type of bug is the most dificult to isolate and fix; it probably involves some kind of resource contention or race condition. We have a large number of people using 6.0 and 6-STABLE (and thus the prerelease code) and only a few people are reporting stability problems. There is clearly some triggering factor such as workload that we don't understand yet. Although GNATS is hardly ideally-suited to tracking this kind of problem, it's the best system that we have right now (and, there may be no ideal system even possible for such things). So, as GNATS co-administrator, I encourage people to file PRs for suspected stability problems. I have been trying to track the ones that have come in and so far I see no pattern to them at all. Do you use quotas? kern/91631 seems to comment on panics in this situation. mcl