From: Tao Ren <taoren@fb.com>
To: "Jerry.Hoemann@hpe.com" <jerry.hoemann@hpe.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH] watchdog: core: suppress "watchdog did not stop" message
Date: Tue, 27 Nov 2018 06:11:46 +0000 [thread overview]
Message-ID: <12D0F3A5-602E-4C4B-908D-55C3C50823BB@fb.com> (raw)
In-Reply-To: <20181127013117.GB11080@anatevka>
On 11/26/18, 5:31 PM, "Jerry Hoemann" <jerry.hoemann@hpe.com> wrote:
> Tao,
>
> If you're on a system running systemd, the default behavior is to
> enable the watchdog during shutdown. This guards against shutdown hanging.
> So this message will be routinely printed out during orderly shutdown.
Thank you Jerry for the comments.
I actually use a separate daemon process to kick the watchdog on my BMC system. The daemon monitors temperature sensors and other system states and kicks watchdog periodically: if the daemon gets stuck or exits, then the machine needs to reboot even if kernel/systemd is fine. Perhaps I need to look for a better/official way to manage the watchdog device..
BTW, I will be travelling abroad in the new few days and may not be able to reply emails timely. Thank you again for jumping in.
Best regards,
Tao Ren
prev parent reply other threads:[~2018-11-27 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 23:44 [PATCH] watchdog: core: suppress "watchdog did not stop" message Tao Ren
2018-11-16 0:19 ` Guenter Roeck
2018-11-16 0:37 ` Tao Ren
2018-11-27 1:31 ` Jerry Hoemann
2018-11-27 6:11 ` Tao Ren [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12D0F3A5-602E-4C4B-908D-55C3C50823BB@fb.com \
--to=taoren@fb.com \
--cc=jerry.hoemann@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=openbmc@lists.ozlabs.org \
--cc=wim@linux-watchdog.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).