Hardware fault inspection method, device and equipment and readable storage medium

By obtaining the fault inspection list and determining the target fault inspection process, the problem of insufficient flexibility and automation in hardware fault detection is solved, and efficient and stable hardware fault detection is achieved, avoiding the inability to continue to complete the inspection due to failure interruption. question.

CN119003224APending Publication Date: 2024-11-22INSPUR SUZHOU INTELLIGENT TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411206059.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-30
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

The existing technology lacks flexibility and automation in hardware failure detection, which leads to a long time detection and cannot be flexibly adjusted according to actual needs.

Method used

By obtaining the fault inspection list, determine the target fault inspection process, and record the interrupt location when it is necessary to perform time-consuming tasks, switch the hardware thread to execute time-consuming tasks, and continue to execute the inspection process after the task is completed until the entire hardware inspection is completed .

Benefits of technology

It realizes the flexibility, stability and efficiency of hardware failure detection, avoids the problem of inability to continue to complete the inspection due to failure interruption, and ensures the integrity and efficiency of the inspection.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003224A_ABST
    Figure CN119003224A_ABST
Patent Text Reader

Abstract

The invention discloses a hardware fault inspection method, apparatus and device, and a readable storage medium. The method comprises the steps of obtaining a fault inspection list; wherein the index of the fault inspection process is recorded in the fault inspection list; determining a target fault inspection flow by using the index corresponding to the fault inspection flow; executing the target fault inspection flow, recording an interruption position of the target fault inspection flow under the condition that the target fault inspection flow needs to execute a time-consuming task, and switching a hardware thread to execute the time-consuming task; after the time-consuming task is executed, continuing to execute the target fault inspection flow from the interruption position; and after the target fault inspection process is executed, re-determining the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed, and determining that the hardware inspection is completed. According to the invention, the hardware platform can be automatically inspected, and the inspection process is efficient and flexible.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to a hardware fault inspection method, device, equipment and readable storage medium. Background Art

[0002] In the era of cloud computing, storage devices are developing rapidly, and both software functions and storage performance are becoming more and more powerful. Powerful software functions and storage performance rely on the integration and cooperation of many hardware. Since storage devices integrate a large number of electronic components, storage devices may age or experience abnormal high temperatures after long-term operation, so it is essential to detect hardware failures.

[0003] However, current hardware fault detection often cannot be performed according to actual needs and lacks flexibility, while manual hardware inspection is very time-consuming.

[0004] In summary, how to effectively solve the problems of hardware automatic detection is a technical problem that technical personnel in this field urgently need to solve. Summary of the invention

[0005] The purpose of this application is to provide a hardware fault inspection method, device, equipment and readable storage medium, which can automatically inspect the hardware platform, and the inspection process is efficient, flexible and stable.

[0006] In order to solve the above technical problems, this application provides the following technical solutions:

[0007] A fault inspection method, comprising:

[0008] Obtain a fault inspection list; wherein the fault inspection list records the index of the fault inspection process;

[0009] Using the index corresponding to the fault inspection process, determine the target fault inspection process;

[0010] Execute the target fault inspection process, and if the target fault inspection process needs to execute a time-consuming task, record the interruption position of the target fault inspection process, and switch the hardware thread to execute the time-consuming task;

[0011] After the time-consuming task is completed, the target fault inspection process is continued from the interruption position;

[0012] After executing the target fault inspection process, the target fault inspection process is re-determined until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0013] Preferably, determining that the time-consuming task has been completed includes:

[0014] When switching the hardware thread to execute the time-consuming task, starting a fault inspection timer;

[0015] Monitoring the fault inspection timer;

[0016] After the time of the fault inspection timer expires, it is determined that the time-consuming task has been completed.

[0017] Preferably, obtaining a fault inspection list includes:

[0018] Obtain hardware inspection requirement information of the local hardware platform;

[0019] Using the hardware inspection requirement information, create a fault inspection process and determine the execution order;

[0020] According to the execution order, the index of the created fault inspection process is added to the fault inspection list.

[0021] Preferably, the target fault inspection process is determined by using the index corresponding to the fault inspection process, including:

[0022] Read the index from the fault inspection list in order;

[0023] The fault inspection process corresponding to the index is determined as the target fault inspection process.

[0024] Preferably, executing the target fault inspection process includes:

[0025] During the execution of the target fault inspection process, triggering the underlying hardware access thread;

