HP Visualize b1000 hp Visualize b1000, c3000, c3600 workstations service handb - Page 83

Memory Failures

Page 83 highlights

Troubleshooting Selftest Failures Table 3-2. Chassis Codes for B Class and C Class Workstations Ostat INI INI TST WRN INI INI WRN FLT WRN Code FRU CC3n SYS BD CC4n SYS BD D000 SYS BD D004 SYS BD D005 SYS BD D006 SYS BD D007 SYS BD D01n D02n SYS/IO SYS/IO Message Description CPUn cache rend Slave CPU n entering cached rendezvous, waiting for the monarch CPU to configure the system bus. CPUn mem rendez Slave CPU n entering memory rendezvous, waiting for the monarch CPU to select a boot device. micro controller Firmware is initializing communications with the system controller. micro not resp Firmware detected a communications error with the system controller. set dom1 fan spd Firmware is initializing communications with the system controller. set dom2 fan spd Firmware is initializing communications with the system controller. bad microctl cmd Firmware detected a communications error with the system controller. fan n: failure! Firmware detected system fan n stopped. fan n: too slow! Firmware detected system fan n is running too slowly. Memory Failures The B Class and C Class system requires Memory Page Deallocation to be implemented. This feature allows the workstation to provide information to the operating system about memory failures. HP-UX 10.x uses 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 "Boot Console Menus" on page 159). For allowable memory configurations see Chapter 2 of this manual. Chapter 3 83

  • 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
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239

Chapter 3
83
Troubleshooting
Selftest Failures
Memory Failures
The B Class and C Class system requires Memory Page Deallocation to be implemented.
This feature allows the workstation to provide information to the operating system about
memory failures.
HP-UX 10.x uses 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 “Boot Console Menus” on page 159).
For allowable memory configurations see Chapter 2 of this manual.
INI
CC3
n
SYS BD
CPU
n
cache rend
Slave CPU
n
entering cached rendezvous,
waiting for the monarch CPU to configure
the system bus.
INI
CC4
n
SYS BD
CPU
n
mem rendez
Slave CPU
n
entering memory
rendezvous, waiting for the monarch CPU
to select a boot device.
TST
D000
SYS BD
micro controller
Firmware is initializing communications
with the system controller.
WRN
D004
SYS BD
micro not resp
Firmware detected a communications
error with the system controller.
INI
D005
SYS BD
set dom1 fan spd
Firmware is initializing communications
with the system controller.
INI
D006
SYS BD
set dom2 fan spd
Firmware is initializing communications
with the system controller.
WRN
D007
SYS BD
bad microctl cmd
Firmware detected a communications
error with the system controller.
FLT
D01
n
SYS/IO
fan
n
: failure!
Firmware detected system fan
n
stopped.
WRN
D02
n
SYS/IO
fan
n
: too slow!
Firmware detected system fan
n
is
running too slowly.
Table 3-2. Chassis Codes for B Class and C Class Workstations
Ostat
Code
FRU
Message
Description