From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, minyard@acm.org
Subject: Re: IPMI watchdog question
Date: Wed, 28 Jul 2004 12:46:27 +0200 [thread overview]
Message-ID: <200407281246.27304.arekm@pld-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407281021530.31636@praktifix.dwd.de>
On Wednesday 28 of July 2004 12:33, Holger Kiehl wrote:
> > Do you have CONFIG_WATCHDOG_NOWAYOUT enabled?
>
> No this is not set. Must this be set? Actually I want that one can stop the
> watchdog gracefully. And this is done by writting a 'V' to /dev/watchdog,
> correct?
Without CONFIG_WATCHDOG_NOWAYOUT (or nowayout=1 module option added by my
patch just sent to lkml) when /dev/watchdog is closed then watchdog timer is
disabled.
> I noticed that CONFIG_WATCHDOG is also not set since CONFIG_IPMI_WATCHDOG
> is set under IPMI. Must this be set?
Currently these two are unrelated in technical terms.
> Is the IPMI watchdog different to
> all the other watchdogs or why is it listed seperatly?
CONFIG_WATCHDOG only purpose is to disable all watchdogs living in
drivers/char/watchdog directory, nothing more. Enabling it doesn't add any
code unless you also add some specific watchdog.
ipmi_watchdog relies on IPMI (IPMI_HANDLER) and probably that's why it's
listed separatly.
> Holger
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux
next prev parent reply other threads:[~2004-07-28 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 9:08 IPMI watchdog question Holger Kiehl
2004-07-28 9:29 ` Arkadiusz Miskiewicz
2004-07-28 10:33 ` Holger Kiehl
2004-07-28 10:46 ` Arkadiusz Miskiewicz [this message]
2004-08-02 12:02 ` Holger Kiehl
2004-08-02 15:35 ` Corey Minyard
2004-08-02 16:29 ` Arkadiusz Miskiewicz
2004-08-02 16:51 ` Corey Minyard
2004-08-02 17:05 ` Arkadiusz Miskiewicz
2004-08-03 8:46 ` Holger Kiehl
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=200407281246.27304.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=Holger.Kiehl@dwd.de \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.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