Abstract: Example method and apparatus, systems, and articles of manufacture for immersion cooling systems are disclosed herein. An example apparatus disclosed herein includes a tank to hold a coolant, an overflow chamber to direct the coolant toward an outlet, and a plate within the overflow chamber, the plate including a plurality of openings, the coolant to pass through at least one of the plurality of openings before reaching the outlet.

Abstract: A system and method of accessing basic input output system (BIOS) change summary information within a BIOS operating environment is disclosed. According to an aspect, a basic input output system (BIOS) set-up interface is disclosed. The BIOS set-up interface includes a navigation routine accessible via a BIOS set-up menu and operable to initiate displaying a secondary user display interface. The BIOS set-up interface further includes a BIOS change summary interface accessible using the secondary display user interface and configured to display BIOS set-up changes made using the BIOS set-up menu.

Abstract: Methods and systems are disclosed for using a server management program for an error configuration table, wherein a user loads the management program, which receives a Hardware Error Configuration Table (HECT) from baseboard management controller (BMC) firmware, the HECT table containing error control parameters for a hardware error event table. A replica of the HECT is maintained in SRAM using BMC firmware. The HECT is sent via the basic input output system (BIOS) during system power up. An interface is set up to allow the user to configure error event thresholds. The user can set preferred threshold of a system management requirement without rebooting system. If the user makes changes to the HECT, the management program sends the new HECT to BMC firmware to feedback the completion. A software SMI is issued to inform BIOS of HECT changes during the BMC completion. BIOS informs the operating system (OS) to discard and reload the new HECT.

Abstract: Methods and systems are disclosed for using a server management program for an error configuration table, wherein a user loads the management program, which receives a Hardware Error Configuration Table (HECT) from baseboard management controller (BMC) firmware, the HECT table containing error control parameters for a hardware error event table. A replica of the HECT is maintained in SRAM using BMC firmware. The HECT is sent via the basic input output system (BIOS) during system power up. An interface is set up to allow the user to configure error event thresholds. The user can set preferred threshold of a system management requirement without rebooting system. If the user makes changes to the HECT, the management program sends the new HECT to BMC firmware to feedback the completion. A software SMI is issued to inform BIOS of HECT changes during the BMC completion. BIOS informs the operating system (OS) to discard and reload the new HECT.

Abstract: A system and method of accessing basic input output system (BIOS) change summary information within a BIOS operating environment is disclosed. According to an aspect, a basic input output system (BIOS) set-up interface is disclosed. The BIOS set-up interface includes a navigation routine accessible via a BIOS set-up menu and operable to initiate displaying a secondary user display interface. The BIOS set-up interface further includes a BIOS change summary interface accessible using the secondary display user interface and configured to display BIOS set-up changes made using the BIOS set-up menu.

Abstract: Non-fatal errors at an information handling system link are managed by firmware of the information handling system. For example, a PCI Express link controller initiates an SMI interrupt upon detection of a non-fatal error associated with the PCI Express link. A non-fatal error monitor associated with an SMI handler in the BIOS of the information handling system receives the interrupt, determines the component of the information handling system associated with non-fatal error and issues an error message if the non-fatal error meets a predetermined condition, such as a predetermined number of errors associated with the component.