[0026] Utilize the underlying hardware access thread to collect hardware information;

[0027] Using the hardware information, performing fault detection;

[0028] Wherein, using the hardware information to perform fault detection includes:

[0029] Using the hardware information, performing alarm detection and alarm processing;

[0030] Utilizing the hardware information to detect events and report them;

[0031] Utilizing the hardware information, performing fault detection, and after detecting the fault, performing fault elimination processing;

[0032] Among them, alarm processing includes:

[0033] Output alarm events; wherein the alarm events carry alarm information; the alarm information includes alarm event description information, event repair information and alarm detail information;

[0034] The alarm event description information includes: event description number and event description information and event classification;

[0035] The event repair information includes: event repair number and repair description information;

[0036] The alarm details information includes: fault location information and fault cause information.

[0037] Preferably, it also includes:

[0038] Using the hardware information to determine whether a triggering condition for a time-consuming action is met;

[0039] If yes, start the fault inspection timer and monitor the fault inspection timer;

[0040] After the time of the fault inspection timer expires, the target fault inspection process continues to be executed.

[0041] Preferably, the fault inspection list records the hardware platforms supported by the fault inspection process;

[0042] Accordingly, the target fault inspection process is determined by using the index corresponding to the fault inspection process, including:

[0043] Access the local hardware platform and use the hardware acquisition thread to collect hardware status information;

[0044] Using the hardware status information, installing hardware classification and obtaining hardware information;

[0045] Using the hardware information, determine whether a triggering condition for hardware inspection is met;

[0046] If so, the hardware platforms supported by the fault inspection processes are recorded in the fault inspection list, the fault inspection processes supporting the local hardware platform are screened out from the fault inspection list, and the determined fault inspection processes are determined as the target fault inspection processes.

[0047] A fault inspection device, comprising:

[0048] A list acquisition module is used to acquire a fault inspection list; wherein the fault inspection list records the index of the fault inspection process;

[0049] A process determination module is used to determine a target fault inspection process by using an index corresponding to the fault inspection process;

[0050] A process execution module, used to execute the target fault inspection process;

[0051] A thread switching module, used to record the interruption position of the target fault inspection process and switch the hardware thread to execute the time-consuming task when the target fault inspection process needs to execute a time-consuming task;

[0052] A breakpoint resume module, used to continue executing the target fault inspection process from the interruption position after the time-consuming task is completed;

[0053] The inspection completion determination module is used to re-determine the target fault inspection process after executing the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed to determine that the hardware inspection is completed.

[0054] An electronic device, comprising:

[0055] Memory for storing computer programs;

[0056] A processor is used to implement the steps of the above-mentioned hardware fault inspection method when executing the computer program.

[0057] A readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned hardware fault inspection method are implemented.

[0058] A computer program product includes a computer program / instruction, which, when executed by a processor, implements the steps of the above-mentioned hardware fault inspection method.

[0059] Apply the method provided in the embodiment of the present application to obtain a fault inspection list; wherein, the fault inspection list records the index of the fault inspection process; using the index corresponding to the fault inspection process, determine the target fault inspection process; execute the target fault inspection process, and when the target fault inspection process needs to execute a time-consuming task, record the interruption position of the target fault inspection process, and switch the hardware thread to execute the time-consuming task; after the time-consuming task is executed, continue to execute the target fault inspection process from the interruption position; after executing the target fault inspection process, re-determine the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0060] In the present application, after obtaining the fault inspection list, based on the index of the fault inspection process recorded therein, the target fault inspection process can be determined, and then the target inspection process is executed. In the case where the fault inspection process needs to execute a time-consuming task (such as detecting a fault), the interruption position of the target fault inspection process is recorded, and the hardware thread is switched to execute the time-consuming task (such as fault repair logic). After the time-consuming task is completed, the target fault inspection process continues to be executed from the interruption position. After the fault inspection process corresponding to the fault inspection list is executed, it can be determined that the hardware inspection is completed.

[0061] Technical effect: In this application, the fault inspection process to be executed and its order can be determined based on the fault inspection list. When a time-consuming task needs to be executed, the hardware thread can be switched to execute the time-consuming task by recording the interruption position. After the time-consuming task is completed, the target fault inspection process can be continued based on the interruption position, and it can continue to run at the breakpoint to avoid interruption due to fault detection and inability to continue to complete the hardware inspection. That is, this application can ensure the flexibility, stability and efficiency of inspection.

