blob: 96f03946ce068f27316d17bae23aefcc6344af48 (
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
|
<!-- IBM_PROLOG_BEGIN_TAG -->
<!-- This is an automatically generated prolog. -->
<!-- -->
<!-- $Source: src/usr/hwpf/hwp/dimm_errors.xml $ -->
<!-- -->
<!-- IBM CONFIDENTIAL -->
<!-- -->
<!-- COPYRIGHT International Business Machines Corp. 2012,2014 -->
<!-- -->
<!-- p1 -->
<!-- -->
<!-- Object Code Only (OCO) source materials -->
<!-- Licensed Internal Code Source Materials -->
<!-- IBM HostBoot Licensed Internal Code -->
<!-- -->
<!-- The source code for this program is not published or otherwise -->
<!-- divested of its trade secrets, irrespective of what has been -->
<!-- deposited with the U.S. Copyright Office. -->
<!-- -->
<!-- Origin: 30 -->
<!-- -->
<!-- IBM_PROLOG_END_TAG -->
<!-- $Id: dimm_errors.xml,v 1.7 2014/02/27 21:40:32 mjjones Exp $ -->
<hwpErrors>
<!-- *********************************************************************** -->
<hwpError>
<rc>RC_BAD_DQ_DIMM_BAD_PARAM</rc>
<description>
A HWP called a utility function to access the bad DQ data but specified
an invalid PORT/DIMM/RANK
</description>
<ffdc>FFDC_PORT</ffdc>
<ffdc>FFDC_DIMM</ffdc>
<ffdc>FFDC_RANK</ffdc>
</hwpError>
<!-- *********************************************************************** -->
<hwpError>
<rc>RC_BAD_DQ_DIMM_NOT_FOUND</rc>
<description>
A HWP called a utility function to accessing the bad DQ data. The
utility function could not find a functional DIMM associated with the
specified MBA/PORT/DIMM
</description>
<ffdc>FFDC_MBA_TARGET</ffdc>
<ffdc>FFDC_PORT</ffdc>
<ffdc>FFDC_DIMM</ffdc>
</hwpError>
<!-- ********************************************************************* -->
<hwpError>
<rc>RC_BAD_DQ_MFG_MODE_BITS_FOUND_DURING_GET</rc>
<description>
A HWP noted additional bad bits in the bad dq bitmap of the
specified DIMM while in the manufacturing DISABLE_DRAM_REPAIRS
mode during a read operation.
CLEAN_BAD_DQ_BITMAP represents a bad dq bitmap with the appropriate
spare and ECC DQs (if any) set to 1 and all other DQs set to 0.
CURRENT_BAD_DQ_BITMAP represents the current bad dq bitmap. Any
discrepancies with CLEAN_BAD_DQ_BITMAP are the result of a manufacturing
mode process.
</description>
<ffdc>DIMM</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK0</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK1</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK2</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK3</ffdc>
<ffdc>CURRENT_BAD_DQ_BITMAP_RANK0</ffdc>
<ffdc>CURRENT_BAD_DQ_BITMAP_RANK1</ffdc>
<ffdc>CURRENT_BAD_DQ_BITMAP_RANK2</ffdc>
<ffdc>CURRENT_BAD_DQ_BITMAP_RANK3</ffdc>
<callout>
<target>DIMM</target>
<priority>HIGH</priority>
</callout>
</hwpError>
<!-- ********************************************************************* -->
<hwpError>
<rc>RC_BAD_DQ_MFG_MODE_BITS_FOUND_DURING_SET</rc>
<description>
A HWP noted an attempt to set additional bad bits in the bad dq bitmap
of the specified DIMM while in the manufacturing DISABLE_DRAM_REPAIRS
mode during a write operation.
CLEAN_BAD_DQ_BITMAP represents a bad dq bitmap with the appropriate
spare and ECC DQs (if any) set to 1 and all other DQs set to 0.
UPDATE_BAD_DQ_BITMAP represents the proposed updates to set. Any
discrepancies with CLEAN_BAD_DQ_BITMAP are the result of a manufacturing
mode process and should not be made.
</description>
<ffdc>DIMM</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK0</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK1</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK2</ffdc>
<ffdc>CLEAN_BAD_DQ_BITMAP_RANK3</ffdc>
<ffdc>UPDATE_BAD_DQ_BITMAP_RANK0</ffdc>
<ffdc>UPDATE_BAD_DQ_BITMAP_RANK1</ffdc>
<ffdc>UPDATE_BAD_DQ_BITMAP_RANK2</ffdc>
<ffdc>UPDATE_BAD_DQ_BITMAP_RANK3</ffdc>
<callout>
<target>DIMM</target>
<priority>HIGH</priority>
</callout>
</hwpError>
<!-- ********************************************************************* -->
</hwpErrors>
|
