[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | laser |
|
| Moderator: | PROXY::ALLEN |
|
| Created: | Thu Jul 16 1992 |
| Last Modified: | Wed May 28 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1267 |
| Total number of notes: | 4891 |
1244.0. "Need help breaking down 2GB module CRD" by CSC32::MCLEAN () Thu Jan 30 1997 21:11
Having trouble breaking down CRD errors on a 2GB MS7AA-PA module in a
VAX 7000-730 running VMS 6.1. This system has been logging CRD errors as
hanging intermittently.
This system has hung at least 3 times in the last 4 months with indications
that it has tied up at high ipl (8 or above) for an extended (29 minutes
yesterday) period. Last entries on the interrupt stack prior to the forced
crash some CRD error handling active and valid CRD footprint being setup.
The standard error log doesn't break out the Syndrome or string information.
A binary dump of the errorlog shows the error to be in string 0 and a syndrome
7C. Binary errorlog has been run against ANAL/ERROR on versions 6.1, 6.2 and
7.0 with the same results.
That syndrome does not appear to be valid. It doesn't appear in any breakout
table we have found so far.
I ran the error past the DECevent development folks here in CXO and they
couldn't shed any additional light on the matter.
At this point we're looking for some additional insight into the error. Are
we looking at a motherboard or a simm failure? And if it is a simm what simm
or simms?
Swapping an entire 2BG at a rather high cost to the local DEC office is not
seen as a workable solution at this point.
I've included an example error found the system as well as a dump output of
a single entry binary errorlog file.
Note that additional errors showed the same string and syndrome but slight
variations in the actual physical addresses.
Thanks
Jim McLean
Mission Critical Support Team
--------------------------------------------------------------------------------
MARLIN$ anal/err/sin=today/incl=mem/excl=unknown
Error Log Report Generator Version V6.1
******************************* ENTRY 5667. *******************************
ERROR SEQUENCE 12656. LOGGED ON: SID 17000201
DATE/TIME 30-JAN-1997 10:39:33.21 SYS_TYPE 01420201
SYSTEM UPTIME: 0 DAYS 17:14:02
SCS NODE: MARLIN VAX/VMS V6.1
MEMORY CRD EVENT
FLAGS 0002
SYSLOA MEMORY DESCRIPTOR
LOG REASON 0020
DOMAIN EXTENDS BEYOND A SINGLE PAGE
ENTRY REVISION = 0.
RELATED ENTRY 1 OF 1
00000000 RPB$L_BADPGS = 00000000 (HEX)
MEMORY DESCRIPTOR
MEMORY DESC F9C00000
00004000
0000000D
00000321
10000000
00000000
1 FOOTPRINTS IN THIS PACKET
CRD FOOTPRINT #1
FOOTPRINT 0704FDA8
00000000
SYSTEM TIME 30-JAN-1997 09:03:32.05
LOW PHY ADR 00250D80
00000000
HIGH PHY ADR 00252F40
00000000
CUM ADR 000022C0
00000000
STATIC FLAGS 0003
FOOTPRINT IN USE
HARDWARE SCRUBBED
DYNAMIC FLAGS 0001
CALLER FLAGS 00000000
SCRUB BLKSIZE 00000040
MAX PAGREP 0400
UNIT ID 0004
PAGE TYPE 0001
PROCESS PAGE
LOG REASON 0020
SCRUB FAIL 00000000
PAGREP FAIL 00000000
SCRUB PGLOC 00000000
PAGREP PGLOC 00000000
MATCH COUNT 00000001
PAGE REP CNT 00000000
NUMBER OF PAGES REPLACED = 0.
PRE SCRUB CNT 00000000
POST SCRUB CNT 00000000
Buddry $ dump jan_30_mem.bin
File ID (11486,242,0) End of file block 1 / Allocated 3
Virtual block number 1 (00000001), 512 (0200) bytes
00000000 01420201 FFFB1700 020100E8 �.....�...B..... 000000
00000000 0020204E 494C5241 4D080000 ...MARLIN ..... 000010
009AF222 57F89CF4 000E4001 00000000 .....@..�.�W"�.. 000020
F25A0000 00042020 2020312E 36563170 p1V6.1 ....Z� 000030
00000000 00000101 00200002 00000000 ...... ......... 000040
006C0000 00010000 00640000 00180000 ......d.......l. 000050
000D0000 4000F9C0 00000000 007C0000 ..|.....��.@.... 000060
^^ ^^
Failing string Syndrome
FDA80000 00001000 00000000 03210000 ..!............. 000070
0D80009A F214EE0D 5C740000 00000704 ......t\.�.�.... 000080
22C00000 00000025 2F400000 00000025 %.....@/%.....�" 000090
00400000 00000001 00030000 00000000 ..............@. 0000A0
00000000 00000020 00010004 04000000 ........ ....... 0000B0
00000000 00010000 00000000 00000000 ................ 0000C0
00000000 00000000 00000000 00000000 ................ 0000D0
00000000 00000000 00000000 00000000 ................ 0000E0
00000000 00000000 00000000 00000000 ................ 0000F0
00000000 00000000 00000000 00000000 ................ 000100
00000000 00000000 00000000 00000000 ................ 000110
00000000 00000000 00000000 00000000 ................ 000120
00000000 00000000 00000000 00000000 ................ 000130
00000000 00000000 00000000 00000000 ................ 000140
00000000 00000000 00000000 00000000 ................ 000150
00000000 00000000 00000000 00000000 ................ 000160
00000000 00000000 00000000 00000000 ................ 000170
00000000 00000000 00000000 00000000 ................ 000180
00000000 00000000 00000000 00000000 ................ 000190
00000000 00000000 00000000 00000000 ................ 0001A0
00000000 00000000 00000000 00000000 ................ 0001B0
00000000 00000000 00000000 00000000 ................ 0001C0
00000000 00000000 00000000 00000000 ................ 0001D0
00000000 00000000 00000000 00000000 ................ 0001E0
00000000 00000000 00000000 00000000 ................ 0001F0
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1244.1 | | PROXY::HELLEN | | Mon Feb 03 1997 11:03 | 6 |
| Using the value A8 from FOOTPRINT as the syndrome and the value 4 for
string from nibble 4 in FOOTPRINT yields J4 assuming the A side. If A8
is the correct syndrome then this error comes from J4 or J5 or J30 or
J31. If you can control P when the machine hangs save the contents of
MS7AAn:2100 MS7AAn:2140 MS7AAn:2180 MS7AAn:4140 MS7AAn:4180 for the
2Gig. This will tell more.
|