Mailinglist Archive: opensuse-bugs (4655 mails)

< Previous Next >
[Bug 1042933] kernel panic due to nmi caused by systemd-watchdog test
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 16 Jun 2017 08:04:51 +0000
  • Message-id: <bug-1042933-21960-cwchYW4TkV@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1042933
http://bugzilla.suse.com/show_bug.cgi?id=1042933#c10

--- Comment #10 from Thomas Blume <thomas.blume@xxxxxxxx> ---
(In reply to Borislav Petkov from comment #9)
So, I guess this is the reason why the watchdog timer expires, triggering
the panic.

So I still am unclear as to why exactly the NMI fires. The test sets
the watchdog timeout to 10 seconds. That would mean, the test runs for
longer than 10 seconds, yes?

You hit the nail.
The watchdog test takes ages.
Increasing the timeout to 100s let the test succeeds:

-->
teviot:/systemd-testsuite/run # ./test-watchdog
Hardware watchdog 'HPE iLO2+ HW Watchdog Timer', version 0
Set hardware watchdog to 1min 40s.
Pinging...
Pinging...
[ 5266.922072] systemd-journald[401]: Sent WATCHDOG=1 notification.

Pinging...
[ 5336.922068] systemd-journald[401]: Sent WATCHDOG=1 notification.
Pinging...
Pinging...
[ 5446.922087] systemd-journald[401]: Sent WATCHDOG=1 notification.
teviot:/systemd-testsuite/run #
--<

The only question is now why it takes so long on SUSE whereas on RH/Debian 10s
are apparently sufficient.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References