AM740_110_042 / FW740.60
04/30/13 |
Impact: Serviceability
Severity: ATT
New features and functions
- Support for booting an IBM i partition from a USB flash
drive.
System firmware changes that affect all systems
- A problem was
fixed that prevented predictive guard errors from being deleted on the
secondary service processor. This caused hardware to be
erroneously guarded out if a service processor failover occurred, then
the system was rebooted.
- A problem was fixed that prevented the system attention
indicator from being turned off when a service processor reset occurred.
- A problem was fixed that caused SRC B1813221, which
indicates a failure of the battery on the service processor, to be
erroneously logged after a service processor reset or power cycle.
- A problem was fixed that caused various parts to be
erroneously guarded out in some cases, and the clock card being called
out as defective in other cases, when both ac cords providing power to
a drawer were unplugged when the system was powered on.
- A problem was fixed that caused the Advanced System
Management Interface (ASMI) to produce a service processor dump when
changing the admin user password.
- A problem was fixed that caused various SRCs to be
erroneously logged at boot time including B181E6C7 and B1818A14.
- A problem was fixed that caused a card (and its children)
that was removed after the system was booted to continue to be listed
in the guard menus in the Advanced System Management Interface (ASMI).
- A problem was fixed that caused system fans to be
erroneously called out as failing with one or more of the following
SRCs: 11007610,11007620,11007630,11007640, or 11007650.
- A problem was fixed that caused the service processor to
crash when it boots from the new level during a concurrent firmware
installation.
- A problem was fixed that caused various parts to be
erroneously guarded out in some cases, and the clock card being called
out as defective in other cases, when both ac cords providing power to
a drawer were unplugged when the system was powered on.
- A problem was fixed that caused the management console to
display incorrect data for a virtual Ethernet adapter's transactions
statistics.
- A problem was fixed that caused a hibernation resume
operation to hang if the connection to the paging space is lost near
the end of the resume processing. This is more likely on a
partition that supports remote restart.
- A problem was fixed that caused the system power to be
throttled, resulting in decreased performance. This problem
typically occurs after a PCI adapter is plugged into a node (CEC
drawer), and can also happen when a dedicated I/O partition is powered
on or off.
- A problem was fixed that caused the system to terminate
with a bad address checkstop during mirroring defragmentation.
- A problem was fixed that caused the hibernation validation
of a remote restart partition operation to fail with an "NvRam size
error". This also affects the capability to migrate the partition.
- The Power Hypervisor was enhanced to insure better
synchronization of vSCSI and NPIV I/O interrupts to partitions.
- A problem was fixed that caused SRCs B70069F4 and B130E504
to be erroneously logged when a system was powered down. This
also results in I/O hardware being guarded out, and the hypervisor is
not able to "unguard" the I/O hardware at runtime.
- A problem was fixed that was caused by an attempt to modify
a virtual adapter from the management console command line when the
command specifies it is an Ethernet adapter, but the virtual ID
specified is for an adapter type other than Ethernet. The managed
system has to be rebooted to restore communications with the management
console when this problem occurs; SRC B7000602 is also logged.
- The Hypervisor was enhanced to allow the system to continue
to boot using the redundant Anchor (VPD) card, instead of stopping the
Hypervisor boot and logging SRC B7004715, when the primary Anchor
card has been corrupted.
- A problem was fixed that caused an error log generated by
the
partition firmware to show conflicting firmware levels. This
problem occurs after a firmware update or a logical partition migration
(LPM) operation on the system.
System firmware changes that affect certain systems
- On systems with I/O
towers attached, a problem was fixed that caused SRC 10009135, followed
by SRC 10009139, to be logged, indicating that SPCN loop mode was being
broken, then reestablished.
- On systems with I/O towers attached, a problem was fixed
that caused multiple service processor reset/reloads if the tower was
continuously sending invalid System Power Control Network (SPCN) status
data.
- On partitions with the virtual Trusted Platform Module
(vTPM) enabled, a problem was fixed that caused a memory leak, and
failure, when vTPM was disabled, a vTPM-enabled partition was migrated,
or a vTPM-enabled partition was deleted.
- On systems running multiple IBM i partitions that are
configured to communicate with each other via virtual Opticonnect, and
Active Memory Sharing (AMS), AMS operations may time-out. When
this problem occurs, a platform reboot may be required to recover.
- On a partition with the virtual Trusted Platform Module
(vTPM) enabled, a problem was fixed that caused the partition to stop
functioning after certain operations. When this problem occurs,
the client partition may not power off.
- When switching between turbocore and maxcore mode, a
problem was fixed that caused the number of supported partitions to be
reduced by 50%.
- On systems running Active Memory Sharing (AMS) partitions,
a problem was fixed that may arise due to the incorrect handling of a
return code in an error path during the logical partition migration
(LPM) of an AMS partition.
- On systems using IPv6 addresses, the firmware was enhanced
to reduce the time it take to install an operating system using the
Network Installation Manager (NIM).
- On systems with F/C EU07, the RDX SATA internal docking
station for removable disk cartridge, a problem was fixed that caused
SRCs BA210000 and BA210003 to be logged, and the System Management
Services (SMS) menu firmware to drop into the ok> prompt, when the
default boot list was built.
- A problem was fixed that caused SRC BA330000 to be logged
after the successful migration of a partition running Ax740_xxx
firmware to a system running Ax760, or a later release, or
firmware. This problem can also cause SRCs BA330002, BA330003,
and BA330004 to be erroneously logged over time when a partition is
migrated from a system running Ax760, or a later release, to a system
running Ax740_xxx firmware.
- On system running an IBM i partition, the partition boot
may succeed after a long delay, or may fail, if a mode D boot attempt
is made, there is more than one USB device attached, and the IBM i
operating system (OS) image is on the second USB device.
- On system running an IBM i partition, a problem was fixed
that caused a number of informational SRC BA09000F to be logged when a
mode D partition boot is done. This SRC is logged if a device
that supports removable media is installed and the media is not present.
- On systems with redundant service processors, a problem was
fixed that caused the sibling service processor state to show up as
"unknown" in the service processor error log if a code synchronization
problem was detected after a service processor was replaced.
- On systems running Active Memory Sharing (AMS) partitions,
a timing problem was fixed that may occur if the system is undergoing
AMS pool size changes.
Concurrent hot add/repair
maintenance firmware fixes
- A problem was fixed that caused SRC 11001512 or 11001522 to
be erroneously logged against a node that was added or removed during a
concurrent hot add/repair maintenance operation.
- A problem was fixed that caused SRC B15738B0 to be
erroneously logged against the target node during the node-level
deactivation phase of a concurrent hot add/repair maintenance operation.
- A problem was fixed that caused CHARM operations to fail
when a memory channel failure is followed by a service processor
reset/reload (which is caused by a firmware installation, for example).
- On systems with a GX++ 2-port PCIe2 x8 adapter, feature
code (F/C) 1914, a problem was fixed that caused the location code of
the adapter to be incorrect in the operating system after a hot repair
of the adapter.
- On systems in which there are no processors in the shared
processor pool, a problem was fixed that caused the Hypervisor to
become unresponsive (the service processor starts logging time-out
errors against the Hypervisor, and the HMC can no longer talk to the
Hypervisor) during a concurrent hot add/repair maintenance operation.
- A problem was fixed that caused a hypervisor memory leak
during a concurrent hot add/repair maintenance operation.
- A problem was fixed that caused a concurrent node repair or
upgrade to fail during the system deactivation step with a Hypervisor
error code of 0x300.
- A problem was fixed that caused the system to hang if
memory relocation is performed during a concurrent hot add/repair
maintenance operation.
- A problem was fixed that caused partition activations to
fail during or after a node repair operation.
- A problem was fixed that caused synchronization problems in
an application using the Barrier Synchronization Register (BSR)
facility during the memory relocation that occurs in a concurrent hot
add/repair maintenance operation.
- On systems with an IBM i partition and performance data
collection enabled, a problem was fixed that caused SRC B170E540 to be
logged during a hot repair of a GX++ 2-port PCIe2 x8 adapter, feature
code (F/C) 1914.
- A problem was fixed that prevented the I/O slot information
from being presented on the management console after a concurrent node
repair.
- On systems running multiple IBM i partitions that are
configured to communicate with each other via virtual Opticonnect,
concurrent hot add/repair maintenance operations may time-out.
When this problem occurs, a platform reboot may be required to recover.
|
AM740_088_042
05/25/12 |
Impact: Availability
Severity: SPE
New features and functions
- Support for IBM i Live Partition Mobility (LPM)
- Support for the EXP30 Ultra SSD I/O Drawer, feature code
(F/C) 5888.
System firmware changes that affect all systems
- A problem was
fixed that prevented the user from changing the boot mode or keylock
setting after a remote restart-capable partition is created, even after
the partition's paging device is on-line.
- A problem was fixed that caused a partition with dedicated
processors to hang with SRC BA33xxxx when rebooted, after it was
migrated using a Live Partition Mobility (LPM) operation from a system
running Ax730 to a system running Ax740, or vice-versa.
- A problem was fixed that caused the service processor's
eth0 or eth1 IP addresses to change to "IPv6 NA" when viewed on
the control (operator) panel when a laptop was connected to the service
processor.
- A problem was fixed that caused a system to crash when the
system was in low power (or safe) mode, and the system attempted to
switch over to nominal mode.
- A problem was fixed that caused booting from a virtual
fibre channel tape device to fail with SRC B2008105.
- The firmware was enhanced to increase the threshold of soft
NVRAM errors on the service processor to 32 before SRC B15xF109 is
logged. (Replacement of the service processor is recommended if
more than one B15xF109 is logged per week.)
- A problem was fixed that caused informational SRC A70047FF,
which may indicate that the Anchor (VPD) card should be replaced, to be
erroneously logged again after the Anchor card was replaced.
- A problem was fixed that caused the lsstat command on the
HMC to display an erroneously high number of packets transmitted and
received on a vlan interface.
System firmware changes that affect certain systems
- The firmware
resolves undetected N-mode stability problems and improves error
reporting on the feature code (F/C) 5802 and 5877 I/O drawer power
subsystem.
- On systems on which the service processor is using IPv6
Ethernet addresses, a problem was fixed that caused a service processor
dump to be taken with SRC B181EF88.
- On systems running the virtual Trusted Platform Module
(vTPM), a problem was fixed that caused the system to crash when the
vTPM adjunct was reset.
- On 8231-E1C, 8231-E2C, 8202-E4C and 8205-E6C systems
running IBM i partitions, a problem was fixed that prevented slots on
the same PCI bus from being assigned to different partitions.
This can result in SRC B600690B being logged when a partition is booted.
- A problem was fixed that caused various operations to hang,
such as concurrent hot add/repair maintenance (CHARM) operations,
running lsvpd from a partition, or a concurrent firmware installation.
Concurrent hot add/repair
maintenance firmware fixes
- A problem was fixed that caused a hot node repair
operation to fail with PhypRc=0x0300, indicating the deactivate system
resource operation failed.
- On systems running the virtual Trusted Platform Module
(vTPM), a problem was fixed that caused SRC B400F104, and possibly SRC
BA54504D, to be erroneously generated during a node repair operation.
|