WO2017131776A1 - System state information monitoring - Google Patents

System state information monitoring Download PDF

Info

Publication number
WO2017131776A1
WO2017131776A1 PCT/US2016/015792 US2016015792W WO2017131776A1 WO 2017131776 A1 WO2017131776 A1 WO 2017131776A1 US 2016015792 W US2016015792 W US 2016015792W WO 2017131776 A1 WO2017131776 A1 WO 2017131776A1
Authority
WO
WIPO (PCT)
Prior art keywords
state information
system state
monitoring
processor
band
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2016/015792
Other languages
French (fr)
Inventor
Thomas L. VADEN
Micah PARRISH
Andrew Brown
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett Packard Enterprise Development LP
Original Assignee
Hewlett Packard Enterprise Development LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hewlett Packard Enterprise Development LP filed Critical Hewlett Packard Enterprise Development LP
Priority to US15/777,002 priority Critical patent/US20180336086A1/en
Priority to EP16888504.4A priority patent/EP3362903A4/en
Priority to PCT/US2016/015792 priority patent/WO2017131776A1/en
Publication of WO2017131776A1 publication Critical patent/WO2017131776A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0751—Error or fault detection not based on redundancy
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3055—Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3089—Monitoring arrangements determined by the means or processing involved in sensing the monitored data, e.g. interfaces, connectors, sensors, probes, agents
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/865—Monitoring of software

Definitions

  • the out-of-band monitoring engine 106 can determine system state information before an operating system is operational and/or after the operating system is initialized.
  • the out-of-band monitoring engine 106 can utilize SAWBASE hardware and the operating system memory topology to extract the system state information
  • the dump engine 108 can provide the system state information for analysis in response to a failure of the operating system.
  • the failure of the operating system can be during start-up of the operation system and/or a catastrophic failure after the operating system has initialized.
  • the dump engine 108 can provide the system state information to an out-of-band monitoring device or another computing device for analysis.
  • the dump engine 106 can output (e.g., send via a network) the system state information to a computing device for analysis.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

In one example, a system includes an out-of-band monitoring engine to determine system state information by monitoring a system state of the system and a dump engine to provide the system state information to a computing device for analysis. The out-of-band monitoring engine can determine system state information in response to a failure of an operating system during start-up, determine system state information in response to a catastrophic error occurring to an operating system, and determine system state information of a functioning operating system

Description

