diff options
author | Sui Chen <suichen@google.com> | 2022-01-05 04:33:31 +0300 |
---|---|---|
committer | Sui Chen <suichen@google.com> | 2022-01-05 04:43:05 +0300 |
commit | 11b7ccf247c14c9c0a0ecde299c45318ff7067a4 (patch) | |
tree | 80f0d95a2d421b7e622e5481d13d92da0f5ac1b8 | |
parent | 27849ef7c0a5d88a4497b840ebaf9d33830663fe (diff) | |
download | openbmc-11b7ccf247c14c9c0a0ecde299c45318ff7067a4.tar.xz |
meta-google: Increase hardware watchdog timeout to 60s
When running an image with a certain version of QEMU, the emulated BMC
may enter bootloop due to the Watchdog not getting petted for more than
10s.
One can check this by monitoring
s->tim[1]->watchdog_timer.base_timer.expires_ns in QEMU (where s may be
an NPCM7xxState or similar hardware state object).
Reverting the timeout to 60s seems to resolve the issue with QEMU usage.
Signed-off-by: Sui Chen <suichen@google.com>
Change-Id: I29313ff67415003d5f82f0f8a5cc1703b34fb2c0
-rw-r--r-- | meta-google/recipes-google/systemd/files/40-system.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta-google/recipes-google/systemd/files/40-system.conf b/meta-google/recipes-google/systemd/files/40-system.conf index 5f770d01f0..601e0a5abb 100644 --- a/meta-google/recipes-google/systemd/files/40-system.conf +++ b/meta-google/recipes-google/systemd/files/40-system.conf @@ -1,4 +1,4 @@ [Manager] DefaultMemoryAccounting=yes -RuntimeWatchdogSec=10s +RuntimeWatchdogSec=60s WatchdogDevice=/dev/watchdog |