Fault elastic start watchdog function test method, device and program product
By generating test configuration files and automatically identifying and flexibly activating the watchdog timer, the inefficiency of existing testing methods is solved, achieving a highly efficient and automated testing process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHANGHAI EVEX INFORMATION TECHNOLOGY CO LTD
- Filing Date
- 2025-12-17
- Publication Date
- 2026-05-08
AI Technical Summary
Existing fault elastic start watchdog function testing methods require the collection of faulty hardware, resulting in low testing efficiency and low repeatability, making it difficult to perform multiple repeated tests quickly and efficiently.
By generating a test configuration file, importing it into the test machine, sending hot reset and debugging commands, simulating the fault initialization state, obtaining the event log of the baseboard management controller, and automatically determining whether the fault elastic start watchdog function is normal.
It eliminates the need to collect faulty hardware, enabling fully automated testing, improving testing efficiency and repeatability, lowering the testing threshold, and allowing non-professionals to complete the tests.
Smart Images
Figure CN121996539A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of server technology, and in particular to a fault-tolerant watchdog function testing method, device, and program product. Background Technology
[0002] The fault-tolerant start watchdog is a watchdog timer for the server's fault-tolerant start phase. Its function is to start a firmware-level timer during the fault-tolerant start phase to monitor timeouts. If the server fails to complete the fault-tolerant start phase on time, the server firmware will trigger a preset recovery mechanism after the timer expires in order to attempt to restore the server to normal operation.
[0003] Therefore, to ensure the proper functioning of the fault-tolerant start watchdog timer, functional testing of the watchdog timer is necessary. Existing methods for testing fault-tolerant start watchdog timers primarily involve installing faulty hardware on the server motherboard to create an abnormal initialization state for the server's basic input / output system. This causes the server to get stuck in the hardware initialization phase during startup, triggering the fault-tolerant start watchdog timer to check if its functionality is normal.
[0004] However, this testing approach requires testers to collect faulty hardware for fault testing, and each test requires rebuilding the test environment using the faulty hardware, making it difficult to perform repeated tests quickly and efficiently, resulting in low testing efficiency and low test repeatability. Summary of the Invention
[0005] This application provides a fault-tolerant start watchdog function testing method, device, and program product to solve the technical problems of low testing efficiency and low test repeatability in existing fault-tolerant start watchdog function testing schemes.
[0006] According to a first aspect disclosed in this application, this application provides a fault-tolerant start-up watchdog function testing method, applied to an actuator, wherein the actuator is connected to at least one test machine to be tested, the method comprising:
[0007] A test configuration file is generated based on the test information, and the test configuration file is imported into the test machine; wherein, the test information includes a timeout period and a timeout policy corresponding to the timeout period;
[0008] Send a hot reset command to the test machine; wherein the hot reset command is used to instruct the test machine to enter the initialization phase of the basic input / output system;
[0009] During the initialization phase of the basic input / output system, a debugging command is sent to the test machine, and a timer is started; wherein, the debugging command is used to instruct the CPU of the test machine to enter debug mode;
[0010] When the timeout period is reached, the event log of the baseboard management controller of the test machine is retrieved;
[0011] Based on the event log, determine whether the watchdog timer function of the test machine is working properly.
[0012] In one feasible implementation, determining whether the fault elastic start watchdog function of the test machine is normal, based on the event log, includes:
[0013] Based on the event log, the operation event corresponding to the timeout period of the baseboard management controller is obtained;
[0014] If the operation event is consistent with the timeout policy, then the watchdog timer function is determined to be normal.
[0015] In one feasible implementation, the method further includes:
[0016] If the operation event is inconsistent with the timeout policy, then the watchdog timer function is determined to be faulty.
[0017] In one feasible implementation, the method further includes, before sending a thermal reset command to the test machine:
[0018] A restart command is sent to the test machine; wherein the restart command is used to instruct the test machine to perform a restart operation;
[0019] After the test machine restarts, obtain the current configuration file of the fault elastic startup watchdog.
[0020] If the current configuration file matches the test configuration file, a hot reset command is sent to the test machine.
[0021] In one feasible implementation, the method further includes:
[0022] If the current configuration file does not match the test configuration file, then proceed to the step of generating a test configuration file based on the test information and importing the test configuration file into the test machine.
[0023] In one feasible implementation, the method further includes, before sending debugging instructions to the test machine:
[0024] Send an unlock command to the test machine; wherein the unlock command is used to instruct the CPU of the test machine to unlock;
[0025] If the CPU is successfully unlocked, a debugging command is sent to the test machine.
[0026] In one feasible implementation, the test configuration file further includes a functional state configured as an enabled state.
[0027] According to a second aspect disclosed in this application, this application provides a fault-tolerant start-up watchdog function testing device, applied to an actuator, wherein the actuator is connected to at least one test machine to be tested, the device comprising:
[0028] A configuration import module is used to generate a test configuration file based on test information and import the test configuration file into the test machine; wherein, the test information includes a timeout period and a timeout policy corresponding to the timeout period;
[0029] The instruction input module is used to send a hot reset instruction to the test machine; wherein the hot reset instruction is used to instruct the test machine to enter the initialization phase of the basic input / output system; and is used to send a debug instruction to the test machine and start timing during the initialization phase of the basic input / output system; wherein the debug instruction is used to instruct the CPU of the test machine to enter debug mode.
[0030] The log acquisition module is used to acquire the event log of the baseboard management controller of the test machine when the timeout period is reached.
[0031] The function detection module is used to determine, based on the event log, whether the fault elastic start watchdog function of the test machine is normal.
[0032] According to a third aspect disclosed in this application, this application provides an electronic device, including a processor and a memory communicatively connected to the processor;
[0033] The memory stores computer-executed instructions;
[0034] The processor executes computer execution instructions stored in the memory to implement the method described in any one of the first aspects.
[0035] According to the fourth aspect disclosed in this application, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed, are used to implement the method described in any one of the first aspects.
[0036] According to the fifth aspect disclosed in this application, this application provides a computer program product, including a computer program, which, when executed, is used to implement the method described in any one of the first aspects.
[0037] Compared with the prior art, this application has the following beneficial effects:
[0038] This application provides a fault-tolerant watchdog timer function testing method, device, and program product. Firstly, compared to traditional testing methods, it eliminates the need for testers to collect faulty CPUs, faulty memory, faulty peripheral high-speed serial devices, and other necessary hardware, saving on spare parts costs and conserving testers' time and effort. Secondly, the fault-tolerant watchdog timer function testing process can be fully automated, eliminating the need to rebuild the test environment using faulty hardware, resulting in high test repeatability and improved testing efficiency. Finally, it lowers the barrier to entry for fault-tolerant watchdog timer function testing, allowing even non-professionals to successfully complete the testing process. Attached Figure Description
[0039] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.
[0040] Figure 1 A schematic diagram of the system architecture of a fault-tolerant start-up watchdog function testing system provided in this application embodiment;
[0041] Figure 2 A flowchart illustrating a fault-tolerant start-up watchdog function testing method provided in this application embodiment;
[0042] Figure 3 A flowchart illustrating another fault-tolerant start-up watchdog function testing method provided in this application embodiment;
[0043] Figure 4 A schematic diagram of a fault-tolerant start-up watchdog function testing device provided in this application embodiment;
[0044] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.
[0045] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0046] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.
[0047] The failover phase is a crucial stage in the server's transition from firmware (UEFI) boot to loading the operating system (such as Linux or Windows Server). During this phase, the firmware needs to complete critical operations such as hardware detection, driver initialization, and identification of boot devices (e.g., hard drives, RAID cards). Only when all operations in this phase are successfully completed can the server smoothly enter the operating system loading phase.
[0048] The fault-tolerant startup watchdog is a watchdog timer specifically designed for the fault-tolerant startup phase of servers. Its main functions are twofold: First, timeout monitoring; a firmware-level timer is started simultaneously during the fault-tolerant startup phase. The timeout period of this timer can usually be configured according to actual needs, typically ranging from 30 seconds to 5 minutes. If, during the fault-tolerant startup process, hardware failure (such as disk corruption, memory errors, etc.), firmware errors, or configuration conflicts cause the startup process to stall and fail to complete the various operations of the fault-tolerant startup phase on time, the timer will time out. Second, automatic recovery; once the timer times out, the firmware will immediately trigger a preset recovery mechanism, such as forcing the server to stop in the fault state phase so that testers can conduct detailed troubleshooting; or forcing the server to perform a hot reset, attempting to restart the server without a complete power outage; or forcing the server to shut down and then restart; or forcing the server to perform a cold reset, i.e., completely powering off and then restarting the server, in order to attempt to restore the server to normal operation.
[0049] Therefore, to ensure the proper functioning of the fault-tolerant boot watchdog, functional testing of the watchdog is necessary. Currently, existing methods for testing fault-tolerant boot watchdogs primarily involve constructing an abnormal initialization state of the server's Basic Input Output System (BIOS) by installing a faulty CPU, faulty memory, or faulty peripheral high-speed serial device on the server motherboard. This causes the server to get stuck in the hardware initialization phase during startup, triggering the fault-tolerant boot watchdog timer. When the timer expires, the server's Baseboard Management Controller (BMC) performs shutdown, warm reboot, or cold reboot operations to attempt to restore the server to a normal state.
[0050] However, this testing approach has several problems. On the one hand, testers need to collect the necessary hardware, such as faulty memory and faulty peripheral high-speed serial devices, which requires a significant amount of time and effort to find and prepare. On the other hand, this testing method requires rebuilding the test environment using the faulty hardware for each test, making it difficult to perform repeated tests quickly and efficiently, resulting in low testing efficiency and low repeatability.
[0051] To address the aforementioned technical issues, this application proposes a fault-tolerant start watchdog function testing method, equipment, and program product, which significantly improves the testing efficiency and repeatability of fault-tolerant start watchdog function testing.
[0052] The technical solutions for the fault-tolerant start-up watchdog function testing method, equipment, and program product provided in this application are described in detail below through specific embodiments. It should be noted that the following embodiments may exist independently or in combination with each other; for the same or similar content, descriptions may not be repeated in different embodiments.
[0053] Below, in conjunction with Figure 1 The system architecture involved in the fault elastic start watchdog function test method of this application is described.
[0054] Figure 1 A schematic diagram of the system architecture of a fault-tolerant start-up watchdog function testing system provided in this application embodiment is shown below. Figure 1 The system architecture includes an actuator 101 and at least one test machine 102. The actuator 101 is connected to the test machine 102 to test the watchdog function of the test machine 102 in case of failure.
[0055] In this embodiment, when the test machine 102 needs to be tested for the fault elastic start watchdog function, the executor 101 and the test machine 102 are first connected via wired or wireless means. Then, the executor 101 generates a corresponding test configuration file based on the test information and imports the test configuration file into the test machine 102 to change the configuration of the fault elastic start watchdog in the test machine 102. After the configuration of the test machine 102 is modified, the executor 101 sends a hot service command to the test machine 102 to restart the test machine 102 and enter the initialization phase of the basic input / output system. While the test machine 102 is in the initialization phase of the basic input / output system, the executor 101 sends a debug command to the test machine 102 and starts timing, so that the CPU of the test machine 102 enters debug mode to simulate the abnormal initialization state of the basic input / output system. When the timing reaches the timeout time configured in the test, the event log of the baseboard management controller of the test machine 102 is obtained, and the time log is used to determine whether the test machine 102 executes the configured timeout policy to determine whether the fault elastic start watchdog function is normal.
[0056] It should be noted that, Figure 1 This is merely a schematic diagram of a system architecture provided in an embodiment of this application. This embodiment does not represent... Figure 1 The document does not limit the actual form of the various devices included, nor does it specify the form of the devices. Figure 1 The interaction or connection methods between various devices are limited, and can be set according to actual needs in the specific application of the technical solution.
[0057] It should be noted that the execution subject of the fault elastic start watchdog function test method provided in this application embodiment is the execution machine, and correspondingly, the fault elastic start watchdog function test device is also set in the execution machine.
[0058] Figure 1 A flowchart illustrating a fault-tolerant start-up watchdog function testing method provided in this application embodiment is shown below. Figure 1 In some embodiments, this fault-tolerant start watchdog function testing method is applied to an actuator connected to at least one test machine to be tested, and its specific process includes the following steps:
[0059] S201, Generate a test configuration file based on the test information and import the test configuration file into the test machine; wherein, the test information includes the timeout period and the timeout policy corresponding to the timeout period.
[0060] Among them, a test configuration file is generated based on test information including timeout time and timeout policy, and this test configuration file is used to test the watchdog function of the test machine's fault elastic startup.
[0061] Optionally, the test configuration file may also include a feature state, which is configured to be enabled.
[0062] Specifically, by configuring the function status in the test configuration file to the enabled state, the watchdog function is resiliently started in case of a test machine failure, ensuring the smooth progress of the test.
[0063] Specifically, the configuration file for the server failure elastic startup watchdog can be in JSON format. An example configuration file is shown below:
[0064] "Fault Resilient Startup": "Enable",
[0065] "Fault-based flexible start timeout": [3,4,5]
[0066] "Fault-Resilience Startup Timeout Strategy": ["Hot Reset", "Shutdown", "Cold Reset"]
[0067] }
[0068] Among them, "Fault Elastic Startup" indicates the functional status of the server's fault elastic startup watchdog, "Enable" indicates that the fault elastic startup watchdog function is enabled, "Fault Elastic Startup Timeout" indicates the time the server is in the fault elastic startup phase, and "Fault Elastic Startup Timeout Policy" indicates the operation policy to be executed after the server's fault elastic startup phase timeout.
[0069] Therefore, the configuration file indicates that when the test server is in the fault elastic startup phase for more than 3 minutes, 4 minutes, and 5 minutes respectively, the server will sequentially perform hot reset, shutdown, and cold reset operations to attempt to restore the server to a normal state.
[0070] When testing the test machine, if the configuration file includes multiple timeouts and timeout policies, it is impossible to complete a full test of all functions of the fault-tolerant startup watchdog. For example, if the function of performing a hot reset is normal when the timeout period is 4 minutes, then a hot reset will be performed every time at this stage, making it impossible to test the subsequent 5-minute shutdown operation and the 6-minute cold reset operation.
[0071] Therefore, the test configuration file only configures one function of the fault elastic start watchdog for testing. If multiple functions need to be tested, the corresponding test configuration file is generated separately and the test machine is tested multiple times to achieve a complete test of all functions of the fault elastic start watchdog.
[0072] Specifically, the test configuration file example is as follows:
[0073] "Fault Resilient Startup": "Enable",
[0074] "Fault-based flexible restart timeout": 3.
[0075] "Fault-Resilient Startup Timeout Strategy": "Hot Reset"
[0076] }
[0077] Therefore, the test configuration file indicates that if the test machine is in the fault resilience startup phase for more than 3 minutes, the test machine will perform a hot reset operation to attempt to restore the server to a normal state.
[0078] Specifically, the timeout period can be flexibly adjusted according to actual testing needs, such as 3 minutes, 4 minutes, 5 minutes, 6 minutes, etc.
[0079] Specifically, the timeout strategy can be flexibly adjusted according to actual testing needs, such as hot reset, shutdown, cold reset, etc.
[0080] S202, send a hot reset command to the test machine; the hot reset command is used to instruct the test machine to enter the initialization phase of the basic input / output system.
[0081] After importing the test configuration file into the test machine, a hot reset command is sent to the test machine so that the test machine can enter the initialization phase of the basic input / output system by restarting.
[0082] Specifically, the initialization phase of the basic input / output system is a critical process to ensure that the system can correctly identify, configure and manage hardware devices, mainly involving hardware detection, device driver loading, and system parameter configuration.
[0083] S203, during the initialization phase of the basic input / output system, sends a debugging command to the test machine and starts timing; the debugging command is used to instruct the CPU of the test machine to enter debug mode.
[0084] During the initialization phase of the basic input / output system, a debug command is sent to the test machine to put its CPU into debug mode. In debug mode, all CPU cores are suspended, and the server startup will be suspended at this stage. Ultimately, it can simulate the abnormal initialization state of input / output, that is, simulate the stuck state of fault elastic startup, and start timing.
[0085] S204: When the timeout period is reached, retrieve the event log of the baseboard management controller of the test machine.
[0086] Specifically, when the timing reaches the timeout period, which refers to the time the test machine has been in the fault-tolerant startup phase and has exceeded the timeout period configured in the test configuration file, the Baseboard Management Controller (BMC) of the test machine will execute the corresponding timeout policy according to the contents of the test configuration file if the fault-tolerant startup watchdog function is normal. If the fault-tolerant startup watchdog function is abnormal, the Baseboard Management Controller of the test machine will not execute the corresponding timeout policy according to the contents of the test configuration file.
[0087] Since all events performed by the baseboard management controller are recorded in the event log, the event log of the baseboard management controller of the test machine is obtained for further judgment.
[0088] Specifically, the baseboard management controller is a dedicated controller used to monitor and manage servers. It operates as an independent system, independent of the server's main hardware and operating system. It achieves functions such as remote management, status monitoring, and fault early warning through a dedicated interface, and is the core component of server management.
[0089] S205, based on the event log, determines whether the watchdog timer function of the test machine's fault elastic startup is normal.
[0090] Specifically, the operation records in the event log are used to determine whether the baseboard management controller of the test machine has executed the corresponding timeout policy, thereby determining whether the watchdog timer function of the test machine is working properly.
[0091] In this embodiment, firstly, compared to traditional testing methods, testers are no longer required to collect the necessary hardware such as faulty CPUs, faulty memory, and faulty peripheral high-speed serial devices, saving on spare parts costs and conserving testers' time and effort. Secondly, the fault-tolerant start-up watchdog function testing process can be fully automated, eliminating the need to rebuild the test environment using faulty hardware, resulting in high test repeatability and improved testing efficiency. Finally, the barrier to entry for fault-tolerant start-up watchdog function testing is lowered, allowing even non-professionals to successfully complete the testing process.
[0092] exist Figure 2 Based on the embodiments shown, the following is combined with Figure 3 The technical solution for the above-mentioned fault elastic start watchdog function test method is further introduced.
[0093] Figure 3 A flowchart illustrating another fault-tolerant start watchdog function testing method provided in this application embodiment is shown below. Figure 3 In some embodiments, the fault resilience start watchdog function test method includes the following steps:
[0094] S301 generates a test configuration file based on the test information and imports the test configuration file into the test machine; the test information includes the timeout period and the timeout policy corresponding to the timeout period.
[0095] S302 sends a restart command to the test machine; the restart command is used to instruct the test machine to perform a restart operation.
[0096] After importing the test configuration file into the test machine, a restart command is used to cause the test machine to restart.
[0097] S303: After the test machine restarts, obtain the current configuration file of the fault elastic startup watchdog.
[0098] After the test machine restarts, the current configuration file of the test machine's fault elastic startup watchdog is obtained.
[0099] Specifically, the execution machine pings the test machine's OS IP address from outside the execution machine until the ping is successful, confirming that the test machine has fully entered the system. Then, the execution machine exports the test machine's configuration file using the SCE tool from within the execution machine.
[0100] S304 matches the current configuration file with the test configuration file.
[0101] Specifically, for matching configuration files, taking JSON-formatted configuration files as an example: first, the two JSON configuration files are parsed into data structures in memory, and then all key-value pairs of the two data structures are recursively compared to determine whether they match by checking the existence of the key and the equality of the corresponding value.
[0102] S305: If the current configuration file matches the test configuration file, a hot reset command is sent to the test machine.
[0103] If the current configuration file of the test machine matches the test configuration file, it means that the test configuration file has been successfully imported into the test machine, and the subsequent test process can continue.
[0104] S306. If the current configuration file does not match the test configuration file, proceed to step S301.
[0105] If the current configuration file of the test machine does not match the test configuration file, it indicates that the test configuration file has failed to be successfully imported into the test machine. In this case, the process jumps to step S301 and re-imports the test configuration file into the test machine.
[0106] S307 sends an unlock command to the test machine; the unlock command is used to instruct the CPU of the test machine to unlock.
[0107] This involves sending an unlock command to the test machine to ensure that the CPU of the test machine is in an unlocked state, thereby ensuring that the CPU can enter the debug mode normally.
[0108] For example, taking the test machine as an AMD platform CPU, the execution machine opens the Go-Pi command line and connects to the test machine's BMC IP address. With the help of the preset script, the unlock() function is sent to unlock the CPU of the test machine. After unlocking, the isLock() function is sent to confirm that the CPU is now in the unlocked state. If it returns true, it means that the CPU has been successfully unlocked. If it returns false, it means that the CPU is in the locked state.
[0109] If the CPU is successfully unlocked, the S308 sends a debugging command to the test machine and starts timing.
[0110] For example, taking the test machine as an AMD platform CPU, the execution machine opens the Go-Pi command line and sends the pdm() command to make the AMD CPU enter pdm mode. At this time, the server startup will be suspended at the current stage because all the CPU cores are in a suspended state. In the end, it can simulate the abnormal initialization state of input and output, and start the timer (hour:minute:second).
[0111] S309: When the timeout period is reached, retrieve the event log of the baseboard management controller of the test machine.
[0112] S310, based on the event log, obtains the operation event corresponding to the timeout period of the baseboard management controller.
[0113] Based on the information recorded in the event log, the corresponding operation event executed by the baseboard management controller during the timeout period can be obtained.
[0114] S311 compares the operation event with the timeout policy.
[0115] S312, if the operation event is consistent with the timeout policy, then the watchdog timer function is confirmed to be working properly.
[0116] If the operation event matches the timeout policy, it indicates that the fault elastic startup watchdog of the test machine has executed the timeout policy in the test configuration file, and the fault elastic startup watchdog is functioning normally.
[0117] S313 If the operation event is inconsistent with the timeout policy, the watchdog timer function is determined to be faulty.
[0118] If the operation event matches the timeout policy, it indicates that the fault elastic start watchdog of the test machine has not executed the timeout policy in the test configuration file, and the fault elastic start watchdog is malfunctioning.
[0119] In this embodiment, the comparison results between this application and traditional testing methods are shown in Table 1.
[0120] Table 1. Comparison of Test Parameters
[0121]
[0122] Figure 4 This is a schematic diagram of a fault-tolerant start-up watchdog function testing device provided in an embodiment of this application. (See attached diagram.) Figure 4 The fault-tolerant start watchdog function test device includes various functional modules for implementing the aforementioned fault-tolerant start watchdog function test method. Any functional module can be implemented by software and / or hardware.
[0123] In some embodiments, the fault-tolerant start watchdog function testing device 400 is applied to an actuator, which is connected to at least one test machine to be tested, and includes a configuration import module 401, an instruction input module 402, a log acquisition module 403, and a function detection module 405. Wherein:
[0124] The configuration import module 401 is used to generate a test configuration file based on the test information and import the test configuration file into the test machine; wherein, the test information includes the timeout time and the timeout policy corresponding to the timeout time;
[0125] The instruction input module 402 is used to send a hot reset instruction to the test machine; wherein the hot reset instruction is used to instruct the test machine to enter the initialization phase of the basic input / output system; and is used to send a debug instruction to the test machine and start timing during the initialization phase of the basic input / output system; wherein the debug instruction is used to instruct the CPU of the test machine to enter debug mode;
[0126] The log acquisition module 403 is used to acquire the event log of the baseboard management controller of the test machine when the timing time reaches the timeout period;
[0127] The function detection module 404 is used to determine whether the fault elastic start watchdog function of the test machine is normal based on the event log.
[0128] In some embodiments, the function detection module 404 is specifically used for:
[0129] Based on the event log, obtain the operation events of the baseboard management controller corresponding to the timeout period;
[0130] If the operation event matches the timeout policy, then the watchdog timer function is confirmed to be working correctly.
[0131] In some embodiments, the function detection module 404 is further configured to:
[0132] If the operation event is inconsistent with the timeout policy, it is determined that the watchdog timer function is malfunctioning.
[0133] In some embodiments, before sending a thermal reset command to the test machine, the command input module 402 is further configured to:
[0134] Send a restart command to the test machine; the restart command is used to instruct the test machine to perform a restart operation.
[0135] After the test machine restarts, retrieve the current configuration file of the fault elastic startup watchdog.
[0136] If the current configuration file matches the test configuration file, a hot reset command is sent to the test machine.
[0137] In some embodiments, the instruction input module 402 is further configured to:
[0138] If the current configuration file does not match the test configuration file, proceed to the step of generating a test configuration file based on the test information and importing the test configuration file into the test machine.
[0139] In some embodiments, before sending debugging instructions to the test machine, the instruction input module 402 is further configured to:
[0140] Send an unlock command to the test machine; the unlock command is used to instruct the CPU of the test machine to unlock.
[0141] If the CPU is successfully unlocked, a debugging command is sent to the test machine.
[0142] In some embodiments, the test configuration file also includes a functional state configured as an enabled state.
[0143] The fault-tolerant start watchdog function test device 400 provided in this application embodiment is used to execute the technical solution provided in the aforementioned fault-tolerant start watchdog function test method embodiment. Its implementation principle and technical effect are similar to those in the aforementioned method embodiment, and will not be repeated here.
[0144] It should be noted that the division of the various modules in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, these modules can be implemented entirely in software via processing element calls, entirely in hardware, or partially in software calls via processing element calls, with some modules implemented in hardware. For example, the configuration import module 401 can be a separate processing element, or it can be integrated into a chip in the above device. Alternatively, it can be stored as program code in the memory of the above device, and its functions can be called and executed by a processing element of the device. The implementation of other modules is similar. Moreover, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules can be completed through integrated logic circuits in the hardware of the processor element or through software instructions.
[0145] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. (See attached diagram.) Figure 5 The electronic device 500 includes a processor 501 and a memory 502 communicatively connected to the processor 501;
[0146] Memory 502 stores instructions executed by the computer;
[0147] The processor 501 executes the computer execution instructions stored in the memory 502 to implement the technical solution of the aforementioned fault elastic start watchdog function test method.
[0148] In the aforementioned electronic device 500, the memory 502 and the processor 501 are electrically connected directly or indirectly to achieve data transmission or interaction. For example, these components can be electrically connected to each other through one or more communication buses or signal lines, such as bus connections. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be classified as address buses, data buses, control buses, etc., but this does not mean that there is only one bus or one type of bus. The memory 502 stores computer execution instructions that implement the aforementioned fault-tolerant start-up watchdog function test method, including at least one software function module that can be stored in the memory 502 in the form of software or firmware. The processor 501 executes various functional applications and data processing by running the software program and module stored in the memory 502.
[0149] The memory 502 includes at least one type of readable storage medium, not limited to Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory 502 stores programs, and the processor 501 executes the programs after receiving execution instructions. Furthermore, the software programs and modules within the memory 502 may also include an operating system, which may include various software components and / or drivers for managing system tasks (e.g., memory management, storage device control, power management, etc.) and can communicate with various hardware or software components to provide an operating environment for other software components.
[0150] Processor 501 can be an integrated circuit chip with signal processing capabilities. The aforementioned processor 501 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor, or processor 501 can be any conventional processor.
[0151] The electronic device 500 is used to execute the technical solution provided in the aforementioned fault elastic start watchdog function test method embodiment. Its implementation principle and technical effect are similar to those in the aforementioned method embodiment, and will not be repeated here.
[0152] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed, implement the technical solution of the aforementioned fault-tolerant start-up watchdog function test method.
[0153] The aforementioned computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The computer-readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0154] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Alternatively, the readable storage medium can be an integral part of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components within the control unit of a fault-tolerant start-up watchdog function test apparatus.
[0155] This application also provides a computer program product, including a computer program, which, when executed, is used to implement the technical solution of the aforementioned fault-tolerant start-up watchdog function test method.
[0156] In the above embodiments, those skilled in the art will understand that the above method embodiments can be implemented entirely or partially by software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented entirely or partially in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless network, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
[0157] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.
[0158] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.
[0159] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.
Claims
1. A method for testing a fault-tolerant start-up watchdog function, characterized in that, Applied to an actuator, the actuator being connected to at least one test machine to be tested, the method includes: A test configuration file is generated based on the test information, and the test configuration file is imported into the test machine; wherein, the test information includes a timeout period and a timeout policy corresponding to the timeout period; Send a hot reset command to the test machine; wherein the hot reset command is used to instruct the test machine to enter the initialization phase of the basic input / output system; During the initialization phase of the basic input / output system, a debugging command is sent to the test machine, and a timer is started; wherein, the debugging command is used to instruct the CPU of the test machine to enter debug mode; When the timeout period is reached, the event log of the baseboard management controller of the test machine is retrieved; Based on the event log, determine whether the watchdog timer function of the test machine is working properly.
2. The method according to claim 1, characterized in that, Based on the event log, determine whether the watchdog timer function of the test machine's fault elastic startup is normal, including: Based on the event log, the operation event corresponding to the timeout period of the baseboard management controller is obtained; If the operation event is consistent with the timeout policy, then the watchdog timer function is determined to be normal.
3. The method according to claim 2, characterized in that, The method further includes: If the operation event is inconsistent with the timeout policy, then the watchdog timer function is determined to be faulty.
4. The method according to claim 1, characterized in that, Before sending a thermal reset command to the test machine, the method further includes: A restart command is sent to the test machine; wherein the restart command is used to instruct the test machine to perform a restart operation; After the test machine restarts, obtain the current configuration file of the fault elastic startup watchdog. If the current configuration file matches the test configuration file, a hot reset command is sent to the test machine.
5. The method according to claim 4, characterized in that, The method further includes: If the current configuration file does not match the test configuration file, then proceed to the step of generating a test configuration file based on the test information and importing the test configuration file into the test machine.
6. The method according to any one of claims 1-5, characterized in that, Before sending debugging commands to the test machine, the method further includes: Send an unlock command to the test machine; wherein the unlock command is used to instruct the CPU of the test machine to unlock; If the CPU is successfully unlocked, a debugging command is sent to the test machine.
7. The method according to any one of claims 1-5, characterized in that, The test configuration file also includes a functional state, which is configured to be enabled.
8. An electronic device, characterized in that, Includes a processor and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1 to 7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, are used to implement the method as described in any one of claims 1 to 7.
10. A computer program product, characterized in that, Includes a computer program, which, when executed, is used to implement the method as described in any one of claims 1 to 7.