WO2018036318A1 - Procédé et dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation - Google Patents

Procédé et dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation Download PDF

Info

Publication number
WO2018036318A1
WO2018036318A1 PCT/CN2017/093792 CN2017093792W WO2018036318A1 WO 2018036318 A1 WO2018036318 A1 WO 2018036318A1 CN 2017093792 W CN2017093792 W CN 2017093792W WO 2018036318 A1 WO2018036318 A1 WO 2018036318A1
Authority
WO
WIPO (PCT)
Prior art keywords
operating system
information
kernel
abnormal
memory
Prior art date
Application number
PCT/CN2017/093792
Other languages
English (en)
Chinese (zh)
Inventor
蒋彪
谈虎
王亮
蒋勇
蔡衢
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018036318A1 publication Critical patent/WO2018036318A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR 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; CALCULATING OR 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

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and apparatus for collecting abnormal information during an operating system startup phase.
  • system logs In the operating system, common exception information collection mechanisms include: system logs, crash dumps, screen printing, etc., but these mechanisms are difficult to play a practical role in the system startup phase.
  • system log In the normal operating system, the system log is started in the system service mode, and in the initial stage of system startup, the corresponding service may not be started yet, even at the beginning of the system startup, used to store the log. The hardware device (or driver) may not be ready, and the system log will not take effect.
  • the known system crash dump mechanism in the operating system depends on the user-mode service for the collection of dump files. Compression, etc., but during the system startup phase, these services are often not ready yet, and they will not work properly.
  • the embodiment of the invention provides a method and a device for collecting abnormal information during the startup phase of the operating system, so as to solve the problem that the abnormal information collection mechanism cannot be effectively collected in the system startup phase in the prior art.
  • the problem of detailed exception information is a problem of detailed exception information.
  • An embodiment of the present invention provides a method for collecting abnormal information during an operating system startup phase, where the method includes:
  • the second memory other than the first memory in the physical memory is used for operating system startup;
  • the exception information is collected by the custom kernel when an operating system abnormal state is detected.
  • the method further includes: during the process of installing the operating system before the operating system is started, the method further includes:
  • the step of loading the custom kernel from the predetermined storage location to the first memory includes:
  • the read custom kernel is loaded into the first memory for storage.
  • the operating system abnormal state includes the operating system kernel being in an abnormal state; and correspondingly, when the operating system abnormal state is detected, the step of collecting the abnormal information by using the customized kernel includes:
  • the collected first abnormal information is compressed, it is stored in a corresponding dump location, and the operating system is restarted after the storage is completed.
  • the operating system abnormal state includes the user state being in an abnormal state; and correspondingly, when the operating system abnormal state is detected, collecting the abnormal information by using the customized kernel includes:
  • the collected second abnormal information is compressed, it is stored to the corresponding dump location, and the process is stopped after the storage is completed.
  • An embodiment of the present invention further provides an apparatus for collecting abnormal information during an operating system startup phase, where the apparatus includes:
  • a first processing module configured to use a second memory other than the first memory in the physical memory for the operating system to start when the operating system starts;
  • Loading a module configured to load a custom kernel from the predetermined storage location to the first memory
  • the collection module is configured to collect exception information through the custom kernel when an operating system abnormal state is detected.
  • the device further comprises:
  • a second processing module configured to perform a trimming process on a standard kernel of the operating system during the installation of the operating system before the operating system is started, to generate the customized kernel that has a smaller volume and a faster startup rate than the standard kernel. And generating the generated custom kernel in a predetermined storage location;
  • the configuration module is configured to configure capacity information and location information of the first memory.
  • the loading module includes:
  • Reading a sub-module configured to read the customized kernel stored in a predetermined storage location through an interface provided by the basic input/output system
  • Loading a submodule configured to load the read custom kernel into the first memory for storage.
  • the operating system abnormal state includes the operating system kernel being in an abnormal state; the corresponding collection module includes:
  • the first collection submodule is configured to collect the first abnormality information of the operating system by using the custom kernel when the operating system kernel is detected to be in an abnormal state;
  • a first acquiring submodule configured to acquire related information of a dump location of the first abnormal information
  • the first processing submodule is configured to compress the collected first abnormal information, store the data to a corresponding dump location, and restart the operating system after the storage is completed.
  • the abnormal state of the operating system includes the user state being in an abnormal state; the corresponding collection module includes:
  • the triggering submodule is configured to trigger a hardware exception when the user state is detected to be in an abnormal state, and obtain an abnormal state level in the exception processing flow;
  • the second collection submodule is configured to collect, by using the custom kernel, second abnormal information corresponding to the user state, when the abnormal state level is greater than the preset level;
  • a second obtaining submodule configured to acquire related information of a dump location of the second abnormal information
  • the second processing submodule is configured to compress the collected second abnormality information, store the data to a corresponding dump location, and stop the process after the storage is completed.
  • a storage medium comprising a stored program, wherein the program is executed to perform the method of any of the above.
  • the custom kernel located at the predetermined storage location is started when the operating system is started.
  • the custom kernel located at the predetermined storage location is started when the operating system is started.
  • collecting abnormal information through the customized kernel can not only solve the problem of collecting abnormal information during the startup phase of the operating system, but also can be used for collecting abnormal information after the operating system is started.
  • it has strong versatility.
  • FIG. 1 is a schematic diagram of a method for collecting abnormal information during an operating system startup phase according to Embodiment 1 of the present invention
  • FIG. 2 is a schematic diagram of a method for collecting abnormal information during an operating system startup phase according to Embodiment 2 of the present invention
  • FIG. 3 is a schematic diagram of a method for collecting abnormal information during an operating system startup phase according to Embodiment 3 of the present invention
  • FIG. 4 is a schematic diagram of a method for processing abnormality information of an operating system kernel abnormality according to Embodiment 3 of the present invention.
  • FIG. 5 is a schematic diagram of a method for processing abnormality information of a user state abnormality according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic diagram of an apparatus for collecting abnormal information during an operating system startup phase according to Embodiment 4 of the present invention.
  • a method for collecting abnormal information in an operating system startup phase includes:
  • Step 101 When the operating system is started, use the second memory other than the first memory in the physical memory for the operating system to start.
  • step 102 when the operating system is started, it is determined that the second memory in the physical memory of the operating system is used for booting of the operating system, and the first memory in the physical memory is determined to be used for storing the custom kernel.
  • the first memory is isolated from the second memory used for starting the operating system, and the first memory and the second memory do not affect each other, and the first memory is not used by the operating system.
  • the custom kernel is smaller, lighter, faster to boot, includes only the necessary drivers, and only performs the necessary hardware initialization.
  • Step 102 Load a custom kernel from a predetermined storage location to the first memory.
  • the custom kernel located at the predetermined storage location needs to be loaded into the physical memory.
  • the predetermined storage location is a location for storing the custom kernel when generating the custom kernel.
  • step 103 needs to be performed.
  • Step 103 Collect abnormal information by using a custom kernel when an abnormal state of the operating system is detected.
  • the operating system After determining the second memory for operating system boot and the first memory isolated from the second memory for storing the custom kernel at the time of operating system startup, and loading the custom kernel to the first memory, the operating system is required The status is monitored. When the operating system is detected to be in an abnormal state, an exception information collection process is required, and the abnormal information is collected through the customized kernel. After the collection of the exception information is completed, the exception information needs to be dumped to the corresponding location for saving.
  • the abnormal state of the operating system includes: the operating system kernel is abnormal. State and user mode are in an abnormal state.
  • the abnormal information can be directly collected and the abnormal information is stored.
  • the abnormal information at this time is the abnormal information of the entire operating system.
  • the exception information includes: register context exception information, stack exception information, and current system memory mirroring exception information.
  • the user state is in an abnormal state, it is necessary to determine the level of the abnormal state.
  • the abnormal information collecting process may be entered, and the abnormal information is collected through the customized kernel.
  • the abnormality information at this time is abnormal information corresponding to the user state process.
  • the exception information at this time includes:
  • the customization will be located at a predetermined storage location.
  • the kernel is loaded in the first memory separated from the operating system.
  • the abnormal information is collected through the customized kernel, which not only solves the problem of difficulty in collecting abnormal information during the startup phase of the operating system, but also can be used for The collection of abnormal information after the operating system is started does not depend on the specific hardware and has strong versatility.
  • the method for collecting abnormal information in the startup phase of the operating system includes:
  • Step 201 Before the operating system is started, during the process of installing the operating system, the standard kernel of the operating system is tailored to generate a customized kernel that is smaller in volume and faster in starting rate than the standard kernel, and stores the generated customized kernel in the operating system.
  • the predetermined storage location Before the operating system is started, during the process of installing the operating system, the standard kernel of the operating system is tailored to generate a customized kernel that is smaller in volume and faster in starting rate than the standard kernel, and stores the generated customized kernel in the operating system. The predetermined storage location.
  • custom kernel Before starting the operating system, you need to generate a custom kernel, which is tailored based on the operating system standard kernel to obtain a custom kernel that is smaller, lighter, and faster to start up than the operating system standard kernel. And the custom kernel only includes the necessary drivers, only the necessary hardware initialization.
  • the custom kernel After the custom kernel is generated, the custom kernel needs to be stored, and the custom kernel needs to be stored in a predetermined storage location. That is, when the operating system is installed, the custom kernel is installed to the specified storage location. It is also possible to copy the custom kernel to the specified storage location after the operating system installation is complete.
  • step 202 needs to be configured to store information about the first memory of the custom kernel when the operating system starts.
  • Step 202 Configure capacity information and location information of the first memory.
  • the first memory is isolated from the physical memory used for booting the operating system, and it is necessary to ensure that the operating system does not use the first memory.
  • step 203 After completing the related operations of the operating system installation phase, it is necessary to enter the startup phase of the operating system, that is, step 203 needs to be continued.
  • the operating system after the operating system is installed, after the operating system is started, when the user changes the related configuration, the operating system needs to be restarted at this time, and the related configuration is changed during the restart of the operating system.
  • the configuration takes effect.
  • Step 203 When the operating system is started, use the second memory other than the first memory in the physical memory for the operating system to start.
  • the operating system When the operating system starts, it is necessary to determine the second memory in the physical memory of the operating system for starting the operating system, and determine that the first memory in the physical memory is used to store the custom kernel.
  • the first memory is isolated from the second memory used for starting the operating system, and the first memory and the second memory do not affect each other, and the first memory is not used by the operating system.
  • the second memory other than the first memory in the physical memory may be used for booting of the operating system.
  • the custom kernel can be loaded into the first memory. That is, step 204 and step 205 need to be performed in sequence at this time.
  • Step 204 Read a custom kernel stored in a predetermined storage location through an interface provided by the basic input/output system.
  • the custom kernel stored in the predetermined storage location is read through an interface provided by the basic input output system. Because the related storage device driver may not be ready at the beginning of the operating system startup, you cannot use the original input and output process of the operating system to read the custom kernel from the specified storage device. You need a reliable way.
  • the custom kernel stored in the predetermined storage location is directly read through the interface provided by the basic input/output system.
  • step 205 After reading the custom kernel stored in the predetermined storage location through the interface provided by the basic input/output system, step 205 needs to be performed.
  • Step 205 Load the read custom kernel into the first memory for storage.
  • the read custom kernel is loaded into the first memory that is isolated from the operating system. Then you need to monitor the status of the operating system.
  • Step 206 When the operating system abnormal state is detected, the abnormal information is collected by the customized kernel, and the abnormal information is stored to the corresponding dump location.
  • the operating system When it is detected that the operating system is in an abnormal state, it is necessary to collect the abnormal information through the customized kernel and store the collected abnormal information. When storing the abnormal information, it is necessary to acquire the storage location of the abnormal information according to the storage location information of the abnormality information configured in the operating system installation phase, and then store the abnormality information. It should be noted that the collection of the abnormal information and the storage of the abnormal information after the completion of the collection are completed in the kernel state of the operating system, and do not depend on any user state components, thereby preventing the abnormality caused by the user state component itself (if not ready). The problem that the information could not be successfully dumped.
  • the abnormal state of the operating system includes: the operating system kernel is in an abnormal state and the user state is in an abnormal state.
  • the first abnormal information of the operating system is collected through the customized kernel; the related information of the dump location of the first abnormal information is obtained; and the collected first abnormal information is compressed and stored. Go to the appropriate dump location and restart the operating system after the storage is complete.
  • the hardware exception is triggered and an abnormal state level is obtained in the exception processing flow; when the abnormal state level is greater than the preset level, the second abnormal information corresponding to the user state is collected through the custom kernel; The information about the dump location of the abnormal information is compressed; the collected second abnormal information is compressed, stored in the corresponding dump location, and the process is stopped after the storage is completed.
  • the first abnormal information needs to be collected through the customized kernel.
  • the first abnormal information at this time is the entire operating system (including the operating system kernel and the user state process).
  • the abnormality information for example, the first abnormality information includes: register context exception information, stack exception information, memory mirroring abnormality information of the current operating system, and the like.
  • the storage location of the abnormality information needs to be acquired according to the storage location information of the abnormality information configured in the operating system installation phase.
  • the first abnormal information is then compressed to reduce information collection time and storage usage.
  • the compressed first abnormal information is dumped to a corresponding location of the specified storage device according to a storage location of the abnormal information, for example, the compressed first abnormal information is stored on a local disk or a network. After storing the first exception information on the local disk or the network, you need to restart the operating system.
  • the system When it is detected that the user state is in an abnormal state, it is necessary to trigger a hardware exception, such as a page fault exception and a divide-by-zero exception.
  • a hardware exception such as a page fault exception and a divide-by-zero exception.
  • the system enters the exception handling process pre-registered by the operating system kernel, intercepts the related abnormality in the exception handling process, and determines the level of the abnormal state according to the severity of the abnormality.
  • the second state may be entered.
  • the abnormal information collection process collects the second abnormal information corresponding to the user state through the customized kernel.
  • the second abnormal information at this time includes: register context abnormality information, stack abnormality information, memory mirroring abnormality information of the current process, and address space distribution abnormality information.
  • the storage location information of the abnormality information configured in the system installation phase is used to obtain the storage location of the abnormal information.
  • the second abnormal information is then compressed to reduce information collection time and storage usage.
  • the compressed second abnormal information is dumped to the corresponding location of the specified storage device according to the storage location of the abnormal information, for example, the compressed second abnormal information is stored on the local disk or the network. After storing the second exception information on the local disk or network, you need to stop the current process.
  • the customization will be located at a predetermined storage location.
  • the kernel is loaded in the first memory separated from the operating system.
  • the abnormal information is collected through the customized kernel, which not only solves the problem of difficulty in collecting abnormal information during the startup phase of the operating system, but also can be used for The collection of abnormal information after the operating system is started does not depend on the specific hardware and has strong versatility.
  • a method for collecting abnormal information in an operating system startup phase includes:
  • Step 301 Before the operating system is started, configure the size of the reserved memory to store and start the custom kernel, and store the customized kernel in the specified storage location.
  • Step 302 When the operating system is started, the physical memory is reserved according to the size and location of the configuration, and is isolated from the operating system.
  • Step 303 Load the custom kernel from the specified storage location into the reserved physical memory.
  • Step 304 Monitor all exceptions from the operating system kernel and user mode.
  • Step 305 Start a custom kernel after detecting an abnormality, so that the customized kernel collects abnormal information after performing related initialization.
  • Step 306 Acquire a storage location of the abnormality information according to the storage location information of the preset abnormality information, and dump the abnormality information into a related location of the corresponding device.
  • Step 401 Actively trigger to enter an abnormal information collection process.
  • Step 402 Read storage location information of the abnormal information to obtain a storage location of the abnormal information.
  • Step 403 The abnormal information of the entire operating system is compressed and then dumped to a specified storage location.
  • Step 404 After the dump is completed, restart the operating system.
  • Step 501 Trigger a hardware exception, and enter an exception processing procedure pre-registered by the operating system kernel after triggering a hardware exception.
  • Step 502 Intercept the relevant abnormality in the abnormal processing flow, and determine the abnormal state level.
  • Step 503 Collect abnormal information when the abnormal state level is greater than a preset level.
  • Step 504 Read storage location information of the abnormal information to obtain a storage location of the abnormal information.
  • Step 505 Perform compression processing on the abnormal information corresponding to the user state, and then dump the information to the specified storage location.
  • Step 506 After the dump is completed, stop the current process.
  • the custom kernel located at the predetermined storage location is loaded into the memory separated from the operating system, and when the operating system is detected to be in an abnormal state, the abnormal information is collected through the customized kernel. It can solve the problem of collecting abnormal information in the startup phase of the operating system. At the same time, it can also be used for collecting abnormal information after the operating system is started. It does not depend on specific hardware and has strong versatility.
  • the apparatus for collecting abnormal information in the startup phase of the operating system includes:
  • the first processing module 10 is configured to use, when the operating system is started, a second memory other than the first memory in the physical memory for the operating system to be started;
  • the loading module 20 is configured to load the custom kernel from the predetermined storage location to the first memory
  • the collection module 30 is configured to collect exception information through the custom kernel when an operating system abnormal state is detected.
  • the device further comprises:
  • the second processing module 40 is configured to: before the operating system is started, during the process of installing the operating system, trimming the standard kernel of the operating system to generate a customized kernel with a smaller volume and a faster startup rate than the standard kernel, and generating The custom kernel is stored in a predetermined storage location;
  • the configuration module 50 is configured to configure capacity information and location information of the first memory.
  • the loading module 20 includes:
  • Reading sub-module 21 configured to read a custom kernel stored in a predetermined storage location through an interface provided by the basic input/output system;
  • the load sub-module 22 is configured to load the read custom kernel into the first memory for storage.
  • the operating system abnormal state includes the operating system kernel being in an abnormal state; the corresponding collecting module 30 includes:
  • the first collection submodule 31 is configured to collect the first abnormality information of the operating system by using a custom kernel when the operating system kernel is detected to be in an abnormal state;
  • the first obtaining submodule 32 is configured to acquire related information of a dump location of the first abnormal information
  • the first processing sub-module 33 is configured to compress the collected first abnormality information, store the data to the corresponding dump location, and restart the operating system after the storage is completed.
  • the operating system abnormal state includes the user state being in an abnormal state; the corresponding collecting module 30 includes:
  • the triggering sub-module 34 is configured to trigger a hardware different when the user state is detected to be in an abnormal state. Often, the abnormal state level is obtained in the exception handling process;
  • the second collecting sub-module 35 is configured to collect the second abnormal information corresponding to the user state by using a custom kernel when the abnormal state level is greater than the preset level;
  • the second obtaining sub-module 36 is configured to acquire related information of the dump location of the second abnormal information
  • the second processing sub-module 37 is configured to compress the collected second abnormality information, store it to the corresponding dump location, and stop the process after the storage is completed.
  • a custom kernel is generated in the operating system installation process by using the foregoing module, and related information for storing the first memory of the customized kernel in the startup phase of the operating system is configured, and is located at a predetermined storage location when the operating system is started.
  • the customized kernel is loaded in the first memory separated from the operating system.
  • the apparatus for collecting abnormal information in the startup phase of the operating system provided by the embodiment of the present invention is the apparatus applying the foregoing method, and all the embodiments of the foregoing method are applicable to the apparatus, and both can achieve the same or similar benefits. effect.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present invention also provide a storage medium including a stored program, wherein the program described above executes the method of any of the above.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • the method and apparatus for collecting abnormal information in the startup phase of the operating system have the following beneficial effects: when the operating system is started, the custom kernel located at the predetermined storage location is loaded into the operating system.
  • the custom kernel located at the predetermined storage location is loaded into the operating system.
  • collecting abnormal information through the customized kernel can not only solve the problem of difficulty in collecting abnormal information during the startup phase of the operating system, but also can be used after the operating system is started.
  • Abnormal information collection, independent of specific hardware, has strong versatility.

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

