From: Guenter Roeck <linux@roeck-us.net>
To: Marc van der Wal <x0r+kernel@x0r.fr>, Wim Van Sebroeck <wim@iguana.be>
Cc: linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] it87_wdt: Work around non-working CIR interrupts
Date: Sun, 09 Mar 2014 19:29:16 -0700 [thread overview]
Message-ID: <531D237C.5070400@roeck-us.net> (raw)
In-Reply-To: <20140306093659.GA24854@freyja>
On 03/06/2014 01:36 AM, Marc van der Wal wrote:
> From: Marc van der Wal <x0r+kernel@x0r.fr>
>
> On some hardware platforms, the it87_wdt watchdog resets the machine
> despite the watchdog daemon running and writing to /dev/watchdog.
>
> This is due to Consumer IR buffer underrun interrupts being used as
> triggers to reset the timer. On some buggy hardware implementations
> such as the iEi AFL-12A-N270 single-board computer, this method does
> not work.
>
> However, resetting the timer by writing its original timeout value in
> its configuration register over and over again suppresses the unwanted
> reboots.
>
> Add a module option (nocir), 0 by default in order not to break existing
> setups. Setting it to 1 enables the workaround.
>
> Fixes bug #42801 <https://bugzilla.kernel.org/show_bug.cgi?id=42801>.
> Tested primarily on Linux 3.5.7, applies cleanly on Linux 3.13.5.
>
> Signed-off-by: Marc van der Wal <x0r+kernel@x0r.fr>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2014-03-10 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 9:36 [PATCH] it87_wdt: Work around non-working CIR interrupts Marc van der Wal
2014-03-10 2:29 ` Guenter Roeck [this message]
2014-03-15 19:40 ` Wim Van Sebroeck
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=531D237C.5070400@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wim@iguana.be \
--cc=x0r+kernel@x0r.fr \
/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