Date: Tue, 21 Aug 2001 15:28:31 -0400 (EDT) From: mi@aldan.algebra.com To: bright@mu.org Cc: jhb@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: "current is broken" (Re: cvs commit: src/sys/kern kern_condvar.c kern_synch.c src/sys/sys proc.h) Message-ID: <200108211928.f7LJSXk01254@misha.privatelabs.com> In-Reply-To: <20010821134601.J81307@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200108211928.f7LJSXk01254>