All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/2] ia64 kdump: add kdump_on_fatal_mca
Date: Wed, 09 Apr 2008 00:36:11 +0000	[thread overview]
Message-ID: <47FC0F7B.2080204@jp.fujitsu.com> (raw)
In-Reply-To: <47FAF533.8010707@jp.fujitsu.com>

>> I saw the proposed
>> patch that changes the current behavior without mentioning it
>> at the summary, so i brought it up. ;)

Sorry about that.  It's my fault.

But as the result it was lucky that we can have a good
discussion about "required action after a fatal MCA".

> So far SGI are voting for enabling dumping for MCA, and
> Fujitsu have implicitly voted to disable (as that is what
> Seto-san's patch sets).  Any other opinions?

Ah, my vote can be invalid.
AFAIK, Fujitsu have both situation where kdump_on_fatal_mca
should be enabled and where it should be disabled.
Therefore I don't mind which is the default.
Anyway we need to put a line to /etc/sysctl.conf of one of both.

So now "enable vs disable" is not 1:1 but 1:0 or 1.5:0.5.

Tony, (if there are no other votes until your poll closing)
would you apply my patch modifying the default to 1?
Or I need to resend you all just modified the one byte?

Thanks,
H.Seto

  parent reply	other threads:[~2008-04-09  0:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  4:31 [PATCH 1/2] ia64 kdump: add kdump_on_fatal_mca Hidetoshi Seto
2008-04-08 17:36 ` Jay Lan
2008-04-08 17:51 ` Luck, Tony
2008-04-08 18:19 ` Jay Lan
2008-04-08 18:21 ` Russ Anderson
2008-04-08 18:34 ` Jay Lan
2008-04-08 18:54 ` Luck, Tony
2008-04-09  0:36 ` Hidetoshi Seto [this message]
2008-04-09 21:59 ` Luck, Tony
2008-04-09 23:01 ` Bjorn Helgaas

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=47FC0F7B.2080204@jp.fujitsu.com \
    --to=seto.hidetoshi@jp.fujitsu.com \
    --cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.