[0062] Correspondingly, the embodiments of the present application also provide a hardware fault inspection device, equipment, readable storage medium and computer program product corresponding to the above-mentioned hardware fault inspection method, which have the above-mentioned technical effects and are not repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the drawings required for use in the embodiments or the related technical descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0064] FIG1 is a flowchart of a method for hardware fault inspection in an embodiment of the present application;

[0065] FIG2 is a flowchart of a specific implementation of a hardware fault inspection method in an embodiment of the present application;

[0066] FIG3 is a schematic diagram of the structure of a hardware fault inspection device in an embodiment of the present application;

[0067] FIG4 is a schematic diagram of the structure of an electronic device in an embodiment of the present application;

[0068] FIG5 is a schematic diagram of the specific structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0069] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0070] Please refer to Figure 1, which is a flowchart of a hardware fault inspection method in an embodiment of the present application. The method can perform hardware inspection on a hardware platform, and the hardware platform can be a hardware platform in a storage system. The method includes the following steps:

[0071] S101. Obtain a fault inspection list.

[0072] The fault inspection list records the index of the fault inspection process.

[0073] In an embodiment of the present application, only the index corresponding to the fault inspection process supporting the local hardware platform can be recorded in the fault inspection list; or the indexes corresponding to all fault inspection processes and the hardware platform information supported by the fault inspection process can also be recorded in the fault inspection list.

[0074] In a specific implementation of the present application, in the case where only the index corresponding to the fault inspection process supporting the local hardware platform is recorded in the fault inspection list, obtaining the fault inspection list includes:

[0075] Obtain hardware inspection requirement information of the local hardware platform;

[0076] Use hardware inspection requirement information to create a fault inspection process and determine the execution order;

[0077] In the order of execution, the index of the created fault inspection process is added to the fault inspection list.

[0078] For ease of description, the above three steps are combined for explanation below.

[0079] In actual applications, the hardware inspection requirement information of the local hardware platform can be obtained first. The hardware inspection requirement information can specifically include which hardware needs to be inspected, as well as trigger conditions, inspection time settings, inspection fault handling methods and other information.

[0080] Based on these hardware inspection requirement information, a corresponding fault inspection process can be created. When there is more than one fault inspection process, the execution order of the fault inspection processes can be determined.

[0081] When adding the index corresponding to the fault inspection process to the fault inspection list, it can be added in order according to the execution order. In this way, when the fault inspection process is subsequently executed, the corresponding index can be read in order and the corresponding fault inspection process can be executed, so that the fault inspection process can be executed in the set execution order.

[0082] S102: Determine a target fault inspection process by using an index corresponding to the fault inspection process.

[0083] Since the fault inspection list records the index corresponding to the fault inspection process, the target fault inspection process can be determined based on the index.

[0084] The target fault inspection process is the fault inspection process currently to be executed.

[0085] In a specific implementation of the present application, when only the index corresponding to the fault inspection process supporting the local hardware platform is recorded in the fault inspection list, the target fault inspection process is determined by using the index corresponding to the fault inspection process, including:

[0086] Read the index from the fault inspection list in order;

[0087] The fault inspection process corresponding to the index is determined as the target fault inspection process.

[0088] For ease of description, the above steps are combined for explanation below.

[0089] In one embodiment of the present application, when the fault inspection list only records the indexes corresponding to the fault inspection processes that support the local hardware platform, the indexes can be read out in sequence from the fault inspection list, and then the fault inspection process corresponding to the index can be directly determined as the target fault inspection process.

[0090] For example, the fault inspection list records index A of fault inspection process 1 and index B of fault inspection process 2. Index A is recorded before index B. When the fault inspection list is read for the first time, index A is read, and fault inspection process 1 corresponding to index A is determined as the target fault inspection process. After executing fault inspection process 1, the fault inspection list is read again, and index B is read, and fault inspection process 2 corresponding to index B is determined as the target fault inspection process. The order of index A and index B can be determined when writing records to the fault inspection list, and will not be repeated here.

[0091] In a specific implementation of the present application, the indexes corresponding to all fault inspection processes and the hardware platform information corresponding to the fault inspection processes are also recorded in the fault inspection list, that is, the hardware platform supported by the fault inspection process is recorded in the fault inspection list;

[0092] Accordingly, the target fault inspection process is determined by using the index corresponding to the fault inspection process, including:

[0093] Access the local hardware platform and use the hardware acquisition thread to collect hardware status information;

[0094] Using hardware status information, install hardware classification and obtain hardware information;

[0095] Use hardware information to determine whether the triggering conditions for hardware inspection are met;

[0096] If so, the hardware platforms supported by the fault inspection process are recorded in the fault inspection list, the fault inspection process supporting the local hardware platform is screened out from the fault inspection list, and the determined fault inspection process is determined as the target fault inspection process.

[0097] For ease of description, the above steps are combined for explanation below.

[0098] Please refer to Figure 2. In this embodiment, a fault inspection list can be created first through thread 1, and then the index corresponding to one or more fault inspection processes and the relevant information of the hardware platform supported by the fault inspection process index can be added therein. The triggering conditions of the hardware inspection can be set, for example, when the hardware platform reaches a certain condition, the hardware inspection needs to be started.

[0099] On the other hand, a separate thread 2 can be set up, in which the hardware can be accessed, the hardware status can be collected, the hardware classification can be installed, and the hardware information can be sorted. The collection and sorting of hardware information can be executed in a loop, and the hardware information can be continuously fed back to thread 1. For example, after adding hardware information collection to the underlying hardware access thread, the hardware information can be notified to thread 1, and thread 1 performs fault inspection based on the received hardware information.

[0100] For example, a hardware information collection thread can be designed for the storage system. This thread reads hardware information such as hardware temperature, voltage, power, in-place status, hard disk port bit errors, and SAS port bit errors through I2C / ipmitool, etc. Temperature exceeding the threshold, power exceeding the threshold, hardware not in place, too many hard disk port bit errors and continuous growth, and too many SAS port bit errors and continuous growth are all considered faults.

[0101] After receiving the hardware information, thread 1 can determine whether the triggering conditions for hardware inspection are met based on the hardware information. If so, the fault inspection list can be used to record the hardware platforms supported by the fault inspection process, and the fault inspection process that supports the local hardware platform can be filtered out from the fault inspection list. The determined fault inspection process is determined as the target fault inspection process, and the fault inspection process can be executed sequentially subsequently.

[0102] S103, executing a target fault inspection process, and when the target fault inspection process needs to execute a time-consuming task, recording an interruption position of the target fault inspection process, and switching a hardware thread to execute the time-consuming task.

[0103] In a specific implementation of the present application, executing a target fault inspection process includes:

[0104] During the execution of the target fault inspection process, the underlying hardware access thread is triggered;

[0105] Use the underlying hardware to access the thread and collect hardware information;

[0106] Use hardware information to perform fault detection;

[0107] Among them, using hardware information for fault detection includes:

[0108] Use hardware information to detect and process alarms;

[0109] Use hardware information to detect and report events;

[0110] Use hardware information to detect faults and perform troubleshooting after faults are detected;

[0111] Among them, alarm processing includes:

[0112] Output alarm events; wherein the alarm events carry alarm information; the alarm information includes alarm event description information, event repair information and alarm detail information;

[0113] The alarm event description information includes: event description number, event description information and event classification;

[0114] Event repair information, including: event repair number and repair description information;

[0115] Alarm details, including fault location information and fault cause information.

[0116] For ease of description, the above steps are combined for explanation below.

[0117] In this embodiment, when the target fault inspection process is executed, the hardware information can be collected through the underlying hardware access thread, and the hardware information can be used to perform fault detection.

[0118] Among them, fault detection includes but is not limited to alarm detection, event detection and fault detection, as well as processing operations after detecting related content.

[0119] Among them, the alarm event is used to notify the customer that the storage device has failed and needs to be handled in time. The alarm information mainly includes three parts of information:

[0120] 1. Event description ID and information are used to simply describe the event information and its classification;

[0121] 2. Event repair ID and its description information, which are used to determine the processing flow of alarm repair;

[0122] 3. Detailed information of the alarm, used to indicate the specific location and cause of the fault.

[0123] The alarm elimination logic is divided into two categories. One is automatic elimination, such as the over-temperature alarm of the storage device environment. When the temperature drops to the normal temperature, the alarm is automatically eliminated. The second category is manual repair. For example, the power supply of the storage device is not in place alarm. You can plug the power supply back in according to the alarm repair guide and forcibly repair the alarm.

[0124] In a specific implementation of the present application, it also includes:

[0125] Use hardware information to determine whether the triggering conditions of time-consuming actions are met;

