docs/designs/bmc-reboot-cause-update.md

13 vendors to record different types of BMC reboot cause event logs. The purpose of
14 this proposal is to update the existing method, consolidating more BMC reboot
19 In the current approach, the only defined reboot causes are **WDIOF_EXTERN1**
22 cover all possible reboot causes. In this update, we will add support for
28    corresponding BMC reboot cause.
29 2. Each BMC vendor needs to record the results of the retrieved reboot cause to
31 3. Each vendor needs to ensure the accuracy of interpreting the reboot cause
33 4. New reboot cause types need to be defined to cover the requirements
34 5. Revise the definitions of certain existing reboot cause types to better
43     A[BMC reboot] --> B[Driver get the reboot cause]
44 …B --> C[Driver set the corresponding flag based on the reboot cause to /sys/class/watchdog/watchdo…
49 After a BMC reboot, each BMC vendor’s driver first retrieves the reboot cause.
50 Then, based on the reboot cause, it sets different flags to the specified path.
52 determine the type of reboot cause. Finally, it generates the corresponding
55 This process ensures accurate logging and handling of different BMC reboot
61 - Each BMC vendor must provide a driver to retrieve the BMC reboot cause and
64 2. Redefining Reboot Cause Type **WDIOF_EXTERN1**:
79 5. Update Reboot Cause Interpretation:
89 - After interpreting the reboot cause, the system should issue the corresponding
102 1. Common reboot causes across vendors can be consolidated to issue a unified
104 2. If any functions rely on the original reboot cause, the code must be adjusted
114 Reboot the BMC under various conditions and check whether the corresponding