Table of Contents
Advertisement
Corrective Maintenance
Prime Proprietary
TABLE 6-10: DSWPARITY WORD FORMAT: LOW SIDE
SIGNAL
BIT
NAME
PCB
PURPOSE
1
GCBDPE-
Cc
C board detected error
2
FBMDEVPE+
c
BMD input even word
3
FBMDODPE+
Cc
BMD input odd word
4
LMMOD+
c
Missing memory module at CACHE-MISS
5
LBMAPE+
Cc
Memory reports BMA error at CACHE-MISS
6
LFERNEXT-
Cc
RMA was incremented at time of error
(CACHE-MISS)
7
LFLRMA15+
Cc
Indicator of BMA15 at time of error
( CACHE-MISS)
8
LMISFL16+
C
Indicator of BMA16 at time of error
(CACHE-MISS)
9
LBMDECCU+
Cc
Memory reports ECC uncorrectable on
CACHE-MISS
10
LBMDECCC+
Cc
Memory reports ECC correctable on
CACHE-MISS
ll
LRCIAPE+
c
CACHE~INDEX error on CACHE-READ
12
LRCDODPE+
Cc
CACHE-DATA odd word error on CACHE-READ
13
LRCDEVPE+
Cc
CACHE-DATA evev word error on CACHE-READ
14
LFSERVDBD
Cc
Purpose if CACHE CYCLE:
l=Execute, 0=Prefetch
15
Not Used
16
Not Used
6.2.4.2 General System Halt Handling
Locations
at
which
PRIMOS halts are defined in the PRIMOS load maps
(RINGO.MAP and RING3.MAP).
These maps are in the UFD in which
PRIMOS
was
built and from which it is normally RESUMED (usually UFD PRIRUN).
To determine the actual halt location, check the
address
within
the
correct segment.
For
effective
use of system halt handling, familiarize yourself with
VCP operations
as
described
in
Chapter
3.
Refer
to
the
troubleshooting flowcharts for additional troubleshooting tips.
NOTE
DO NOT Master Clear or SYSCLR at this point.
The following steps outline system halt handling:
l.
2.
Note the halt location that appears on the system
console.
This
will contain the segment number and address of the halt.
Go to the load maps for PRIMOS (RINGO.MAP and RING3.MAP).
Look up
the halt location in the map.
The
address
or
previous
address
should
indicate
a
recognized
halt
location.
—
Use
the
troubleshooting flow charts to aid in isolating the cause
of
the
halt.
070-C
6-
12
Advertisement
Table of Contents
