From: "Jeff Millar" <jeff@wa1hco.mv.com>
To: "Dan Malek" <dan@netx4.com>,
"Graham Stoney" <greyham@research.canon.com.au>
Cc: "Dan Malek" <dan@penguin.netx4.com>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: /dev/watchdog for onchip MPC860 watchdog?
Date: Tue, 19 Oct 1999 21:56:38 -0400 [thread overview]
Message-ID: <003e01bf1a9e$59f44980$0201a8c0@home> (raw)
In-Reply-To: 380CCBAC.7C0DB544@netx4.com
I've also been thinking about this...
If the boot process goes bad, then the interrupt driven watchdog will
keep getting reset and prevent the watchdog from firing...leading to a
unrecoverable hang. So, what's the likely hood of the boot process
going bad?
Our application requires downloading new kernels and applications and this
may
increase the likely hood that a kernel fails to complete the boot process.
This idea has a window of vunerability but how much and how likely???
Maybe the timer can be set longer than the longest bootup time or at least
until the first daemon gets going?
jeff
----- Original Message -----
From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: Dan Malek <dan@penguin.netx4.com>;
<linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, October 19, 1999 3:51 PM
Subject: Re: /dev/watchdog for onchip MPC860 watchdog?
>
> Graham Stoney wrote:
>
>
> > .... The watchdog can't
> > be disabled/reenabled, and its maximum period is only a couple of
seconds;
> > there's no guarantee that the kernel will have booted and loaded the
> > application by then, so the watchdog is likely to go off during the boot
> > process. I think this probably puts my plans to use it on hold for
now...
>
> Maybe not. I was thinking about this (when I should have been doing
> other things :-) earlier today. What we could do when the internal
> watchdog is configured is to service it during the Linux timer
> interrupt when an application doesn't have it "enabled". This
> doesn't provide a watchdog service, just ensures it doesn't
> unexpectedly expire. When an application decides it wants the
> watchdog, we don't service it in the timer ISR.
>
> We would have to litter the boot code with some service calls,
> like when you wait at the Linux boot prompt, and make sure
> you can uncompress and enable timer interrupts before the next
> expiration. Beyond that, we wouldn't have to look for any
> watchdog service points in the kernel.
>
> I may play with it later tonight........
>
>
> -- Dan
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-20 1:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <380B6A1B.E5D02094@netx4.com>
1999-10-19 8:56 ` /dev/watchdog for onchip MPC860 watchdog? Graham Stoney
1999-10-19 19:51 ` Dan Malek
1999-10-20 1:56 ` Jeff Millar [this message]
1999-10-20 17:47 ` Dan Malek
1999-10-21 3:49 ` Graham Stoney
1999-10-21 4:06 ` Cort Dougan
2000-07-13 7:24 Tania Boak
2000-07-13 7:47 ` Graham Stoney
-- strict thread matches above, loose matches on Subject: below --
1999-10-20 7:33 Raphael Massin
1999-10-20 17:56 ` Dan Malek
1999-10-15 3:30 Graham Stoney
1999-10-18 20:24 ` Dan Malek
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='003e01bf1a9e$59f44980$0201a8c0@home' \
--to=jeff@wa1hco.mv.com \
--cc=dan@netx4.com \
--cc=dan@penguin.netx4.com \
--cc=greyham@research.canon.com.au \
--cc=linuxppc-embedded@lists.linuxppc.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).