From owner-freebsd-sparc64@FreeBSD.ORG Mon Jun 7 05:52:16 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 7C01616A4CE for ; Mon, 7 Jun 2004 05:52:16 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 525C843D49 for ; Mon, 7 Jun 2004 05:52:16 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 40E4272DF4; Sun, 6 Jun 2004 22:52:16 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3BE6D72DB5; Sun, 6 Jun 2004 22:52:16 -0700 (PDT) Date: Sun, 6 Jun 2004 22:52:16 -0700 (PDT) From: Doug White To: Mark Cartwright In-Reply-To: <20040604195317.45403.qmail@web21508.mail.yahoo.com> Message-ID: <20040606224703.Q12662@carver.gumbysoft.com> References: <20040604195317.45403.qmail@web21508.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-sparc64@freebsd.org Subject: Re: freebsd-sparc64 Digest, Vol 63, Issue 4 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: Mon, 07 Jun 2004 05:52:16 -0000 On Fri, 4 Jun 2004, Mark Cartwright wrote: > Heya. I'm not a developer, so can't speak to all > possible causes of this (such as actual kernel code, > etc), but I am a pretty proficient Sun guy so can > speak on at leas thte first part. > > 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. Sounds about right. From a sunsolve doc: "Red State" exception error messages are generated by the OBP when a CPU is hung and normal execution cannot be continued. The specific article this appeared in referred to a firmware bug in V480/V880 systems, so it can be caused by CPU or chipset programming bugs. For a machine that hasn't died before, though, I'd suspect a hardware issue. > > Hope this helps. > > > Message: 1 > > Date: Thu, 3 Jun 2004 18:24:14 -0700 > > From: Kris Kennaway > > Subject: Re: panic: trapanic: vm_fault: fault on > > nofault entry, addr: > > cfd76000 > > To: Kris Kennaway > > Cc: sparc64@FreeBSD.org > > Message-ID: > > <20040604012414.GA89079@xor.obsecurity.org> > > Content-Type: text/plain; charset="us-ascii" > > > > On Mon, May 31, 2004 at 08:08:07PM -0700, Kris > > Kennaway wrote: > > > One of the sparc machines (running -CURRENT from > > about 2 days ago) panicked: > > > > > > panic: trapanic: vm_fault: fault on nofault entry, > > addr: cfd76000 > > > at line 277 in file > > > /a/portbuild/sparc64/src-client/sys/vm/vm_fault.ccpuid > > = 0; > > > Debugger("panic") > > > Stopped at > > > RED State Exception > > > > > > TL=0000.0000.0000.0005 TT=0000.0000.0000.0080 > > > TPC=0000.0000.c003.c208 > > TnPC=0000.0000.c003.c20c TSTATE=0000.0044.5800.1507 > > > TL=0000.0000.0000.0004 TT=0000.0000.0000.0010 > > > TPC=0000.0000.c004.0f48 > > TnPC=0000.0000.c004.0f4c TSTATE=0000.0044.5800.1507 > > > TL=0000.0000.0000.0003 TT=0000.0000.0000.0010 > > > TPC=0000.0000.c004.0f48 > > TnPC=0000.0000.c004.0f4c TSTATE=0000.0044.5800.1506 > > > TL=0000.0000.0000.0002 TT=0000.0000.0000.0063 > > > TPC=0000.0000.c004.0fac > > TnPC=0000.0000.c004.0fb0 TSTATE=0000.0044.5800.1605 > > > TL=0000.0000.0000.0001 TT=0000.0000.0000.0068 > > > TPC=0000.0000.4020.f87c > > TnPC=0000.0000.4020.f880 TSTATE=0000.0099.0000.1206 > > > > > > It hung here. > > > > Got another one: > > > > TL=0000.0000.0000.0005 TT=0000.0000.0000.0068 > > TPC=0000.0000.c003.d000 TnPC=0000.0000.c003.d004 > > TSTATE=0000.0044.5800.1504 > > TL=0000.0000.0000.0004 TT=0000.0000.0000.0080 > > TPC=0000.0000.c003.c208 TnPC=0000.0000.c003.c20c > > TSTATE=0000.0044.5800.1502 > > TL=0000.0000.0000.0003 TT=0000.0000.0000.0010 > > TPC=0000.0000.c003.cd00 TnPC=0000.0000.c003.cd04 > > TSTATE=0000.0044.5804.1402 > > TL=0000.0000.0000.0002 TT=0000.0000.0000.0068 > > TPC=0000.0000.c004.0f64 TnPC=0000.0000.c004.0f68 > > TSTATE=0000.0044.5800.1502 > > TL=0000.0000.0000.0001 TT=0000.0000.0000.0063 > > TPC=0000.0000.0012.687c TnPC=0000.0000.0012.6880 > > TSTATE=0000.0099.0000.1201 > > > > Is this a sign of hardware failure? > > > > > > > > __________________________________ > Do you Yahoo!? > Friends. Fun. Try the all-new Yahoo! Messenger. > http://messenger.yahoo.com/ > _______________________________________________ > freebsd-sparc64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64 > To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org