From owner-freebsd-alpha Tue Dec 5 12:34:47 2000 From owner-freebsd-alpha@FreeBSD.ORG Tue Dec 5 12:34:45 2000 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 7B7A337B400 for ; Tue, 5 Dec 2000 12:34:45 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id PAA02809; Tue, 5 Dec 2000 15:34:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eB5KYiX18274; Tue, 5 Dec 2000 15:34:44 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 5 Dec 2000 15:34:44 -0500 (EST) To: Wilko Bulte Cc: freebsd-alpha@freebsd.org Subject: Re: part numbers for 2100 5/300 processor modules? In-Reply-To: <20001205210513.M346@freebie.demon.nl> References: <20001204155447.E1431@layer8.net> <14892.14352.956036.813077@grasshopper.cs.duke.edu> <20001205205555.H346@freebie.demon.nl> <14893.18646.222048.868530@grasshopper.cs.duke.edu> <20001205210513.M346@freebie.demon.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14893.20355.234641.954094@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > > Tomorrow we will know more. Today I first had to remove the broken > 512Mb memory module from the Lynx. FreeBSD does not tolerate memory errors, > the ECC needs CPU help and that is not given. Instead a panic is done ;-) Ecc errors are tolerated: Jul 11 13:50:00 hurricane /kernel: Warning: received processor correctable error. This is an AS600 5/266. I'm pretty sure its an ecc error because it complained of them fairly bitterly back when it was running Tru64. I think the problem is that memory which is totally broken and generates a machine-check when accessed is not tolerated by FreeBSD, but is tolerated by Tru64. Somebody once told me that Tru64 probes all the memory and is smart enough to not use bad memory, that's probably how it survives on your machine.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message