All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
	dvhart@infradead.org, wim@iguana.be
Cc: linux-watchdog@vger.kernel.org
Subject: Re: Can't query Intel's iTCO watchdog reboot reason
Date: Sat, 16 Jul 2016 10:18:41 -0700	[thread overview]
Message-ID: <578A6C71.8080705@roeck-us.net> (raw)
In-Reply-To: <CAAEAJfAEKvLCk2gjj6MR00t-Yg_-XEG1qb0ij6jse=FV3ez5bw@mail.gmail.com>

On 07/15/2016 04:21 PM, Ezequiel Garcia wrote:
> Hi everyone,
>
> A large portion of my intel-based products are suffering from
> a nasty hardware freeze [1], and so I'm currently working this around
> enabling the iTCO watchdog -- which in any case, it's a good idea
> to have enabled.
>
> So, it would be interesting to find out on each boot if the machine was
> rebooted due to a watchdog timeout, but so far I'm not having any luck.
>
> As per Intel's appnote [2] the BIOS should update the WDDT ACPI table,
> so I added something like this to the iTCO driver:
>
>         status = acpi_get_table(ACPI_SIG_WDDT, 1,
>                                 (struct acpi_table_header **) &buf);
>         if (ACPI_FAILURE(status) || buf->header.length < sizeof(*buf)) {
>                 pr_err(FW_BUG "failed to get WDDT ACPI table\n");
>                 return;
>         }
>
> But it doesn't find the table. Strangely, reading TCO1_STS
> and TCO2_STS always gives 0x0.
>

That sounds like either the BIOS resets those bits, or the reboots
are not caused by the watchdog. Are you sure that you see reboots
that are caused by the watchdog ?

Guenter

> Tests were done on a Lynx Point:
>
> [    7.131502] iTCO_wdt: Found a Lynx Point TCO device (Version=2,
> TCOBASE=0x1860)
>
> Any ideas? Is it possible to get this information or should I just gave up?
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=109051
> [2] http://download.intel.com/design/chipsets/applnots/29227301.pdf
>
> Thanks!
>


  reply	other threads:[~2016-07-16 17:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 23:21 Can't query Intel's iTCO watchdog reboot reason Ezequiel Garcia
2016-07-16 17:18 ` Guenter Roeck [this message]
2016-07-17 22:13   ` Ezequiel Garcia
2016-07-19 16:21     ` Ezequiel Garcia

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=578A6C71.8080705@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=dvhart@infradead.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=wim@iguana.be \
    /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.