Linux-Watchdog Archive on
 help / color / Atom feed
From: Guenter Roeck <>
To: "Uwe Kleine-König" <>
Cc: Wim Van Sebroeck <>,,
Subject: Re: What to set in struct watchdog_device::bootstatus?
Date: Thu, 9 May 2019 20:53:42 -0700
Message-ID: <> (raw)
In-Reply-To: <>

On 5/9/19 12:25 PM, Uwe Kleine-König wrote:
> Hello Guenter,
> On Wed, Feb 20, 2019 at 09:14:08PM +0100, Uwe Kleine-König wrote:
>> In a custom kernel patch stack I found a patch that uses (apart from
>> differentiate the different reset causes. Now that you told using this
>> is wrong, I wonder how these are supposed to be used instead; and there
>> are a few more that according to
>> Documentation/watchdog/watchdog-kernel-api.txt might be used to set
>> bootstatus. Are these a relic? What do these signal?
> I'm still interested in an answer here. While it is currently not
> possible to "fix" the custom kernel as some other software that is
> already shipping depends on this. Still I'd like to know the details
> here to maybe suggest an alternative for the longterm future.
>> IMHO there is a patch opportunity waiting to improve the documenation
>> :-) Or maybe even change watchdog_get_status() to ensure that only

The basic problem, as I see it, is that the bits were defined a long time
ago as standard API, even tough they really only apply to a small subset
of watchdog cards. Personally I tend to believe that any set of bits
would be insufficient. Maybe it should have been a string. Either case,
I don't believe in forcing more or less random reboot reasons into a
given set of bits. On the other side I also don't see the point in
arbitrarily limiting the bit values returned by WDIOC_GETSTATUS.
With that, my general approach would be some kind of report-what-makes-sense
approach. But using WDIOF_POWERUNDER for "power cycle" just goes a bit too


      reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-08 10:52 Uwe Kleine-König
2019-02-08 14:05 ` Guenter Roeck
2019-02-20 20:14   ` Uwe Kleine-König
2019-05-09 19:25     ` Uwe Kleine-König
2019-05-10  3:53       ` Guenter Roeck [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Watchdog Archive on

Archives are clonable:
	git clone --mirror linux-watchdog/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-watchdog linux-watchdog/ \
	public-inbox-index linux-watchdog

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox