From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: David Madore <david+ml@madore.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Linux Kernel mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: iTCO_wdt watchdog on Asus P10S-WS motherboard FREEZES MOTHERBOARD COMPLETELY
Date: Wed, 21 Sep 2016 10:24:16 -0300 [thread overview]
Message-ID: <20160921132416.GA5574@khazad-dum.debian.net> (raw)
In-Reply-To: <20160921121041.GA20766@achernar.madore.org>
On Wed, 21 Sep 2016, David Madore wrote:
> On Tue, Sep 20, 2016 at 03:50:09PM +0300, Mika Westerberg wrote:
> > Does the machine have WDAT ACPI table (see /sys/firmware/acpi/tables/*)?
> > If it does, you can try the new WDAT watchdog driver instead [1]. It
> > still uses the same hardware, though but via set of instructions
> > provided by the BIOS that should work (given the vendor has tested
> > it on Windows).
> >
> > [1] http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1230607.html
>
> Thanks for pointing this out. My motherboard's BIOS does not have
> this ACPI table, unfortunately, but it's at least good to know that
> some do, and take the hardware watchdog seriously.
The ones that take the hardware watchdog seriously will command the
power supply to do a power cycle when it triggers, which pretty much
cuts power to everything that is not hanging off the +5VSB (standby
power) line.
Let's just say that SSDs don't like it, at all. Avoid at *all* *costs*.
I have been using the kernel's software watchdog on most systems because
of that: it just soft-reboots, which is good enough almost every time
and doesn't mess with the SSDs.
The proper fix is to have two levels of watchdogs, a soft reboot on time
T for the first level, and a power cycle on time 5T (to give the BIOS
enough of a time window to reset the second level watchdog during a soft
reboot).
--
Henrique Holschuh
prev parent reply other threads:[~2016-09-21 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 17:01 David Madore
2016-09-20 12:50 ` Mika Westerberg
2016-09-21 12:10 ` David Madore
2016-09-21 13:24 ` Henrique de Moraes Holschuh [this message]
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=20160921132416.GA5574@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=david+ml@madore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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
all inboxes | Powered by JetHome®