From owner-freebsd-sparc64@FreeBSD.ORG Fri Sep 17 19:20:10 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 3787E16A4D0 for ; Fri, 17 Sep 2004 19:20:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606EB43D45 for ; Fri, 17 Sep 2004 19:20:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 4A2421FF9A7 for ; Fri, 17 Sep 2004 21:20:07 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id 3C8D81FF9A6; Fri, 17 Sep 2004 21:20:05 +0200 (CEST) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id D7554155A0; Fri, 17 Sep 2004 19:19:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id CC925154FC for ; Fri, 17 Sep 2004 19:19:42 +0000 (UTC) Date: Fri, 17 Sep 2004 19:19:42 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-sparc64@freebsd.org In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: Re: RED State Exception 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, 17 Sep 2004 19:20:10 -0000 On Fri, 17 Sep 2004, Bjoern A. Zeeb wrote: Hi, thanks for the immediate help again. As this is not freebsd specific you might want to ignore or respond off-list. I am posting this for the archives as googling hasn't presented that many results and few details. I might put a page once I find the time for that. Does anyone know how or where to decrypt this correctly ? If I should guess what is what I would say it goes like this: > ==== booting ==== > ... > Timecounters tick every 10.000 msec > > RED State Exception 4 memory banks first: bank 1: > TL=0000.0000.0000.0005 TT=0000.0000.0000.0010 > TPC=0000.0000.c003.c200 TnPC=0000.0000.c003.c204 TSTATE=0000.0044.5800.1505 bank 2: > TL=0000.0000.0000.0004 TT=0000.0000.0000.0010 > TPC=0000.0000.c003.c200 TnPC=0000.0000.c003.c204 TSTATE=0000.0044.5800.1505 bank 3: > TL=0000.0000.0000.0003 TT=0000.0000.0000.0010 > TPC=0000.0000.c003.c200 TnPC=0000.0000.c003.c204 TSTATE=0000.0044.5800.1505 bank 4: > TL=0000.0000.0000.0002 TT=0000.0000.0000.0010 > TPC=0000.0000.c004.0f80 TnPC=0000.0000.c004.0f84 TSTATE=0000.0044.5800.1505 CPU: > TL=0000.0000.0000.0001 TT=0000.0000.0000.0068 > TPC=0000.0000.f000.93d8 TnPC=0000.0000.f000.93dc TSTATE=0000.0044.0000.1606 > ==== dead ==== why ? the first four look quite similar apart from bank 4; the last one is different and thus might be CPU. I had 4 equal memory modules installed and I know that either the one in bank 3 or 4 or both might be damaged. With them in I got the 'RED State Exception' with them pulled off everything is fine. From the above output it might have only been the one in bank 4 that is damaged. I will check this once I will install the one/two replacement modules I luckily have but unluckily didn't have with me. If someone knows better and this is only BS please correct me! -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT