From owner-freebsd-alpha Thu Jul 13 22:45:41 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 91DF437BAD3; Thu, 13 Jul 2000 22:45:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id WAA12580; Thu, 13 Jul 2000 22:45:22 -0700 Date: Thu, 13 Jul 2000 22:45:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: wilko@FreeBSD.ORG Cc: Andrew Gallatin , Alec Wolman , freebsd-alpha@FreeBSD.ORG Subject: Re: warning: received processor correctable error message In-Reply-To: <20000713194911.D975@freebie.demon.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I did a bit of this kind of stuff for NetBSD-alpha for decoding the logout frames and reporting errors. Mostly this stuff is only important for doing SIMM replacement, and as such it fell to the bottom of my list of important things to do. But not quite true for the TurboLaser because you have to do some patchups even for a 670 error because the I/O boards (KTLA, KFTH) can cause such errors when they fill ram on the memory boards, and the PAL code for any particular processor hasn't got the smarts or moxie to go out and then do the ECC scrub it would do if it were the CPU causing the error- or at leat that's my recollection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message