UEFI Boot Path Driver Override for Single-Boot Fault Remediation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing firmware update processes in information handling systems often require time-consuming and device-specific operations, such as erasing and writing to nonvolatile memory, which can be inconvenient for end users and lead to inefficiencies.
Innovation Solution
A firmware update override procedure that boots a platform operating system after detecting a faulty driver during preboot, loading a remediation driver from an update payload without performing NVM erase and write operations, and dynamically updating the driver dispatch list to remediate the fault without a full firmware update.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional firmware update processes are performed to fix faulty drivers, then system reliability is improved, but update time and complexity increase due to NVM erase and write operations
Solution Approach 1:
The patent segments the firmware update process into two distinct paths: a conventional path that performs full NVM erase and write operations, and a new expedited path that loads remediation drivers directly from an update payload in memory. This segmentation allows the system to choose the appropriate path based on the situation, using the expedited path for driver faults to avoid time-consuming memory operations while preserving the conventional path for other firmware update scenarios.
Solution Approach 2:
The patent implements preliminary action by pre-loading remediation drivers into an update payload in memory before a fault occurs. When a driver fault is detected during preboot, the system can immediately load the remediation driver from this pre-prepared payload without needing to perform erase and write operations to NVM, thus significantly reducing update time while ensuring system reliability.
2Reliability
If conventional firmware update processes are performed to remediate faulty drivers, then system reliability is improved, but device wear increases due to repeated NVM erase and write operations
Solution Approach 1:
The patent segments the firmware update process into two distinct paths: a conventional path that performs full NVM erase and write operations, and a new expedited path that loads remediation drivers directly from an update payload in memory. This segmentation allows the system to choose the appropriate path based on the situation, using the expedited path for driver faults to avoid time-consuming memory operations while preserving the conventional path for other firmware update scenarios.
Solution Approach 2:
The patent uses copying by creating a copy of the remediation driver in an update payload stored in volatile memory. Instead of writing to NVM, the system copies the remediation driver from the payload into the active driver dispatch list in memory, allowing the system to remediate driver faults without subjecting NVM to wear-inducing erase and write operations.
3Reliability
If multiple reboots are performed to apply firmware updates, then system reliability is improved, but productivity decreases due to system downtime
Solution Approach 1:
The patent implements preliminary action by pre-loading remediation drivers into an update payload in memory before a fault occurs. When a driver fault is detected during preboot, the system can immediately load the remediation driver from this pre-prepared payload without needing to perform erase and write operations to NVM, thus significantly reducing update time while ensuring system reliability.
Solution Approach 2:
The patent applies skipping by allowing the system to skip the time-consuming NVM erase and write operations when a driver fault is detected. Instead of following the conventional firmware update path, the system rushes through the remediation process by directly loading the remediation driver from the update payload in memory, thereby maintaining system availability and productivity.
4Adaptability or versatility
If firmware updates are performed frequently to fix bugs and add features, then system functionality is improved, but user convenience deteriorates due to time-consuming update processes
Solution Approach 1:
The patent segments the firmware update process into two distinct paths: a conventional path that performs full NVM erase and write operations, and a new expedited path that loads remediation drivers directly from an update payload in memory. This segmentation allows the system to choose the appropriate path based on the situation, using the expedited path for driver faults to avoid time-consuming memory operations while preserving the conventional path for other firmware update scenarios.
Solution Approach 2:
The patent uses copying by creating a copy of the remediation driver in an update payload stored in volatile memory. Instead of writing to NVM, the system copies the remediation driver from the payload into the active driver dispatch list in memory, allowing the system to remediate driver faults without subjecting NVM to wear-inducing erase and write operations.
Data Source
AI summary
A disclosed method monitors boot path driver events to identify faulty boot path drivers in a UEFI-compliant boot path. Upon identifying a faulty boot path driver, the faulty driver is isolated and a corresponding remediation driver is fetched. An override driver dispatch list is created by modifying an original driver dispatch list to replace the faulty driver with the remediation driver, wherein the remediation driver occupies the same place in the execution order of the override driver dispatch list as the faulty driver occupies in the original driver dispatch list. Following a warm reset, a boot path load is performed in accordance with the override driver dispatch list, thereby remediating the boot path without performing a firmware update on a serial peripheral interface (SPI) flash device or the like. In this manner, a faulty driver is detected, isolated, and remediated in a single boot path.