Des modes de réalisation de la présente invention concernent un procédé et un dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation. Le procédé comprend les étapes suivantes : lors du démarrage d'un système d'exploitation, sélection d'une deuxième mémoire interne autre qu'une première mémoire interne dans une mémoire physique pour démarrer le système d'exploitation; chargement d'un noyau personnalisé depuis un emplacement de stockage prédéterminé vers la première mémoire interne; et après détection d'un état anormal du système d'exploitation, collecte d'informations d'anomalie par le noyau personnalisé. Dans les modes de réalisation de la présente invention, lors du démarrage du système d'exploitation, le noyau personnalisé situé dans un emplacement de stockage prédéterminé est chargé vers la première mémoire interne, séparée du système d'exploitation. Après détection d'un démarrage anormal du système d'exploitation, le noyau personnalisé collecte des informations d'anomalie. La présente invention permet ainsi non seulement de résoudre le problème selon lequel des informations d'anomalie sont difficiles à collecter pendant le démarrage du système d'exploitation, mais peut également être appliquée pour collecter des informations d'anomalie après le démarrage d'un système d'exploitation. La présente invention ne dépend pas d'un matériel spécifique et possède un champ d'application large.
PCT/CN2017/093792 2016-08-26 2017-07-21 Procédé et dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation WO2018036318A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610736253.4A CN107783853A (zh) 2016-08-26 2016-08-26 一种在操作系统启动阶段收集异常信息的方法及装置
CN201610736253.4 2016-08-26

