mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: LM Sensors <sensors@stimpy.netroedge.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFT] Preliminary w83627ehf hardware monitoring driver
Date: Mon, 28 Feb 2005 09:50:12 +0200	[thread overview]
Message-ID: <20050228075012.GN25818@edu.joroinen.fi> (raw)
In-Reply-To: <20050227184837.2563a454.khali@linux-fr.org>

On Sun, Feb 27, 2005 at 06:48:37PM +0100, Jean Delvare wrote:
> Hi Pasi,
> 
> > Do you know about driver for W83627THF watchdog? I'm using Supermicro
> > P8SCI motherboard, and I haven't found working driver for it..
> 
> Have you tried w83627hf_wdt? I took a quick look at the W83627HF and
> W83627THF datasheets and watchdog timer seems to work identically. Since
> the driver doesn't seem to identify the chip (it probably should, BTW),
> I'd expect it to work.
> 

Yes, I have tried it. It doesn't work. 

The machine reboots always after the watchdog timeout set in the BIOS. I've
tried with the example watchdog daemon from the watchdog.txt, and with the
Debian "watchdog" package.

When I enable the debug messages and logging in the Debian watchdog package,
I can see that the watchdog daemon gets stuck while trying to update the
/dev/watchdog.. so the driver hangs..

-- Pasi Kärkkäinen
       
                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.

  reply	other threads:[~2005-02-28  7:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-26 18:11 Jean Delvare
2005-02-27 13:10 ` Pasi Kärkkäinen
2005-02-27 17:48   ` Jean Delvare
2005-02-28  7:50     ` Pasi Kärkkäinen [this message]
2005-02-28 11:00       ` Jean Delvare
2005-02-28 11:19         ` P

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=20050228075012.GN25818@edu.joroinen.fi \
    --to=pasik@iki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@stimpy.netroedge.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®