From owner-cvs-all Tue Aug 21 12:28:52 2001 Delivered-To: cvs-all@freebsd.org Received: from misha.privatelabs.com (misha.privatelabs.com [66.9.25.166]) by hub.freebsd.org (Postfix) with ESMTP id 17CE637B407; Tue, 21 Aug 2001 12:28:45 -0700 (PDT) (envelope-from mi@aldan.algebra.com) Received: from misha.privatelabs.com (mi@localhost [127.0.0.1]) by misha.privatelabs.com (8.11.3/8.11.1) with ESMTP id f7LJSXk01254; Tue, 21 Aug 2001 15:28:34 -0400 (EDT) (envelope-from mi@aldan.algebra.com) Message-Id: <200108211928.f7LJSXk01254@misha.privatelabs.com> Date: Tue, 21 Aug 2001 15:28:31 -0400 (EDT) From: mi@aldan.algebra.com Reply-To: mi@aldan.algebra.com Subject: "current is broken" (Re: cvs commit: src/sys/kern kern_condvar.c kern_synch.c src/sys/sys proc.h) To: bright@mu.org Cc: jhb@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org In-Reply-To: <20010821134601.J81307@elvis.mu.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 21 Aug, Alfred Perlstein wrote: > How likely are these sort of fixes going to be able to help the > perceived instability of -current? Is -current noticeably unstable or > do we just have the usual crowd of people screaming sort of like what > was going on a couple of months ago. > > "current is broken" > "no it's not" > "yes it is" > "give me a crashdump" "yes it is, here:" http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=634686+642584+/usr/local/www/db/text/2001/freebsd-current/20010812.freebsd-current > ":P" Indeed. Not a word of reaction... Or should I've stuck this crash dump into some real flesh somewhere instead of just submitting it to -current? Just had another _reproduceable_ crash today again -- in ufshashdir (yes, it is a new feature).... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message