Service manual

Troubleshooting 3-65
Example 3– 42 Acer_io_diag
P01>>> set d_trace on |
P01>>> set d_group mfg |
P01>>> set d_harderr continue |
P01>>> acer_io_diag -h 12
acer_io_diag 00000075 Std-I/O H12 1 1 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 3 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 4 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 5 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 7 0 0 12:00:*
acer_io_diag 00000075 Std-I/O H12 1 8 0 0 12:00:*
acer_io_diag 00000075 Std-I/O H12 1 9 0 0 12:00:01
Cannot run this test on the Console Standard I/O
acer_io_diag 00000075 Std-I/O H12 1 10 0 0 12:00:01
Cannot run this test on the Console Standard I/O
acer_io_diag 00000075 Std-I/O H12 1 11 0 0 12:00:01
Cannot run this test on the Console Standard I/O
acer_io_diag 00000075 Std-I/O H12 1 12 0 0 12:00:01
Cannot run this test on the Console Standard I/O
acer_io_diag 00000075 Std-I/O H12 1 13 0 0 12:00:01
Cannot run this test on the Console Standard I/O
acer_io_diag 00000075 Std-I/O H12 1 15 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 16 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 17 0 0 12:00:01
acer_io_diag 00000075 Std-I/O H12 1 19 0 0 12:00:01
Cannot run this test on the Console Standard I/O
The set d_trace command causes the diagnostic output to display on the
console. The set d_group mfg command permits the test to be run. The
set d_harderr continue command causes the diagnostic to continue
running after a hard error.
The acer_io_diag – h 12 command causes a suite of diagnostic tests to run
on the standard I/O module.
In this case the standard I/O module being tested is
on PCI hose 12.
The generic syntax is:
acer_io_diag -h<dev. ID> -t<test#> –p<pass count>
Tests 1 through 20 are run on the standard I/O module except those that
would affect the SRM console operation.
Tests are not run that would affect SRM console operation.