Bo:
In this HH explain Asyc. Mem Fault in Box style B.
Regards,
HH#: HH927
IA INFO: aja0001
File: Solaris
Release: Solaris 2.x
Date: Mar 03, 2000
Subject: Asynchronous Memory Fault DSIMM Identification
Source: TAC
If a station panics due to an asynchronous memory fault, it is possible to
identify what memory DSIMM board caused the problem. The panic string
usually
will reveal the memory address of the fault as in the example below.
Feb 26 10:57:37 AWLBUG unix: panic: asynchronous memory fault: MFSR=81804860
MFAR=245a258
The useful bit here is the Memory Fault Address Register, MFAR. This
register contains the physical address of the faulting location. Compare
the address in the MFAR, 0x245a258, to the address ranges depicted in
the appropriate Manufacturing Kit Document found on
http://www.csc.foxboro.com/
under stuffer documents and you'll see that it falls in the range of
0x02000000
to 0x03FFFFF which corresponds to J0301.
Example of AW51B memory slot layout found in B0193PF-B:
(NOTE: assumes 32M DSIMM's are installed)
Slot Slot # Physical Memory Address Ranges
0 J0300 0000 0000 through 01FF FFFF
1 J0301 0200 0000 through 03FF FFFF
2 J0302 0400 0000 through 05FF FFFF
3 J0303 0600 0000 through 07FF FFFF
4 J0400 0800 0000 through 09FF FFFF
5 J0401 0A00 0000 through 0BFF FFFF
6 J0402 0C00 0000 through 0DFF FFFF
7 J0403 0E00 0000 through 0FFF FFFF
In most cases reseating the DSIMM board will correct any future faults.
However,
if the problem persists and the address of the fault is within the same
DSIMM,
it should be replaced.
Dante C�sar DI SPALATRO
Invensys Process Automation - Argentina
-----Mensaje original-----
De: Stear, Bo [mailto:[EMAIL PROTECTED]]
Enviado el: Thursday, April 26, 2001 14:06
Para: 'Foxboro Mail Forum'
Asunto: Asynchronous Memory Errors
Good day all.
I am trying to gather as much information as I can to help analyze
persistent Asynchronous Memory Error reboots on some, if not all, of our
AP51B and WP51B boxes. These are fairly rare reboots and usually are not
hard failures. The symptom is simple, an AP, AW, or WP reboots without
warning. the /var/adm/messages file contains a message that states a Panic
dump was made, the Asynchronous Memory Error was the reason and also lists
the offending memory address. As far as I can remember, this problem has
existed since the very first 'B' box was installed in our plant. Now, with
nearly 100 of them in service, we see altogether too many of them over a
years time. Since we have such a large number of 'B' boxes, it appears to
Foxboro that we here at PPG are seeing more of these faults than the rest of
the customer base (thats YOU). But I wonder???
If you would be so kind, please answer the following questions:
1. Have you ever experienced this failure?
If so, please continue:
2. On average, how many times per year?
3. How many 'B' boxes do you have in service?
4. What method have you been using to repair (reboot, replace cimms,
replace 'B' box, etc.)
Thanks to all who participate...
Bo
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All postings from
this list are the work of list subscribers and no warranty is made or implied as to
the accuracy of any information disseminated through this medium. By subscribing to
this list you agree to hold the list sponsor(s) blameless for any and all mishaps
which might occur due to your application of information received from this mailing
list.
To be removed from this list, send mail to [EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
