Date: Wed, 9 Jun 2004 14:18:05 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Chris Flecknell <cflecknell@altsoftware.com> Cc: freebsd-sparc64@freebsd.org Subject: Re: RED State Message-ID: <20040609141758.W41595@carver.gumbysoft.com> In-Reply-To: <000a01c44ca7$88457800$c702a8c0@altsoftware.com> References: <000a01c44ca7$88457800$c702a8c0@altsoftware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Jun 2004, Chris Flecknell wrote:
> I had asked about this previously and was told remounting the CPU and/or RAM
> can sometimes fix this.. I remounted the CPU in my Ultra10 and it's now
> been up and online for over a month.
I think that qualifies as a "hardware issue." :-)
>
> Chris Flecknell
> System Administrator
> Alt Software Inc.
> 416.203.8058 ext 1600
> cflecknell@altsoftware.com
>
> > -----Original Message-----
> > From: owner-freebsd-sparc64@freebsd.org
> > [mailto:owner-freebsd-sparc64@freebsd.org]On Behalf Of Doug White
> > Sent: June 7, 2004 1:52 AM
> > To: Mark Cartwright
> > Cc: freebsd-sparc64@freebsd.org
> > Subject: Re: freebsd-sparc64 Digest, Vol 63, Issue 4
> >
> >
> > 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 <kris@obsecurity.org>
> > > > Subject: Re: panic: trapanic: vm_fault: fault on
> > > > nofault entry, addr:
> > > > cfd76000
> > > > To: Kris Kennaway <kris@obsecurity.org>
> > > > 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
> > _______________________________________________
> > 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"
>
> _______________________________________________
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040609141758.W41595>