pe_macro(1)
You can still glean some useful information because the front-end program
indicates which message record it was waiting for when it timed out. This
record number is the distance the test was attempting to shift data when the
error occurred. This record number is also the row/column address of the PE
which was attempting the shift.
•
xnetNE
: XNet Shift Northeast Test — This test selects a single PE at a time
and shifts data northeast a distance which is a function of the PEs address.
For each of the 1024 PEs (in a single board system), the test checks the loop
count.
This test is attempting to provoke a parity error. When one occurs, the front-
end program times out waiting for more data from the test and prints the
status of the HSR register which indicates why the test halted.
You can still glean some useful information because the front-end program
indicates which message record it was waiting for when it timed out. This
record number is the distance the test was attempting to shift data when the
error occurred. This record number is also the row/column address of the PE
which was attempting the shift.
•
xnetNW
: XNet Shift Northwest Test — This test selects a single PE at a time
and shifts data northwest a distance which is a function of the PEs address.
For each of the 1024 PEs (in a single board system), the test checks the loop
count.
This test is attempting to provoke a parity error. When one occurs, the front-
end program times out waiting for more data from the test and prints the
status of the HSR register which indicates why the test halted.
You can still glean some useful information because the front-end program
indicates which message record it was waiting for when it timed out. This
record number is the distance the test was attempting to shift data when the
error occurred. This record number is also the row/column address of the PE
which was attempting the shift.
•
xnetS
: XNet Shift South Test — This test selects a single PE at a time and
shifts data south a distance which is a function of the PEs address. For each
of the 1024 PEs (in a single board system), the test checks the loop count.
This test is attempting to provoke a parity error. When one occurs, the front-
end program times out waiting for more data from the test and prints the
status of the HSR register which indicates why the test halted.
You can still glean some useful information because the front-end program
indicates which message record it was waiting for when it timed out. This
record number is the distance the test was attempting to shift data when the
error occurred. This record number is also the row/column address of the PE
which was attempting the shift.
•
xnetSE
: XNet Shift Southeast Test — This test selects a single PE at a time
and shifts data SouthEast a distance which is a function of the PEs address.
For each of the 1024 PEs (in a single board system), the test checks the loop
count.
This test is attempting to provoke a parity error. When one occurs, the front-
end program times out waiting for more data from the test and prints the
status of the HSR register which indicates why the test halted.
Data Parallel Unit Reference Pages B–57
Содержание DECmpp 12000/Sx 100
Страница 36: ......
Страница 82: ......
Страница 84: ......
Страница 91: ...mpstat 1 Files usr adm dpuacct See Also dpumanager 8 mpq 1 Data Parallel Unit Reference Pages B 7...
Страница 145: ...pe_rtbp 1 Files Executable binary MP_PATH field bin pe_rtbp Data Parallel Unit Reference Pages B 61...