linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Flavio Leitner <fbl@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	WANG Cong <xiyou.wangcong@gmail.com>, Tejun Heo <tj@kernel.org>,
	ianfang.cn@gmail.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kexec/kdump kernel fails to start
Date: Tue, 4 Sep 2012 15:25:45 -0700	[thread overview]
Message-ID: <CAE9FiQXCzQ+GCCqx4+=ZSijn+_+ekfGrUABiWNuX2H8BL+j9tg@mail.gmail.com> (raw)
In-Reply-To: <20120904183708.5f10fbde@obelix.rh>

On Tue, Sep 4, 2012 at 2:37 PM, Flavio Leitner <fbl@redhat.com> wrote:
> On Tue, 4 Sep 2012 13:45:23 -0700
> Yinghai Lu <yinghai@kernel.org> wrote:
>
>> On Tue, Sep 4, 2012 at 1:26 PM, Flavio Leitner <fbl@redhat.com> wrote:
>> >
>> > Sorry, but it didn't work.
>> > The same problem happened.
>>
>> can you send out boot log ?
>
> sure, there you go:
> http://sysclose.org/kdump/dmesg-debug.log
> http://sysclose.org/kdump/config.log

looks like you did not use for-x86-mm branch.

[    0.000000] initial memory mapped: [mem 0x00000000-0x1fffffff]
[    0.000000] Base memory trampoline at [ffff880000097000] 97000 size 24576
[    0.000000] init_memory_mapping: [mem 0x00000000-0xbf7fffff]
[    0.000000]  [mem 0x00000000-0xbf7fffff] page 2M
[    0.000000] kernel direct mapping tables up to 0xbf7fffff @ [mem
0x1fa00000-0x1fffffff]
[    0.000000] init_memory_mapping: [mem 0x100000000-0x43fffffff]
[    0.000000]  [mem 0x100000000-0x43fffffff] page 2M
[    0.000000] kernel direct mapping tables up to 0x43fffffff @ [mem
0xbf7ce000-0xbf7dffff]
[    0.000000] RAMDISK: [mem 0x351d2000-0x368e0fff]
[    0.000000] Reserving 256MB of memory at 592MB for crashkernel
(System RAM: 16372MB)

please try:

mkdir linux || exit -1
cd linux

git init-db

# Add Linus's tree as a remote
git remote add linus
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git

# Add the -tip tree as a remote
git remote add tip git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git

# Add yinghai's tree

git remote add yinghai
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git

git remote update

git checkout -b yinghai-for-x86-mm yinghai/for-x86-mm

  reply	other threads:[~2012-09-04 22:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 17:32 kexec/kdump kernel fails to start Flavio Leitner
2012-09-04 19:02 ` Yinghai Lu
2012-09-04 19:17   ` Flavio Leitner
2012-09-04 19:20     ` Yinghai Lu
2012-09-04 20:00       ` Flavio Leitner
2012-09-04 20:26       ` Flavio Leitner
2012-09-04 20:45         ` Yinghai Lu
2012-09-04 21:37           ` Flavio Leitner
2012-09-04 22:25             ` Yinghai Lu [this message]
2012-09-04 22:40               ` Flavio Leitner
2012-09-05  0:01               ` Flavio Leitner
2012-09-05  1:15                 ` Yinghai Lu
2012-09-05 13:46                   ` Flavio Leitner
2012-09-05 15:34 ` Cong Wang
2012-09-23 20:27   ` Dan Carpenter
2012-09-23 20:52     ` Yinghai Lu
2012-09-29  7:13       ` Ingo Molnar
2012-10-18  2:16         ` Dave Young
2012-10-18  6:33           ` Dave Young
2012-10-18 13:57             ` Cong Wang
2012-10-18 16:27             ` Flavio Leitner

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='CAE9FiQXCzQ+GCCqx4+=ZSijn+_+ekfGrUABiWNuX2H8BL+j9tg@mail.gmail.com' \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=fbl@redhat.com \
    --cc=ianfang.cn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).