SYSTEM STATE INFORMATION MONITORING
Background
[0001] Operating systems can be monitored using an in-band monitoring system to determine system state information. The in-band monitoring system uses
applications that are operating on the system that is being monitored to obtain system state information. When an operating system fails, the system state information may not be available when using an in-band monitoring system. When the system state information is not available, a dump may not be performed. Therefore, the cause of the failure will not be known and other problems with the computing system may occur due to the system state information being unavailable.
Brief Description of the Drawings
[0002] Figure 1 illustrates a diagram of an example system for system state information monitoring consistent with the present disclosure.
[0003] Figure 2 illustrates a diagram of an example computing device for system state information monitoring consistent with the present disclosure.
[0004] Figure 3 illustrates a diagram of an example system for system state information monitoring consistent with the present disclosure.
[0005] Figure 4 illustrates a flow chart of an example method for system state information monitoring consistent with the present disclosure. Detailed Description
[0006] A set of examples for system state monitoring are described herein. In one example, a system includes an out-of-band monitoring engine to determine system state information by monitoring a system state of the system and a dump engine to provide the system state information for analysis.
[0007] in some examples, a dump of system state information can be enabled by monitoring the system state information using an out-of-band monitoring engine (e.g., out-of-band embedded controller). An application running on the out-of-band monitoring engine can monitor and extract system state information of the system to dump the system state information. The system state information can be monitored and extracted during start-up of an operation system and/or while the operating system is initialized and functional. The system state information that is extracted by the out-of-band monitoring engine can be beneficial when there is not an operative in-band crash dump. There may not be an operative in-band crash dump available if the operating system crashes during early stages of start-up. An in-band crash dump may not be available when a catastrophic error occurs, A catastrophic error can include an error where the system state information may not be available as a result of the error. A catastrophic error can occur after the operating system has begun to boot, but before the operating system as initialized enough the capture system state information and/or after the operating system has initialized. Also, the monitoring the system state information can be beneficial while the operating system is initialized and functional to provide verification and analysis of the system state information for a functional operation system.
[0008] The examples of system state monitoring described herein can monitor and extract system state information using an out-of-band monitoring engine. An out-of- band monitoring engine can include system access window base address (SAWBASE) hardware, for example. SAWBASE hardware can extract system state information from a computing device. In some examples, an operating system memory topology can be exported to the out-of-band monitoring engine and then be used by the SAWBASE hardware to extract system state information. Also, an application running on a computing device external to the out-of-band monitoring engine can connect with the out~of-band monitoring engine to use the SAWBASE hardware to monitor and extract the system state information.
[0009] The figures herein follow a numbering convention in which the first digit corresponds to the drawing figure number and the remaining digits identify an element or component in the drawing. Elements shown in the various figures herein may be capable of being added, exchanged, and/or eliminated so as to provide a set of additional examples of the present disclosure. In addition, the proportion and the relative scale of the elements provided in the figures are intended to illustrate the examples of the present disclosure, and should not be taken in a limiting sense.
[0010] Figures 1 and 2 respectively illustrate an example system 100 and an example computing device 214 consistent with the present disclosure. Figure 1 illustrates a diagram of an example system 100 for system state information monitoring consistent with the present disclosure. The system 100 can include a database 104, a system state information monitoring system 102, or a set of engines (e.g., out-of-band engine 106 and dump engine 108). The system state information monitoring system 102 can be in communication with the database 104 via a communication link, and can include the set of engines (e.g., out-of-band monitoring engine 106 and dump engine 108). The system state information monitoring system 102 can include additional or fewer engines than are illustrated to perform the various functions as will be described in further detail in connection with Figures 3-4.
[0011] The set of engines (e.g., out-of-band engine 106 and dump engine 108) can include a combination of hardware and programming, but at least hardware, that can perform functions described herein (e.g., determine system state information and provide the system state information to a computing device, etc.) stored in a memory resource (e.g., computer readable medium, machine readable medium, etc.) as well as hard-wired program (e.g., logic).
[0012] The out-of-band monitoring engine 106 and dump engine 108 can include hardware or a combination of hardware and programming, but at least hardware, to monitoring system state information. In some examples, out-of-band monitoring engine 06 can determine system state information of a system and dump engine 108 can provide the system state information to a memory device for analysis.
[0013] in some examples, the out-of-band monitoring engine 106 can determine system state information before an operating system is operational and/or after the operating system is initialized. For example, the out-of-band monitoring engine 106 can utilize SAWBASE hardware and the operating system memory topology to extract the system state information, in some examples, the dump engine 108 can provide the system state information for analysis in response to a failure of the operating system. The failure of the operating system can be during start-up of the operation system and/or a catastrophic failure after the operating system has initialized. The dump engine 108 can provide the system state information to an out-of-band monitoring device or another computing device for analysis. The dump engine 106 can output (e.g., send via a network) the system state information to a computing device for analysis. The system state information can include a copy of a computing device's memory when the operating system failed and/or include copy of the computing device's memory when the operating is functional. An out-of-band monitoring device and/or another computing device can analyze the system state information to diagnose and cure the problem that caused the operation system to fail and/or to provide analysis of a functioning operating system.
[0014] Figure 2 illustrates a diagram of an example computing device 214 consistent with the present disclosure. The computing device 214 can utilize software, hardware, firmware, or logic to perform functions described herein.
[0015] The computing device 214 can be any combination of hardware and program instructions configured to share information. The hardware, for example, can include a processing resource 216 or a memory resource 220 (e.g., computer-readable medium (CRM), machine readable medium (MRM), database, etc.). A processing resource 216, as used herein, can include any set of processors capable of executing instructions stored by a memory resource 220. Processing resource 216 may be implemented in a single device or distributed across multiple devices. The program instructions (e.g., computer readable instructions (CRI)) can include instructions stored on the memory resource 220 and executable by the processing resource 216 to implement a function (e.g., determine system state information and provide the system state information to a computing device for analysis, etc.).
[0016] The memory resource 220 can be in communication with a processing resource 2 8. A memory resource 220, as used herein, can include any set of memory components capable of storing instructions that can be executed by processing resource 216. Such memory resource 220 can be a non-transitory CRM or MRM.
Memory resource 220 may be integrated in a single device or distributed across muitipie devices. Further, memory resource 220 may be fully or partially integrated in the same device as processing resource 216 or it may be separate but accessible to that device and processing resource 216. Thus, if is noted that the computing device 214 may be implemented on a participant device, on a server device, on a collection of server devices, or a combination of the participant device and the server device.
[0017] The memory resource 220 can be in communication with the processing resource 216 via a communication link (e.g., a path) 218. The communication link 218 can be local or remote to a machine (e.g., a computing device) associated with the processing resource 218. Examples of a communication link 218 can include an electronic bus internal to a machine (e.g., a computing device) where the memory resource 220 is one of volatile, non-volatile, fixed, or removable storage medium in communication with the processing resource 216 via the electronic bus.
[0018] A set of modules (e.g., ouf-of-band monitoring module 222 and dump module 224) can include CRI that when executed by the processing resource 216 can perform functions. The set of modules (e.g., ouf-of-band monitoring module 222 and dump module 224) can be sub-modules of other modules. For example, the ouf-of- band monitoring module 222, dump module 224 and/or another module can be sub- modules or contained within the same computing device. In another example, the set of modules (e.g., out-of-band monitoring module 222 and dump module 224) can comprise individual modules at separate and distinct locations (e.g., CRM, etc.).
[0019] As used herein, a set of modules (e.g., out-of-band monitoring module 222 and dump module 224) can include instructions that when executed by the processing resource 216 can function as a corresponding engine as described herein. For example, the out-of-band monitoring module 222 can include instructions that when executed by the processing resource 216 can function as the out-of-band monitoring engine 106.
[0020] Figure 3 illustrates a diagram of an example system 330 for system state information monitoring consistent with the present disclosure. In some examples, the system 330 can represent a computing system where a set of computing devices 332, 334 are communicating with an out-of-band monitoring device 336. in some examples, the number of computing devices 332, 334 can be a participant device, a server device, or a collection of server devices, or a combination of the participant device and the server device. The computing device 332 can be monitored by the out-of-band monitoring device 336 to determine system state information for the computing device. The system state information can include a copy of the computing device's memory, which can include system status data and/or host data. The system state information can also include CPU registers, vendor MSR, PCI configuration space, and/or PCI registers, among other information. The system state information can also include a copy of the crash dump crash kernel for computing device 332.
[0021] The computing device 332 can be monitored by the out-of-band monitoring device 336 during start-up of the operation system of the computing device 332 and/or after the operating system of the computing device 332 has initialized and is functional. The system state information can be obtained during and/or after a successful start-up of the operation system or during a failed start-up of the operation system. In the case of a failure of the operating system during start-up the system state information that is obtained by the out-of-band monitoring device 336 can be used to crash dump that computing device's memory. The system state information obtained by the out-of-band monitoring device 336 can be useful when there is not an operative in- band crash dump. There may not be an operative in-band crash dump available if the operating system crashes during early stages of start-up. An in-band crash dump may not be available when a catastrophic error happens after the operating system has begun to boot, but before the operating system has initialized enough the capture system state information. For example, unified extensible firmware interface (UEFi) systems are susceptible to not having an in-band crash dump available because they have a separate boot services environment that is unavailable when the operating system initialization leaves the booting phase to execute the early phases of construction of the running operating system environment. Also, a running operating system that has fully initialized could become incapacitated to the point of not being able to successfully accomplish an in-band crash dump when a catastrophic error occurs.
[0022] in some examples, out-of-band monitoring device 336 can include access window base address (SAWBASE) hardware 338. SAWBASE hardware 338 can be used to extract system state information from computing device 332. In some examples, an operating system memory topology can be exported to the out-of-band monitoring device 336 and then used by the SAWBASE hardware 338 to extract system state information from computing device 332.
[0023] in some examples, computing device 334 can be coupled via a network to the out-of-band monitoring device 336. The computing device 334 can run an application that connects with the out-of-band monitoring engine to use the SAWBASE hardware to monitor and extract the system state information from computing device 332. The system state information can then be stored on computing device 334.
[0024] The system state information extracted by the out-of-band monitoring device 336 can be analyzed by the out-of-band monitoring device 336 and/or another computing device, such as computing device 334. The system state information can be analyzed in real time (e.g., as the operating system is crashing) or can be stored in the out-of-band monitoring device 336 and/or another computing device, such as computing device 334, for analysis at a later time. The system state information can be analyzed in real time to determine a cause of a failure and provide a solution for the failure so the operating system can properly start-up.
[0025] Figure 4 illustrates a flow chart of an example method 470 for system state information monitoring consistent with the present disclosure. The method 470 can be executed by a system and/or computing device as described herein. In some examples, the method 470 can be executed by a computing device (e.g., computer, controller, microcontroller, etc.) that monitoring system state information of another computing device. In some examples, the computing device that is monitoring the system state information can execute an application on the computing to monitor the system state information.
[0026] At 472, the method 470 can include monitoring system state information of an operating system using an out-of-band monitoring engine. In some examples, the method 470 can include monitoring instruction pointers and registers to obtain system status data and/or host memory data.
[0027] At 474, the method 470 can include providing the system state information to the out-of-band monitoring engine for analysis of the system memory state in response to a failure of the operating system. Also, the method 470 includes analyzing the system state information during the operating system start-up and/or after the operating system has initialized.
[0028] As used herein, "logic" is an alternative or additional processing resource to perform a particular action or function, etc., described herein, which includes hardware, e.g., various forms of transistor logic, application specific integrated circuits (ASICs), etc., as opposed to computer executable instructions, e.g., software firmware, etc., stored in memory and executable by a processor. Further, as used herein, "a" or "a set of something can refer to one or more such things. For example, "a set of widgets" can refer to one or more widgets.
[0029] The above specification, examples and data provide a description of the method and applications, and use of the system and method of the present disclosure. Since many examples can be made without departing from the spirit and scope of the system and method of the present disclosure, this specification merely sets forth some of the many possible example configurations and implementations.

