CN102063344A - Method and system for system fault information dump - Google Patents
Method and system for system fault information dump Download PDFInfo
- Publication number
- CN102063344A CN102063344A CN2009101096693A CN200910109669A CN102063344A CN 102063344 A CN102063344 A CN 102063344A CN 2009101096693 A CN2009101096693 A CN 2009101096693A CN 200910109669 A CN200910109669 A CN 200910109669A CN 102063344 A CN102063344 A CN 102063344A
- Authority
- CN
- China
- Prior art keywords
- dump
- memory
- function
- arrived
- information
- 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.)
- Pending
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
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method for kernel fault information dump. According to the method, operating system kernel debugging information and fault information are acquired aiming at different conditions of system machine faults, and the information is dumped in different modes such as an internal memory, a network, a non-volatile memory medium and the like so that as more useful information as possible is stored when the operating system kernel has faults, and the method is convenient to position the system fault problems.
Description
Technical field
The present invention relates to the operating system failure location technology, relate in particular to a kind of when being used for being implemented in operating system and breaking down, the method for failure message being carried out dump.
Background technology
Along with the high speed development of embedded OS in industries such as the communications industry, auto manufacturing, war industrys, and the operating system of increasing income is flourish, and the operating system kernel technology is no longer by the minority business monopoly.Concerning enterprise, the operating system that customizes oneself no longer has been a difficult problem.But from another aspect, there is its uniqueness in operating system software, existing ripe debugging technique, and the function that all being based on operating system itself provides realizes that the BUG of debugging utility but can not well debug kernel itself easily.Operating system when collapse particularly, may cause system in case of system halt, phenomenon such as restart automatically, cause fault in-situ not preserved, common debugging acid also can't use.
At present, the common method of analytic system crash reason is: by debugging acid analytic system deadlock file, find the assembly code that breaks down, then according to fault in-situ (register value when breaking down, stack information, current task title etc.), analyzing failure cause.
But the weak point of this method is: must have the deadlock file to exist.This condition is not easy to be met in some cases, such as:
1, system does not preserve the medium of deadlock file.
2, during system crash, file operation function lost efficacy, and can't preserve the deadlock file.
3, during system crash, do not trigger kernel exception, but in the Interrupt Process code, be absorbed in endless loop, cause system to dispatch, and then crash.
Summary of the invention
Technical matters to be solved by this invention is that a kind of method and system of dump system failure information are provided.
The present invention has adopted following technical scheme:
A kind of method of system failure memory dump comprises:
Steps A, according to system running environment, the dump interface function of registration failure message is provided with the corresponding relation of failure message and dump position when moving in system in the described interface function;
Step B, when the system failure, adjust back described interface function, and according to the log-on message dump failure message of this function to corresponding dump position.
Described interface function is registered in kernel, driver, module;
Described failure message comprises one of following information at least: task stack, CPU buffer status, kernel key data structure information;
The described system failure comprises one of following fault at least: system crash, kernel are absorbed in endless loop.
One or more that may further comprise the steps are handled in the memory dump of described step B:
If the described interface function of step B1 is to have registered internal memory is arrived in memory dump, then adjust back this function, internal memory is arrived in memory dump;
If the described interface function of step B2 is to have registered network is arrived in memory dump, then adjust back this function, network is arrived in memory dump;
If the described interface function of step B3 is to have registered non-volatile memory medium is arrived in memory dump, then adjust back this function, non-volatile memory medium is arrived in memory dump.
Described step B1 when dump information, be with memory dump in the reserved memory of system; Also comprise following processing procedure after the described step B1: system is charged restart after, the information in the described reserved memory can be carried out the secondary dump, perhaps print.
Described step B2 when dump information, be system pass through directly to control network interface card through network to other equipment sending data bags, preserve information by other equipment.
A kind of system of system failure memory dump comprises:
The memory dump Registering modules, log-on message dump interface function when being used for moving in system according to system running environment is provided with the corresponding relation of failure message and dump position in the described interface function;
The memory dump module is used for arriving corresponding dump position according to the log-on message dump failure message of described interface function;
Whether fault detection module is used for detection system and breaks down.
The described system failure comprises one of following fault at least: system crash, kernel are absorbed in endless loop.
Described memory dump module comprises one or more of following processing when the dump failure message:
Handle 1: if described interface function is to have registered internal memory is arrived in memory dump, then adjust back this function, internal memory is arrived in memory dump;
Handle 2: if described interface function is to have registered network is arrived in memory dump, then adjust back this function, network is arrived in memory dump;
Handle 3: if described interface function is to have registered non-volatile memory medium is arrived in memory dump, then adjust back this function, non-volatile memory medium is arrived in memory dump.
Described processing 1 be with memory dump in the reserved memory of system; Also comprise following processing procedure after the described processing 1: system is charged restart after, the information in the described reserved memory can be carried out the secondary dump, perhaps print.
Described processing 2 be system pass through directly to control network interface card through network to other equipment sending data bags, preserve information by other equipment.
The invention has the beneficial effects as follows: the present invention is saved in system failure information in internal memory, network and the non-volatile memory medium, obtain situation when having avoided system not preserve the medium of deadlock file less than the deadlock file, can't preserve the situation of deadlock file when also having avoided system crash, also avoid to obtain when crashing the situation of failure message.
Description of drawings
Fig. 1 is the schematic flow sheet of a kind of specific embodiment of the inventive method.
Fig. 2 is the logical organization synoptic diagram of system of the present invention.
Embodiment
In conjunction with the accompanying drawings the present invention is described in further detail below by embodiment.
The schematic flow sheet of the inventive method specific embodiment as shown in Figure 1, after operating system brings into operation,
1: log-on message dump function.
The transfer the information for storage this moment initialization of call back function promptly at kernel, driver, module log-on message dump call back function, is provided with the corresponding situation of failure message and dump position in the call back function of registration.Can be according to the actual conditions of system, difference registers memory memory dump call back function, network information dump call back function, non-volatile media memory dump call back function.
2: detect deadlock.
In system's operational process, the detecting operation system failure, fault comprise that system crash or kernel are absorbed in endless loop.In case find that operating system breaks down, then the trigger message dump procedure.But the trigger point comprises not only and comprises:
(1) fatefulue address access errors has taken place in kernel;
(2) the kernel key data structure is destroyed causes continuing moving;
(3) endless loop has taken place under the interruption situation and causes and can not dispatch closing in kernel.
More than three kinds of situations use when all needing to preserve Debugging message, fault in-situ for fault analysis.
For address access errors and the destroyed class mistake of key data structure, with exception throw, operating system can trigger to be called do_page_fault, die function etc. and carries out abnormality processing, in these abnormality processing function, calls call back function to transfer the information for storage;
For the endless loop fault, system notes the time that enters the Interrupt Process function at Interrupt Process function entrance place, when withdrawing from the Interrupt Process function, notes the time of withdrawing from the Interrupt Process function.Interrupt by NMI and SMI then, regularly detect the processing time of Interrupt Process function,, so just think the endless loop fault, and then call call back function and transfer the information for storage if interrupt handling routine does not withdraw from for a long time.
In case system detects deadlock, then handle according to the following steps.
3: need to be saved in internal memory?
Judge whether to have registered the dump call back function, if registered this call back function, expression need be saved in Debugging message, fault in-situ in the internal memory, then continues execution in step 5.If do not register this call back function, then forward step 5 to.
4: internal memory is arrived in memory dump.
But memory dump is the simplest the most reliable to this mode of internal memory.Because it does not rely on system break, do not rely on specific hardware (as disk, network interface card) yet.Under the limited situation of hardware, can use.Because internal memory is Volatile media, therefore, when dump information, in the internal memory that memory dump should be kept to system, promptly call the dump call back function of registration, Debugging message, fault in-situ are saved in the internal memory.Be finished memory dump behind internal memory, forward step 5 to.
In the practical operation, after preservation information, equipment can not cut off the power supply.Equipment is charged restart after, can again the information in the reserved memory be carried out the secondary dump or print.
5: need to be saved in network?
Judge whether to have registered network information dump call back function, if registered this call back function, expression need be preserved Debugging message, fault in-situ by network, then continue execution in step 6.If do not register this call back function, then forward step 7 to.
6: network is arrived in memory dump.
When system breaks down, the network interface that operating system provides not necessarily can operate as normal, therefore, when dump information, directly calling system network interface function (for example web socket interface) is not preserved, but call the dump call back function of registration, directly the control network interface card sends packet by network interface card to other main frames of network, and Debugging message, fault in-situ are saved in other main process equipments of network, after being finished, forward step 7 to.
7: need to be saved in disk?
Judge whether to have registered non-volatile media memory dump call back function, if registered this call back function, expression need be saved in Debugging message, fault in-situ in the non-volatile media, then continues execution in step 8.If do not register this call back function, end process flow process then.
8: non-volatile media is arrived in memory dump, as disk.
Dump information is the most frequently used dump mode to non-volatile memory medium.Except disk, also can be dumped in other non-volatile memory mediums such as flash memory flash.
Because following situation may cause the dump disabler:
As, in the internal memory, kernel code is destroyed, causes file system unavailable;
As, closing under the interruption situation, carried out endless loop, cause system not respond interruption, also just can't carry out the disk read-write operation;
As, the disk drive function is undesired.
Therefore, generally speaking, preferentially with memory dump in internal memory and network, at last just with memory dump in non-volatile memory medium.This also is the processing thinking of the best specific embodiment of the inventive method.Be by calling the non-volatile media memory dump call back function of registration, Debugging message, fault in-situ being saved in the non-volatile media during dump.After being finished, the end process flow process.
The present invention also provides a kind of kernel failure message dump system, and its logical organization comprises as shown in Figure 2: memory dump Registering modules, memory dump module, fault detection module.
The memory dump Registering modules according to the actual conditions of system at kernel, driver, module the transfer the information for storage initialization of call back function, registers memory memory dump call back function, network information dump call back function, non-volatile memory medium memory dump call back function respectively.
Whether fault detection module is used for detection system and breaks down.When kernel has taken place that address access errors or key data structure are destroyed etc. to be captured to unusually, operating system can trigger to be called do_page_fault, die function etc. and carries out abnormality processing, in these abnormality processing function, call call back function and transfer the information for storage in the memory dump module; For the endless loop fault, system notes the time that enters the Interrupt Process function at Interrupt Process function entrance place, when withdrawing from the Interrupt Process function, notes the time of withdrawing from the Interrupt Process function.Interrupt by NMI and SMI then, regularly detect the processing time of Interrupt Process function,, so just think the endless loop fault, and then call call back function and transfer the information for storage in the memory dump module if interrupt handling routine does not withdraw from for a long time.
The memory dump module is judged according to the call back function of having registered: if registered the dump call back function, then dump information is to internal memory; If registered network information dump call back function, then dump information is to network; If registered non-volatile memory medium memory dump call back function, then dump information is to non-volatile memory medium.
Above content be in conjunction with concrete embodiment to further describing that the present invention did, can not assert that concrete enforcement of the present invention is confined to these explanations.For the those of ordinary skill of technical field of the present invention, without departing from the inventive concept of the premise, can also make some simple deduction or replace, all should be considered as belonging to protection scope of the present invention.
Claims (10)
1. the method for a system failure memory dump is characterized in that, comprising:
Steps A, according to system running environment, the dump interface function of registration failure message is provided with the corresponding relation of failure message and dump position when moving in system in the described interface function;
Step B, when the system failure, adjust back described interface function, and according to the log-on message dump failure message of this function to corresponding dump position.
2. the method for claim 1 is characterized in that:
Described interface function is registered in kernel, driver, module;
Described failure message comprises one of following information at least: task stack, CPU buffer status, kernel key data structure information;
The described system failure comprises one of following fault at least: system crash, kernel are absorbed in endless loop.
3. method as claimed in claim 1 or 2 is characterized in that, one or more that may further comprise the steps are handled in the memory dump of described step B:
If the described interface function of step B1 is to have registered internal memory is arrived in memory dump, then adjust back this function, internal memory is arrived in memory dump;
If the described interface function of step B2 is to have registered network is arrived in memory dump, then adjust back this function, network is arrived in memory dump;
If the described interface function of step B3 is to have registered non-volatile memory medium is arrived in memory dump, then adjust back this function, non-volatile memory medium is arrived in memory dump.
4. method as claimed in claim 3 is characterized in that, described step B1 when dump information, be with memory dump in the reserved memory of system; Also comprise following processing procedure after the described step B1: system is charged restart after, the information in the described reserved memory can be carried out the secondary dump, perhaps print.
5. method as claimed in claim 3 is characterized in that, described step B2 when dump information, be system pass through directly to control network interface card through network to other equipment sending data bags, preserve information by other equipment.
6. the system of a system failure memory dump is characterized in that, comprising:
The memory dump Registering modules, log-on message dump interface function when being used for moving in system according to system running environment is provided with the corresponding relation of failure message and dump position in the described interface function; The memory dump module is used for arriving corresponding dump position according to the log-on message dump failure message of described interface function;
Whether fault detection module is used for detection system and breaks down.
7. system as claimed in claim 6 is characterized in that, the system failure comprises one of following fault at least: system crash, kernel are absorbed in endless loop.
8. system as claimed in claim 6 is characterized in that, described memory dump module comprises one or more of following processing when the dump failure message:
Handle 1: if described interface function is to have registered internal memory is arrived in memory dump, then adjust back this function, internal memory is arrived in memory dump;
Handle 2: if described interface function is to have registered network is arrived in memory dump, then adjust back this function, network is arrived in memory dump;
Handle 3: if described interface function is to have registered non-volatile memory medium is arrived in memory dump, then adjust back this function, non-volatile memory medium is arrived in memory dump.
9. system as claimed in claim 8 is characterized in that, described processing 1 be with memory dump in the reserved memory of system; Also comprise following processing procedure after the described processing 1: system is charged restart after, the information in the described reserved memory can be carried out the secondary dump, perhaps print.
10. system as claimed in claim 8 is characterized in that, described processing 2 be system pass through directly to control network interface card through network to other equipment sending data bags, preserve information by other equipment.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101096693A CN102063344A (en) | 2009-11-18 | 2009-11-18 | Method and system for system fault information dump |
| PCT/CN2010/073639 WO2010148940A1 (en) | 2009-11-18 | 2010-06-07 | Method and system for dumping fault information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2009101096693A CN102063344A (en) | 2009-11-18 | 2009-11-18 | Method and system for system fault information dump |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102063344A true CN102063344A (en) | 2011-05-18 |
Family
ID=43385987
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2009101096693A Pending CN102063344A (en) | 2009-11-18 | 2009-11-18 | Method and system for system fault information dump |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102063344A (en) |
| WO (1) | WO2010148940A1 (en) |
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102622322A (en) * | 2012-02-24 | 2012-08-01 | 华为技术有限公司 | Method for acquiring crash information through black box, black box and server |
| CN102722916A (en) * | 2012-05-23 | 2012-10-10 | 南京智达康无线通信科技股份有限公司 | Fault information record method and fault management system used for access controller |
| CN102831069A (en) * | 2012-06-30 | 2012-12-19 | 华为技术有限公司 | Memory processing method and memory management equipment |
| CN102866932A (en) * | 2011-11-14 | 2013-01-09 | 新游游戏株式会社 | Method and device for providing and collecting data related to abnormal terminal |
| CN103809989A (en) * | 2012-11-08 | 2014-05-21 | 英华达（南京）科技有限公司 | Method for reading complete core log under situation of core collapse of operating system |
| CN103927240A (en) * | 2014-05-06 | 2014-07-16 | 成都西加云杉科技有限公司 | Information dumping method and device answering to software breakdown |
| CN104268067A (en) * | 2014-09-24 | 2015-01-07 | 湖北盛天网络技术股份有限公司 | Method and device for acquiring collapse information of operation system |
| CN104699615A (en) * | 2012-03-31 | 2015-06-10 | 北京奇虎科技有限公司 | System failure processing method and device |
| CN104750605A (en) * | 2013-12-30 | 2015-07-01 | 伊姆西公司 | Method for including kernel object information in user dump |
| CN105512008A (en) * | 2014-09-22 | 2016-04-20 | 华为技术有限公司 | Method and device obtaining fault information |
| CN105843705A (en) * | 2016-03-22 | 2016-08-10 | 青岛海信移动通信技术股份有限公司 | Mobile communication terminal and memory dumping method thereof |
| CN106201751A (en) * | 2016-06-29 | 2016-12-07 | 北京北信源软件股份有限公司 | A kind of detection method of Windows operating system collapse |
| CN106844078A (en) * | 2016-12-27 | 2017-06-13 | 郑州云海信息技术有限公司 | A kind for the treatment of method and apparatus of PCIE failures |
| WO2018036318A1 (en) * | 2016-08-26 | 2018-03-01 | 中兴通讯股份有限公司 | Method and device for collecting abnormality information during startup of operating system |
| CN107908537A (en) * | 2017-11-27 | 2018-04-13 | 郑州云海信息技术有限公司 | A kind of system and method based on the processing of kernel module exception information |
| CN109471777A (en) * | 2018-11-15 | 2019-03-15 | 百度在线网络技术（北京）有限公司 | The method and apparatus for determining operating system collapse |
| CN112052125A (en) * | 2020-09-28 | 2020-12-08 | 联想(北京)有限公司 | Dump processing method and device for operating system kernel and electronic equipment |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043653B2 (en) | 2012-08-31 | 2015-05-26 | International Business Machines Corporation | Introspection of software program components and conditional generation of memory dump |
| CN105389227A (en) * | 2015-11-05 | 2016-03-09 | 上海斐讯数据通信技术有限公司 | System crash information remote transmitting method and network device |
| WO2018082176A1 (en) * | 2016-11-03 | 2018-05-11 | 华为技术有限公司 | Method for processing fault of terminal device, and terminal device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7506203B2 (en) * | 2005-11-10 | 2009-03-17 | International Business Machines Corporation | Extracting log and trace buffers in the event of system crashes |
| US8972794B2 (en) * | 2008-02-26 | 2015-03-03 | International Business Machines Corporation | Method and apparatus for diagnostic recording using transactional memory |
| CN100570581C (en) * | 2008-04-09 | 2009-12-16 | 中兴通讯股份有限公司 | The method and apparatus of localization of fault |
-
2009
- 2009-11-18 CN CN2009101096693A patent/CN102063344A/en active Pending
-
2010
- 2010-06-07 WO PCT/CN2010/073639 patent/WO2010148940A1/en active Application Filing
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102866932A (en) * | 2011-11-14 | 2013-01-09 | 新游游戏株式会社 | Method and device for providing and collecting data related to abnormal terminal |
| CN102622322A (en) * | 2012-02-24 | 2012-08-01 | 华为技术有限公司 | Method for acquiring crash information through black box, black box and server |
| CN104699615B (en) * | 2012-03-31 | 2017-09-22 | 北京奇虎科技有限公司 | A kind for the treatment of method and apparatus of the system failure |
| CN104699615A (en) * | 2012-03-31 | 2015-06-10 | 北京奇虎科技有限公司 | System failure processing method and device |
| CN102722916A (en) * | 2012-05-23 | 2012-10-10 | 南京智达康无线通信科技股份有限公司 | Fault information record method and fault management system used for access controller |
| CN102831069B (en) * | 2012-06-30 | 2016-03-30 | 华为技术有限公司 | Internal memory processing method, memory management equipment |
| CN102831069A (en) * | 2012-06-30 | 2012-12-19 | 华为技术有限公司 | Memory processing method and memory management equipment |
| CN103809989A (en) * | 2012-11-08 | 2014-05-21 | 英华达（南京）科技有限公司 | Method for reading complete core log under situation of core collapse of operating system |
| CN104750605A (en) * | 2013-12-30 | 2015-07-01 | 伊姆西公司 | Method for including kernel object information in user dump |
| CN103927240A (en) * | 2014-05-06 | 2014-07-16 | 成都西加云杉科技有限公司 | Information dumping method and device answering to software breakdown |
| CN105512008A (en) * | 2014-09-22 | 2016-04-20 | 华为技术有限公司 | Method and device obtaining fault information |
| CN105512008B (en) * | 2014-09-22 | 2018-05-11 | 华为技术有限公司 | A kind of method and device for obtaining fault message |
| CN104268067B (en) * | 2014-09-24 | 2017-06-06 | 湖北盛天网络技术股份有限公司 | Method and apparatus for obtaining the crash info of operating system |
| CN104268067A (en) * | 2014-09-24 | 2015-01-07 | 湖北盛天网络技术股份有限公司 | Method and device for acquiring collapse information of operation system |
| CN105843705A (en) * | 2016-03-22 | 2016-08-10 | 青岛海信移动通信技术股份有限公司 | Mobile communication terminal and memory dumping method thereof |
| CN106201751A (en) * | 2016-06-29 | 2016-12-07 | 北京北信源软件股份有限公司 | A kind of detection method of Windows operating system collapse |
| CN106201751B (en) * | 2016-06-29 | 2019-02-19 | 北京北信源软件股份有限公司 | A kind of detection method of Windows operating system collapse |
| WO2018036318A1 (en) * | 2016-08-26 | 2018-03-01 | 中兴通讯股份有限公司 | Method and device for collecting abnormality information during startup of operating system |
| CN106844078A (en) * | 2016-12-27 | 2017-06-13 | 郑州云海信息技术有限公司 | A kind for the treatment of method and apparatus of PCIE failures |
| CN107908537A (en) * | 2017-11-27 | 2018-04-13 | 郑州云海信息技术有限公司 | A kind of system and method based on the processing of kernel module exception information |
| CN109471777A (en) * | 2018-11-15 | 2019-03-15 | 百度在线网络技术（北京）有限公司 | The method and apparatus for determining operating system collapse |
| CN112052125A (en) * | 2020-09-28 | 2020-12-08 | 联想(北京)有限公司 | Dump processing method and device for operating system kernel and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2010148940A1 (en) | 2010-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102063344A (en) | Method and system for system fault information dump | |
| CN101377750B (en) | System and method for cluster fault toleration | |
| US10423783B2 (en) | Methods and apparatus to recover a processor state during a system failure or security event | |
| US7966528B2 (en) | Watchdog mechanism with fault escalation | |
| CN101154180B (en) | Method for monitoring task stack overflow | |
| EP3142011A1 (en) | Anomaly recovery method for virtual machine in distributed environment | |
| CN101542444B (en) | Security features in interconnect centric architectures | |
| US20060212754A1 (en) | Multiprocessor system | |
| KR101770949B1 (en) | Robust hardware/software error recovery system | |
| CN109491958B (en) | Error processing system and error processing method | |
| US20140122421A1 (en) | Information processing apparatus, information processing method and computer-readable storage medium | |
| CN101373450B (en) | Method and system for processing CPU abnormity | |
| CN104685474A (en) | Notification of address range including non-correctable error | |
| CN107168773A (en) | Positioning problems and the processing method and processing device of application recovery after a kind of JVM collapses | |
| CN101034369A (en) | Software anti-interference method and device | |
| CN102609327A (en) | Method and device for improving reliability of multi-core processor | |
| CN101221518B (en) | Method, device and system for preventing timing device overflow of hardware watchdog | |
| CN101546279A (en) | Device, system and method for exception processing of embedded device | |
| CN100449495C (en) | System and method for assisting CPU to drive chips | |
| CN109828945A (en) | A kind of service message processing method and system | |
| US7966527B2 (en) | Watchdog mechanism with fault recovery | |
| CN103617023A (en) | Method and device for recycling system garbage resources | |
| CN101282244B (en) | Method for detecting instruction based on SPM | |
| CN100419689C (en) | Processing method for interruption and apparatus thereof | |
| CN114756832A (en) | Watchdog overtime restart field capture system, method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110518 |