From: Guenter Roeck <linux@roeck-us.net>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Jean Delvare <jdelvare@suse.de>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org,
Wim Van Sebroeck <wim@linux-watchdog.org>,
linux-watchdog@vger.kernel.org, Tom Abraham <tabraham@suse.com>
Subject: Re: Forcing non-ACPI watchdog driver
Date: Wed, 5 Feb 2020 08:30:48 -0800 [thread overview]
Message-ID: <20200205163048.GD25403@roeck-us.net> (raw)
In-Reply-To: <20200205152435.GE2667@lahna.fi.intel.com>
On Wed, Feb 05, 2020 at 05:24:35PM +0200, Mika Westerberg wrote:
> On Wed, Feb 05, 2020 at 04:05:29PM +0100, Jean Delvare wrote:
> > Hi all,
>
> Hi,
>
> > Is there a way to prevent the ACPI WDAT watchdog interface from being
> > used and force the use of a native watchdog driver instead?
> >
> > I have a customer who reports a regression on kernel upgrade. Old
> > kernel (v4.4) uses iTCO_wdt and watchdog works, new kernel (v4.12) uses
> > wdat_wdt and watchdog doesn't work (instant reboot when opening the
> > device). While I'm going to look for fixes to backport, I think it
> > would be pretty convenient to have a way to just revert to the working
> > driver until the new driver is fixed somehow. But I can't see any way
> > to do that at the moment, short of disabling ACPI completely, which is
> > definitely too extreme to be considered.
> >
> > Am I missing something?
>
> You should be able to revert to iTCO_wdt by simply disabling
> CONFIG_WDAT_WDT from .config. Then acpi_has_watchdog() returns false
> which means that iTCO_wdt is used instead.
That may not be possible in a generic distribution.
Guenter
next prev parent reply other threads:[~2020-02-05 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 15:05 Forcing non-ACPI watchdog driver Jean Delvare
2020-02-05 15:24 ` Mika Westerberg
2020-02-05 16:30 ` Guenter Roeck [this message]
2020-02-05 16:38 ` Mika Westerberg
2020-02-06 14:45 ` Jean Delvare
2020-02-06 14:56 ` Mika Westerberg
2020-02-06 15:50 ` Rafael J. Wysocki
2020-02-06 16:00 ` Rafael J. Wysocki
2020-02-06 19:14 ` Mika Westerberg
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=20200205163048.GD25403@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=tabraham@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.