From owner-freebsd-current Thu Nov 16 10:44:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 7430137B479 for ; Thu, 16 Nov 2000 10:44:25 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eAGIgpi10148; Thu, 16 Nov 2000 10:42:51 -0800 (PST) Date: Thu, 16 Nov 2000 10:42:51 -0800 From: Alfred Perlstein To: "Steven E. Ames" Cc: Soren Schmidt , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... Message-ID: <20001116104251.D830@fw.wintelcom.net> References: <200011161717.SAA30813@freebsd.dk> <027d01c04ff1$90d9cf40$8a1a050a@winstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <027d01c04ff1$90d9cf40$8a1a050a@winstar.com>; from steve@virtual-voodoo.com on Thu, Nov 16, 2000 at 12:20:49PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Steven E. Ames [001116 09:27] wrote: > It seems to only do it SMP... the same machine built with a non-SMP > kernel (same source code) runs just fine for extended periods. John just checked in some code last night that may address your problems. I would try a new kernel, and perhaps some collabaration with John to debug these problems rather than just complaining about the situation. I see at least two experianced developers in the CC list, there's no reason for these poor bug reports. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message