From owner-freebsd-sparc64@FreeBSD.ORG Wed Apr 6 05:38:14 2005 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 B6A2316A4CE for ; Wed, 6 Apr 2005 05:38:14 +0000 (GMT) Received: from tts.orel.ru (tts.orel.ru [213.59.64.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78CEC43D5A for ; Wed, 6 Apr 2005 05:38:13 +0000 (GMT) (envelope-from bel@orel.ru) Received: from orel.ru (pf1.net.orel.ru [213.59.64.75]) by tts.orel.ru (8.13.1/8.13.1/bel) with ESMTP id j365c7ki025449; Wed, 6 Apr 2005 09:38:08 +0400 Message-ID: <425375BA.5030003@orel.ru> Date: Wed, 06 Apr 2005 09:38:02 +0400 From: Andrew Belashov Organization: ORIS User-Agent: Mozilla/5.0 (X11; U; FreeBSD sparc64; en-US; rv:1.6) Gecko/20040407 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: imencke@servecentric.com References: <1112709924.9499.108.camel@slacker.servecentric.com> In-Reply-To: <1112709924.9499.108.camel@slacker.servecentric.com> X-Enigmail-Version: 0.83.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Zombi-Check: on netra2.orel.ru cc: freebsd-sparc64@freebsd.org Subject: Re: "RED state exception" on sun E220R 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: Wed, 06 Apr 2005 05:38:14 -0000 Hello, Ivo! Ivo Mencke wrote: > Recently installed 5.3-RELEASE on a sun E220R, single CPU, 256MB. The > machine has had nothing done to it, vanilla install and left there for a > few days. It was fine for over a week. Then yesterday, > > When i came back minicom told me the output below. These messages are > CPU or OBP problems i believe, or is it a known issue? Could it be bad > memory? > > Any advice much appreciated, > > Best regards, > ivo. > > test# uname -a > FreeBSD test.servecentric.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri > Nov 5 19:4 > test# > test# > test# > RED State > Exception > > TL=0000.0000.0000.0005 > TT=0000.0000.0000.0010 > TPC=0000.0000.c003.c200 TnPC=0000.0000.c003.c204 > TSTATE=0000.0044.5800.1502 > TL=0000.0000.0000.0004 > TT=0000.0000.0000.0010 > TPC=0000.0000.c003.c200 TnPC=0000.0000.c003.c204 > TSTATE=0000.0044.5800.1502 > TL=0000.0000.0000.0003 > TT=0000.0000.0000.0010 > TPC=0000.0000.c004.0f20 TnPC=0000.0000.c004.0f24 > TSTATE=0000.0044.5800.1502 > TL=0000.0000.0000.0002 > TT=0000.0000.0000.0063 > TPC=0000.0000.c004.0f8c TnPC=0000.0000.c004.0f90 > TSTATE=0000.0044.5800.1601 > TL=0000.0000.0000.0001 > TT=0000.0000.0000.0063 > TPC=0000.0000.4042.73f0 TnPC=0000.0000.4042.73dc > TSTATE=0000.0000.0000.1202 I shall try to interpret this message: Trap level (TL) = 1 (userland exception handler): Trap Type (TT) = 0x63 - implementation_dependent_exception_3 (impl. dep. #35) [1] - corrected_ECC_error [2] Trap Program Counter (TPC) = 0x404273f0 Trap level (TL) = 2 (exception in exception handler): Trap Type (TT) = 0x63 - implementation_dependent_exception_3 (impl. dep. #35) [1] - corrected_ECC_error [2] Trap Program Counter (TPC) = 0xc0040f90 Trap level (TL) = 3 (crash): Trap Type (TT) = 0x10 - illegal_instruction [1] Trap Program Counter (TPC) = 0xc0040f20 [1] The SPARC Architecture Manual, Version 9. [2] UltraSPARC-IIi User's Manual. This problem is very similar to another, described in message . IMHO, this is hardware problem. First, try to clean contacts (or simply reinsert) RAM and CPU modules. SAFETY WARNING: Always follow ELECTROSTATIC DISCHARGE DAMAGE prevention procedures when removing and replacing components. -- With Best Regards, Andrew Belashov.