Troubleshooting
Problem
This document includes a list of DPO fixes for Power Hypervisor (PHYP), Partition Firmware (PFW), IBM i OS, AIX OS, and HMC.
Resolving The Problem
This document includes a list of DPO fixes for Power Hypervisor (PHYP), Partition Firmware (PFW), IBM i OS, AIX OS, and HMC.
Firmware
IBM i OS
AIX
HMC
Note: For 9119-FHB, 9117-MMD, and 9179-MHD systems, feature code EB33 is needed to enable DPO at Ax760. For systems at Ax770 and beyond, no Feature Code order is needed.
If doing DPO, it is always recommended to have the latest firmware and Hiper PTFs
Firmware
| o | FW760 |
| - SW212592 - Partition Placement of dedicated processors incorrect after DPO - fix in 760.31 (Ax760_069) | |
| - SW189640 - Affinity change for LMBs failed with the last given LMB phandle – fix in 760.31 (Ax760_069) | |
| - SW192884 - DPO Scoring issue – fix in 760.31 (Ax760_069) | |
| - SW199566 - DPO Scoring improve for memory DLPAR – fix in 760.31 (Ax760_069) | |
| - SW201265 - Affinity Score too low for large dedicated processor partition and dedicated processor placement not being reported to partitions correctly – fix in 760.31 (Ax760_069) | |
| o | FW770 |
| - SW212592 - Partition Placement of dedicated processors incorrect after DPO - fix in 770.21 | |
| - A defect that causes the incorrect display of SRAD assignments of CPU after DPO and before restart is known to exist on a pre-GA level of 770, including at least FW770.00 (AM770_029) | |
| - SW189640 - Affinity change for LMBs failed with the last given LMB phandle – fix in 770.21 | |
| - SW192884 - DPO Scoring issue – fix in 770.21 | |
| - SW199566 - DPO Scoring improve for memory DLPAR – fix in 770.21 | |
| - SW201265 - Affinity Score too low for large dedicated processor partition & dedicated processor placement not being reported to partitions correctly – fix in 770.21 |
IBM i OS
| o | 7.3 |
| - MA47328 - MF65437 - srcB6000103 or hand during normal operations | |
| - MA47257 - MF65295 - LIC Post DPO processing by the partition cannot be monitored | |
| o | 7.2 |
| - MA47328 - MF65442 - srcB6000103 or hand during normal operations | |
| - MA44869 - MF60602 - Dynamic Platform Optimizer - srcB6000103 during IBM i memory fixup routine and an IASP is in use. | |
| - MA44792 - 7.2 TR3 (MF99103) - Dynamic Platform Optimizer - IBM i memory page fixup cannot be stopped or metered. | |
| - MA44775 - MF60459 - Journal forcing not occurring as expected | |
| - MA44598 - MF60120 - Journal forcing not occurring as expected | |
| - MA44402 - MF59773 - Memory pool lock contention during Dynamic Memory Optimizer page fixup step. | |
| - MA44234 - MF59445 - DLPAR remove memory removed access to an LMB of memory, but did not clear a field in the node object that is used to identify the memory location of the next 64K page to be built. DPO attempted to use inaccessible memory, which caused the tasks to go into an infinite loop. | |
| - MA43865 - MF58849 - During page map update, a small number of 64K pages may be broken up, and then not be remapped properly. | |
| - MA43514 - MF58095 - Partition termination - attempt to get the pool configuration lock when it was already held, or concurrent maintenance attempted to get the pool configuration lock when it was already held. | |
| o | 7.1 |
| - MA44869 - MF60599 - Dynamic Platform Optimizer - srcB6000103 during IBM i memory fixup routine and an IASP is in use. | |
| - MA44792 - MF60571 - Dynamic Platform Optimizer - IBM i memory page fixup cannot be stopped or metered. | |
| - MA44775 - MF60460 - Journal forcing not occurring as expected | |
| - MA44598 - MF60121 - Journal forcing not occurring as expected | |
| - MA44402 - MF59778 - Memory pool lock contention during Dynamic Memory Optimizer page fixup step. | |
| - MA44234 - MF59439 - DLPAR remove memory removed access to an LMB of memory, but did not clear a field in the node object that is used to identify the memory location of the next 64K page to be built. DPO attempted to use inaccessible memory, which caused the tasks to go into an infinite loop. | |
| - MA43865 - MF58758 - During page map update, a small number of 64K pages may be broken up, and then not be remapped properly. | |
| - MA43107 - MF57511 - If all memory has been moved from one node to another, the subsequent IPL can hang at C6003962 if tasks early in the IPL are running on the node from which the memory was removed. | |
| - MA42999 - MF57459 - After Dynamic Platform Optimizer (DPO) moved all the memory from one node and onto another, jobs requiring a 64K page got stuck in a loop trying to get the 4K pages required to make the 64K page. | |
| - MA42985 - SMLMBAFFINIFYFIX task locks out memory pool changes until the page updates are completed. | |
| - MA42956 - MF57328 - When Dynamic Platform Optimizer (DPO) completes, IBM i memory adjustments are held off until IBM i Main Storage Management updates all of the memory page descriptors. | |
| - MA42795 - MF56959 (requires TR6 & MF56675 & MF56678) - MAIN STORAGE POOL COUNTS GET OUT OF SYNC - LOOP ATTEMPTING TO ADJUST TO CORRECT VALUE. | |
| - MA42656 - MF56948 -> Partition Termination - SRCB6000103 during a DPO operation. | |
| - MA42625 - MF56675 (requires TR6) -> Performance degrades severely during a Dynamic Platform Optimizer operation, and does not recover when it finishes. | |
| - MA42617 - MF56678 (requires TR6) -> Performance degrades severely during a Dynamic Platform Optimizer operation, and does not recover when it finishes. | |
| - MA42546 - MF56679 -> LIC REDUCE TIME NECESSARY TO PROCESS MEMORY AFTER A PARTITION MIGRATION | |
| o | 6.1.1 |
| - MA44234 - MF59461 - DLPAR remove memory removed access to an LMB of memory, but did not clear a field in the node object that is used to identify the memory location of the next 64K page to be built. DPO attempted to use inaccessible memory, which caused the tasks to go into an infinite loop. | |
| - MA43107 - MF57505 - If all memory has been moved from one node to another, the subsequent IPL can hang at C6003962 if tasks early in the IPL are running on the node from which the memory was removed. | |
| - MA42999 - MF57314 - After Dynamic Platform Optimizer (DPO) moved all the memory from one node and onto another, jobs requiring a 64K page got stuck in a loop trying to get the 4K pages required to make the 64K page. | |
| - MA42959 - MF57260 - Memory management post-DPO can leave insufficient memory in a memory node, while demand for that node continues. This leads to a Main Storage Management looping condition. | |
| - MA42956 - MF57344 - When Dynamic Platform Optimizer (DPO) completes, IBM i memory adjustments are held off until IBM i Main Storage Management updates all of the memory page descriptors. | |
| o | 6.1.0 |
| - MA43107 - MF57514 - If all memory has been moved from one node to another, the subsequent IPL can hang at C6003962 if tasks early in the IPL are running on the node from which the memory was removed. | |
| - MA42999 - MF57438 - After Dynamic Platform Optimizer (DPO) moved all the memory from one node and onto another, jobs requiring a 64K page got stuck in a loop trying to get the 4K pages required to make the 64K page. | |
| - MA42956 - MF57343 - When Dynamic Platform Optimizer (DPO) completes, IBM i memory adjustments are held off until IBM i Main Storage Management updates all of the memory page descriptors. |
AIX
| o | 61-08 |
| - IV37371 - DPO NOT OPTIMIZING MEMORY DURING RUNTIME | |
| - IV39929 – CRASH IF A VMPOOL RUNS OUT OF FREE PAGES OF A GIVEN SIZE | |
| - IV41591 – SYSTEM CRASH FOLLOWING DPO EVENT | |
| o | 61-09 |
| - IV37544 - DPO NOT OPTIMIZING MEMORY DURING RUNTIME | |
| - IV39110 – CRASH IF A VMPOOL RUNS OUT OF FREE PAGES OF A GIVEN SIZE | |
| - IV41722 - SYSTEM CRASH FOLLOWING DPO EVENT | |
| o | 71-02 |
| - IV37309 - DPO NOT OPTIMIZING MEMORY DURING RUNTIME | |
| - IV40012 - CRASH IF A VMPOOL RUNS OUT OF FREE PAGES OF A GIVEN SIZE | |
| - IV41474 - SYSTEM CRASH FOLLOWING DPO EVENT | |
| o | 71-03 |
| IV37482 - DPO NOT OPTIMIZING MEMORY DURING RUNTIME | |
| IV39566 – CRASH IF A VMPOOL RUNS OUT OF FREE PAGES OF A GIVEN SIZE | |
| IV42416 - SYSTEM CRASH FOLLOWING DPO EVENT |
HMC
| o | 7.7.6 |
| - SW170615 - 7.7.6.1 - DPO incorrectly shows enabled |
Note: For 9119-FHB, 9117-MMD, and 9179-MHD systems, feature code EB33 is needed to enable DPO at Ax760. For systems at Ax770 and beyond, no Feature Code order is needed.
If doing DPO, it is always recommended to have the latest firmware and Hiper PTFs
[{"Product":{"code":"SSB6AA","label":"Power System Hardware Management Console Physical Appliance"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"POWER7","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}}]
Historical Number
669691974
Was this topic helpful?
Document Information
Modified date:
22 September 2021
UID
nas8N1010394