From: Guenter Roeck <linux@roeck-us.net>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-watchdog@vger.kernel.org, linux-pci@vger.kernel.org,
wim@linux-watchdog.org
Subject: Re: watchdog: how to enable?
Date: Sat, 16 Nov 2019 08:01:35 -0800 [thread overview]
Message-ID: <e5b24949-5215-9d3d-ca45-cab221d4f58a@roeck-us.net> (raw)
In-Reply-To: <CAHhAz+iSXZSY012-jNx_wmNmgx_UiHZ4rjxkCUcHk3CjLc9gDg@mail.gmail.com>
On 11/15/19 7:03 PM, Muni Sekhar wrote:
[ ... ]
>>
>> Another possibility, of course, might be to enable a hardware watchdog
>> in your system (assuming it supports one). I personally would not trust
>> the NMI watchdog because to detect a system hang, after all, there are
>> situations where even NMIs no longer work.
>
>>From dmesg , Is it possible to know whether my system supports
> hardware watchdog or not?
> I assume that my system supports the hardware watchdog , then how to
> enable the hardware watchdog to debug the system freeze issues?
>
Hardware watchdog support really depends on the board type. Most PC
mainboards support a watchdog in the Super-IO chip, but on some it is
not wired correctly. On embedded boards it is often built into the SoC.
The easiest way to see if you have a watchdog would be to check for the
existence of /dev/watchdog. However, on a PC that would most likely
not be there because the necessary module is not auto-loaded.
If you tell us your board type, or better the Super-IO chip on the board,
we might be able to help.
Note though that this won't help to debug the problem. A hardware
watchdog resets the system. It helps to recover, but it is not intended
to help with debugging.
Guenter
next prev parent reply other threads:[~2019-11-16 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:35 watchdog: how to enable? Muni Sekhar
2019-11-16 1:04 ` Guenter Roeck
2019-11-16 3:03 ` Muni Sekhar
2019-11-16 16:01 ` Guenter Roeck [this message]
2019-11-16 18:34 ` Muni Sekhar
2019-11-16 21:42 ` Guenter Roeck
2019-11-18 9:52 ` Muni Sekhar
2019-11-18 14:10 ` Guenter Roeck
2019-11-18 15:07 ` Muni Sekhar
2019-11-18 14:38 ` Bjorn Helgaas
2019-11-18 14:41 ` Bjorn Helgaas
2019-11-18 15:09 ` Muni Sekhar
2019-11-22 10:59 ` Guenter Roeck
2019-11-22 12:54 ` Muni Sekhar
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=e5b24949-5215-9d3d-ca45-cab221d4f58a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-pci@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=munisekharrms@gmail.com \
--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).