blob: fb9abebbc85963dea0aa4b47ea47deacf190a3b5 (
plain)
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
|
<!-- IBM_PROLOG_BEGIN_TAG -->
<!-- This is an automatically generated prolog. -->
<!-- -->
<!-- $Source: src/import/chips/p9/procedures/xml/error_info/p9_avsbus_lib_errors.xml $ -->
<!-- -->
<!-- OpenPOWER HostBoot Project -->
<!-- -->
<!-- Contributors Listed Below - COPYRIGHT 2015,2017 -->
<!-- [+] International Business Machines Corp. -->
<!-- -->
<!-- -->
<!-- Licensed under the Apache License, Version 2.0 (the "License"); -->
<!-- you may not use this file except in compliance with the License. -->
<!-- You may obtain a copy of the License at -->
<!-- -->
<!-- http://www.apache.org/licenses/LICENSE-2.0 -->
<!-- -->
<!-- Unless required by applicable law or agreed to in writing, software -->
<!-- distributed under the License is distributed on an "AS IS" BASIS, -->
<!-- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or -->
<!-- implied. See the License for the specific language governing -->
<!-- permissions and limitations under the License. -->
<!-- -->
<!-- IBM_PROLOG_END_TAG -->
<!-- *HWP HWP Owner: Greg Still <stillgs @us.ibm.com> -->
<!-- *HWP FW Owner : Prasad BG Ranganath <prasadbgr@in.ibm.com> -->
<!-- *HWP Team: PM -->
<!-- *HWP Level: 3 -->
<!-- *HWP Consumed by: FSP:HS -->
<!-- Error definitions for p9_avsbus_lib procedure -->
<!-- NOTE: The AVSBus goes through the PM Subsystem Reset flow that is -->
<!-- performed up to 3 times in 24 hour period by TMGT in the event of any -->
<!-- failure (including the AVSBus). If the any of these failures persist, -->
<!-- the chip is called out by TMGT. Thus, no callouts are made here as -->
<!-- they would all result in a chip hardware callout as described. -->
<hwpErrors>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PROCPM_AVSBUS_POLL_TIMEOUT</rc>
<description>
A timeout occured while polling OCB status register O2SST for o2s_ongoing=0
</description>
<ffdc>CHIP_TARGET</ffdc>
<ffdc>AVSBUS_NUM</ffdc>
<ffdc>AVSBUS_BRIDGE_NUM</ffdc>
<ffdc>AVSBUS_MAX_POLL_CNT</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PROCPM_AVSBUS_VOLTAGE_TIMEOUT</rc>
<description>
A timeout occured reading/writing voltage from an AVSBus
interface
</description>
<ffdc>CHIP_TARGET</ffdc>
<ffdc>AVSBUS_NUM</ffdc>
<ffdc>AVSBUS_BRIDGE_NUM</ffdc>
<ffdc>AVSBUS_CMD_TYPE</ffdc>
<ffdc>AVSBUS_CMD_GROUP</ffdc>
<ffdc>AVSBUS_CMD_DATATYPE</ffdc>
<ffdc>AVSBUS_RAILSELECT</ffdc>
<ffdc>AVSBUS_CMD_DATA</ffdc>
<ffdc>CRC</ffdc>
<ffdc>AVSBUS_OP_TYPE</ffdc>
</hwpError>
<!-- ********************************************************************-->
<hwpError>
<rc>RC_PROCPM_AVSBUS_IDLEFRAME_TIMEOUT</rc>
<description>
A timeout occured writing an idle from to an AVSBus interface
</description>
<ffdc>CHIP_TARGET</ffdc>
<ffdc>AVSBUS_NUM</ffdc>
<ffdc>AVSBUS_BRIDGE_NUM</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_ZERO_RESP_ERROR</rc>
<description>
AVS command failed. All 0 response data received possibly due to AVSBus IO RI/DIs disabled.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_NO_RESP_ERROR</rc>
<description>
AVS command failed. No response from VRM device, Check AVSBus interface connectivity to VRM in system.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_MASTER_BAD_CRC_ERROR</rc>
<description>
AVS command failed. Bad CRC detected by P9 on AVSBus Slave Segement.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_SLAVE_BAD_CRC_ERROR</rc>
<description>
AVS command failed failed. Bad CRC indicated by Slave VRM on AVSBus Master Segement.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_UNAVAILABLE_RESOURCE_ERROR</rc>
<description>
AVS command failed. Valid data sent but no action is taken due to unavailable resource.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
<hwpError>
<rc>RC_PM_AVSBUS_INVALID_DATA_ERROR</rc>
<description>
AVS command failed. Unknown resource, invalid data, incorrect data or incorrect action.
</description>
<ffdc>TARGET</ffdc>
<ffdc>BUS</ffdc>
<ffdc>BRIDGE</ffdc>
</hwpError>
<!-- ******************************************************************** -->
</hwpErrors>
|
