From owner-freebsd-hackers Wed Jul 24 15:42: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7093C37B400 for ; Wed, 24 Jul 2002 15:42:03 -0700 (PDT) Received: from zang.com (zang.com [216.34.130.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF5BB43E31 for ; Wed, 24 Jul 2002 15:42:02 -0700 (PDT) (envelope-from johne@zang.com) Received: by zang.com (Postfix, from userid 100) id 353044EBE0; Wed, 24 Jul 2002 15:42:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by zang.com (Postfix) with ESMTP id 0F7D63B6D7; Wed, 24 Jul 2002 15:42:02 -0700 (PDT) Date: Wed, 24 Jul 2002 15:42:01 -0700 (PDT) From: John Engelhart To: Wilko Bulte Cc: hackers@FreeBSD.ORG Subject: Re: Serious File System problems (4.6-Release) In-Reply-To: <20020725001049.B67097@freebie.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 25 Jul 2002, Wilko Bulte wrote: > On Wed, Jul 24, 2002 at 02:32:25PM -0700, John Engelhart wrote: > > > > Thoughts? Is it memory? Is it CPU? One of the CPU's is brand new. One > > of the CPU's is left over from one of the original systems. I've just > > purchased another CPU to rule that out. I've also picked up a stick of > > 128 megs of ram, one with and one without ECC, to see if that's causing > > the problem. Or am I on to some insidous SMP bug? > > > > Guessing (obviously): power supply? Good suggestion. I've been through four, however. All with the same problem. The original 2460 was kinda particular about it's power supplies, the 2466 seems less so as it's got the P4 extra power supply connector to help with the dual proc power needs. No special voltage requirements are specificed for the 2466. I'm wondering if it's not the CPU. If it were the RAM, I'd figure that ECC would trip up before it allowed for that kind of corruption. *sigh*. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message