HP Visualize J5000 hp Visualize J5000, J7000 workstations service handbook (a4 - Page 59

Selftest Failures

Page 59 highlights

Selftest Failures Chassis codes are the key to debugging selftest errors. If a failure is found during selftest, chassis codes are displayed in the LCD. The procedure for using these codes to debug a failure is as follows: 6. Using Table 4-1, find the chassis code listed on the LCD. Codes 7000 through 7Dxx are memory errors. Codes CBxx through 500F in Table 4-1 are HPMC errors. 7. A 7Fxx code means a memory SIMM error. Figure 4-3 is a layout of the memory SIMMs on the CPU board that goes down to the SIMM pair. To continue beyond the pair, run Offline Diagnostics. To get additional information about failures from the boot console interface, use the Service menu pim, pdt, and ChassisCode commands. In the following table, the FRU column shows messages printed on the LCD that refer to system FRUs. Only FLT codes have FRUs associated with them. Some WARN codes are also device-specific, especially to IODC calls; for example, 8XXY codes. Test and INIT codes don't correspond to any FRU. All codes are listed in numeric order. For the FRUs labled 'Selftest CPU 0', there is also a corresponding CPU x code, where x indicates the CPU number. Memory Failures The J Class system requires special Memory Page Deallocation (PDC) to be implemented. This PDC feature allows the workstation to provide information to the operating system about memory failures. HP-UX 10.x uses PDC information to map out failing memory areas and continue normal operation. You can use the command memrpt with the detail switch to obtain information about the Memory Page Deallocation Table (PDT) as well as single bit errors logged by the system. # /usr/sbin/sysdiag Enter DUI >logtool Enter LOGTOOL> memrpt detail Enter The PDT can also be checked using the pdt command in the Service menu of the boot console handler (Refer to Chapter 9). If a failing SIMM is replaced, use the command pdt clear in the Service menu to clear out the PDT. HP-UX 9.0x will halt upon detecting the presence of bad memory at boot up and display the following message: ISL booting hpux Secondary Loader 9000/700 Revision 3.08 Booting /hp-ux 2103692 + 319488 + 309344 start 0x25030 panic: Memory self-test failed Troubleshooting 4-9

  • 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

Troubleshooting
4–9
Selftest Failures
Chassis codes are the key to debugging selftest errors. If a failure is found during
selftest, chassis codes are displayed in the LCD. The procedure for using these codes
to debug a failure is as follows:
6.
Using Table 4–1, find the chassis code listed on the LCD.
Codes 7000 through 7Dxx are memory errors.
Codes CBxx through 500F in Table 4–1 are HPMC errors.
7.
A 7Fxx code means a memory SIMM error. Figure 4–3
is a layout of the
memory SIMMs on the CPU board that goes down to the SIMM pair. To contin-
ue beyond the pair, run Offline Diagnostics.
To get additional information about failures from the boot console interface, use the
Service menu
pim
,
pdt
, and
ChassisCode
commands.
In the following table, the FRU column shows messages printed on the LCD that refer
to system FRUs. Only FLT codes have FRUs associated with them. Some WARN codes
are also device-specific, especially to IODC calls; for example, 8XXY codes. Test and
INIT codes don’t correspond to any FRU. All codes are listed in numeric order.
For the FRUs labled ’Selftest
CPU 0’, there is also a corresponding CPU x code, where x
indicates the CPU number.
Memory Failures
The J Class system requires special Memory Page Deallocation (PDC) to be
implemented. This PDC feature allows the workstation to provide information to the
operating system about memory failures.
HP-UX 10.x uses PDC information to map out failing memory areas and continue
normal operation. You can use the command
memrpt
with the detail switch to obtain
information about the Memory Page Deallocation Table (PDT) as well as single bit
errors logged by the system.
# /usr/sbin/sysdiag
Enter
DUI >logtool
Enter
LOGTOOL> memrpt detail
Enter
The PDT can also be checked using the
pdt
command in the Service menu of the
boot console handler (Refer to Chapter 9). If a failing SIMM is replaced, use the
command
pdt clear
in the Service menu to clear out the PDT.
HP-UX 9.0x will halt upon detecting the presence of bad memory at boot up and
display the following message:
ISL booting hpux
Secondary Loader 9000/700
Revision 3.08
Booting /hp-ux
2103692 + 319488 + 309344 start 0x25030
panic: Memory self-test failed