From owner-freebsd-alpha Mon Apr 1 6:47:19 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id F232E37B417 for ; Mon, 1 Apr 2002 06:47:14 -0800 (PST) Received: from kemoauc.mips.inka.de (uucp@) by mail.inka.de with local-bsmtp id 16s35V-0005IG-00; Mon, 1 Apr 2002 16:47:13 +0200 Received: from kemoauc.mips.inka.de (localhost [127.0.0.1]) by kemoauc.mips.inka.de (8.12.2/8.12.2) with ESMTP id g31EkDiM098029 for ; Mon, 1 Apr 2002 16:46:13 +0200 (CEST) (envelope-from mailnull@localhost.mips.inka.de) Received: (from mailnull@localhost) by kemoauc.mips.inka.de (8.12.2/8.12.2/Submit) id g31EkDTf098028 for freebsd-alpha@freebsd.org; Mon, 1 Apr 2002 16:46:13 +0200 (CEST) (envelope-from mailnull) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Source of "processor correctable error"? Date: Mon, 1 Apr 2002 14:46:13 +0000 (UTC) Message-ID: Originator: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-alpha@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Since the weekend my PC164 has taken to almost continuously spewing gobs of Warning: received processor correctable error. In fact I first noticed this because writing the error messages to the serial console took so much time the machine became sluggish. I've switched to a graphics console now. Anyway, is there a way to narrow down the source of the underlying hardware problem? What are the candidates anyway? On-chip cache, off-chip cache, main memory? The machine has eight SIMMs (for a total of 256M). I guess, I'll start by taking out half (and setting the memory width back to 128 bits) and see whether this has any effect. Suggestions? -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message