DataMuseum.dk

top - download

    Length: 2236 (0x8bc)
    Types: ERRMESS, TextFile
    Names: »P2EVNT.ERRMESS«

└─⟦24d56d853⟧ Bits:30000744 8mm tape, Rational 1000, DFS, D_12_6_5 SEQ293
    └─ ⟦this⟧ »P2EVNT.ERRMESS« 
└─⟦9031b0687⟧ Bits:30000407 8mm tape, Rational 1000, DFS, D_12_7_3
    └─ ⟦this⟧ »P2EVNT.ERRMESS« 

TextFile

0	No errors were detected by P2EVNT.
1	The %1% board generated a %2% event even though
	no events should have been generated.
2	The %1% board did not detect a %2% event when it
	should have. The SEQ board correctly detected the event.
3	The SEQ board did not detect an event when the %3% board 
	generated a %2% event. The %3% board correctly detected
	the event. The problem is either with the logic on the SEQ
	board or else the SEQ board has a bad backplane connection.
4	The SEQ and %1% boards both incorrectly detected an event,
	however the errors they detected are inconsistent with one
	another. This is an unexplainable problem and no conclusion can
	be drawn to isolate a particular FRU.
5	The signal for the %2% event is stuck low on the backplane.
6	Both the SEQ board and the %1% board received a %2%
	event from the %3% board even though no events should have
	been generated.
7	Neither the SEQ board nor the %1% board received a %2%
	event even though the %3% board should have generated one.
	Either there is a problem with the %3% board or else the 
	%3% board is not making connection to the MICROS_EN signal on
	the backplane.
8	Both the SEQ board and the %1% board detected multiple events
	when the %3% board was generating a %2% event. This could
	be caused by a short on either the SEQ, the %1%, or the
	backplane.
9	The %1% board generated some other (unknown) event when it
	should have generated a %2% event;
10	The %1% board unexpectedly generated a %2% event while
	the %3% board was under test.
11	The SEQ board unexpectedly detected a %2% event from
	the %1% board while the %3% board was being tested. The
	%1% board (correctly) did not detect the event.
12	An unexplainable problem was encountered when trying to isolate
	a problem with the MICROS_EN signal on the  backplane. No 
	conclusion can be drawn to isolate a FRU.
13	None of the boards in the processor correctly receive the MICROS_EN
	signal from the SEQ board (pin 128 on the backplane). By far the
	most likely problem is either that something has gone bad on the 
	SEQ or else the SEQ has a bad connection to the	backplane. It is 
	possible that one of the other boards called out as a FRU is
	shorting the signal but this is very unlikely.