From: Guenter Roeck <linux@roeck-us.net>
To: Nicolas Boullis <nboullis@debian.org>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: Linux-compatible watchdog add-on?
Date: Mon, 29 Aug 2016 16:53:01 -0700 [thread overview]
Message-ID: <20160829235301.GA2073@roeck-us.net> (raw)
In-Reply-To: <20160825163149.GB3636@haddock.home>
On Thu, Aug 25, 2016 at 06:31:49PM +0200, Nicolas Boullis wrote:
> Hi,
>
> Sorry if my question is off-topic for this list.
>
> I have a computer that experienced a kernel failure while a was far away
> and nobody could reboot it. So I thought it would be nice to have a
> watchdog. Unfortunately, to the best of my knowledge, it has no hardware
> watchdog, so I thought I should add one.
>
> Hence, do you have suggestions for I²C-, serial- or USB-connected
> watchdog add-ons? It should of course be compatible with linux.
>
> I found
> http://www.berkprod.com/Product_Web_Pages/usb_v1_pc_watchdog.aspx
> but I think it is a little too expensive.
>
> If no such thing exists, I might consider designing my own (open
> hardware) I²C- or USB-connected watchdog add-on, using a cheap MCU. But
> then I would welcome opinions on what the interface between the host and
> watchdog should look like.
>
Anything you come up with will need a connection to the system reset,
so you'll have to have an in-chassis solution. Any cheap MCU with USB
or I2C port and a couple of GPIO ports would probably do.
If you consider the above product, make sure that you get an assurance
that its Linux driver still works - it is quite old.
Guenter
prev parent reply other threads:[~2016-08-29 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 16:31 Linux-compatible watchdog add-on? Nicolas Boullis
2016-08-26 4:58 ` Oleksij Rempel
2016-08-26 23:14 ` Nicolas Boullis
2016-08-27 11:38 ` Oleksij Rempel
2016-08-29 23:53 ` Guenter Roeck [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=20160829235301.GA2073@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=nboullis@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).