Publications (1)

Publication Number Publication Date
WO2018036318A1 true WO2018036318A1 (fr) 2018-03-01

Family

ID=61245487

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/093792 WO2018036318A1 (fr) 2016-08-26 2017-07-21 Procédé et dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation

Country Status (2)

Country Link
CN (1) CN107783853A (fr)
WO (1) WO2018036318A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024012603A1 (fr) * 2022-07-11 2024-01-18 合肥杰发科技有限公司 Système embarqué basé sur un système d'exploitation multiple et son procédé de commande

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102063344A (zh) * 2009-11-18 2011-05-18 中兴通讯股份有限公司 一种系统故障信息转储的方法与系统
CN104899111A (zh) * 2015-06-09 2015-09-09 烽火通信科技股份有限公司 一种处理家庭网关系统内核崩溃的方法及系统
CN105204977A (zh) * 2014-06-30 2015-12-30 中兴通讯股份有限公司 一种系统异常的捕获方法、主系统、影子系统及智能设备
CN105512000A (zh) * 2014-09-24 2016-04-20 中兴通讯股份有限公司 一种操作系统异常信息收集方法、装置及计算机

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102063344A (zh) * 2009-11-18 2011-05-18 中兴通讯股份有限公司 一种系统故障信息转储的方法与系统
CN105204977A (zh) * 2014-06-30 2015-12-30 中兴通讯股份有限公司 一种系统异常的捕获方法、主系统、影子系统及智能设备
CN105512000A (zh) * 2014-09-24 2016-04-20 中兴通讯股份有限公司 一种操作系统异常信息收集方法、装置及计算机
CN104899111A (zh) * 2015-06-09 2015-09-09 烽火通信科技股份有限公司 一种处理家庭网关系统内核崩溃的方法及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024012603A1 (fr) * 2022-07-11 2024-01-18 合肥杰发科技有限公司 Système embarqué basé sur un système d'exploitation multiple et son procédé de commande

