From: ralf@uni-koblenz.de
To: LetherGlov@aol.com, linux@cthulhu.engr.sgi.com
Subject: Re: Running Linux on Linus
Date: Mon, 22 Jun 1998 11:11:54 +0200 [thread overview]
Message-ID: <19980622111154.I418@uni-koblenz.de> (raw)
In-Reply-To: <f48fe728.358c76bd@aol.com>; from LetherGlov@aol.com on Sat, Jun 20, 1998 at 10:58:04PM -0400
On Sat, Jun 20, 1998 at 10:58:04PM -0400, LetherGlov@aol.com wrote:
> In response to the ideas floating around about running Linux on Linus,
> I think that before you give Bob Mende and William Earl tons of work
> configuring it (and rebooting), that If I understand things correctly it is a
> good idea to enable the Watchdog features of the Dallas 1386 clock, so that if
> there are any kernel panics or troubles or whatever may occur that the
> watchdog would automatically restart linus in the event that the kernel was
> no-longer updating the timer.
Talking about the Dallas chip, we still don't have proper Dallas RTC
support (/proc/rtc rsp. /dev/rtc), so we currently cannot even adjust
the rtc under Linux. Definately a must before we switch.
I had my headaches about the stability of the kernel - I should probably
given them up. I'm running crashless and hickupless since two weeks
even though I've been trying hard to stress the system and trigger the
one known problem causing a bus error. Probably time for wider testing.
> If I am just completely off on the whole general concept of a Watchdog please
> tell me, but I think that(if I'm right) it might be a good idea for everybody
> to have that feature available to them :-) The documentation that I was
> reading at Dallas' website implied that the only thing involved was to have
> the clock stuff to reset, or update, the reset time of the timer every xxx
> seconds to prevent it from restarting an out-of-control processor.
The idea of a software watchdog is good, it's somewhere on the bottom of
my to do list since quite some time.
Ralf
prev parent reply other threads:[~1998-06-22 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-21 2:58 Running Linux on Linus LetherGlov
1998-06-22 9:11 ` ralf [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=19980622111154.I418@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=LetherGlov@aol.com \
--cc=linux@cthulhu.engr.sgi.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