Claims

Claims What is claimed:
1. A system, comprising:
an out-of-band monitoring engine to determine system state information by monitoring a system state of the system; and
a dump engine to provide the system state information to a computing device for analysis.
2. The system of claim 1 , wherein the out-of-band monitoring engine is to determine the system state information in response to a failure of an operating system during startup,
3. The system of claim 1 , wherein the out-of-band monitoring engine is to determine the system state information in response to a catastrophic error occurring to an operating system.
4. The system of claim 1 , wherein the out-of-band monitoring engine is to determine the system state information of a functioning operating system.
5. The system of claim 1 , wherein the system state information includes system status data and host memory data.
6. A method, comprising:
monitoring a system state of a system using an out-of-band monitoring engine to determine system state information; and
providing the system state information to the out-of-band monitoring engine for analysis of the system state in response to a failure of the operating system.
7. The method of claim 6, wherein monitoring the system state information includes monitoring instruction pointers and registers to obtain system state information.
8. The method of claim 6, wherein monitoring the system state information includes monitoring system state information to obtain host memory data,
9. The method of claim 6, wherein providing the system state information includes storing the system state information for analysis at a later time.
10. The method of claim 6, wherein monitoring system state information includes using system access window base address (SAWBASE) hardware to access the system state information.
1 1. A non-transitory machine-readable medium comprising instructions executable by a processor to cause the processor to:
determine system state information of a system using an out-of-band monitoring engine; and
output the system state information for analysis of the system.
12. The non-transitory machine-readable medium of claim 1 1 , wherein the instructions executable by the processor to cause the processor to determine the system state information that includes a crash dump crash kernel.
13. The non-transitory machine-readable medium of claim 1 1 , wherein the instructions executable by the processor to cause the processor to determine the system state information during a successful start-up of the operating system.
14. The non-transitory machine-readable medium of claim 1 1 , wherein the instructions executable by the processor to cause the processor to determine the system state information are from an application external to the out-of-band monitoring engine.
15. The non-transitory machine-readable medium of claim 1 , wherein the instructions executable by the processor to cause the processor to determine the system state information are from an application running on the out-of-band monitoring engine.
PCT/US2016/015792 2016-01-29 2016-01-29 System state information monitoring Ceased WO2017131776A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US15/777,002 US20180336086A1 (en) 2016-01-29 2016-01-29 System state information monitoring
EP16888504.4A EP3362903A4 (en) 2016-01-29 2016-01-29 System state information monitoring
PCT/US2016/015792 WO2017131776A1 (en) 2016-01-29 2016-01-29 System state information monitoring

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/015792 WO2017131776A1 (en) 2016-01-29 2016-01-29 System state information monitoring

