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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMciSVVq7LL+c6Va1xqcCfMMMqcM9+3DXsOi+6cyqjPfdLgpGA@mail.gmail.com>
Date:   Tue, 4 Aug 2020 22:39:16 +0530
From:   Naveen Kumar P <naveenkumar.parna@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: iTCO watchdog last reboot reason?

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?
>
> Guenter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