linux-ia64.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luming Yu" <luming.yu@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>, andrew.patterson@hp.com
Cc: linux-ia64@vger.kernel.org, Petr Tesarik <ptesarik@suse.cz>,
	Roland McGrath <roland@redhat.com>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	Simon Horman <horms@verge.net.au>
Subject: Re: kdump regression: /proc/vmcore is 0 after kdump
Date: Sun, 15 Jun 2008 09:26:36 +0000	[thread overview]
Message-ID: <3877989d0806150226x62fc1d1bk96131430f55848e1@mail.gmail.com> (raw)
In-Reply-To: <3877989d0806130922p1f36a3bes9914144ac8c42266@mail.gmail.com>

On Sat, Jun 14, 2008 at 12:22 AM, Luming Yu <luming.yu@gmail.com> wrote:
> On Thu, Jun 5, 2008 at 4:16 PM, Simon Horman <horms@verge.net.au> wrote:
>> On Thu, Jun 05, 2008 at 03:58:40PM +0800, Luming Yu wrote:
>>> On Tue, Jun 3, 2008 at 2:02 PM, Luming Yu <luming.yu@gmail.com> wrote:
>>> >> I'm trying upstream kdump to get more detailed data for help analysis
>>> >> the scenario..
>>> > Upstream kdump doesn't work! don't know what cause the regression,
>>> > possibly kexec-tools...
>>> > Need investigation here!
>>> >
>>>
>>> I tested mainline kernel from 2.6.20 to 2.6.26-rc4 on my tiger4..
>>> whatever I try, /proc/vmcore is always 0 !
>>>
>>> Then I managed to get Nan hai's original patch against 2.6.19..
>>> http://marc.info/?l=linux-ia64&m\x116521104831321&w=2
>>> This patch doesn't have zero-vmcore problem.
>>>
>>> Given the age of the kdump feature and so many upstream releases since
>>> 2.6.20, I'm in doubt why I don't see this kind of bug report on ia64
>>> mailing list before?
>>>
>>> PS. Now I can start to capture info for the strace problem with 2.6.19
>>> kernel +Nahai's 2.6.19 kdump patch, hope the problem is still
>>> reproducible.
>>
>> Which version of kexec-tools are you using?
>> If you haven't done so already, could you try the latest version, 20080324.
>>
>> http://www.eu.kernel.org/pub/linux/kernel/people/horms/kexec-tools/
>>
>
> Yes, this resolves one of my kdump problem.
> But there seems to have a regression introduced into upstream probably
> starting from 2.6.25.
> The last kernel with kdump working on this box is 2.6.24. I don't have
> time to start bisection to find out which patch causes that regression
> right now.Maybe someone on this list can give me some hint..

My git bisection result indicates the following commit causes the
kdump regression in 2.6.25-rc1:
commit 3c75e23784e6ed5f4841de43d0750fd9b37bafcb
Author: Andrew Patterson <andrew.patterson@hp.com>
Date:   Tue Jan 22 17:18:27 2008 -0700

  reply	other threads:[~2008-06-15  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  7:58 kdump regression: /proc/vmcore is 0 after kdump Luming Yu
2008-06-05  8:01 ` Bernhard Walle
2008-06-05  8:16 ` Simon Horman
2008-06-13 16:22   ` Luming Yu
2008-06-15  9:26     ` Luming Yu [this message]
2008-06-15  9:55       ` Bernhard Walle
2008-06-15 10:42         ` Luming Yu

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=3877989d0806150226x62fc1d1bk96131430f55848e1@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=andrew.patterson@hp.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ptesarik@suse.cz \
    --cc=roland@redhat.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;
as well as URLs for NNTP newsgroup(s).