From owner-freebsd-sparc64@FreeBSD.ORG  Fri Mar 18 06:59:40 2005
Return-Path: <owner-freebsd-sparc64@FreeBSD.ORG>
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 E4D4F16A4CE
	for <sparc64@freebsd.org>; Fri, 18 Mar 2005 06:59:40 +0000 (GMT)
Received: from tts.orel.ru (tts.orel.ru [213.59.64.67])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0771343D2D
	for <sparc64@freebsd.org>; Fri, 18 Mar 2005 06:59:40 +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 j2I6xbZc015950;
	Fri, 18 Mar 2005 09:59:38 +0300
Message-ID: <423A7C54.3010509@orel.ru>
Date: Fri, 18 Mar 2005 09:59:32 +0300
From: Andrew Belashov <bel@orel.ru>
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: Xavier Beaudouin <kiwi@oav.net>
References: <2c508b24c1e34f7f72c7e83b07177d81@oav.net>
	<42399873.5020006@orel.ru> <3881aa4a9f1f2b7d65fad2123eaaf721@oav.net>
In-Reply-To: <3881aa4a9f1f2b7d65fad2123eaaf721@oav.net>
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: sparc64@freebsd.org
Subject: Re: RED State Exception with Netra T1 105 and FreeBSD 5.3 (RC
	/RELEASE or even -p5)
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
	<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Mar 2005 06:59:41 -0000

Xavier Beaudouin wrote:
> [...]
> 
>>> RED State Exception
>>> TL=0000.0000.0000.0005 TT=0000.0000.0000.0080
>>>    TPC=0000.0000.c003.4208 TnPC=0000.0000.c003.420c 
>>> TSTATE=0000.0044.5800.1504
>>> TL=0000.0000.0000.0004 TT=0000.0000.0000.0010
>>>    TPC=0000.0000.c003.4218 TnPC=0000.0000.c003.421c 
>>> TSTATE=0000.0044.5800.1504
>>> TL=0000.0000.0000.0003 TT=0000.0000.0000.0010
>>>    TPC=0000.0000.c003.4218 TnPC=0000.0000.c003.421c 
>>> TSTATE=0000.0044.5800.1503
>>> TL=0000.0000.0000.0002 TT=0000.0000.0000.0010
>>>    TPC=0000.0000.c003.8f80 TnPC=0000.0000.c003.8f84 
>>> TSTATE=0000.0044.5800.1402
>>> TL=0000.0000.0000.0001 TT=0000.0000.0000.0063
>>>    TPC=0000.0000.4056.f250 TnPC=0000.0000.4056.f254 
>>> TSTATE=0000.0044.0000.1201
>>
>>
>> Trap level (TL) = 1 (kernel):
>> Trap Type (TT) = 0x63 - implementation_dependent_exception_3 (impl. 
>> dep. #35)
>> - corrected_ECC_error for UltraSPARC-IIi Processor
> 
> 
> This is ... what I was afraid of.... ;/
> 
>> Trap Program Counter (TPC) = 0x4056f250
>>
>> You may try to disassemble kernel code 0x4056f250:
>> (kgdb) x/10i 0x4056f250
>>
>> Trap level (TL) = 2 (exception in kernel routines):
>> Trap Type (TT) = 0x10 - illegal_instruction
>> Trap Program Counter (TPC) = 0xc0038f80
>>
>> See "The SPARC Architecture Manual, Version 9" and "UltraSPARC-IIi 
>> User's Manual".
>>
>> This is harware problem?
> 
> 
> I dunno, but this errors is comming less frequently when I turn off 
> softupdates and
> when I mount all disk with -o sync.
> 
> Do you think this is RAM that is going to be faulty ?

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.

> 
> /Xavier

To ALL:

I have looked the source code (src/sys/sparc64/sparc64/exception.S,
src/sys/i386/i386/trap.c) and has found, that the kernel go to panic,
when corrected ECC error exception occured.

This is correct?

--
With Best Regards,
Andrew Belashov.