[0126] If yes, the fault inspection timer is started and the fault inspection timer is monitored;

[0127] After the fault inspection timer expires, the target fault inspection process continues to be executed.

[0128] Among them, the action of accessing hardware is a time-consuming action, such as resetting chip firmware, opening / closing a hard disk port, opening / closing a SAS port, etc.

[0129] That is to say, when some time-consuming actions are required in the fault inspection business process, it is necessary to switch threads to execute tasks. At this time, it is necessary to record the interruption position of the target fault inspection process. After the time-consuming actions are completed, the fault inspection process continues to run from the breakpoint.

[0130] In a specific implementation of the present application, the interruption position may be recorded in the inspection breakpoint record;

[0131] The inspection breakpoint records are used to count the interruptions that occur during the execution of the fault inspection process to obtain abnormal interruption information.

[0132] In other words, recording the interruption position based on the inspection breakpoint record can not only help record the interruption position and restore the operation of the target fault inspection process, but also count the interruptions that occurred during the execution of the fault inspection process, thereby analyzing and obtaining abnormal interruption information. In order to subsequently optimize the efficiency and stability of the fault inspection process based on the abnormal interruption information.

[0133] The situation where the target fault inspection process needs to execute a time-consuming task may be specifically that a fault is detected, and accordingly, the time-consuming task may be specifically the internal processing logic corresponding to repairing the fault.

[0134] In one embodiment of the present application, when it is found that the target fault inspection process needs to execute a time-consuming task, the interrupt position of the target fault inspection process can be recorded, and the hardware thread can be switched to execute the time-consuming task. Among them, the target fault inspection process needs to execute a time-consuming task, which can be specifically that the target fault inspection process detects a fault and needs to start a hardware thread to execute the internal repair logic, so the target fault inspection process is interrupted. In other words, after the fault occurs, the fault can be modified by executing the internal repair logic, and after the internal modification logic is executed, the fault inspection continues without terminating the inspection, which can ensure the stability of the hardware inspection.

[0135] For example, as shown in FIG2 , when other logic needs to be executed, the fault inspection process is interrupted and thread B is notified to run the logic, thereby running the internal logic of the fault inspection. Thread B can be a hardware thread.

[0136] For example, when the target fault inspection process is the SAS link monitoring thread, when a SAS link fault is detected, it is determined that the hardware thread needs to be switched to execute the time-consuming task. Specifically, in the hardware thread, internal repairs must be attempted first, that is, the SAS port must be closed and then opened, and then the SAS link must be checked. If the link fault still exists, the SAS chip is reset. If the fault cannot be repaired, an alarm event is reported to notify the customer to replace the SAS module.

[0137] Then, when the target fault inspection process is the FRU (Field Replace Unit) fault inspection process, and time-consuming operations are required during the running of the FRU fault inspection process, the time-consuming tasks need to be notified to the hardware access thread for execution, and the breakpoint position of the fault inspection process is recorded and the timer is started at the same time, so that the fault inspection process can continue to run from the breakpoint after the timer expires. For example: after a hard disk fails, the hard disk port needs to be reset for internal repair.

[0138] S104: After the time-consuming task is completed, the target fault inspection process is continued from the interruption position.

[0139] After the logic similar to the time-consuming task is completed, the target fault inspection process is continued from the interruption position.

[0140] In a specific implementation of the present application, determining that the time-consuming task has been completed includes:

[0141] When switching the hardware thread to execute the time-consuming task, start the fault inspection timer;

[0142] Monitor the fault inspection timer;

[0143] After the fault inspection timer expires, it is determined that the time-consuming task has been completed.

[0144] For ease of description, the above steps are combined for explanation below.

[0145] In an embodiment, when a hardware thread needs to be switched to execute a time-consuming task, a fault inspection timer may be started. Then, the fault inspection timer is monitored, and after the time of the fault inspection timer is found to be exhausted, it can be determined that the time-consuming task has been completed.

[0146] In other words, the main function of the fault inspection timer is: when the fault inspection logic needs to run the fault inspection process again after a certain period of time, the fault inspection timer can be used. For example, when the ambient temperature is found to be over-temperature during the temperature training process, anti-shake action is required when an over-temperature fault occurs (that is, the alarm is reported only when the temperature continues to exceed the threshold for a period of time to prevent the temperature from fluctuating up and down near the threshold). At this time, a 30-second fault inspection timer is started, and the temperature inspection is run again after 30 seconds.

[0147] S105 . After executing the target fault inspection process, re-determine the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0148] After executing the fault inspection process corresponding to the fault inspection list, re-determine the target fault inspection process. Specifically, continue to read the next index in the fault inspection list in order, and determine the corresponding fault inspection process as the target fault inspection process. Until the hardware inspection process corresponding to the fault inspection list is executed, it is determined that the hardware inspection is completed. It should be noted that the hardware inspection process corresponding to the fault inspection list here has been fully executed, which means that the hardware inspection process that supports the current hardware platform has been executed.

[0149] Apply the method provided in the embodiment of the present application to obtain a fault inspection list; wherein, the fault inspection list records the index of the fault inspection process; using the index corresponding to the fault inspection process, determine the target fault inspection process; execute the target fault inspection process; when the target fault inspection process needs to execute a time-consuming task, record the interruption position of the target fault inspection process, and switch the hardware thread to execute the time-consuming task; after the time-consuming task is executed, continue to execute the target fault inspection process from the interruption position; after executing the target fault inspection process, re-determine the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0150] In the present application, after obtaining the fault inspection list, based on the index of the fault inspection process recorded therein, the target fault inspection process can be determined, and then the target inspection process is executed. In the case where the fault inspection process needs to execute a time-consuming task (such as detecting a fault), the interruption position of the target fault inspection process is recorded, and the hardware thread is switched to execute the time-consuming task (such as fault repair logic). After the time-consuming task is completed, the target fault inspection process continues to be executed from the interruption position. After the fault inspection process corresponding to the fault inspection list is executed, it can be determined that the hardware inspection is completed.

[0151] Technical effect: In this application, the fault inspection process to be executed and its order can be determined based on the fault inspection list. When a time-consuming task needs to be executed, the hardware thread can be switched to execute the time-consuming task by recording the interruption position. After the time-consuming task is completed, the target fault inspection process can be continued based on the interruption position, and it can continue to run at the breakpoint to avoid interruption due to fault detection and inability to continue to complete the hardware inspection. That is, this application can ensure the flexibility, stability and efficiency of inspection.

[0152] Corresponding to the above method embodiment, the embodiment of the present application further provides a hardware fault inspection device. The hardware fault inspection device described below and the hardware fault inspection method described above can be referenced to each other.

[0153] As shown in FIG3 , the device includes the following modules:

[0154] List acquisition module 101, used to acquire a fault inspection list; wherein the fault inspection list records the index of the fault inspection process;

[0155] A process determination module 102 is used to determine a target fault inspection process by using an index corresponding to the fault inspection process;

[0156] The process execution module 103 is used to execute the target fault inspection process, record the interruption position of the target fault inspection process when the target fault inspection process needs to execute a time-consuming task, and switch the hardware thread to execute the time-consuming task;

[0157] The breakpoint resume module 104 is used to continue executing the target fault inspection process from the interruption position after the time-consuming task is completed;

[0158] The inspection completion determination module 105 is used to re-determine the target fault inspection process after executing the target fault inspection process, until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0159] Apply the device provided in the embodiment of the present application to obtain a fault inspection list; wherein the fault inspection list records the index of the fault inspection process; use the index corresponding to the fault inspection process to determine the target fault inspection process; execute the target fault inspection process, and when the target fault inspection process needs to execute a time-consuming task, record the interruption position of the target fault inspection process, and switch the hardware thread to execute the time-consuming task; after the time-consuming task is completed, continue to execute the target fault inspection process from the interruption position; after executing the target fault inspection process, re-determine the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

[0160] In the present application, after obtaining the fault inspection list, based on the index of the fault inspection process recorded therein, the target fault inspection process can be determined, and then the target inspection process is executed. In the case where the fault inspection process needs to execute a time-consuming task (such as detecting a fault), the interruption position of the target fault inspection process is recorded, and the hardware thread is switched to execute the time-consuming task (such as fault repair logic). After the time-consuming task is completed, the target fault inspection process continues to be executed from the interruption position. After the fault inspection process corresponding to the fault inspection list is executed, it can be determined that the hardware inspection is completed.

[0161] Technical effect: In this application, the fault inspection process to be executed and its order can be determined based on the fault inspection list. When a time-consuming task needs to be executed, the hardware thread can be switched to execute the time-consuming task by recording the interruption position. After the time-consuming task is completed, the target fault inspection process can be continued based on the interruption position, and it can continue to run at the breakpoint to avoid interruption due to fault detection and inability to continue to complete the hardware inspection. That is, this application can ensure the flexibility, stability and efficiency of inspection.

