From: Guenter Roeck <linux@roeck-us.net>
To: Naveen Kumar P <naveenkumar.parna@gmail.com>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: iTCO watchdog last reboot reason?
Date: Tue, 4 Aug 2020 10:18:57 -0700 [thread overview]
Message-ID: <b5123504-7ed0-1a4b-e796-6a9a7f91419e@roeck-us.net> (raw)
In-Reply-To: <CAMciSVVq7LL+c6Va1xqcCfMMMqcM9+3DXsOi+6cyqjPfdLgpGA@mail.gmail.com>
On 8/4/20 10:09 AM, Naveen Kumar P wrote:
> On Tue, Aug 4, 2020 at 9:45 PM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> On 8/4/20 7:41 AM, Naveen Kumar P wrote:
>>> [ Please keep me in CC as I'm not subscribed to the list]
>>>
>>> Hi everyone,
>>>
>>> I enabled the iTCO watchdog in my Linux system.
>>>
>>> sudo cat /dev/watchdog perfectly reboots my system. But, is there a
>>> way to find out on each boot if the machine was rebooted due to a
>>> watchdog timeout or not?
>>>
>>> Any ideas?
>>>
>>
>> If the hardware supports it, the driver could set the reboot reason
>> in its probe function.
> Thank you Guenter for the quick response. Can you please point me to
> the corresponding patch?
I didn't say that one exists, nor that it is possible to actually implement
what I suggested. I only stated a possibility. Please feel free to implement,
test, and submit such a patch yourself.
Thanks,
Guenter
prev parent reply other threads:[~2020-08-04 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 14:41 iTCO watchdog last reboot reason? Naveen Kumar P
2020-08-04 16:15 ` Guenter Roeck
2020-08-04 17:09 ` Naveen Kumar P
2020-08-04 17:18 ` Guenter Roeck [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=b5123504-7ed0-1a4b-e796-6a9a7f91419e@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=naveenkumar.parna@gmail.com \
/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).