mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Anithra P Janakiraman <anithra@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, dave@linux.vnet.ibm.com,
	xiyou.wangcong@gmail.com, sugaken.r3@gmail.com,
	akpm@linux-foundation.org, vatsa@linux.vnet.ibm.com,
	ananth@in.ibm.com
Subject: Re: [RESEND] [PATCH] Softdog enhancement to optionally invoke panic instead of reboot on timer expiry
Date: Mon, 28 Mar 2011 16:16:22 +0100	[thread overview]
Message-ID: <20110328161622.100e3a51@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20110328203502.5d62fea4@linux.vnet.ibm.com>

On Mon, 28 Mar 2011 20:35:02 +0530
Anithra P Janakiraman <anithra@linux.vnet.ibm.com> wrote:

> Hi,
> 
> The patch is needed for determining the reason for failure when a
> softdog timeout occurs. We use softdog to watch for critical
> application failures and at the minimum a snapshot of the system would
> help to determine the cause. In such a scenario the application could
> fail but there isn't a softlockup as such, hence the detect softlockup
> feature does not help. The patch below adds a module parameter
> soft_panic which when set to 1 causes softdog to invoke panic instead
> of reboot when the softdog timer expires. By invoking panic we execute
> kdump if it is configured and the vmcore generated by kdump should
> provide atleast a minimal idea of the reason for failure.

Looks sensible to me.

Acked-by: Alan Cox <alan@linux.intel.com>

Alan

      reply	other threads:[~2011-03-28 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28 15:05 Anithra P Janakiraman
2011-03-28 15:16 ` Alan Cox [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=20110328161622.100e3a51@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=anithra@linux.vnet.ibm.com \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sugaken.r3@gmail.com \
    --cc=vatsa@linux.vnet.ibm.com \
    --cc=xiyou.wangcong@gmail.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

all inboxes | Powered by JetHome®