From owner-freebsd-sparc64@FreeBSD.ORG Fri Oct 29 19:49:02 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E56F716A4CE for ; Fri, 29 Oct 2004 19:49:02 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFD3C43D2F for ; Fri, 29 Oct 2004 19:49:02 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E797952C13; Fri, 29 Oct 2004 12:50:25 -0700 (PDT) Date: Fri, 29 Oct 2004 12:50:25 -0700 From: Kris Kennaway To: Torfinn Ingolfsen Message-ID: <20041029195025.GA13306@xor.obsecurity.org> References: <20041029142314.50f154d3.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1yeeQ81UyVL57Vl7" Content-Disposition: inline In-Reply-To: <20041029142314.50f154d3.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.4.2.1i cc: freebsd-sparc64@freebsd.org Subject: Re: Buildworld on an Ultra1E - exception - what does it mean? X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 19:49:03 -0000 --1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 29, 2004 at 02:23:14PM +0200, Torfinn Ingolfsen wrote: > Hello, >=20 > I'm running FreeBSD 5.3-BETA7 on an Ultra 1E (170). I have cvsup'ed > source using the tag RELENG_5_3) yesterday. I started a buildworld, and > it had been going for som time (some hours) before the machine suddenly > was dead. So today I restarted the machine, thgis time with a serial > console hooked up. I started the buildworld, and sure ebough, after some > hours it hung again. I don't know exactly how far it has gotten, but the > last thing it was compiling (before the hang) was 'fstream-inst.So'. >=20 > On the serial console, I got this message: > ------------[ cut here ]------------ > root@ultra1# > RED State Exception >=20 > TL=3D0000.0000.0000.0005 TT=3D0000.0000.0000.0010 > TPC=3D0000.0000.c003.c200 TnPC=3D0000.0000.c003.c204 > TSTATE=3D0000.0044.5800.1500 TL=3D0000.0000.0000.0004 TT=3D0000.0000.0000= .0010 > TPC=3D0000.0000.c003.c200 TnPC=3D0000.0000.c003.c204 > TSTATE=3D0000.0044.5800.1500 TL=3D0000.0000.0000.0003 TT=3D0000.0000.0000= .0010 > TPC=3D0000.0000.c003.c200 TnPC=3D0000.0000.c003.c204 > TSTATE=3D0000.0044.5800.1500 TL=3D0000.0000.0000.0002 TT=3D0000.0000.0000= .0010 > TPC=3D0000.0000.c004.0f78 TnPC=3D0000.0000.c004.0f7c > TSTATE=3D0000.0044.5800.1400 TL=3D0000.0000.0000.0001 TT=3D0000.0000.0000= .0063 > TPC=3D0000.0000.001b.28e0 TnPC=3D0000.0000.001b.28e4 > TSTATE=3D0000.0000.0000.1202 > ------------[ cut here ]------------ >=20 > I don't know much about Sun hardware. Can anyone tell me what this > means, and what I can do about it? Hardware failure, apparently. From a reply when it happened to me on a particular machine (now decomissioned): ---- 99.99% of the time when you see a RED State exception it is either the CPU itself or its ECache. Since, if I've read the rest of the thread correctly, you're only seeing it under load it sounds like it's likely the ECache, not the processor itself. ---- kris --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBgp8BWry0BWjoQKURAhdpAJ47HQ14I/vM3PWWMG92Ubej29qzgwCdFT0n 4iQxFirALl9JtyLJwnYhHH0= =tVBf -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7--