Abstract: An embedded controller (EC) of an information handling system is configured to detect and respond to anomalous conditions in which a pre-boot or runtime error has occurred and EC-local storage resources are not sufficient to store EC telemetry data, by redirecting the EC telemetry data through an available communication channel, e.g., SBIOS MBOX packets or ACPI MMIO, to offload the data to EC-external storage such as an ESP partition or Cloud storage. In a pre-boot mode, SBIOS may invoke a UEFI storage driver to write out EC log data to EC-external storage, e.g., SSD/NVMe device or the Cloud. In a runtime mode, the EC may be flagged by an OS bugcheck handler, e.g., via eSPI MMIO path, to save the log data. In an OS-context mode, ACPI methods may notify a persistent driver, e.g., Common Platform Services (CPS) driver, to write out the log to the EC-external storage.

Abstract: If a critical event occurs during a boot process, an information handling system may analyze firmware associated with the critical event to determine whether the firmware is unified extensible firmware interface compliant. In response to determining that the firmware is not unified extensible firmware interface compliant, the system may retrieve a rule associated with the firmware, and apply one or more actions to the information handling system based on the rule.

Abstract: A data processing system comprising a processor having a working memory and processing logic, a boot system configured to load one or more algorithms for initializing a basic input output system (BIOS) of the processor into the working memory and an error correction system configured to start a watchdog timer and to monitor initialization of the processor, the error correction system further configured to implement a corrective process if the watchdog timer times out prior to initialization of the BIOS of the processor.

Abstract: Systems and methods for providing a seamless and secure motherboard replacement system and method are described. In some embodiments, an Information Handling System (IHS) may include a processor and a memory coupled to the processor, the memory having program instructions that, upon execution, cause the IHS to when a previous motherboard is replaced with a replacement motherboard; detect that the previous motherboard has been replaced with the replacement motherboard, access context data associated with the previous motherboard from a storage unit configured in the IHS, the context data comprising configuration settings of the previous motherboard, and update the replacement motherboard according to the stored context information.

Abstract: An embedded controller locks down one or more devices within an information handling system based on a detection of an operating system crash. A processor monitors an operating system executing within the information handling system, and detects the operating system crash. In response to the detection of the operating system crash, the processor notifies the embedded controller of the operating system crash.

Abstract: An information handling system may include a processor, a display device communicatively coupled to the processor, and a basic input/output system (BIOS) communicatively coupled to the processor and configured to cause the processor to, during a pre-boot environment of the information handling system, collect contextual information regarding the information handling system, based on the contextual information, determine whether to enable soft keyboard functionality, and responsive to a determination to enable soft keyboard functionality, cause display of soft keyboard functionality to the display device.

Abstract: Methods, systems, and devices for transitioning an information handling system (IHS) to a predetermined operating state is disclosed. During the transition, the IHS may obtain data from a variety of sources which may subject it to compromise. To reduce the likelihood that the IHS is compromised, the IHS may evaluate its environment and its own operation to determine its security state. Depending on its security state, the IHS may perform various actions to reduce the likelihood of it being compromised through its transition process.

Abstract: A basic input output system (BIOS) of an information handling system may access a first list indicating one or more activation statuses of one or more BIOS firmware modules. The BIOS may determine a BIOS firmware module of the one or more BIOS firmware modules to load based, at least in part, on the first list. The BIOS may load the determined BIOS firmware module during booting of the information handling system.

Abstract: An information handling system downloads device drivers for recovery operation of the information handling system, and subsequently obtains first configuration information associated with each of the device drivers. The system performs an inventory of devices associated with the information handling system that includes obtaining second configuration information associated with each of the devices in the inventory, and compares the first configuration information and the second configuration information. If the particular device driver is missing, then the system downloads the particular device driver prior to boot to a service operating system.

Abstract: An information handling system includes an embedded controller and a memory device storing code that when executed causes the embedded controller to perform operations that includes receiving a request to change a security setting, determining a security policy associated with the security setting, and determining whether the change to the security setting deviates from the security policy. In addition, the embedded controller in response to determining that the change to the security setting deviates from the security policy, denying the request and reverting the change to the security setting.

Abstract: An information handling system includes a memory that stores context data associated with a crash of the information handling system. A BIOS determines whether a crash of the information handling system occurred during a most recent operating system runtime of the information handling system. In response to the determination of the crash during the most recent operating system runtime, the embedded controller reads the context data associated with the crash of the information handling system. An embedded controller verifies a golden BIOS image for the information handling system, and sets an indication for an operating system of the information handling system to revert to original setting for a healthy boot.

