[2868] in SIPB-AFS-requests

home help back first fref pref prev next nref lref last post

Re: ra paniced

daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Sun Oct 19 18:23:41 1997

From: mhpower@MIT.EDU
To: jhawk@MIT.EDU
Cc: sipb-afsreq@MIT.EDU
In-Reply-To: "[2864] in SIPB-AFS-requests"
Date: Sun, 19 Oct 1997 18:23:32 EDT

>Async memory fault mfsr=0x81804040 mfar=0x33f5280
>panic on cpu 0: async memory fault
>esp0: Unrecoverable DMA error on dma

This may be a symptom of a hardware problem that occurs on Sparc 5s.
I've attached two messages about it below. We might want to try
installing 101508-15 (101508-07 is apparently already installed),
although I don't have any evidence that -15 better addresses our
particular problem than does -07.

Also, we may want to check whether the amount and arrangement of
memory on ronald-ann is exactly the same as on many other Sparc 5s at
MIT. If it isn't, we may benefit from trying a different memory
configuration.

Matt


------- Forwarded Article 1

Newsgroups: comp.sys.sun.admin
Subject: SS5 Async memory fault - again!
From: Raju Krishnamurthy <raju>
Date: Mon, 22 Jul 1996
Message-Id: <4t0jbq$gjl@odysseus.gonzaga.pvt.k12.dc.us>
...
I just upgraded from SunOS 4.1.3_U1 to Solaris 2.4 on a SPARC 5 with 64MB and
am now occasionally getting a "panic: asynchronous memory fault" and the
machine will reboot.  As I understand it, this is a 'well known' hardware
problem in SPARC 5's with certain memory configurations, and jumbo patch
#101508-XX fixes the problem for SunOS 4.1.3, but I wasn't able to find the
cooresponding patch for Solaris 2.x (I installed #101945-41, thinking that
might be it, but it still panics).
...

------- End of Forwarded Article 1


------- Forwarded Article 2

Newsgroups: comp.sys.sun.admin
Subject: Re: Async memory fault
From: kwieman@bfm.com (Karl Wieman)
Date: Tue, 18 Apr 1995
Message-Id: <D78HFs.HCp@bfm.com>
...
: Can anyone help me with why I would get this panic on a SparcStation 5
: running SunOS 4.1.3_U1 rev B?  What does this error mean?

:       Async memory fault mfsr=0x81884820 mfar=0x10e87a8
...
It means your missing patch 101508-07 or later.  Though it appears to only
slow the frequency of the crashes...not eliminate them.

------- End of Forwarded Article 2

home help back first fref pref prev next nref lref last post