Boot Firmware Memory Dump Selection for Multi-OS Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In computer systems supporting multiple operating systems, existing memory dump methods fail to select and boot the appropriate stand-alone dump program when a fault occurs, leading to inadequate memory dumps due to differing kernel data regions across OS versions and unsupported dump programs.
Innovation Solution
A method that defines and manages boot information for multiple stand-alone dump programs in non-volatile variables, using a table to specify the corresponding dump program based on the operating system, allowing automatic or manual selection of booting targets to support an optimum memory dump.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a stand-alone dump program is booted to perform memory dump, then memory dump capability is achieved, but the system cannot automatically select the appropriate dump program for different operating systems
Solution Approach 1:
The patent applies preliminary action by pre-registering multiple stand-alone dump programs in the boot firmware with their corresponding operating system information stored in advance. When a fault occurs, the boot firmware automatically retrieves the appropriate dump program based on the currently running OS without requiring manual selection or real-time decision-making, thus ensuring reliable memory dump capability across different operating systems.
Solution Approach 2:
The boot firmware acts as an intermediary between the operating system and the stand-alone dump programs. It stores mapping information between OS types and corresponding dump programs, and automatically selects and boots the appropriate dump program when a fault occurs, eliminating the need for manual intervention and ensuring compatibility across different OS environments.
2Adaptability or versatility
If multiple stand-alone dump programs are supported for different OS versions, then compatibility is improved, but the boot process complexity increases
Solution Approach 1:
The patent reduces boot process complexity by performing all selection logic in advance during firmware initialization. The boot firmware pre-stores mapping information between operating systems and their corresponding dump programs in non-volatile memory. When a fault occurs, the system simply retrieves the pre-determined dump program information based on the current OS, avoiding complex real-time decision-making and maintaining a simple boot process while supporting multiple OS versions.
3Ease of operation
If the dump program is embedded within the operating system, then the dump process is simplified, but the system cannot perform dumps when the OS is crashed or unresponsive
Solution Approach 1:
The patent extracts the memory dump functionality from the operating system and implements it as a separate stand-alone dump program that boots independently. This extracted dump program runs in a minimal environment with only essential drivers, allowing it to access and dump memory even when the original operating system is crashed or unresponsive, thereby improving reliability while maintaining operational simplicity through automated boot selection.
Data Source
AI summary
A memory dump program boot method includes the steps of defining, in non-volatile variables that are managed by a boot firmware of a computer system, boot information of a plurality of stand-alone dump programs that are installed in the computer system, and a table variable indicating a corresponding relationship of the plurality of stand-alone dump programs and a plurality of operating systems, specifying the boot information of a corresponding one of the plurality of stand-alone dump programs from the table variables when the boot firmware boots an arbitrary one of the plurality of operating systems, and writing information indicating the specified boot information in the non-volatile variables that are referred to when executing a stand-alone dump, and booting the corresponding one of the plurality of stand-alone dump programs when a booting of the stand-alone dump is instructed, by checking existence of variables that are referred to when executing the stand-alone dump and referring to information of the variables if the variables exist.