01SF240_320_201 Additional features Support was added for certain traveling keyboards. System firmware changes that affect all p5 and i5 systems: HIPER : A problem was fixed that caused a system to crash with SRC B182E500 if a virtual adapter was configured with a virtual slot number that was a multiple of 512. HIPER : A problem was fixed that caused the reboot to fail, after the installation of Linux, if too many command-line parameters were entered. SRC BA210012 sometimes occurred in this scenario, depending on the number of command-line parameters. HIPER : A problem was fixed in open firmware that caused a Linux kernel fault because a list pointer was corrupted during boot. A problem was fixed that could cause the system to boot slowly, or hang, before the operating system got started. If this occurred, the service processor might have rebooted or generated a dump. A problem was fixed that might have caused PCI I/O adapters on a bus to fail after several successive concurrent slot maintenance operations were performed on other PCI I/O adapters on that PCI bus. A problem was fixed that caused a partition to fail to boot with SRC B2001230 (with word 13 = 000000BF and word 14 = 00000002) after the DLPAR removal of a PCI I/O adapter from that partition. The firmware was updated to add the system VPD card and service processor to the Advanced System Management Interface (ASMI) deconfiguration menu under the celogin. On systems running system firmware SF240, a problem was fixed that caused the system to stop booting and log SRC B1xxB0BF. A problem was fixed that prevented the correct FRU callouts from being made when a certain type of L3 cache failure occurred, with SRC B1xxE500 and word 8 being 00100016 or 00100017. A problem was fixed that prevented the correct FRU callouts from being made when memory UEs (uncorrectable errors) occurred, with SRC B1819522 (an informational SRC) followed by B170E500. In this level, SRC B1819522 is followed by SRC B123E500, with the correct FRU callouts for the memory UE. A problem was fixed that might have caused partitions that were sharing processors to hang. A problem was fixed that intermittently prevented a USB keyboard and mouse from being configured during boot. A problem was fixed that prevented an operating system installation from CDs when the CD drive was set up using virtual SCSI (vSCSI). A problem was fixed that prevented enhanced error handling (EEH) from working on systems and partitions running Linux. A problem was fixed that prevented some virtual SCSI (vSCSI) devices from being listed in the SMS boot list menu. A problem was fixed that caused the operating system to crash, or future operating system dumps to fail, when certain adapters (usually FDDI adapters) were hot-plugged. A problem was fixed that caused the operating system to crash after a processor host bus (PHB) was added by a DLPAR operation, followed by a concurrent firmware update. A problem was fixed that caused partition firmware to hang if a USB headset was attached to the system during boot. A problem was fixed that caused partition firmware to crash with SRC BA210000 if an attempt was made to boot from a CD or DVD that is not bootable. A message was added to the "Configure I/O Enclosure" menu on the ASMI (advanced system management interface) asking the user to wait for the operation to be completed, because submitting multiple requests can cause the service processor to crash. System firmware changes that affect HMC-controlled servers and clustered systems: HIPER : A problem was fixed that caused the service processor's /tmp filesystem to became full. This caused failures with various symptoms, the most common one being system termination. This problem also could cause a concurrent firmware installation to fail with SRC B1818A03. HIPER : On models 570, 590 and 595, the firmware was changed so that SRCs B150E678, B150E679, B150E67B, B150E67C, B150E67D, B150E67E and B150E67F have been made informational events; they no longer generate a call home. In addition, the algorithm that is used to determine when to label SRCs B150E675, B150E676 and B150E67A "serviceable events" has been altered; the threshold is now more than 15 errors on a multiplexer card (also known as a "mux" card) have to be logged in less than 24 hours. Here are the details for each SRC mentioned above: B150E675: Marked "informational" until the threshold is exceeded, then marked "predictive". B150E676: Marked "predictive" if the mux in both node 0 (or drawer 0) and node 1 (or drawer 1) fails to ping; informational in all other cases. B150E678: Informational B150E679: Informational B150E67A: Informational until the threshold is exceeded, then marked "predictive, degraded". B150E67B: Informational B150E67C: Informational B150E67D: Informational B150E67E: Informational B150E67F: Informational HIPER : A problem was fixed that caused SRC B155B086 to be logged, and a call home to be made, when the service processor was reset when the CEC was powered on. HIPER : On systems with a redundant service processor, a problem was fixed that caused redundant service processor failover to be disabled after the concurrent installation of system firmware level SF240_299. A problem was fixed that was causing the HMC to time out when doing a system firmware update, with SRC E302F928 logged. A problem was fixed in the service processor firmware that caused the HMC to appear to be hung when the managed system was powering on. On model 590 and 595 systems with four processor nodes, a problem was fixed that prevented the system from booting when an InfiniBand adapter was installed in slot P5-C13. On systems running i5/OS, a problem was fixed that caused i5/OS to continue to report a firmware update policy of "OS managed", even though an HMC had been reattached and the firmware update policy changed to "HMC managed". On models 590 and 595, the firmware was changed so that the JMUX is called out first in the FRU list for SRC B1xxF131. A problem was fixed that prevented the HMC from reestablishing a connection to the managed system's service processor when the network between the two was fixed after a long outage. A problem was fixed that caused the HMC to be in the "incomplete" state after a service processor reset/reload. problem was fixed that prevented the HMC from correctly opening a VTERM. A problem was fixed that caused the managed system to crash with SRC B181EF88 being logged, and a service processor dump being generated. On systems with a redundant service processor, a problem was fixed that added approximately 10 minutes to the time it took the system to reboot. On systems with a redundant service processor, a problem was fixed that caused an unrecoverable error with SRC B1818610 during a firmware installation by the HMC. This also prevents the new level of firmware from being activated. On systems with a redundant service processor, a problem was fixed that caused the redundancy status panel on the HMC to be blank when the primary service processor had lost communication with the secondary, but the secondary service processor was still able to communicate with the primary. On systems with a redundant service processor, a problem was fixed that caused the system to crash (with SRC B18187E3 being logged) when an administrative failover to the secondary service processor was initiated and Ethernet port 0 on the service processors was not available. On systems with a redundant service processor, a problem was fixed that caused the system to crash (with SRC B1818600 being logged), followed by a service processor failover. On systems with a redundant service processor, a problem was fixed that caused the ASMI hardware configuration/deconfiguration menus to display "Invalid" for the state of the secondary service processor. System firmware changes that affect certain p5, i5, and OpenPower systems: On model 55A, 52A, and 285 systems with a graphics adapter, a problem was fixed that caused the system to hang when it rebooted the first time after AIX was installed. 01SF240_299_201 System firmware changes that affect all p5 and i5 systems: HIPER : The initialization settings of the memory buffers were changed to eliminate spurious checkstops that were causing system and partition crashes with SRC B124E500 and word 8=0095xxxx. 01SF240_298_201 HIPER On systems using virtual I/O services (VIOS), a problem was fixed that caused a system checkstop, with SRC B182E500, during a DLPAR memory removal action. HIPER On systems using virtual I/O adapters, a problem was fixed that caused physical I/O adapters to be left in an unusable state, and therefore unavailable to the partitions. 01SF240_284_201 New Features/Functions On systems with a redundant service processor, a function was added so that a call home with SRC B181610E is made when the system is booted with failover disabled. ATTENTION: On systems with redundant service processors that are being upgraded from an SF235 release level to SF240_297 or later, SRC B181610E will be posted during the firmware upgrade process. In this case only, the B181610E SRC can be ignored. System firmware changes that affect the model 575, 590, and 595, other HMC-controlled servers, and clustered systems: HIPER: On systems with a redundant service processor, a problem was fixed that caused service processor failover to be erroneously disabled after a CEC deconfiguration action. HIPER: On systems with a redundant service processor, a problem was fixed that caused the system to terminate with SRC B1xx951C after a failover to the secondary service processor. This problem can also cause the system to terminate with SRC B1xx9523 after a reset/reload of the primary service processor. A problem was fixed that was causing multiple service processor reset/reload operations with SRC B1817201. On a partitioned system running i5/OS, a problem was fixed that caused error CPF9E75 ("i5/OS usage limit exceeded - operator action required") to be posted about once an hour, even though the system had a valid number of processor licenses. The firmware was changed so that HMC surveillance errors with SRC B1xxE433 are logged as informational (without hardware callouts) instead of predictive. On systems with a redundant service processor, a problem was fixed that caused a service processor failover to fail with SRC B181E911. On systems with a redundant service processor, a problem was fixed that caused platform dump data files to be unavailable from the new primary service processor after a service processor failover. On systems with a redundant service processor, a problem was fixed that caused SRC B1818A0E to be logged when the system was rebooted after a dump was captured. A problem was fixed that caused the managed system to appear to be hung when viewed from the HMC. System firmware changes that affect systems using HSL Opticonnect: HIPER For systems in an Opticonnect cluster with firmware levels prior to SF240_284 installed, a problem was fixed that caused a system to terminate with SRC B182E500. Unlike the fix provided for this problem in SF240_284, this fix can be concurrently activated. A problem was fixed that caused SRC 10009118 to be posted erroneously on systems in an Opticonnect cluster. 01SF240_261_201 System firmware changes that affect systems using HSL Opticonnect: A problem was fixed that caused a system in an Opticonnect cluster to crash with SRC B182E500 when partitions were activated. A problem was fixed that might have caused partitions running on systems in an Opticonnect loop to become unresponsive. A problem was fixed that might have caused HSL Opticonnect connections between partitions in a cluster (which has three platforms in a common HSL ring) to fail when one of the platforms is rebooted. A problem was fixed that prevented errors on PCI buses (connected by an HSL Opticonnect loop) from being handled properly; unpredictable results occurred in active partitions that were using the failing hardware. A problem was fixed that caused the HSL loops to fail, when the loop had switchable towers, and one of the servers on the loop was booted. A problem was fixed that prevented the hypervisor from correctly moving an IOP-less adapter if an I-ASP failover occurred. A problem was fixed that caused the ownership of the IOP to be out of sync after an I-ASP failover. A problem was fixed that caused the adapters that were not involved in an I-ASP failover to be missing, because they were not fully processed. The symptom depends on the adapters that were not fully processed. System firmware changes that affect the model 575, 590, and 595, other HMC-controlled servers, and clustered systems: HIPER : On model 575, 590, and 595 systems, a problem was fixed that caused a memory failure with SRC B123E500 after the concurrent repair of a CEC DCA. In a large cluster of systems, a problem was fixed that caused the clustered system manager to receive the same IP address for multiple managed systems - causing no connect or incomplete status to be displayed on the HMC for those managed systems. In a large cluster of systems, a problem was fixed that caused the AIX DHCP server to assign a new IP address to a service processor, even though the service processor was already using its old (valid) IP address. When this problem occurs, the HMCs start seeing different frames and/or CECs in the list of managed systems from the ones they normally see. On model 590 and 595 systems, this firmware level fixes a problem that prevented capacity upgrade on demand (CUoD) DDR2 memory from being activated properly when it was installed in a system that had been running with non-CUoD DDR2 memory. The problem is usually seen as having less memory activated than expected, possibly not enough to activate a partition. To correct this problem if it currently exists on the system, after installing this firmware level the system must be rebooted (to recollect the memory configuration data) and new activation codes for the CUoD memory have to be entered. SF240_284 now becomes the new minimum firmware level required for FCs 4500, 4501, and 4502 CUoD DDR2 memory cards. On a partition booting i5/OS, a problem was fixed that prevented the partition from booting if the partition had a large amount of memory (greater than approximately 200 GB) allocated to it. On systems that are partitioned, a problem was fixed that caused a partition with more than 128 MB of memory, and with a logical memory block (LMB) size of 16 MB, to fail to boot. A problem was fixed that prevented a partition with huge pages (with a page size of 16 GB) from completing the power-off process. A problem was fixed that prevented some partitions from being reactivated after a short power outage caused them to be deactivated. A problem was fixed that caused dynamic logical partitioning (DLPAR) operations to fail (with SRC HSCL025A: "Service processor lock failed.") even though there appeared to be no other activity that would cause them to fail. A problem was fixed that caused a switchable tower to fail to recover after a tower switch operation A problem was fixed that caused the HMC to go to the incomplete state when utilization data was requested from the managed system. A problem was fixed that caused the HMC to erroneously go to the incomplete state with SRC B7000602. A problem was fixed that was delaying the reporting of some platform errors to the partitions running on the system. A problem was fixed that caused an IOP-less i5/OS partition with a large amount of memory and a small logical memory block (LMB) size to fail to boot. A problem was fixed that prevented the enclosure LED from being turned on when the FRU identify LED on one of the components in the enclosure was turned on. On systems with a redundant service processor, a problem was fixed that caused SRC B181B013 to be erroneously generated when the system firmware was upgraded from SF235_xxx to SF240_xxx. On systems with a redundant service processor, a problem was fixed that caused a duplicate IP address to be assigned to the eth0 port of the service processors. This problem is most likely seen at first install of the machine, with an "invalid readiness" connection status shown on the HMC and an SRC B1xx3598 posted in the error log. On systems with a redundant service processor, a problem was fixed that caused an entry in the service processor error log that erroneously indicated that the secondary service processor had been guarded out. On systems with a redundant service processor, a problem was fixed that caused the secondary service processor to reset/reload after several months of run time (with SRC B1817201), due to an out-of-memory condition. On systems with a redundant service processor, a problem was fixed that caused SRC B1815008 to be erroneously logged in the secondary service processor's error log. On systems with a redundant service processor, a problem was fixed that caused the wrong service processor to be called out in the error log entry for SRC B7006990. On systems with a redundant service processor, a problem was fixed that caused the connection state to toggle between "Incomplete", "No Connection" and "Already Connected". On systems with a redundant service processor, a problem was fixed that could have allowed the firmware to initiate a service processor failover, even though the secondary service processor was not ready for the failover. System firmware changes that affect certain p5, i5, and OpenPower systems: On model 520, 52A, 550 and 55A systems, a problem was fixed that caused the second power supply to be called out as defective if power was applied to it after the system had started to power on. If this error condition is already present on the system, the power supply will have to be reseated to clear the error. A problem was fixed that would have caused the memory DIMMs to be replaced prematurely if correctable errors start to occur. This applies to model 561 systems with processor features code 7295 or 7781 installed, and model 570 systems with processor feature code 7782 installed. A problem was fixed that might have caused the wrong memory DIMM to be called out if a memory failure occurs. This applies to model 561 systems with processor features code 7295 or 7781 installed, and model 570 systems with processor feature code 7782 installed. On model 561 systems, a problem was fixed that caused B181B08E to be erroneously posted during the cold repair of a service processor. This problem may occur in systems with processor feature code 7295 or 7781 installed. A problem was fixed that might prevent the system from booting to runtime with power SRCs 11008456 and 110015x4, even though the power subsystem was functioning within specifications. System firmware changes that affect all p5 and i5 systems: HIPER : A problem was fixed that caused the system to crash with SRC B150D133. A system dump is generated as a result of the problem (SRC B181F03B). HIPER : A problem was fixed that caused the system or partition to crash when corruption was detected in low memory. DEFERRED : A change was made to improve the reliability of system memory. This change reduces the likelihood of SRC B123E500 occurring, and also reduces the likelihood of a system crash with SRC B1xxF667. HIPER : A problem was fixed that caused I/O paths to be deconfigured after certain types of failures, indicated by SRC B170100A, until no I/O paths were left. The firmware has been changed so that the I/O paths are no longer deconfigured under these circumstances. A problem was fixed that caused the "ping" command in the system management services (SMS) to fail during a NIM installation. A problem was fixed that caused a large number of B181C00A SRCs to be erroneously posted in the service processor's error log. A problem was fixed that caused the service processor to run out of memory with SRC B1817201 and generate a service processor dump. A problem was fixed that prevented the service processor's serial ports from being configured to run at 50 baud and 2400 baud. A problem was fixed that prevented the protocol menu in the system management services (SMS) menu for virtual LAN adapters from being displayed. A problem was fixed that caused AIX to incorrectly report errors that occurred during booting and were then passed to the AIX error log. A problem was fixed that prevented a beep or bell sound from being heard when an error occurred in an X window. A problem was fixed that erroneously caused a service processor dump when a power-off request was issued before a reboot that was in progress was complete. The firmware was changed so that SRC B1xx3008 will not be reported to the error logs during and after a concurrent firmware update. The firmware was changed so that SRCs B1xxE676, B1xxE678, and B1xxE67A will not be reported during and after a concurrent firmware update unless a threshold is reached. 01SF240_259_201 System firmware changes that affect model 575, 590 and 595 systems: On model 590 and 595 systems, additional enhancements were made to the memory timing parameters for systems with feature codes 4500, 4501, and 4502 installed (DDR2 memory cards). On model 575, 590, and 595 systems, a problem was fixed that caused SRCs 11008720 and 11008721 to be erroneously generated when the HMC was off-line (due to an HMC code update or network problem) for more than 21 minutes. Bulk power code BP240_197, or a later level, must also be installed to fully implement this fix. 01SF240_258_201 System firmware changes that affect model 570 systems: A problem was fixed that caused an erroneous system memory failure with SRC B123E500 on model 561 systems with processor feature code 7781 and model 570 systems with processor feature code 7782. 01SF240_233_201 New features and Functions: With this service pack, 1 TB segments, 64 KB pages, and 16 GB large pages, are supported on model 590 and 595 systems. New processor feature code / CCIN code combination are supported - Service pack SF240_258 provides the minimum firmware support level for these processor feature code/CCIN combinations: Processor feature code 7654 with CCIN 53C0 Processor feature code 8325 with CCIN 53C2 Processor feature code 8327 with CCIN 53C3 Processor feature code 8330 with CCIN 53C4 Processor feature code 8323 with CCIN 53C1 Processor feature code 8312 with CCIN 53C6 Processor feature code 7781 with CCIN 53C7 Processor feature code 7782 with CCIN 53C8 Processor feature code 8338 with CCIN 53C9 Processor feature code 7675 with CCIN 53CB, 7676 with CCIN 53CC New Power 5++ processor feature codes are supported on the following systems: Processor feature code 8282, 8283, 8284 Processor feature code 5326, 5327 Processor feature code 8314, 8315, 8316 Processor feature code 8285, 8286 System firmware changes that affect clustered systems using InfiniBand switches: HIPER : Various fixes and enhancements were made in firmware that supports InfiniBand switches attached to partitions running AIX or Linux. This set of changes only affects clustered systems using InfiniBand switches. System firmware changes that affect model 575 systems with DDR2 memory (processor feature codes 7675 and 7676): DEFERRED HIPER : On model 575 systems with processor feature codes 7675 and 7676 and DDR2 memory, a problem was fixed that caused a system crash with SRC B1xxE500. This only affects model 575 systems with processor feature codes 7675 and 7676. System firmware changes that affect systems using HSL Opticonnect: DEFERRED HIPER : A problem was fixed that caused a partition to terminate during boot with SRC B6000103. This change only affects systems running in an HSL Opticonnect cluster environment. A problem was fixed that prevented an HSL Opticonnect loop from reconnecting to one system in the cluster after a system in the Opticonnect cluster was rebooted. A problem was fixed that prevented an HSL Opticonnect loop from initializing correctly for high bandwidth operation. A problem was fixed that caused partitions to fail to establish a connection with an HSL Opticonnect loop. System firmware changes that affect all 9131-52A systems and 9405-520 and 9406-520 systems with processor feature code 8325, 8327, or 8330: DEFERRED HIPER : A problem was fixed that caused the system to crash with SRC B131E500, an I/O hub error. This affects the following: all 9131-52A systems, and 9405-520 and 9406-520 systems with processor feature code 8325, 8327, or 8330. System firmware changes that affect all p5 and i5 systems with Power 5+ processors and DDR2 memory: Enhancements were made to memory timing parameters for systems using DDR2 memory. System firmware changes that affect the model 575, 590, and 595, other HMC-controlled servers, and clustered systems: A problem was fixed that kept entitled weight from being added to a partition if the logical partition (LPAR) group was changed while the partition was active. A problem was fixed that caused SRC B700F103 to occur if, when adding memory to a partition and the size requested exceeded the maximum amount of memory allocated to the partition, there were already dynamic logical partition (LPAR) changes in progress. A problem was fixed that prevented a service processor failover from being completed successfully after the primary service processor experienced a DMA transfer timeout. On model 575, 590, and 595 systems, a problem was fixed that caused the IPL time to possibly be longer than normal. If this problem is encountered, the system will complete the IPL but the IPL may be delayed by as much as 40 minutes. During this delay, a C7004091 SRC with word 7 equal to 00000402 will be displayed. A problem was fixed that caused system dumps to be truncated when more than one HMC was attached to the managed system. A problem was fixed that caused the HMC to truncate dumps that were larger than 4 GB. A problem was fixed that caused a platform dump to fail internally in a way that the dump did not terminate the system, and no dump was available. When this failure occurs, the service processor dump data should be available on the HMC. In a system with redundant service processors, a problem was fixed that caused the secondary service processor to be guarded out when the network the service processor was on was set up incorrectly. A problem was fixed that caused a platform dump to fail with SRCs B1xxF141 and B1xxE500, followed by multiple B1xxF511 SRCs, and possibly B1xxF6D3 SRCs. In a system with redundant service processors, a problem was fixed that caused the service processor error logs to be overwritten. In a system with redundant service processors, a problem was fixed that required a reset/reload of the secondary service processor to get it up to standby after an emergency power off (EPO). In a system with redundant service processors, a problem was fixed that caused the secondary service processor to be unresponsive, and the failover to fail, with SRC B113E500. In a system with redundant service processors, a problem was fixed that caused SRCs such as 11001D02, 11001D03, and 11001D11 through 11001D18 to be erroneously logged during a failover. In a system with redundant service processors, a problem was fixed that caused a platform reboot to fail with SRC B181850E. In a system with redundant service processors, a problem was fixed that prevented redundancy from being restored after the communication link between the service processors was broken, then re-established. A problem was fixed that caused extraneous B181F000 SRCs to be posted. A problem was fixed that caused an incomplete FRU list to be generated after an unrecoverable memory error. A problem was fixed that caused SRC B157F22A to be posted and the IPL to be halted after a platform dump. In a system with redundant service processors, a problem was fixed that caused platform dumps to be corrupted. A problem was fixed that cause the HMC to report that a dump was incomplete, even though all of the dump data was present. A problem was fixed the prevented a concurrently-added expansion unit from being displayed on the HMC when there were active i5/OS partitions, and expansion units in the inactive state, on the system. A problem was fixed that caused certain operating system commands (such as snap and lsvpd) to hang after a hardware problem flooded the hypervisor with errors. On a system configured with the virtual partition manager (VPM), a problem was fixed that caused the F6 option in the i5/OS service activity log (SAL) to be unavailable when the system attention indicator was on. A problem was fixed that caused the system firmware to crash (indicated by "default catch") when booting a partition on a model 590 or 595 system with twelve fully configured 7040-61D I/O drawers. A problem was fixed that caused a partition to boot very slowly, and the system management services (SMS) menu to be displayed incorrectly, on large model 590 and 595 systems with many USB adapters. In a system with redundant service processors, a problem was fixed that caused SRC HSCL1400 to be erroneously generated, and the backup service processor to be guarded out, during the cold replacement of one of the service processors. System firmware changes that affect certain p5, i5, and OpenPower systems: HIPER : On model 590 and model 595 systems, a problem was fixed that caused memory to be deconfigured due to an erroneous memory controller failure, with SRC B121E500 and word 8 = 00EA0035 On model 561, 570, 590, and 595 systems, a problem was fixed that caused the software portion of a dump to be lost, and SRC B150F62A to occur. On model 561, 570 and 575 systems, a problem was fixed that caused the system to fail to collect dump data, and post SRC B1xx1007, after a system crash. On model 505 systems, a problem was fixed the caused the HMC to incorrectly display the location codes of the PCI slots in the managed system. System firmware changes that affect model 570 systems: A problem was fixed that caused system power control network (SPCN) error codes with the format 110015xx and 110016xx to be erroneously generated (against the drawer being serviced) during the replacement of the service processor at standby. In a system with redundant service processors, a problem was fixed that caused C1001020 to persist in the control (operator) panel after the service processor that's in the same drawer as the operator panel was restored to the configuration and had come up to standby. A problem was fixed that caused a voltage regulation fault that persisted through a service processor reset to result in an erroneous posting of SRC 11001632. A problem was fixed that caused system power control network (SPCN) firmware downloads to expansion drawers to initially fail, with the system retrying the downloads until they were successful. In a system with redundant service processors, a problem was fixed that prevented the IP information from the secondary service processor (that was deconfigured or not working) from being displayed by control (operator) panel function 30. System firmware changes that affect certain p5 and i5 systems: DEFERRED and HIPER The hardware initialization settings were changed to reduce the likelihood of a system crash with SRC B114E500 and word 8 = 03010008. This affects the following systems: i5:9405-520 and 9406-520 with processor feature code 8325, 8327 or 8330. p5:9115-505, 9111-285, 9131-52A and 9133-55A. System firmware changes that affect all p5 and i5 systems: HIPER A problem was fixed that was causing the service processor to reboot with SRC B1817201 when dump files were extracted by the HMC. A problem was fixed that caused SRC BA188002, an EEH error, to be posted during a dynamic memory removal operation or high adapter usage, which resulted in the loss of an I/O adapter. The partition had to be rebooted to recover the adapter. A problem was fixed that caused the hardware management console (HMC) to report that a partial platform dump was collected, even though all dump data are present. A problem was fixed that caused platform dumps to be incomplete or missing. A problem was fixed that caused the system to hang with SRC C700406E when the "reset PCI bus configuration" option was invoked. This option is in the factory configuration menu in the advanced system management interface (ASMI). A problem was fixed that caused the additional error data words with SRC B2001150 to be incomplete. A problem was fixed that caused the system to fail to boot with SRC B181F407 if the vital product data (VPD) for a dual in-line memory module (DIMM) was not available. A problem was fixed that caused the system to fail to boot with SRC B181B0BF, even though a recoverable error had been logged. A problem was fixed that caused incorrect hardware FRUs to be called out after a power failure. A problem was fixed that caused the system to fail to boot using the automatic power on restart function after AC power had been restored. A problem was fixed that caused SRCs 11001D11 through 11001D18 to be erroneously generated after a reset was issued from the advanced system management interface (ASMI). A problem was fixed that was causing firmware to fail to boot an AIX or Linux partition (indicated by displaying "default catch") when the firmware console had been changed from one graphics adapter to another. A problem was fixed that was causing the firmware to crash, when booting an AIX or Linux partition, when the boot device in the system management services (SMS) menu was changed to a SAN or SCSI device. 01SF240_219_201 System firmware changes that affect all p5 and i5 systems: A problem was fixed that caused the "ping" command in the system management services (SMS) menus to fail during a NIM installation. A problem was fixed that caused the hardware management console (HMC) to report that a partial platform dump was collected, even though all dump data are present. A problem was fixed that caused platform dumps to be incomplete. A problem was fixed that caused a logical partition to terminate during boot with SRC B6000103. A problem was fixed that caused the system to hang with SRC C700406E when the "reset PCI bus configuration" option was invoked. This option is in the factory configuration menu item in the advanced system management interface (ASMI). A problem was fixed that caused the additional error data words with SRC B2001150 to be incomplete. System firmware changes that affect the model 575, 59x, other HMC-controlled servers, and clustered systems: HIPER : Various fixes and enhancements were made in firmware that supports InfiniBand switches attached to partitions running AIX or Linux. DEFERRED HIPER : On model 575 systems with Power5+ processors, a problem was fixed that caused a system crash with SRC B1xxE500. A problem was fixed that kept entitled weight from being added to a partition if the logical partition (LPAR) group was changed while the partition was active. A problem was fixed that caused SRC B700F103 to occur if, when adding memory to a partition and the size requested exceeded the maximum amount of memory allocated to the partition, there were already dynamic logical partition (LPAR) changes in progress. A problem was fixed that prevented an HSL Opticonnect loop from reconnecting to one system in the cluster after a system in the Opticonnect cluster was rebooted. A problem was fixed that prevented a service processor failover from being completed successfully. On model 575 and 59x systems, a problem was fixed that caused the IPL time to possibly be longer than normal. If this problem is encountered, the system will complete the IPL but the IPL may be delayed by as much as 40 minutes. During this delay, a C7004091 SRC with word 7 equal to 00000402 will be displayed. System firmware changes that affect model 570 systems: A problem was fixed that caused system power control network (SPCN) error codes with the format 110015xx and 110016xx to be erroneously generated (against the drawer being serviced) during the replacement of the service processor at standby. System firmware changes that affect p5 and i5 systems with the P5IOC chip DEFERRED A problem was fixed that caused SRC B131E500 ("A phased-lock-loop lock failure") to be erroneously generated. This affects the following systems: i5:9405-520 and 9406-520 with processor feature code 8325, 8327 or 8330. p5:9115-505, 9110-51A, 9111-285, 9131-52A and 9133-55A. 01SF240_202_201 Support for 4GB, 8GB, and 16GB DDR II memory cards on the p5 models 9119-590 and 9119-595. System firmware changes that affect all p5 and i5 systems: HIPER : A problem was fixed that caused the system to interpret a machine condition as requiring special attention handling, where no such special attention existed. This could result in a system checkstop. This problem is also known as the "Master Attention Alone" condition. HIPER : A problem was fixed that could cause unpredictable results when the control logic on the service processor is reset. HIPER : The hardware initialization settings were changed to prevent system checkstops with error code B1xxE500. HIPER : A problem was fixed that caused a machine check with error code B121E500 (with word 8 = 00530006) after a memory steering operation. DEFERRED : A problem was fixed that prevented a system dump from completing after a hardware failure, with error code B181F22A being logged. A problem was fixed that caused the system to fail to boot if the white power button was pressed within 10 seconds after reaching standby, but before C1802000 was posted on the control (operator) panel. A problem was fixed that caused the service processor to perform a reset/reload too frequently, which caused too many dump files to be generated. A problem was fixed that caused the system to crash with error code B181F141 when a PCI adapter was hot-plugged. A problem was fixed that caused informational SRC B1813028 to appear in the service processor error log after a firmware update from one SF235 level to a subsequent SF235 level. A problem was fixed that was causing some types of error codes to be defined incorrectly in the service processor error log. The processor runtime diagnostic code was enhanced to more accurately point to the processor that is suspected to be failing when a dump is taken. A problem was fixed on p5 systems (that have a graphics adapter and a USB adapter) that caused the firmware's console selection to be lost when firmware level SF240_202_201 was installed. A problem was fixed that was causing the system or partition to drop to the open firmware prompt when trying to view the fibre-channel boot devices in SMS menus. A problem was fixed that was causing error code B181B013 to be erroneously generated during a code update from an SF230 level to an SF235 level. A problem was fixed that prevented the "identify" LEDs from being toggled correctly on some enclosures. A problem was fixed that prevented virtual adapters from being configured. A problem was fixed that, in certain configurations, caused the HSL Opticonnect loop to fail when a single loop failed, even though a redundant path was available. A problem was fixed that was causing excessive B7006970 error codes to be logged when an I/O tower or drawer failed. A problem was fixed that caused the system to hang when booting after a main storage dump. A problem was fixed that, under some circumstances, prevented remote support from gathering information about partitions that are running. A problem was fixed that caused the HSL Opticonnect ring between systems to fail when concurrently adding a tower to an HSL Opticonnect ring. A problem was fixed that caused a frame that had been concurrently removed from an HSL Opticonnect ring to remain in the configuration displayed by the hardware service manager tool. A problem was fixed that caused the macro "nm lcsnm verifyvpd -xm" not to display all the bus VPD from XM. A problem was fixed that caused two successive in-band server firmware installations attempts to fail, but the third one to succeed. - If the inband firmware installation fails on power down of the service partition, in some cases the next attempt will fail. Retrying the inband update by powering down the service partition again will succeed. A problem was fixed that caused the error data that is captured after an extended error handling (EEH) event to be zeroed out. A problem was fixed that caused error code B7006970 to be logged after a partition is shutdown when certain types of DDR adapters are plugged into a DDR slot. A problem was fixed that caused some slots to be unusable by a partition, and error codes B7006970 and B7006971 errors to be logged, even though the hardware error for that slot or bus was recoverable. A problem was fixed that caused system firmware to report incorrect error information for some PCI slots, which prevented the adapters in these slots from being configured. System firmware changes that affect the model 575, 59x, other HMC-controlled servers, and clustered systems: DEFERRED HIPER : A potential server checkstop issue exists in clusters using p5 models p575, p590, and p595, when these models are used to execute compute-intensive applications tuned with the November Power5 Fortran compiler. Clusters executing applications that are compiled for optimal performance by utilizing the software pre-fetch function are exposed to a server checkstop (B1xxE500). Hardware initialization settings were changed to fix this problem and the performance tools modified to take these new settings into account . DEFERRED HIPER : An initialization problem was fixed that was causing the high-performance switch (HPS) network adapter to hit the adapter error threshold during run-time. HIPER : In a system with a redundant service processor, a problem was fixed that caused the corruption of registry values on the primary service processor. This registry corruption was evidenced by the fact that the hypervisor reported the amount of configurable memory incorrectly. HIPER : In a system with a redundant service processor, a problem was fixed that caused error code B1818A09 to be generated intermittently. HIPER : In a system with a redundant service processor, a problem was fixed that caused runtime fail-over to the secondary service processor to fail. HIPER : In a system with a redundant service processor, a problem was fixed that caused the system to fail to boot, and one of the service processors to become deconfigured. HIPER : A problem was fixed that was causing the power control code to time out when querying the vital product data (VPD) on large system configurations. DEFERRED : A problem with the memory being allocated to high-performance switch (HPS) network adapters was fixed. A problem was fixed that was causing a model 59x system to fail to boot (with error code BxxxF7A9) when a memory card failure was detected during the boot. In a system with a redundant service processor, a problem was fixed that caused a firmware installation to fail with multiple occurrences of error code B1818A0E. In a system with a redundant service processor, a problem was fixed that caused error code B181B013 to be logged in the secondary service processor's error log. In a system with a redundant service processor, a problem was fixed that caused both service processors to become "primary" after termination under certain conditions. In a system with a redundant service processor, a problem was fixed that caused error code B181E678 to be generated erroneously very early in the power-on sequence. In a model 59x system with a redundant service processor installed, a problem was fixed that caused the "concurrent addition" of a node to fail with error code B1xxE500. In a model 59x system or a model 570 system with a redundant service processor installed, a problem was fixed that caused the IPLing of the secondary service processor to fail due and error code B1xxF684 to be generated In a system with a redundant service processor, the firmware was changed so that error code B181E911 is reported (with a recommendation to look at other error logs to isolate the problem), instead of B181E901 or B181E90C, when the firmware cannot identify the reason for a reset/reload. In a model 59x system with a redundant service processor installed, a problem was fixed that caused error code B181F684 to be erroneously logged by the secondary service processor. In a model 59x system with a redundant service processor, a problem was fixed that caused error codes 1000911C and 10009138 to be logged erroneously during a service processor failover. In a system with a redundant service processor, a problem was fixed that caused the error "Message Not Found" to be generated during the cold repair of a service processor. In a system with a redundant service processor, a problem was fixed that caused the secondary service processor to be removed from the configuration under some circumstances during an emergency power off. In a system with a redundant service processor, a problem was fixed that was causing the system to reboot continuously while the secondary service processor was attempting to mount a file system. For the model 59x systems, the FRU list for MCM and memory card VPD access errors was updated to include the MUX card. A problem was fixed that caused error code HSCL1400 to be generated when a redundant service processor was installed with firmware release SF230 or earlier. A problem was fixed that was causing all of the hardware in a processor node (in a multi-node 59x system) to be erroneously shown as "Deconfigured" with an error type of "Association" in the ASMI hardware deconfiguration menus. A problem was fixed that caused some error log entries not to be seen on the HMC. A problem was fixed that caused multiple B176871C error codes to be generated. A problem was fixed that was causing dynamic logical partitioning operations in a Linux environment to hang intermittently. The firmware was enhanced so that the service processor will report a timeout if the hypervisor does not acknowledge a "memory resilience" message. A problem was fixed that prevented system power control network (SPCN) firmware downloads from occurring after a hardware service action is performed from the HMC. System firmware changes that affect p5 and i5 systems not in 24 inch racks: A problem was fixed that caused error code 11002600 SRC to be generated during the power-down sequence, and a failure of the subsequent power-on with error code B150F22A. System firmware changes that affect model 570 systems: A problem was fixed that caused error code B182E500 to occur during a slow mode IPL of a model 570 system with two drawers and processor card feature code 29AE, 7781, 7782, 832E, or 8338. System firmware changes that affect certain p5 and i5 systems: Additional hardware initialization settings were changed to prevent system hangs with error code B7xx406E. This affects the following systems: i5: 9405-520 and 9406-520 with processor feature code 8325, 8327 or 8330 p5: 9115-505, 9110-51A, 9111-285, 9131-52A, and 9133-551 DEFERRED HIPER : A problem was fixed that caused certain I/O adapters to fail at runtime. This affects the following systems: i5: 9405-520 and 9406-520 with processor feature code 8325, 8327 or 8330 p5: 9115-505, 9110-51A, 9111-285, 9131-52A, and 9133-551 01SF240_201_201 A problem was corrected that caused the advanced system management interface (ASMI) menus to be displayed incorrectly in languages other than English. 01SF235_185_160 The following system firmware functions were added in this release: Support for the model 9116-561 (System p5 560Q) Support for model 9110-51A (OpenPower p5-511 and p5-511Q.) Support for Power5+ processors on the pSeries models 510, 510Q, 520, 520Q, 570, and 575. Support for Power5+ processors on the iSeries models 520, 550, and 570. Support for IOP-less configurations on iSeries models 520, 550, and 570. Support for mixing CoD-capable DDR2 memory with DDR2 memory that is not CoD-capable in a system. Support for F/C 0649 (internal version) and F/C 0650 (external version), a new high-performance SCSI adapter with RAID 6 disk controller. Support for the collection (and viewing on the HMC) of logical partitions' utilization of processor and memory resources. Support for a thin console on iSeries systems. Support for huge pages (16 GB) in the Advanced System Management Interface (ASMI) menus. Enhancements to the "Restore to factory default" option, CoD options, time-of-day menu, and firmware update policy menu on the ASMI menus. Location codes of the memory DIMMs were added to the memory deconfiguration menu interface in the ASMI menus. The option to set the number of virtual LAN (VLAN) switches was added to the ASMI menus. A feature to retry boot from a hard disk after an initial failure due to firmware timing, instead of immediate failure. (This type of failure is typically seen on boot disks from external disk subsystem.) Various enhancements and fixes to DS6000 and DS8000 storage systems firmware. The following system firmware changes affect specific p5 and i5 systems not in 24 inch racks: The System Management Services (SMS) password recognition code was changed so that passwords that are allowed in the Advanced System Management Interface (ASMI) can now be typed to enter the SMS. LIC code updated. None. When a system with an uninterruptible power supply (UPS) connected experienced a reset/reload of the service processor, the UPS was not being detected correctly. LIC code updated. None. A problem was fixed that was causing SRC B1xxE500 (with SRC word 8 equal to DD02) when processor runtime diagnostics were called during a dump. LIC code updated. None. A problem was fixed that caused the subsystem ID (the xx in B1xx yyyy) to be changed between the time processor runtime diagnostics reported an error to the gard code and when the service processor error log entry was created. LIC code updated. None. A problem was fixed that was causing the location codes in the VPD data to be invalid after the VPD (Anchor) card was replaced. LIC code updated. None. A problem was fixed that caused the system firmware to report an RTAS error (with error code FFFF D8F1 and malfunction code of 0000 000C) when certain types of hardware errors were encountered. LIC code updated. None. A problem was fixed that was causing the system firmware to crash when a certain type of KVM (keyboard, video, mouse) switch was used. LIC code updated. None. A problem was fixed that caused a BA180010 error to be logged when a PCI-X DDR slot was empty. LIC code updated. None. A problem was fixed that was causing an "IOP-less partition" to fail to boot; the partition was hanging at SRC B200F008. LIC code updated. None. The firmware console selection code was changed so that the time-out for console selection (approximately one minute) is independent of the number of potential consoles. LIC code updated. None. A problem with the slot allocation code was fixed that prevented partitions from being opened by the IVM (integrated virtualization manager). LIC code updated. None. A problem was fixed that caused extended SRC data to be missing when SRC B7000103 was generated. LIC code updated. None. System firmware changes that affect model 570 systems with more than one processor drawer: On model 570 systems with more than one processor drawer, a problem was fixed that was preventing enclosure VPD keywords from being changed in the second, third, and fourth processor drawers using the ASMI menus. LIC code updated. None. On a system in which a redundant service processor is installed, a problem was fixed that was causing the wrong service processor to be called out when certain types of failures occurred . LIC code updated. None. System firmware changes that affect models 575, 590, and 595, other HMC-controlled servers, and clustered systems: A problem was fixed that was causing the status of the HMC's connection (to the service processor) to be reported incorrectly to the server firmware. LIC code updated. None. A problem was fixed that caused model 575 nodes to fail to boot with SRC B1817201. LIC code updated. None. System firmware changes that affect p5 and i5 systems not in 24 inch racks On a system that is not managed by an HMC, progress codes were being displayed on the potential firmware consoles; this caused the console selection message to scroll off the screen. LIC code updated. None.