Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
To: Bernhard Walle <bwalle@suse.de>
Cc: Jay Lan <jlan@sgi.com>, kexec@lists.infradead.org
Subject: Re: makedumpfile fails on SGI machine
Date: Thu, 31 Jul 2008 19:25:10 +0900	[thread overview]
Message-ID: <48919306.80103@mxs.nes.nec.co.jp> (raw)
In-Reply-To: <20080731104726.035850be@halley.suse.de>

[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]


Hi Bernhard,

Bernhard Walle wrote:
> * Ken'ichi Ohmichi [2008-07-31 10:46]:
>> Bernhard Walle wrote:
>>> After debugging that, I didn't find an error code. That address is in
>>> fact the beginning of the mem_map of that node, and is in fact not
>>> mapped (I verified that in crash).
>>>
>>> With an older kernel and an older makedumpfile it succeeds.
>> I'd like to know whether this problem is due to the makedumpfile
>> regression or either the unsupported kernel. Could you please
>> fill the following items ?
>  
> * Problematic condition
>   kernel version: 2.6.26
>   makedumpfile version: 1.2.7
> 
> * Successful condition
>   kernel version: 2.6.16.60 (SLES kernel)
>   makedumpfile version: 1.1.4 (SLES 10 SP2 version, but in fact that is
>                                1.1.4 although -v displays something
>                                different ;-))
>
>> And could you please test the combination of successful kernel
>> and problematic makedumpfile(1.2.7) ?
> 
> That works. Seems to be some kernel change.

Thank you for quick response.

I tried to reproduce this problem on my machine by using an ia64 linux-2.6.26
discontigmem kernel, but it could not do it. makeudmpifle did not fail.
I want to know whether this problem depends on the kernel or either the machine.
Could you send me the kernel .config file ?


Thanks
Ken'ichi Ohmichi


[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-07-31 10:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-30 14:14 makedumpfile fails on SGI machine Bernhard Walle
2008-07-31  1:46 ` Ken'ichi Ohmichi
2008-07-31  8:47   ` Bernhard Walle
2008-07-31 10:25     ` Ken'ichi Ohmichi [this message]
2008-07-31 11:18       ` Bernhard Walle
2008-07-31 11:36         ` Ken'ichi Ohmichi
2008-07-31 11:38           ` Bernhard Walle
2008-08-05 12:07           ` Ken'ichi Ohmichi
2008-08-05 15:11             ` Bernhard Walle
2008-08-18  7:19               ` Ken'ichi Ohmichi
2008-08-18 11:00                 ` Bernhard Walle
2008-08-19 12:14                   ` Ken'ichi Ohmichi
2008-08-27  9:00                   ` Ken'ichi Ohmichi
2008-08-28  1:43                     ` Jay Lan
2008-08-28  4:33                       ` Ken'ichi Ohmichi
2008-08-28  7:25                       ` Bernhard Walle
2008-08-29  6:45                         ` [PATCH][ia64] Fix the difference between node_mem_map and node_start_pfn. (Re: makedumpfile fails on SGI machine) Ken'ichi Ohmichi
2008-08-29 16:54                           ` Bernhard Walle
2008-09-01  2:13                             ` Ken'ichi Ohmichi
2008-08-29 18:14                           ` Jay Lan
2008-08-29 20:12                             ` Jay Lan
2008-09-01  2:32                               ` Ken'ichi Ohmichi

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=48919306.80103@mxs.nes.nec.co.jp \
    --to=oomichi@mxs.nes.nec.co.jp \
    --cc=bwalle@suse.de \
    --cc=jlan@sgi.com \
    --cc=kexec@lists.infradead.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