linux-kernel - Re: iTCO watchdog last reboot reason?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <b5123504-7ed0-1a4b-e796-6a9a7f91419e@roeck-us.net>
Date:   Tue, 4 Aug 2020 10:18:57 -0700
From:   Guenter Roeck <linux@...ck-us.net>
To:     Naveen Kumar P <naveenkumar.parna@...il.com>
Cc:     linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: iTCO watchdog last reboot reason?

On 8/4/20 10:09 AM, Naveen Kumar P wrote:
> On Tue, Aug 4, 2020 at 9:45 PM Guenter Roeck <linux@...ck-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