From: Joel Becker <Joel.Becker@oracle.com>
To: Brian Gerst <bgerst@didntduck.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Wim Coekaerts <Wim.Coekaerts@oracle.com>
Subject: Re: [RFC] hangcheck-timer module
Date: Thu, 21 Nov 2002 14:08:08 -0800 [thread overview]
Message-ID: <20021121220807.GN770@nic1-pc.us.oracle.com> (raw)
In-Reply-To: <3DDD4288.70605@didntduck.org>
On Thu, Nov 21, 2002 at 03:31:04PM -0500, Brian Gerst wrote:
> Joel Becker wrote:
> > Attached is a module, hangcheck-timer. It is used to detect
> >when the system goes out to lunch for a period of time, such as when a
> >driver like qla2x00 udelays a bunch.
>
> There is already an NMI watchdog that is better than what you propose,
> because it will also catch cases where something gets stuck with
> interrupts disabled.
The issue at hand is not permanent hangs. The issue is hangs
that return. Consider a clustering enviornment where the other nodes
have given up on the delayed node and clean up after it. When the hang
finally ends, the node still thinks it is "alive" and happily scribbles
to places it shouldn't.
udelay will not ever trigger the NMI watchdog, as it is running
on the processor, so the cpu timer will run happily. But as far as
everything higher up (kernel + userspace), the delay will be unnoticed
and bad things can happen.
Joel
--
"I'm so tired of being tired,
Sure as night will follow day.
Most things I worry about
Never happen anyway."
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2002-11-21 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-21 20:17 Joel Becker
2002-11-21 20:31 ` Brian Gerst
2002-11-21 22:08 ` Joel Becker [this message]
2002-11-21 20:19 Joel Becker
2002-11-22 11:56 ` William Lee Irwin III
2002-11-26 13:35 ` Pavel Machek
2002-11-26 22:36 ` Joel Becker
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=20021121220807.GN770@nic1-pc.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=Wim.Coekaerts@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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®