From owner-freebsd-alpha Mon Apr 1 7:24: 3 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by hub.freebsd.org (Postfix) with ESMTP id 17FEB37B41D for ; Mon, 1 Apr 2002 07:23:50 -0800 (PST) Received: (from uucp@localhost) by srv1.cosmo-project.de (8.11.6/8.11.6) with UUCP id g31FNkk38754; Mon, 1 Apr 2002 17:23:47 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.1.10]) by cicely5.cicely.de (8.12.1/8.12.1) with ESMTP id g31FMm6e071321; Mon, 1 Apr 2002 17:22:49 +0200 (CEST)?g (envelope-from ticso@cicely8.cicely.de) Received: from cicely8.cicely.de (localhost [127.0.0.1]) by cicely8.cicely.de (8.12.2/8.12.2) with ESMTP id g31FMlnU041834; Mon, 1 Apr 2002 17:22:48 +0200 (CEST) (envelope-from ticso@cicely8.cicely.de) Received: (from ticso@localhost) by cicely8.cicely.de (8.12.2/8.12.2/Submit) id g31FMkur041833; Mon, 1 Apr 2002 17:22:47 +0200 (CEST) Date: Mon, 1 Apr 2002 17:22:44 +0200 From: Bernd Walter To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020401152244.GE41357@cicely8.cicely.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.26i X-Operating-System: FreeBSD cicely8.cicely.de 5.0-CURRENT i386 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 On Mon, Apr 01, 2002 at 02:46:13PM +0000, Christian Weisgerber wrote: > Since the weekend my PC164 has taken to almost continuously spewing > gobs of > > Warning: received processor correctable error. These are most likely main memory errors. > 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. It's a good start. You might also remove and reinsert the simms as the contacts get bad over time. If you can get such an error while in SRM it will print you a more usefull message. Theoreticaly you could get the simm slot number but FreeBSD doesn't support it because there is no documentation for most boards. Well the PC164 as an OEM board has a better documentation so it may worth to think about implementing such a feature. I often thought about hacking this board as the chipset could handle up to 8G memory with 16 banks while the board only can do with up to 512M in a single bank. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message