From owner-freebsd-hackers Sat Sep 25 9: 0:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 0E37414EF6; Sat, 25 Sep 1999 09:00:11 -0700 (PDT) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id SAA03999; Sat, 25 Sep 1999 18:58:41 +0300 (EEST) (envelope-from ady@warpnet.ro) Date: Sat, 25 Sep 1999 18:58:41 +0300 (EEST) From: Adrian Penisoara To: Mark Powell Cc: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: -stable (in)stability (was Re: Best version of FBSD for INN ?) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Fri, 24 Sep 1999, Mark Powell wrote: > I have INN v2.2 running happily on a 3.1-STABLE machine, with all mmap > options turned on. I read of mmap problems with 3.2-stable. Maybe my > server just isn't loaded enough to grok on these problmes, but when I set > up a new news server should I stay with 3.1 or have these problems been > fixed in 3.3? Cheers. You'd better stay with what it works for you right now. I'm sorry to say it but since upgrading to 3.2-STABLE about end of August I get random freezes every 1-2 days and even in 3.3-STABLE as of 20th September this seems to not have been fixed; other people also reported on -stable problems they had with 3.3 ... Before any of you start flaming me about hardware problems let me assure you I have thoroughly checked the machine and had DDB compiled in kernel; I also might add that this machine had NO problems before upgrading to 3.2/3.3 and had respectable uptimes (now I can't get over 3 days of uptime). This is not intended to subminate FreeBSD's image but rather to launch a "HEADS UP" warning in respect of -stable branch stability in this period of time. I'm willing to cooperate with whoever wants to fix this in the limits of my possibilities (this is a production server)... PS: I could have filed a PR but I can't figure any way of reproducing this -- just a double panic caught by my co-worker, details posted on -stable on 19th Sep with "3.2-STABLE hangs after several hours" in the subject... Thank you, Ady (@warpnet.ro) Warp Net Technologies To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message