From: Raphael Massin <massin@col.bsf.alcatel.fr>
To: jeff@wa1hco.mv.com
Cc: linuxppc-embedded@lists.linuxppc.org, dmalek@jlc.net, massin@cu5s33
Subject: Re: /dev/watchdog for onchip MPC860 watchdog?
Date: Wed, 20 Oct 1999 09:33:32 +0200 (MET DST) [thread overview]
Message-ID: <199910200733.JAA28746@cu5s33.clb> (raw)
>
>
> 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
>
Hello,
I'm using the watchdog timer on a custom board since several months. To
prevent a CPU reset during the kernel is uncompressing, i prorammed it
to generate a Non Maskable Interrupt instead of system reset. Those NMIs
are handled by a special function in the Linux kernel. This function
can reset the board, using a specific I/O, when too many NMIs occurred
without any watchdog timer (SWSR) servicing.
Today, i refresh the timer in my real time application that is launched
immediately after the kernel init. This scheme must work for any board
launching an appli/real time module after kernel init. For other configurations,
Dan's idea seems perfect.
Raphael
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-20 7:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-20 7:33 Raphael Massin [this message]
1999-10-20 17:56 ` /dev/watchdog for onchip MPC860 watchdog? Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2000-07-13 7:24 Tania Boak
2000-07-13 7:47 ` Graham Stoney
[not found] <380B6A1B.E5D02094@netx4.com>
1999-10-19 8:56 ` Graham Stoney
1999-10-19 19:51 ` Dan Malek
1999-10-20 1:56 ` Jeff Millar
1999-10-20 17:47 ` Dan Malek
1999-10-21 3:49 ` Graham Stoney
1999-10-21 4:06 ` Cort Dougan
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=199910200733.JAA28746@cu5s33.clb \
--to=massin@col.bsf.alcatel.fr \
--cc=dmalek@jlc.net \
--cc=jeff@wa1hco.mv.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=massin@cu5s33 \
/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).