| commit | a92dc027c4532d20ba94c96ab7029d74fad6e6cb | [log] [tgz] |
|---|---|---|
| author | Deepa Karthikeyan <deepakala.karthikeyan@ibm.com> | Tue Apr 16 03:45:57 2024 -0500 |
| committer | Deepa Karthikeyan <deepakala.karthikeyan@ibm.com> | Thu Apr 18 15:48:18 2024 +0000 |
| tree | 75dd23423535b1716082f2a26907585191144504 | |
| parent | 4d9adc0f6c1f7f1f75b64ff2a01b669ae4d61013 [diff] |
Disable host watchdog during dump collection Host watchdog to be disabled during hostboot and hardware dump collection. During a checkstop attention, the system is not functioning normally. So a hardware or hostboot dump is collected and it could take a while to get completed. If the watchdog timer is active during that time, it may get triggered. As we already know the system is not functioning normally and are collecting dump, disable the watchdog when the dump collection is in progress. Tested and ensured that one dump is created during a checkstop. From the logs was able to identify that the host watchdog is disabled just when the dump collection starts and host watchdog resumes after the dump collection. It is verified for both hardware dump and hostboot dump Change-Id: I5f9df253594f9e858ca0477acb3ce1f3a4639785 Signed-off-by: deepakala-k <deepakala.karthikeyan@ibm.com>
In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.
Aditional details TBD.
For a standard OpenBMC release build, you want something like:
meson -Dtests=disabled <build_dir> ninja -C <build_dir> ninja -C <build_dir> install
For a test / debug build, a typical configuration is:
meson -Dtests=enabled <build_dir> ninja -C <build_dir> test