Publications (1)

Publication Number Publication Date
WO2017131776A1 true WO2017131776A1 (en) 2017-08-03

Family

ID=59398728

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/015792 Ceased WO2017131776A1 (en) 2016-01-29 2016-01-29 System state information monitoring

Country Status (3)

Country Link
US (1) US20180336086A1 (en)
EP (1) EP3362903A4 (en)
WO (1) WO2017131776A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10817378B2 (en) * 2018-07-24 2020-10-27 Dell Products, L.P. Managing boot failures in an information handling system
US11531578B1 (en) * 2018-12-11 2022-12-20 Amazon Technologies, Inc. Profiling and debugging for remote neural network execution
US12242609B2 (en) * 2022-03-29 2025-03-04 Acronis International Gmbh Exact restoration of a computing system to the state prior to infection
US12204424B2 (en) * 2022-09-08 2025-01-21 Dell Products L.P. Privacy and security assurance during operating system crash events

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267918A1 (en) 2003-06-30 2004-12-30 Guarraci Brian J Managing headless computer systems
US20080256533A1 (en) * 2007-04-10 2008-10-16 Shmuel Ben-Yehuda System, method and computer program product for evaluating a virtual machine
US20090083737A1 (en) * 2007-09-24 2009-03-26 Shmuel Ben-Yehuda Device, System, and Method of Classifying a Workload of a Software Service
US20130212267A1 (en) * 2009-08-25 2013-08-15 International Business Machines Corporation Dynamically Balancing Resources In A Server Farm
US20140095815A1 (en) * 2008-02-01 2014-04-03 Kip Cr P1 Lp Media library monitoring system and method
US20150121152A1 (en) 2013-10-31 2015-04-30 International Business Machines Corporation System monitoring and debugging in a multi-core processor system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7308609B2 (en) * 2004-04-08 2007-12-11 International Business Machines Corporation Method, data processing system, and computer program product for collecting first failure data capture information
US7281163B2 (en) * 2004-06-22 2007-10-09 Hewlett-Packard Development Company, L.P. Management device configured to perform a data dump
JP4700562B2 (en) * 2006-05-18 2011-06-15 株式会社バッファロー Data storage device and data storage method
WO2014000253A1 (en) * 2012-06-29 2014-01-03 Intel Corporation Methods, systems and apparatus to capture error conditions in lightweight virtual machine managers

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267918A1 (en) 2003-06-30 2004-12-30 Guarraci Brian J Managing headless computer systems
US20080256533A1 (en) * 2007-04-10 2008-10-16 Shmuel Ben-Yehuda System, method and computer program product for evaluating a virtual machine
US20090083737A1 (en) * 2007-09-24 2009-03-26 Shmuel Ben-Yehuda Device, System, and Method of Classifying a Workload of a Software Service
US20140095815A1 (en) * 2008-02-01 2014-04-03 Kip Cr P1 Lp Media library monitoring system and method
US20130212267A1 (en) * 2009-08-25 2013-08-15 International Business Machines Corporation Dynamically Balancing Resources In A Server Farm
US20150121152A1 (en) 2013-10-31 2015-04-30 International Business Machines Corporation System monitoring and debugging in a multi-core processor system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3362903A4

