Date: 21 Aug 2001 21:13:02 +0200 From: Dag-Erling Smorgrav <des@ofug.org> To: Alfred Perlstein <bright@mu.org> Cc: John Baldwin <jhb@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_condvar.c kern_synch.c src/sys/sys proc.h Message-ID: <xzppu9p1b29.fsf@flood.ping.uio.no> In-Reply-To: <20010821134601.J81307@elvis.mu.org> References: <200108211842.f7LIgkp03186@freefall.freebsd.org> <20010821134601.J81307@elvis.mu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alfred Perlstein <bright@mu.org> writes: > 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. I don't think -CURRENT is particularly unstable, but it seems to have issues with resource allocations that only affect certain motherboards or chipsets. It's been getting steadily worse since the beginning of June - first my floppy drive stopped working, then I started getting massive ISA interrupt lossage (but only after a few hours of uptime), then my floppy drive stopped even attaching. I haven't had a single crash, though. DES -- Dag-Erling Smorgrav - des@ofug.org 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?xzppu9p1b29.fsf>