PCI option ROM space errors in UEFI servers - IBM Systems
RETAIN tip: H21709
The IBM BladeCenter Advanced Management Module (AMM) Event log and the Integrated Management Module (IMM) chassis log on rack mount servers show the following error:
FW/BIOS, firmware progress (Firmware Error) hang
See the following picture for the IMM System Event Log (SEL) log entry for more details:
Note: With Unified Extensible Firmware Interface (UEFI) code release 1.73, or later levels for IBM EX5 systems and 2012 products, the message improved to the following:
Error: Error: FW/BIOS, connector (No Op ROM Space) PCI express Slot X fault
Also, for more details, see this picture of the IMM system error log entry:
The slot number is identified for the Peripheral Component Interconnect (PCI) device in which the Read Only Memory (ROM) could not run.
Note: The IMM code released in third quarter 2010 turns on both the FAULT Light Emitting Diode (LED) and the BRD LED on some systems (IBM System x3850 X5 and System x3690 X5).
Turning on the BRD LED is not an expected behavior, and this behavior has been corrected in IMM version 1.28, or later versions. The unexpected LED behavior does not exist on systems using Integrated Management Module II (IMM2).
The system can be any of the following IBM servers:
- BladeCenter HS22, type 1936, any model
- BladeCenter HS22, type 7870, any model
- BladeCenter HS22V, type 1949, any model
- BladeCenter HS22V, type 7871, any model
- BladeCenter HS23, type 1929, any model
- BladeCenter HS23, type 7875, any model
- BladeCenter HS23E, type 8038, any model
- BladeCenter HS23E, type 8039, any model
- BladeCenter HX5, type 7872, any model
- BladeCenter HX5, type 7873, any model
- Flex System x220 Compute Node, type 7864, any model
- Flex System x220 Compute Node, type 7906, any model
- Flex System x240 Compute Node, Type 7863, any model
- Flex System x240 Compute Node, Type 8737, any model
- Flex System x240 Compute Node, Type 8738, any model
- Flex System x440 Compute Node, Type 2584, any model
- Flex System x440 Compute Node, Type 7917, any model
- IBM NeXtScale nx360 M4, any model 5455
- System x3500 M4, type 7383, any model
- System x3530 M4, type 7160, any model
- System x3550 M2, type 4198, any model
- System x3550 M2, type 7946, any model
- System x3550 M3, type 4254, any model
- System x3550 M3, type 7944, any model
- System x3550 M4, type 7914, any model
- System x3620 M3, type 7376, any model
- System x3630 M4, type 7158, any model
- System x3650 M2, type 4199, any model
- System x3650 M2, type 7947, any model
- System x3650 M3, type 4255, any model
- System x3650 M3, type 7945, any model
- System x3650 M4, type 7915, any model
- System x3650 M4 HD, Type 5460, any model
- System x3690 X5, type 7147, any model
- System x3690 X5, type 7148, any model
- System x3690 X5, type 7149, any model
- System x3690 X5, type 7192, any model
- System x3750 M4, type 8722, any model
- System x3750 M4, type 8733, any model
- System x3850 X5, type 7143, any model
- System x3850 X5, type 7145, any model
- System x3850 X5, type 7146, any model
- System x3850 X5, type 7191, any model
- System x3950 X5, type 7145, any model
- iDataPlex dx360 M2 server, type 6380, any model
- iDataPlex dx360 M2 server, type 7321, any model
- iDataPlex dx360 M2 server, type 7323, any model
- iDataPlex dx360 M3 server, type 6391, any model
- iDataPlex dx360 M4 server, type 7912, any model
This tip is not software specific.
This tip is not option specific.
The system has the symptom described above.
Best practices for resolution on UEFI machines: Note that Steps 1 through 3 solve most option ROM issues. Continue to Step 4 and the remaining steps as needed.
- Firmware updates can reduce ROM size requirements, so updating the firmware might be a solution. Ensure that all system and adapter firmware is at latest levels.
- Disable the Preboot eXecution Environment (PXE) ROM of on-board Network Interface Controllers (NICs).
The simplest solution to some PCI Option ROM space errors is to reduce the base system ROM requirements to the minimum amount necessary. Typically, this can be accomplished by disabling the PXE (Network start) ROM capability of the on-board Ethernet.
Note: These steps do not disable the device in the operating system, it disables only capability of the device to perform a network start.
- Select F1 setup System Settings -> Network -> PXE Configuration.
- Select the Media Access Control (MAC) address of the on-board NIC-1.
- Change the Enable PXE / PXE Mode setting to Disabled.
- Select Save Changes.
- Select the MAC address of the on-board NIC-2.
- Change the Enable PXE / PXE Mode setting to Disabled.
- Select Save Changes.
- Disable all Legacy Option ROMs for all devices that are not starting.
- Start the system and press F1 to enter the UEFI menu.
- Select System Settings -> Devices and I/O Ports -> Enable/Disable legacy ROM execution.
If the system is PXE or Storage Area Network (SAN) starting, do not disable the Legacy ROMs for adapters that actually are starting a Legacy (non-Extensible Firmware Interface (EFI)) operating system on the machine.
- Change the ROM order.
- Select F1 setup.
- Select System Settings -> Devices and I/O -> Set option ROM execution order.
Ensure that the on-board LSI storage controller is first in the list before the on-board Ethernet devices.
- Move Fibre Channel and Fibre Channel over Ethernet (FCoE) cards to a lower slot number as they tend to require more ROM space and should initialize first to reduce the chance of the issue occurring.
- Peripheral Component Interconnect Express (PCIe) adapters with PCI firmware spec 2.1 should be in lower slot numbers. PCIe adapters with PCI firmware spec 3.x do not need as much Option ROM space due to design changes.
- If the issue is still occurring and there are any Intel Network Interface Controllers (NICs) in the system, complete the following steps:
- Download the Intel v15.7 firmware and driver CD (or higher/newer version): MIGR-5087548.
See also RETAIN tip H202974 (MIGR-5087756) "UEFI SUPPORT FOR BOOT ROM FOR Intel BASED ETHERNET ADAPTERS".
- Create a CD from the ISO image.
- Find the DOS StartUtil utility in this folder:
| ||\APPS\StartUtil\DOS\StartUtil.exe |
- Find the UEFI StartUtil utility in this folder:
| ||\APPS\StartUtil\EFI64\BOOTUTIL64.EFI |
- Use the StartUtil with the following parameters:
For DOS systems:
For EFI systems (if offered by the server):
- Copy the StartUtil.exe onto a startable DOS floppy.
- Start the floppy to DOS and run this command:
c:\> StartUtil.exe -FLASHDISABLE -ALL
Note: Not all servers offer an EFI shell option (for example, IBM System x3690 X5, x3850 X5)
- Copy the BOOTUTIL64.EFI utility to a Universal Serial Bus (USB) Key.
- Start a Full EFI Shell environment, and then run the utility from the USB key with this command:
> BOOTUTIL64.EFI -FLASHDISABLE -ALL
For IBM BladeCenter HX5, type 7873, only:
The IBM BladeCenter HX5, type 7873 has a new setup option called Non-system board PXE under Legacy Support menu ('EnableNonPlanarPxe' in Advanced Settings Utility (ASU)).
If users do not need to use PXE start on NICs other than system board/on-board NICs, then this setting could be set to Disable to free up more space for option ROM and reduce the chances of this error. IBM BladeCenter HX5 7872 UEFI release 1.60, or later releases support this setup option.
This issue was discovered originally on Legacy (non-UEFI) machines and extensive documentation was provided to explain how to resolve the symptoms.
For more details, see the following .pdf file "IBM Support Info - Resolving 1801, 1802 Errors", which is referenced in RETAIN Tip H194252 (MIGR-5078445):
These errors are due to a permanent restriction of legacy PCI ROM space architecture.
Applicable countries and regions
Back to top
Document id: MIGR-5084743
Last modified: 2013-11-06
Copyright © 2013 IBM Corporation