Sun Microsystems Sun Blade 100, Руководство по обслуживанию

Страница: 83 / 222

Chapter 4 Troubleshooting Procedures 4-15
4.7.2.1 PCI/PCIO Diagnostic
To start the PCI/PCIO diagnostic, type
0
at the
OBdiag
Menu prompt. The PCI/
PCIO diagnostic performs the following tests in sequence:
1.
vendor_ID_test
verifies the PCIO ASIC vendor ID is 108e.
2.
device_ID_test
verifies the PCIO ASIC device ID is 1000.
3.
mixmode_read
verifies the PCI configuration space is accessible as
half-word bytes by reading the EBus2 vendor ID address.
4.
e2_class_test
verifies the address class code. Address class codes include
bridge device (0 x B, 0 x 6), other bridge device (0 x A and 0 x 80), and
programmable interface (0 x 9 and 0 x 0).
5.
status_reg_walk1
performs a walk-one test on the status register with mask
0 x 280 (PCIO ASIC is accepting fast back-to-back transactions, DEVSEL timing is
0 x 1).
6.
line_size_walk1
performs tests 1 through 5.
7.
latency_walk1
performs a walk-one test on the latency timer.
8.
line_walk1
performs a walk-one test on the interrupt line.
9.
pin_test
verifies the interrupt pin is logic-level high (1) after reset.
The following code example shows the PCI/PCIO diagnostic output message.
CODE EXAMPLE 4-8
PCI/PCIO Diagnostic Output Message
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===> 0
TEST='all_pci/PCIO_test'
SUBTEST='vendor_id_test'
SUBTEST='device_id_test'
SUBTEST='mixmode_read'
SUBTEST='e2_class_test'
SUBTEST='status_reg_walk1'
SUBTEST='line_size_walk1'
SUBTEST='latency_walk1'
SUBTEST='line_walk1'
SUBTEST='pin_test'
Enter (0-12 tests, 13 -Quit, 14 -Menu) ===>