Also Published As

Publication number Publication date
CN107783853A (zh) 2018-03-09

Similar Documents

Publication Publication Date Title
JP5176837B2 (ja) 情報処理システム及びその管理方法、制御プログラム並びに記録媒体
US7574627B2 (en) Memory dump method, memory dump program and computer system
US6189114B1 (en) Data processing system diagnostics
US7831857B2 (en) Method and system for recovering from operating system crash or failure
KR101930113B1 (ko) 가상 머신 이미지 분석 기법
EP1638000B1 (fr) Procédé, dispositif et programme pour sauvegarder en urgence le contenu d'une mémoire
US8782469B2 (en) Request processing system provided with multi-core processor
US20140068325A1 (en) Test case result processing
CN109445861A (zh) 系统启动方法、装置、计算机装置及存储介质
CN111158945B (zh) 内核故障处理方法、装置、网络安全设备和可读存储介质
CN110609778A (zh) 一种保存服务器宕机日志的方法及系统
WO2012031567A1 (fr) Procédé de résilience, et dispositif pour système de fichiers
WO2017148271A1 (fr) Procédé de traitement de réinitialisation de système linux et dispositif, ainsi que support d'informations d'ordinateur
JP2010522932A (ja) インストールシーケンスのためのブックマークおよび構成ファイル
JP5609242B2 (ja) 情報処理装置及びメモリダンプ採取方法
US20220308963A1 (en) Method and apparatus for providing recovery from a computing device boot up error
CN114116330B (zh) 服务器性能测试方法、系统、终端及存储介质
US20050033952A1 (en) Dynamic scheduling of diagnostic tests to be performed during a system boot process
CN105242981A (zh) 一种Kdump的配置方法及计算机设备
CN111090546A (zh) 一种操作系统重启方法、装置、设备及可读存储介质
US9852028B2 (en) Managing a computing system crash
WO2018036318A1 (fr) Procédé et dispositif de collecte d'informations d'anomalie pendant le démarrage d'un système d'exploitation
CN113536320A (zh) 一种错误信息处理方法、装置及存储介质
CN112579361A (zh) 备份数据重建方法、装置、设备及存储介质
US20230088318A1 (en) Remotely healing crashed processes

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: 17842741

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17842741

Country of ref document: EP

Kind code of ref document: A1