From: Don Zickus <dzickus@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-watchdog@vger.kernel.org, kexec@lists.infradead.org,
wim@iguana.be, LKML <linux-kernel@vger.kernel.org>,
vgoyal@redhat.com, dyoung@redhat.com
Subject: Re: [PATCH v3] watchdog: Add hook for kicking in kdump path
Date: Wed, 24 Apr 2013 10:42:26 -0400 [thread overview]
Message-ID: <20130424144226.GI79013@redhat.com> (raw)
In-Reply-To: <20130418145413.GA1980@roeck-us.net>
On Thu, Apr 18, 2013 at 07:54:13AM -0700, Guenter Roeck wrote:
> > No, that will probably work. It is my misunderstanding. Is there a
> > common way to check the timeout length and the ping frequency?
> >
> Usually it is configured in /etc/watchdog.conf if the watchdog package
> is installed. The standard ping interval is "interval", the timeout is
> "watchdog-timeout". See "man watchdog.conf" for details.
>
> Minimum and maximum values for a given watchdog driver are not exported
> to user space, so you would have to look into the driver sources to find
> out what they are.
Hi Guenter,
Is there an easy way to determine which driver is loaded for each
/dev/watchdogN device (from a script perspective).
Basically, I wanted to determine the module that needs to be included in
the kdump initrd image.
Thanks,
Don
next prev parent reply other threads:[~2013-04-24 14:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 21:19 [PATCH v3] watchdog: Add hook for kicking in kdump path Don Zickus
2013-04-17 21:33 ` Guenter Roeck
2013-04-17 21:49 ` Eric W. Biederman
2013-04-18 3:03 ` Guenter Roeck
2013-04-18 13:00 ` Don Zickus
2013-04-18 13:49 ` Guenter Roeck
2013-04-18 13:52 ` Don Zickus
2013-04-18 14:54 ` Guenter Roeck
2013-04-24 14:42 ` Don Zickus [this message]
2013-04-24 15:21 ` Guenter Roeck
2013-05-27 19:16 ` Wim Van Sebroeck
2013-05-28 1:10 ` Guenter Roeck
2013-05-30 20:37 ` Wim Van Sebroeck
2013-05-28 15:34 ` Guenter Roeck
2013-05-30 21:54 ` Wim Van Sebroeck
2013-04-18 16:35 ` Eric W. Biederman
2013-04-18 17:44 ` Don Zickus
2013-04-18 18:09 ` Eric W. Biederman
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=20130424144226.GI79013@redhat.com \
--to=dzickus@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=vgoyal@redhat.com \
--cc=wim@iguana.be \
/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).