mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel Newby" <daniel.a.newby@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: how to allow board writers to customize driver behavior (watchdog here)
Date: Fri, 25 May 2007 05:09:30 -0500	[thread overview]
Message-ID: <ba1ee50c0705250309j64eb1d99j45b1ed35a4a5b1ed@mail.gmail.com> (raw)
In-Reply-To: <20070525040445.GA8395@linux-sh.org>

On 5/24/07, Paul Mundt <lethal@linux-sh.org> wrote:
> So far the only example anyone has provided outside of periodic timers or
> hardware reset has been dumping the stack when something gets stuck.
> Softlockup does this already today, using a timer.

Many watchdogs can be hooked up to a non-maskable interrupt (NMI) that
cannot be disabled or preempted.  You get a stack dump even for drastic
bugs:  ISR lock up, timer misconfiguration, level-sensitive interrupt
line stuck asserted, and so forth.  Getting that information by other
means can be painful and/or expensive.

The Blackfin chip in the original message appears to support watchdog
NMI.

    -- Daniel

  reply	other threads:[~2007-05-25 10:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24  4:21 Mike Frysinger
2007-05-24  5:23 ` Paul Mundt
2007-05-24  8:47   ` Daniel Newby
2007-05-24  9:32     ` Paul Mundt
2007-05-24 15:08     ` Mike Frysinger
2007-05-24 13:29   ` Robin Getz
2007-05-24 15:23     ` Paul Mundt
2007-05-24 17:32       ` Robin Getz
2007-05-25  4:04         ` Paul Mundt
2007-05-25 10:09           ` Daniel Newby [this message]
2007-05-25 17:55             ` Mike Frysinger
2007-05-24 15:12   ` Mike Frysinger
2007-05-24 10:01 ` Alan Cox

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=ba1ee50c0705250309j64eb1d99j45b1ed35a4a5b1ed@mail.gmail.com \
    --to=daniel.a.newby@gmail.com \
    --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 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®