Also Published As

Publication number Publication date
EP3362903A1 (en) 2018-08-22
EP3362903A4 (en) 2019-06-05
US20180336086A1 (en) 2018-11-22

Similar Documents

Publication Publication Date Title
US8260841B1 (en) Executing an out-of-band agent in an in-band process of a host system
CN105843741B (en) Information processing method and device for application program
US11030047B2 (en) Information handling system and method to restore system firmware to a selected restore point
US8438423B1 (en) Invalid setup recovery
US10831467B2 (en) Techniques of updating host device firmware via service processor
CN110162435B (en) A server PXE boot test method, system, terminal and storage medium
US10089474B2 (en) Virtual machine introspection
US9836386B2 (en) Automatic switch to debugging mode
US11544148B2 (en) Preserving error context during a reboot of a computing device
EP3218818B1 (en) Dual purpose boot registers
US12393486B2 (en) Automatic BMC and bios firmware recovery
US10691468B2 (en) Techniques of retrieving bios data from BMC
US20180336086A1 (en) System state information monitoring
US7900033B2 (en) Firmware processing for operating system panic data
US7984282B2 (en) Evasion of power on self test during an operating system initiated reboot
US10642646B1 (en) Techniques of securely performing logic as service in BMC
US10474517B2 (en) Techniques of storing operational states of processes at particular memory locations of an embedded-system device
US20200134184A1 (en) Auto detection mechanism of vulnerabilities for security updates
US20240241779A1 (en) Signaling host kernel crashes to dpu
US12566670B2 (en) Supporting automatic and failsafe booting of BMC and bios firmware in a critical secured server system
US20200242014A1 (en) Automatic framework to create qa test pass
US10176142B2 (en) Techniques of accessing BMC terminals through serial port
CN113645056A (en) A method and system for locating the fault of an intelligent network card
US20240241728A1 (en) Host and dpu coordination for dpu maintenance events
US20240211602A1 (en) Bmc based hrot implementation establishing chain of trust in a secured server system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16888504

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15777002

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE