A method, device, and storage medium for using BMC to capture PCIE device fault information

Abstract

The present invention relates to a method, device and storage medium for a BMC to capture PCIE device fault information, which realizes capturing PCIE device fault information through the BMC and avoids the problem of being unable to obtain PCIE device faults caused by BIOS hibernation. Before the system is powered on, the BMC connected to each PCIE device communicates to obtain the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information; after the system is powered on, the BMC sends the obtained PCIE device information to the operating system; after the operating system determines that a PCIE device fails through an error report, it sends the serial number of the faulty PCIE device to the BMC by means of in-band access to the BMC; the BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices, and the BMC uses the preset interface to re-obtain the PCIE device information of the target PCIE device, so as to realize capturing PCIE device fault information through the BMC.

Description

Technical Field

[0001] The present invention relates to the technical field of PCIE device fault capture, and particularly to a method, device and storage medium for capturing PCIE device fault information by BMC. Background Art

[0002] Connecting more PCIE devices through the PCIE bus to make the functions of the server more perfect is an important means for designing the server. For a server connected with PCIE devices, whether it can capture the fault information of each PCIE device of the server more accurately, quickly locate the cause of the fault and solve the fault has become an important criterion for customers to select the server.

[0003] The traditional solution for capturing PCIE device fault information is as follows: The BIOS obtains the PCIE device fault information, and then the BIOS sends the fault information of the PCIE device to the BMC. The BMC simply adds logs according to the sent PCIE device fault information. This solution has three main deficiencies: First, after the system boots up, the BIOS enters the sleep state and cannot obtain the PCIE device information, so it cannot capture the fault information of the PCIE device. Second, the fault information obtained by the BIOS and sent to the BMC is also very simple and insufficient for effective fault analysis. Third, when problems such as BIOS failure or communication failure between the BIOS and the PCIE device cause the BIOS to be unable to obtain the PCIE device fault information, it is impossible to effectively sense and process it in a timely manner, that is, during the process of capturing the PCIE device fault information, the faults of related influencing factors cannot be excluded in time, resulting in missed capture of the PCIE device faults. Summary of the Invention

[0004] In order to solve the above technical problems or at least partially solve the above technical problems, the present invention provides a method, device and storage medium for capturing PCIE device fault information by BMC.

[0005] In a first aspect, the present invention provides a method for capturing PCIE device fault information by BMC, including: before the system boots up, the BMC communicatively connected to each PCIE device obtains the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information; after the system boots up, the BMC sends the obtained PCIE device information to the operating system; after the operating system determines that a PCIE device has a fault through an error report, it sends the serial number of the faulty PCIE device to the BMC by means of in-band access to the BMC; the BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices, and the BMC uses the preset interface to re-obtain the PCIE device information of the target PCIE device.

[0006] Furthermore, the PCIE device information includes: PCIE device serial number, PCIE device type, PCIE device status, PCIE device fault information, and the reason for the PCIE device fault. The BMC sends an access instruction to the PCIE device according to a pre-defined interactive interface protocol to obtain the PCIE device information.

[0007] Furthermore, digital simplified encoding is pre-performed on the PCIE device type, PCIE device status, PCIE device fault information, and the reason for the PCIE device fault; the PCIE device stores and transmits the PCIE device information to the BMC in the form of digital simplified encoding.

[0008] Furthermore, the BMC connects to each PCIE device through the I2C bus. Before the system boots up, the BMC scans each PCIE device through the I2C bus, obtains the PCIE device information from the PCIE device through a pre-set interface interaction protocol, and generates a device list file using the PCIE device information of each PCIE device; the BMC sends the PCIE device information to the operating system in the form of a device list file; after the BMC re-obtains the PCIE device information of the PCIE device using the pre-set interface, it updates the device list file before booting up using the re-obtained PCIE device information.

[0009] Furthermore, after the BMC obtains the PCIE device information before the system boots up, the BMC cuts off the connection channel with the PCIE device, and generates a boot prompt after cutting off the connection channel between the BMC and the PCIE device.

[0010] Furthermore, the operating system maintains the PCIE device serial number and the presence status of the PCIE device; after the operating system obtains the PCIE device information transmitted by the BMC, it analyzes whether the present PCIE devices correspond one-to-one with the PCIE device information transmitted by the BMC. If not, the operating system refreshes the present PCIE devices and the operating system controls the BMC to re-obtain the PCIE device information of the PCIE device.

[0011] Furthermore, if the operating system refreshes the present PCIE devices and the operating system controls the BMC to re-obtain the PCIE device information of the PCIE device, and they still do not correspond one-to-one after setting a threshold number of times, then, if there is no corresponding PCIE device information for the present PCIE devices, a prompt for detecting whether there is a fault in the communication between the BMC and the PCIE device is generated; if there is no corresponding present PCIE device for the PCIE device information, a prompt for detecting whether there is a fault in the communication between the PCIE device and the operating system is generated.

[0012] Further, an on-off element for controlling the on-off of the communication link is provided on the communication link between the PCIE device and its access device. The on-off element is controlled and connected to the BMC. The BMC maintains the correspondence between the on-off element and the PCIE device serial number of the PCIE device. The BMC determines the target on-off element to be cut off based on the PCIE device serial number of the target PCIE device with a fault and controls the target on-off element to cut off the communication link between the PCIE device and its access device.

[0013] In a second aspect, the present invention provides a device for using the BMC to capture PCIE device fault information, including: a storage unit, a processor running an operating system, a BMC, a PCIE device, an on-off element, and an access device of the PCIE device. An on-off element is provided on the communication link between the PCIE device and its access device. The on-off element is controlled and connected to the BMC, and the BMC is communicatively connected to the PCIE device; the storage unit stores a program, and when the program is executed by the BMC and the processor running the operating system, the method for using the BMC to capture PCIE device fault information is implemented.

[0014] In a third aspect, the present invention provides a storage medium for implementing the method for using the BMC to capture PCIE device fault information. The storage medium stores a computer program, and is characterized in that when the computer program is executed by a processor, the method for using the BMC to capture PCIE device fault information is implemented.

[0015] The above technical solutions provided by the embodiments of the present invention have the following advantages compared with the prior art:

[0016] The present invention communicatively connects the BMC to the PCIE device; before the system boots, the BMC communicatively connected to each PCIE device obtains the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information; after the system boots, the BMC sends the obtained PCIE device information to the operating system; after the operating system determines that a PCIE device has a fault through an error report, it sends the serial number of the faulty PCIE device to the BMC by accessing the BMC in-band; the BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices, and the BMC uses the preset interface to re-obtain the PCIE device information of the target PCIE device. It realizes directly accessing the PCIE device through the independently operating BMC to obtain detailed PCIE device fault information, and solves the problem that the BIOS sleep causes the inability to capture PCIE device faults in real time.

[0017] The present invention maintains the PCIE device serial number and the corresponding presence status of the PCIE device through the operating system; after the operating system obtains the PCIE device information transmitted by the BMC, it analyzes whether the present PCIE devices correspond one-to-one with the PCIE device information transmitted by the BMC. If not, the operating system refreshes the present PCIE devices and the operating system controls the BMC to re-obtain the PCIE device information of the PCIE devices, avoiding the problem of missed recording of PCIE device failures caused by communication problems between the BMC and the PCIE devices or abnormal communication between the PCIE devices and the operating system. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings herein are incorporated into and constitute a part of this specification, showing embodiments consistent with the present invention and, together with the specification, are used to explain the principles of the present invention.

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0020] Figure 1 It is a flowchart of a method for using a BMC to capture PCIE device fault information provided by an embodiment of the present invention;

[0021] Figure 2 It is a flowchart of a BMC that communicates with each PCIE device to obtain the PCIE device information of each PCIE device through a preset interface before the system is powered on, provided by an embodiment of the present invention;

[0022] Figure 3 It is a flowchart of an operating system for detecting factors affecting PCIE fault capture by analyzing whether the presence status of the PCIE device corresponds one-to-one with the PCIE device information obtained by the BMC, provided by an embodiment of the present invention;

[0023] Figure 4 It is a schematic diagram of a multi-controller hot-plug recording device provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention.

[0025] It should be noted that in this article, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not explicitly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising said element.

[0026] Embodiment 1

[0027] Refer to Figure 1 As shown, the present invention provides a method for a BMC to capture PCIE device fault information, including:

[0028] S100, before the system boots up, the BMC communicatively connected to each PCIE device obtains the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information. The BMC itself is configured with an independent operating system and can operate independently when the system is shut down.

[0029] During the specific implementation process, refer to Figure 2 As shown, S101, configure the pressing of the system power-on key to first trigger the BMC to obtain the PCIE device information of the PCIE device.

[0030] S102, the BMC obtains the PCIE device information of each PCIE device through a preset interface.

[0031] S103, after the BMC obtains the PCIE device information before the system boots up, the BMC cuts off the connection channel with the PCIE device to avoid communication conflicts between the PCIE device and the BIOS during startup.

[0032] S104, generate a power-on prompt after the BMC cuts off the connection channel with the PCIE device, and the power-on prompt triggers the continuation of the power-on process.

[0033] Specifically, the PCIE device information includes: PCIE device serial number, PCIE device type, PCIE device status, PCIE device fault information, PCIE device fault reason, and the BMC sends an access instruction to the PCIE device according to a predefined interactive interface protocol to obtain the PCIE device information.

[0034] In a feasible implementation manner, the BMC connects to each PCIE device through the I2C bus. Before the system boots up, the BMC scans each PCIE device through the I2C bus and obtains the PCIE device information from the PCIE device through a preset interface interaction protocol.

[0035] In a feasible implementation, digital simplified encoding is pre - performed on the PCIE device type, PCIE device status, PCIE device fault information, and PCIE device fault reason; the PCIE device stores and transmits the PCIE device information to the BMC in the form of digital simplified encoding. The BMC parses the corresponding meaning according to the obtained digital simplified encoding.

[0036] In a feasible implementation, a device list file is generated using the PCIE device information of each PCIE device.

[0037] S200, after the system boots up, the BMC sends the obtained PCIE device information to the operating system. In a feasible implementation, the BMC sends the PCIE device information to the operating system in the form of a device list file.

[0038] In a feasible implementation, the operating system detects the factors affecting PCIE fault capture by analyzing whether the PCIE device presence status corresponds one - to - one with the PCIE device information obtained by the BMC. Refer to Figure 3 As shown, it includes:

[0039] S1, the operating system maintains the PCIE device serial number and presence status of the PCIE device, and pre - sets the number threshold for the operating system to refresh the present PCIE devices and the operating system to control the BMC to re - obtain the PCIE device information.

[0040] S2, after the operating system obtains the PCIE device information transmitted by the BMC, it analyzes whether the present PCIE devices correspond one - to - one with the PCIE device information transmitted by the BMC. If not, S3 is executed. Specifically, the operating system finds the present PCIE devices corresponding to the missing PCIE device information and stores them in the first list. Specifically, the operating system finds the PCIE device information corresponding to the missing present PCIE devices, and extracts the PCIE device serial numbers in the PCIE device information into the second list. If both the first list and the second list are empty, the PCIE device information and the present PCIE devices correspond one - to - one; otherwise, the PCIE device information and the present PCIE devices do not correspond one - to - one.

[0041] S3, the operating system refreshes the present PCIE devices and the operating system controls the BMC to re - obtain the PCIE device information of the PCIE device. The BMC is controlled to re - traverse the PCIE devices in the first list to obtain the PCIE device information. The first list records the PCIE devices with communication problems with the BMC, and the second list records the PCIE devices with communication problems with the operating system.

[0042] S4. Detect whether the PCIE device information and the present PCIE devices correspond one by one; otherwise, execute S5. Specifically, the operating system finds the present PCIE devices corresponding to the missing PCIE device information and stores them in the first list. Specifically, the operating system finds the PCIE device information corresponding to the missing present PCIE devices, and extracts the PCIE device serial numbers in the PCIE device information into the second list. If both the first list and the second list are empty, the PCIE device information and the present PCIE devices correspond one by one; otherwise, the PCIE device information and the present PCIE devices do not correspond one by one.

[0043] S5. Detect whether the operation of the operating system to refresh the present PCIE devices and the operating system to control the BMC to re-obtain the PCIE device information of the PCIE devices reaches the set number threshold; otherwise, continue to execute S3, and if yes, execute S6.

[0044] S6. Generate corresponding prompt messages for the present PCIE devices lacking corresponding PCIE device information and the PCIE device information lacking corresponding present PCIE devices. Specifically, generate corresponding prompt messages for the PCIE devices related to the content in the first list and the second list. Generate a prompt to detect whether there is a communication failure between the BMC and the PCIE device for the PCIE devices related to the content in the first list (the present PCIE devices lacking corresponding PCIE device information); generate a prompt to detect whether there is a communication failure between the PCIE device and the operating system for the PCIE devices related to the content in the second list (the PCIE device information lacking corresponding present PCIE devices).

[0045] S300. After the operating system determines that a PCIE device has failed through an error message, send the serial number of the failed PCIE device to the BMC by accessing the BMC in-band.

[0046] S400. The BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices. The BMC uses a preset interface to re-obtain the PCIE device information of the target PCIE device. In the specific implementation process, the BMC reconnects to the PCIE device pointed to by the PCIE device serial number. After the BMC uses the preset interface to re-obtain the PCIE device information of this PCIE device, it updates the device list file before startup with the re-obtained PCIE device information.

[0047] In a feasible implementation, an on-off element for controlling the on-off of the communication link is provided on the communication link between the PCIE device and its access device. The on-off element is controllably connected to the BMC. The BMC maintains the correspondence between the on-off element and the PCIE device number of the PCIE device. The BMC determines the target on-off element to be cut off based on the PCIE device number of the faulty target PCIE device and controls the target on-off element to cut off the communication link between the PCIE device and its access device.

[0048] In a feasible implementation, the device list file is accessed and obtained through the BMC out-of-band communication interface. The user obtains the device list file through the BMC out-of-band.

[0049] Embodiment 2

[0050] Refer to Figure 4 As shown, an embodiment of the present invention provides a device for capturing PCIE device fault information using a BMC, including: a storage unit, a processor running an operating system, a BMC, a PCIE device, an on-off element, and an access device of the PCIE device. An on-off element is provided on the communication link between the PCIE device and its access device. The on-off element is controllably connected to the BMC, and the BMC is communicatively connected to the PCIE device. The storage unit stores a program, and when the program is executed by the BMC and the processor running the operating system, the method for capturing PCIE device fault information using the BMC is implemented. In the specific implementation process, the access device of the PCIE device includes a processor running an operating system.

[0051] Embodiment 3

[0052] An embodiment of the present invention provides a storage medium for implementing a method for capturing PCIE device fault information using a BMC. The storage medium stores a computer program, and when the computer program is executed by a processor, the method for capturing PCIE device fault information using the BMC is implemented.

[0053] The present invention communicatively connects a BMC with a PCIE device; before the system is powered on, the BMC communicatively connected to each PCIE device obtains the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information; after the system is powered on, the BMC sends the obtained PCIE device information to the operating system; after the operating system determines that a PCIE device has failed by reporting an error, it sends the serial number of the faulty PCIE device to the BMC by means of in-band access to the BMC; the BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices, and the BMC uses the preset interface to re-obtain the PCIE device information of the target PCIE device. It is realized that the independent BMC directly accesses the PCIE device to obtain detailed PCIE device fault information, and solves the problem that the BIOS sleep causes the inability to capture the PCIE device fault in real time.

[0054] The present invention maintains the PCIE device serial number and the corresponding presence status of the PCIE device through the operating system; after the operating system obtains the PCIE device information transmitted by the BMC, it analyzes whether the present PCIE devices correspond one by one to the PCIE device information transmitted by the BMC. If not, the operating system refreshes the present PCIE devices and the operating system controls the BMC to re-obtain the PCIE device information of the PCIE device, avoiding the problem of missed recording of PCIE device faults caused by communication problems between the BMC and the PCIE device or abnormal communication between the PCIE device and the operating system.

[0055] In several embodiments provided by the present invention, it should be understood that the disclosed methods and units can be implemented in other ways. For example, the structural embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection can be through some interfaces. The indirect coupling or communication connection of the system or unit can be in electrical, mechanical or other forms.

[0056] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place, or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0057] In addition, in each embodiment of the present invention, each functional unit may be integrated in a processing unit, may exist separately as individual physical units, or two or more units may be integrated in one unit.

[0058] Although the present invention has been described in detail by referring to the accompanying drawings and in conjunction with the preferred embodiments, the present invention is not limited thereto. Without departing from the spirit and essence of the present invention, those of ordinary skill in the art can make various equivalent modifications or substitutions to the embodiments of the present invention, and these modifications or substitutions should all fall within the scope of the present invention. / Any person skilled in the art within the technical scope disclosed by the present invention can easily think of changes or substitutions, which should all be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for using BMC to capture PCIE device fault information, characterized in that, including: The operating system maintains the PCIE device serial number and the corresponding presence status of the PCIE device; Before the system boots up, the BMC connected to each PCIE device through communication obtains the PCIE device information of each PCIE device through a preset interface, and the PCIE device information includes PCIE device fault information; after the system boots up, the BMC sends the obtained PCIE device information to the operating system; After the operating system obtains the PCIE device information transmitted by the BMC, it analyzes whether the present PCIE devices correspond one by one to the PCIE device information transmitted by the BMC. If not, the operating system refreshes the present PCIE devices and the operating system controls the BMC to re-obtain the PCIE device information of the PCIE device; After the operating system determines that a PCIE device fails through error reporting, it sends the serial number of the faulty PCIE device to the BMC by means of in-band access to the BMC; The BMC determines the target PCIE device based on the PCIE device serial number and actively cuts off the communication between the target PCIE device and other access devices, and the BMC uses a preset interface to re-obtain the PCIE device information of the target PCIE device.

2. The method for capturing PCIE device fault information using BMC according to claim 1, wherein The PCIE device information includes: PCIE device serial number, PCIE device type, PCIE device status, PCIE device fault information, PCIE device fault reason, and the BMC sends an access instruction to the PCIE device according to a pre-defined interactive interface protocol to obtain the PCIE device information.

3. The method for capturing PCIE device fault information using BMC according to claim 2, wherein The PCIE device type, PCIE device status, PCIE device fault information, and PCIE device fault reason are pre-digitally simplified and encoded; The PCIE device stores and transmits the PCIE device information to the BMC in the form of digital simplified encoding.

4. The method for capturing PCIE device fault information using BMC according to claim 1, characterized in that, The BMC is connected to each PCIE device through the I2C bus. Before the system boots up, the BMC scans each PCIE device through the I2C bus, obtains the PCIE device information from the PCIE device through a preset interface interaction protocol, and generates a device list file using the PCIE device information of each PCIE device; The BMC sends the PCIE device information to the operating system in the form of a device list file; After the BMC re-obtains the PCIE device information of the PCIE device using a preset interface, it updates the device list file before booting up using the re-obtained PCIE device information.

5. The method for capturing PCIE device fault information using BMC according to claim 1, wherein After the BMC obtains the PCIE device information before the system boots up, the BMC cuts off the connection channel with the PCIE device. After the BMC cuts off the connection channel with the PCIE device, a boot-up prompt is generated, and the boot-up prompt triggers the continued execution of the boot-up process.

6. The method for capturing PCIE device fault information using BMC according to claim 1, characterized in that, If the operation of the operating system refreshing the present PCIE devices and the operating system controlling the BMC to re-obtain the PCIE device information of the PCIE device still does not correspond one by one after reaching the set number threshold, then, if the present PCIE device lacks the corresponding PCIE device information, a prompt for detecting whether there is a fault in the communication between the BMC and the PCIE device is generated; If the PCIE device information lacks the corresponding present PCIE device, a prompt for detecting whether there is a fault in the communication between the PCIE device and the operating system is generated.

7. The method for capturing PCIE device fault information using BMC according to claim 1, wherein, A break-make element for controlling the on / off of a communication link is provided on the communication link between the PCIE device and its access device. The break-make element is controllably connected to the BMC. The BMC maintains the correspondence between the break-make element and the PCIE device number of the PCIE device. The BMC determines the target break-make element to be cut off based on the PCIE device number of the target PCIE device with a fault and controls the target break-make element to cut off the communication link between the PCIE device and its access device.

8. A device for capturing PCIE device fault information using BMC, characterized in that, Including: A storage unit, a processor running an operating system, a BMC, a PCIE device, a break-make element, and an access device of the PCIE device. A break-make element is provided on the communication link between the PCIE device and its access device. The break-make element is controllably connected to the BMC, and the BMC is communicatively connected to the PCIE device; The storage unit stores a program, and when the program is executed by the BMC and the processor running the operating system, it implements the method for the BMC to capture PCIE device fault information as described in any one of claims 1-7.

9. A storage medium for implementing a method of using BMC to capture PCIE device fault information, the storage medium stores a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for the BMC to capture PCIE device fault information as described in any one of claims 1-7.

Images