From owner-freebsd-stable Tue Oct 3 14: 7:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from hal9000.bsdonline.org (ffaxvawx3-4-047.cox.rr.com [24.168.203.47]) by hub.freebsd.org (Postfix) with ESMTP id 5EB1B37B502 for ; Tue, 3 Oct 2000 14:07:11 -0700 (PDT) Received: by hal9000.bsdonline.org (Postfix, from userid 1001) id 1800C1F55; Tue, 3 Oct 2000 17:07:05 -0400 (EDT) Date: Tue, 3 Oct 2000 17:07:05 -0400 From: Andrew J Caines To: FreeBSD Stable Subject: Re: More panics (different hardware) Message-ID: <20001003170705.D20080@hal9000.bsdonline.org> Reply-To: Andrew J Caines Mail-Followup-To: FreeBSD Stable References: <82946.970604803@winston.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <82946.970604803@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Oct 03, 2000 at 01:26:43PM -0700 Organization: H.A.L. Plant X-Powered-by: FreeBSD 4.1.1-STABLE Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, Cy and co., I'll admit my concept of time was taken from me during lectures on special relativity, but for all observers on the list, I added fdesc after the crashes began. I didn't see any problem with trying it. I'll add the mfs mounts back later and poke the system by running "periodic daily", since I think that the evidence is strong enough that there is something in there which is tickling the cause of the crashes. More details later. Thanks for your continued interest and assistance. BTW, I'm intentionally not updating my world, in case a change masks (as opposed to fixes) the problem. -Andrew- -- _______________________________________________________________________ | -Andrew J. Caines- Unix Systems Engineer A.J.Caines@altavista.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message