From: octave klaba <oles@ovh.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: watchdog software
Date: Fri, 01 Dec 2000 20:35:07 +0100 [thread overview]
Message-ID: <3A27FD6B.9CC7CA65@ovh.net> (raw)
In-Reply-To: <E141rHA-0000In-00@the-village.bc.nu>
Alan Cox wrote:
>
> > > > my question is:
> > > > what kind of problem can have this serveur:
> > > > hardware or software ?
> > >
> > > What sort of watchdog are you using ?
> >
> > software. no hardware solution.
> > http://www.ibiblio.org/pub/Linux/system/daemons/watchdog/watchdog-5.1.tar.gz
>
> The software watchdog will fail if the kernel is badly mashed or interrupts
> are disabled.
yes.
> That means it doesn't help tell me if the problem was hardware
> or software (nor in general do hardware watchdogs). Is this one box running
> different loads to the others or different in any notable way ?
nothing really different. we have 5-6 servers like this one and
this one have been crashed for 2 days only (once per day).
never before !? when the server crashed the load was 1.2. nothing
really bad.
the only difference is: this server has the serial cart. I was
in contact with Ted for the serial problem on Linux, but I have
no news from about the crashs.
I do not know if the serial cart can crash the server that
interrupts are disabled ?
Octave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-01 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 12:28 watchdog software octave klaba
2000-12-01 13:06 ` Alan Cox
2000-12-01 14:06 ` octave klaba
2000-12-01 14:34 ` Alan Cox
2000-12-01 19:35 ` octave klaba [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=3A27FD6B.9CC7CA65@ovh.net \
--to=oles@ovh.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 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.