From owner-freebsd-alpha Mon Apr 1 7:29:29 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 3990437B419 for ; Mon, 1 Apr 2002 07:29:08 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g31FT5U38122; Mon, 1 Apr 2002 17:29:05 +0200 (CEST) (envelope-from wkb) Date: Mon, 1 Apr 2002 17:29:05 +0200 From: Wilko Bulte To: Christian Weisgerber Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Source of "processor correctable error"? Message-ID: <20020401172905.A38101@freebie.xs4all.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from naddy@mips.inka.de on Mon, Apr 01, 2002 at 02:46:13PM +0000 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@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 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. > > 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? Main memory would be my #1 guess. -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands We are FreeBSD. Resistance is futile. Prepare to be committed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message