Date: Sat, 21 Nov 1998 20:06:31 +0100 From: Eivind Eklund <eivind@yes.no> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Barrett Richardson <terbart@aye.net>, garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons Message-ID: <19981121200631.G23705@follo.net> In-Reply-To: <199811211840.KAA24741@apollo.backplane.com>; from Matthew Dillon on Sat, Nov 21, 1998 at 10:40:48AM -0800 References: <199811210418.UAA06160@hub.freebsd.org> <Pine.BSF.3.96.981121025345.26942A-100000@phoenix.aye.net> <19981121164344.E17306@follo.net> <199811211840.KAA24741@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 21, 1998 at 10:40:48AM -0800, Matthew Dillon wrote: > >> The bug in question is "new" (23rd february, most likely), and is not >> visible in -stable. It is a serious bug. Saying that his swap usage >> is 'too high' is not going to help us solve it; the system is supposed >> to be stable no matter what. We can't take 3.0 to be -STABLE until >> this bug and the clock bug is solved. >> >> Eivind. > > We need to find a way to reproduce the problem. I'm running serveral > -current systems, one very heavily (nntp1.ba.best.com), and swap > utilization is normal. > > Is the original person who reported the problem using MFS mounts by any > chance? I have the problem. I don't use MFS mounts. It is also extremely difficult to reproduce here (comes when my workstation has been up for weeks, usually). The only common factor I know of so far (and I'm not sure it is common) is that we all run FreeBSD :-); also, all I have asked run X and Netscape. No hardware common in common. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981121200631.G23705>