From: Hans de Goede <hdegoede@redhat.com>
To: Jose Noguera <jnoguera@redhat.com>,
wim@linux-watchdog.org, linux-watchdog@vger.kernel.org,
linux@roeck-us.net
Cc: Peter Robinson <perobins@redhat.com>
Subject: Re: [Watchdog drivers] - WDIOC_GETSUPPORT clarification
Date: Wed, 18 Aug 2021 14:53:09 +0200 [thread overview]
Message-ID: <a6287ec5-3b44-5a65-0534-18b1ebc09348@redhat.com> (raw)
In-Reply-To: <CAKu6O181WOq36RCDO0VPcsZZoUFAJ88BMqv0Hqf+qYCeZsMJtQ@mail.gmail.com>
Hi,
On 8/18/21 11:57 AM, Jose Noguera wrote:
> Hello all!
>
> I’m Jose, working in Red Hat on Fedora IoT and RHEL For Edge related projects.
>
> While trying to add the feature of figuring out whether the current boot was triggered or not by a hardware watchdog using wdctl, we’ve found an odd behaviour in the drivers definition that we would like to check with you.
>
> Looking specifically for the flag WDIOF_CARDRESET, we can find 40 files that contain it:
>
> $ grep -rl CARDRESET drivers/watchdog/ | wc -l
> 40
>
> but only 19 of them have the flag advertised in the options field of the watchdog_info struct returned by the WDIOC_GETSUPPORT ioctl.
>
> This leads to wdctl not showing WDIOF_CARDRESET for drivers like i6300esb, even when the board had been reset this way:
>
> $ sudo wdctl
> Device: /dev/watchdog0
> Identity: i6300ESB timer [version 0]
> Timeout: 30 seconds
> Pre-timeout: 0 seconds
>
> FLAG DESCRIPTION STATUS BOOT-STATUS
> KEEPALIVEPING Keep alive ping reply 1 0
> MAGICCLOSE Supports magic close char 0 0
> SETTIMEOUT Set timeout (in seconds) 0 0
>
> Working with Hans (in CC), we added a little patch (BugZilla ticket: 1993983) on wdctl
To be clear, Jose is talking about this bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1993983
And this is the util-linux commit with the little workaround-patch:
https://github.com/karelzak/util-linux/commit/b1b0259fe42aad1bf0997ce1c03a020ce59e38ab
> and this would be the output of the command when it was a card reset triggered boot:
>
> $ sudo wdctl
> Device: /dev/watchdog0
> Identity: i6300ESB timer [version 0]
> Timeout: 30 seconds
> Pre-timeout: 0 seconds
>
> FLAG DESCRIPTION STATUS BOOT-STATUS
> CARDRESET Card previously reset the CPU 1 1
> KEEPALIVEPING Keep alive ping reply 1 0
> MAGICCLOSE Supports magic close char 0 0
> SETTIMEOUT Set timeout (in seconds) 0 0
>
> So our question is, may we know what is intended to be present in ident.options? What should the API call WDIOC_GETSUPPORT return in the options field?
Regards,
Hans
next parent reply other threads:[~2021-08-18 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKu6O181WOq36RCDO0VPcsZZoUFAJ88BMqv0Hqf+qYCeZsMJtQ@mail.gmail.com>
2021-08-18 12:53 ` Hans de Goede [this message]
2021-08-18 14:13 ` [Watchdog drivers] - WDIOC_GETSUPPORT clarification Guenter Roeck
2021-08-18 14:49 ` Hans de Goede
2021-08-18 14:53 ` Guenter Roeck
2021-09-01 11:15 ` Peter Robinson
2021-09-01 19:51 ` Guenter Roeck
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=a6287ec5-3b44-5a65-0534-18b1ebc09348@redhat.com \
--to=hdegoede@redhat.com \
--cc=jnoguera@redhat.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=perobins@redhat.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).