[0162] In a specific implementation of the present application, the breakpoint resume module is specifically used to start the fault inspection timer when switching the hardware thread to execute the time-consuming task;

[0163] Monitor the fault inspection timer;

[0164] After the fault inspection timer expires, it is determined that the time-consuming task has been completed.

[0165] In a specific implementation of the present application, the list acquisition module is specifically used to obtain hardware inspection requirement information of the local hardware platform;

[0166] Use hardware inspection requirement information to create a fault inspection process and determine the execution order;

[0167] In the order of execution, the index of the created fault inspection process is added to the fault inspection list.

[0168] In a specific implementation of the present application, the process determination module is specifically used to read the index from the fault inspection list in sequence;

[0169] The fault inspection process corresponding to the index is determined as the target fault inspection process.

[0170] In a specific implementation of the present application, the process execution module is specifically used to trigger the underlying hardware access thread during the execution of the target fault inspection process;

[0171] Use the underlying hardware to access the thread and collect hardware information;

[0172] Use hardware information to perform fault detection;

[0173] Among them, using hardware information for fault detection includes:

[0174] Use hardware information to detect and process alarms;

[0175] Use hardware information to detect and report events;

[0176] Use hardware information to detect faults and perform troubleshooting after faults are detected;

[0177] Among them, alarm processing includes:

[0178] Output alarm events; wherein the alarm events carry alarm information; the alarm information includes alarm event description information, event repair information and alarm detail information;

[0179] The alarm event description information includes: event description number, event description information and event classification;

[0180] Event repair information, including: event repair number and repair description information;

[0181] Alarm details, including fault location information and fault cause information.

[0182] In a specific implementation of the present application, it also includes:

[0183] A time-consuming processing module is used to use hardware information to determine whether the triggering conditions of the time-consuming action are met;

[0184] If yes, the fault inspection timer is started and the fault inspection timer is monitored;

[0185] After the fault inspection timer expires, the target fault inspection process continues to be executed.

[0186] In a specific implementation of the present application, the fault inspection list records the hardware platforms supported by the fault inspection process;

[0187] Correspondingly, the process determination module is specifically used to access the local hardware platform and collect hardware status information using the hardware collection thread;

[0188] Using hardware status information, install hardware classification and obtain hardware information;

[0189] Use hardware information to determine whether the triggering conditions for hardware inspection are met;

[0190] If so, the hardware platforms supported by the fault inspection process are recorded in the fault inspection list, the fault inspection process supporting the local hardware platform is screened out from the fault inspection list, and the determined fault inspection process is determined as the target fault inspection process.

[0191] Corresponding to the above method embodiment, the embodiment of the present application further provides an electronic device, and the electronic device described below and the hardware fault inspection method described above can refer to each other.

[0192] As shown in FIG4 , the electronic device includes:

[0193] A memory 332, for storing computer programs;

[0194] The processor 322 is used to implement the steps of the hardware fault inspection method of the above method embodiment when executing the computer program.

[0195] Specifically, please refer to FIG. 5, which is a schematic diagram of the specific structure of an electronic device provided in this embodiment. The electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors (central processing units, CPU) (for example, one or more processors) and a memory 332, and the memory 332 stores one or more computer programs 342 or data 344. Among them, the memory 332 can be a temporary storage or a permanent storage. The program stored in the memory 332 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the data processing device. Furthermore, the processor 322 can be configured to communicate with the memory 332 to execute a series of instruction operations in the memory 332 on the electronic device 301.

[0196] The electronic device 301 may further include one or more power supplies 326 , one or more wired or wireless network interfaces 350 , one or more input and output interfaces 358 , and / or one or more operating systems 341 .

[0197] The steps in the hardware fault inspection method described above can be implemented by the structure of an electronic device.

[0198] Corresponding to the above method embodiment, the embodiment of the present application further provides a readable storage medium. The readable storage medium described below and the hardware fault inspection method described above can refer to each other.

[0199] A readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the hardware fault inspection method of the above method embodiment are implemented.

[0200] The readable storage medium may specifically be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or other readable storage medium that can store program codes.

[0201] Corresponding to the above method embodiment, the embodiment of the present application further provides a computer program product. The computer program product described below and the hardware fault inspection method described above can be referred to each other.

