IBM 8685 Hardware Maintenance Manual - Page 145

Diagnostic error codes, Remove USB devices from USB1 and USB2.

Page 145 highlights

Diagnostic error codes Note: In the following error codes, if xxx is 000, 195, or 197, do not replace a FRU. The description for these error codes are: 000 The test passed. 195 The Esc key was pressed to stop the test. 197 Warning; a hardware failure might not have occurred. For all error codes, replace the FRU or take the action indicated. Note: See "System" on page 162 to determine which components should be replaced by a field service technician. Error code/symptom FRU/action 001-xxx-000 (Failed core tests) v System board 001-xxx-001 (Failed core tests) v System board 001-250-000 (Failed system board ECC) v System board 001-250-001 (Failed system board ECC) v System board 005-xxx-000 (Failed video test) v System board 011-xxx-000 (Failed COM1 serial port test) v System board 011-xxx-001 (Failed COM2 serial port test) v System board 014-xxx-000 (Failed parallel port test) v System board 015-xxx-001 (USB interface not found, board damaged) 1. System board 015-xxx-015 (Failed USB external loopback 1. Make sure the parallel port is not disabled. test) 2. Run the USB external loopback test again. 3. System board. 015-xxx-198 (USB device connected during 1. Remove USB devices from USB1 and USB2. USB test) 2. Run the USB external loopback test again. 3. System board. 020-xxx-000 (Failed PCI interface test) v System board 020-xxx-001 (Failed hot-swap slot 1 PCI latch test) 1. PCI hot-swap latch assembly 2. System board 020-xxx-002 (Failed Hot-swap slot 2 PCI latch test) 1. PCI hot-swap latch assembly 2. System board 020-xxx-003 (Failed hot-swap slot 3 PCI latch test) 1. PCI hot-swap latch assembly 2. System board 020-xxx-004 (Failed hot-swap slot 4 PCI latch test) 1. PCI hot-swap latch assembly 2. System board 030-xxx-000 (Failed internal SCSI interface v System board test) 035-xxx-099 1. No adapters were found. 2. If adapter is installed re-check connection. Chapter 6. Symptom-to-FRU index 135

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220

Diagnostic error codes
Note:
In the following error codes, if
xxx
is
000
,
195
, or
197
,
do not
replace a FRU.
The description for these error codes are:
000
The test passed.
195
The Esc key was pressed to stop the test.
197
Warning; a hardware failure might not have occurred.
For all error codes, replace the FRU or take the action indicated.
Note:
See “System” on page 162 to determine which components should be replaced by a field service technician.
Error code/symptom
FRU/action
001-
xxx
-000
(Failed core tests)
v
System board
001-xxx-001
(Failed core tests)
v
System board
001-250-000
(Failed system board ECC)
v
System board
001-250-001
(Failed system board ECC)
v
System board
005-xxx-000
(Failed video test)
v
System board
011-xxx-000
(Failed COM1 serial port test)
v
System board
011-xxx-001
(Failed COM2 serial port test)
v
System board
014-xxx-000
(Failed parallel port test)
v
System board
015-xxx-001
(USB interface not found,
board damaged)
1.
System board
015-xxx-015
(Failed USB external loopback
test)
1.
Make sure the parallel port is not disabled.
2.
Run the USB external loopback test again.
3.
System board.
015-xxx-198
(USB device connected during
USB test)
1.
Remove USB devices from USB1 and USB2.
2.
Run the USB external loopback test again.
3.
System board.
020-xxx-000
(Failed PCI interface test)
v
System board
020-xxx-001
(Failed hot-swap slot 1 PCI
latch test)
1.
PCI hot-swap latch assembly
2.
System board
020-xxx-002
(Failed Hot-swap slot 2 PCI
latch test)
1.
PCI hot-swap latch assembly
2.
System board
020-xxx-003
(Failed hot-swap slot 3 PCI
latch test)
1.
PCI hot-swap latch assembly
2.
System board
020-xxx-004
(Failed hot-swap slot 4 PCI
latch test)
1.
PCI hot-swap latch assembly
2.
System board
030-xxx-000
(Failed internal SCSI interface
test)
v
System board
035-xxx-099
1.
No adapters were found.
2.
If adapter is installed re-check connection.
Chapter 6. Symptom-to-FRU index
135