■4991972: B200x blade locks into a repeated “boot net” loop following a BIOS update
The CMOS footprint may change between revisions of the BIOS. If this is the case, and the CMOS is not reset to its default values during the blade reboot following a BIOS update, the CMOS configuration may become corrupted and result in repeated network boots.
To avoid this problem, after updating the BIOS on a B200x blade, reset all CMOS settings to their default values when you next reboot the blade. You can do this by typing the bootmode reset_nvram sn command at the SC prompt (where n is the number of the slot containing the blade), or by entering the BIOS setup menu and loading the BIOS defaults.
■5017529: New 1 Gbyte DIMMs used in manufacturing appear as 2x512Mbyte DIMMs
When new 1 Gbyte DIMMs are inserted in DIMM slots on the B200x blade, the ECC driver incorrectly identifies the memory as 2x512Mbyte DIMMs.
This is a cosmetic issue, and can be ignored.
■5015866: Blade does not recognize an SSC which is inserted after a reboot
When a blade is booted without an SSC present, the network interfaces normally attached to the missing switch will not be operational after the SSC is
2.3.2Issues Affecting the B100x Server Blade Only
The following problem has been observed on B100x server blades only:
■4915711: The Real Time Clock (RTC) is updated when resetting from the SC
When you use the reset command from the SC prompt, the blade updates the Real Time Cock (RTC) from the system controller through the BSC. The RTC should be set only when the blade is powered on.
■4979474: The bsc driver cannot allocate IRQ9 or IRQ5 (SuSE with kernel 2.4.21)
The Operating System hangs when the bsc driver attempts to allocate IRQs 9 and 5. This is due to an incorrect ACPI table entry for the bsc hardware.
You can avoid this problem by booting the kernel using the pci=noacpi argument.
■4906666: The BIOS boot menu displays network names incorrectly This is a cosmetic issue and may be ignored.