[0202] A computer program product includes a computer program / instruction. When the computer program / instruction is executed by a processor, the steps of the above-mentioned hardware fault inspection method are implemented.

[0203] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0204] Those skilled in the art may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0205] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0206] Finally, it should be noted that, in this article, relationships such as first and second, etc. are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms include, include or any other variations are intended to cover non-exclusive inclusion, so that a process, method, article or device that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device.

[0207] Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A hardware fault inspection method, characterized in that: include: Obtain a fault inspection list; wherein the fault inspection list records the index of the fault inspection process; Using the index corresponding to the fault inspection process, determine the target fault inspection process; Execute the target fault inspection process, and if the target fault inspection process needs to execute a time-consuming task, record the interruption position of the target fault inspection process, and switch the hardware thread to execute the time-consuming task; After the time-consuming task is completed, the target fault inspection process is continued from the interruption position; After executing the target fault inspection process, the target fault inspection process is re-determined until the hardware inspection process corresponding to the fault inspection list is executed, and it is determined that the hardware inspection is completed.

2. The method according to claim 1, characterized in that: Determining that the time-consuming task is completed includes: When switching the hardware thread to execute the time-consuming task, starting a fault inspection timer; Monitoring the fault inspection timer; After the time of the fault inspection timer expires, it is determined that the time-consuming task has been completed.

3. The method according to claim 1, characterized in that Get the fault inspection list, including: Obtain hardware inspection requirement information of the local hardware platform; Using the hardware inspection requirement information, create a fault inspection process and determine the execution order; According to the execution order, the index of the created fault inspection process is added to the fault inspection list.

4. The method according to claim 3, characterized in that: Using the index corresponding to the fault inspection process, determine the target fault inspection process, including: Read the index from the fault inspection list in order; The fault inspection process corresponding to the index is determined as the target fault inspection process.

5. The method according to claim 1, characterized in that The fault inspection list records the hardware platforms supported by the fault inspection process; Accordingly, the target fault inspection process is determined by using the index corresponding to the fault inspection process, including: Access the local hardware platform and use the hardware acquisition thread to collect hardware status information; Using the hardware status information, installing hardware classification and obtaining hardware information; Using the hardware information, determine whether a triggering condition for hardware inspection is met; If so, the hardware platforms supported by the fault inspection processes are recorded in the fault inspection list, the fault inspection processes supporting the local hardware platform are screened out from the fault inspection list, and the determined fault inspection processes are determined as the target fault inspection processes.

6. The method according to claim 1, characterized in that Executing the target fault inspection process includes: During the execution of the target fault inspection process, triggering the underlying hardware access thread; Utilize the underlying hardware access thread to collect hardware information; Using the hardware information, performing fault detection; Wherein, using the hardware information to perform fault detection includes: Using the hardware information, performing alarm detection and alarm processing; Utilizing the hardware information to detect events and report them; Utilizing the hardware information, performing fault detection, and after detecting the fault, performing fault elimination processing; Among them, alarm processing includes: Output alarm events; wherein the alarm events carry alarm information; the alarm information includes alarm event description information, event repair information and alarm detail information; The alarm event description information includes: event description number and event description information and event classification; The event repair information includes: event repair number and repair description information; The alarm details information includes: fault location information and fault cause information.

7. The method according to claim 6, characterized in that Also includes: Using the hardware information to determine whether a triggering condition for a time-consuming action is met; If yes, start the fault inspection timer and monitor the fault inspection timer; After the time of the fault inspection timer expires, the target fault inspection process continues to be executed.

8. A fault inspection device, characterized in that: include: A list acquisition module is used to acquire a fault inspection list; wherein the fault inspection list records the index of the fault inspection process; A process determination module is used to determine a target fault inspection process by using an index corresponding to the fault inspection process; A process execution module, used to execute the target fault inspection process, record the interruption position of the target fault inspection process when the target fault inspection process needs to execute a time-consuming task, and switch the hardware thread to execute the time-consuming task; A breakpoint resume module, used to continue executing the target fault inspection process from the interruption position after the time-consuming task is completed; The inspection completion determination module is used to re-determine the target fault inspection process after executing the target fault inspection process until the hardware inspection process corresponding to the fault inspection list is executed to determine that the hardware inspection is completed.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the hardware fault inspection method according to any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that: The readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the hardware fault inspection method according to any one of claims 1 to 7 are implemented.