Abstract: An information handling system may determine a pre-boot security posture, and update an advanced configuration and power interface mitigation table with the pre-boot security posture. The system may also update a security mitigation table based on a security mitigation policy, and determine a security mitigation based on a protection flag in the advanced configuration and power interface mitigation table and the security mitigation table.

Abstract: Methods and systems for managing communications is disclosed. A host device and a management controller may communicate via memory mapped communications using shared memory. To improve the security of the memory mapped communications, access requests for shared memory may be monitored. Access controls for the shared memory may be put in place to reduce the likelihood of data being made unavailable before it is processed. The access controls may be lifted when the data stored in shared memory has been read by to complete the memory mapped communications.

Abstract: An information handling system may include at least one processor, a physical storage resource, and a non-volatile memory other than the physical storage resource. The at least one processor may be configured to execute instructions for: storing learned profile data at the physical storage resource; in response to detection of a catastrophic event, copying the learned profile data from the physical storage resource to the non-volatile memory; and subsequent to a remediation event for the catastrophic event, restoring the learned profile data from the non-volatile memory.

Abstract: A method may include during a Pre-Extensible Firmware Interface Initialization phase of a BIOS, receiving a mailbox command from a management controller of an information handling system, the mailbox command including information regarding a driver image stored in computer-readable media associated with the BIOS, the information including uniquely-identifying information for the driver image. The method may also include, during a Driver Execution Environment phase of the BIOS, locating the driver image stored in the computer-readable media, verifying the driver image based on the information from the mailbox command, extracting the driver image from the computer-readable media in response to verifying the driver image, and causing a driver stored within the driver image to load and execute during BIOS execution.

Abstract: An information handling system may include at least one processor, a Basic Input/Output System (BIOS), a physical information handling resource, and a computer-readable medium having instructions thereon that are executable by the at least one processor for: executing an operating system (OS) that includes a BIOS Data Advanced Configuration and Power Interface (ACPI) Table (BDAT) driver; executing at least one virtual machine (VM) that includes a virtual BDAT driver; detecting an event notification generated by the physical information handling resource; and transmitting, to the VM, information regarding the event notification via the BDAT driver and the virtual BDAT driver.

Abstract: A method may include during a Pre-Extensible Firmware Interface Initialization phase of a BIOS, receiving a mailbox command from a management controller of an information handling system, the mailbox command including information regarding a driver image stored in computer-readable media associated with the BIOS, the information including uniquely-identifying information for the driver image. The method may also include, during a Driver Execution Environment phase of the BIOS, locating the driver image stored in the computer-readable media, verifying the driver image based on the information from the mailbox command, extracting the driver image from the computer-readable media in response to verifying the driver image, and causing a driver stored within the driver image to load and execute during BIOS execution.

Abstract: In one embodiment, a method for providing a verbalized diagnostic message to a user of an information handling system includes: determining, by an embedded controller, an error associated with the information handling system; accessing, by the embedded controller, a memory device of the information handling system, the memory device storing a plurality of diagnostic files; selecting, by the embedded controller, a diagnostic file from the plurality of diagnostic files, the diagnostic file indicating the error associated with the information handling system; generating, by the embedded controller, the verbalized diagnostic message; sending, by the embedded controller, the verbalized diagnostic message to an audio device of the information handling system in an embedded controller audio stream; and presenting, by the audio device, the verbalized diagnostic message to the user via one or more speakers of the information handling system.

Abstract: An information handling system may include a physical storage resource having a portion thereof that includes files that are usable during boot of the information handling system; at least one processor; and a Basic Input/Output System (BIOS) including instructions that are executable by the at least one processor for: during a boot process, determining whether any of a plurality of BIOS events have taken place during a previous boot process, wherein the plurality of BIOS events are indicative of malicious behavior during the previous boot process; and in response to a determination that at least a predetermined number of the plurality of BIOS events have taken place during the previous boot process, carrying out a remedial action during the boot process.

Abstract: Methods and systems for managing the operation of data processing systems are disclosed. A data processing system may include a computing device that may enter various operating states by performing various types of startups. Performance the startups may require access to various portions of data which may become unavailable and thereby prevent startup completion. The data processing systems may host a management controller that may facilitating performing a specialized startup process through which unavailable data may be retrieved from other devices via intermediary devices, and may reduce risk in connecting to other devices through verification, validation, and/or other processes.