From: Flavio Leitner <fbl@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
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 17:00:07 -0300 [thread overview]
Message-ID: <20120904170007.5fa65d72@obelix.rh> (raw)
In-Reply-To: <CAE9FiQX7OMdFU6FuTQdz+NdbNt5Hy9zjzSY7y-90G4CbhayfaA@mail.gmail.com>
On Tue, 4 Sep 2012 12:20:14 -0700
Yinghai Lu <yinghai@kernel.org> wrote:
> On Tue, Sep 4, 2012 at 12:17 PM, Flavio Leitner <fbl@redhat.com> wrote:
> > On Tue, 4 Sep 2012 12:02:00 -0700
> > [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> > [ 0.000000] last_pfn = 0xbf800 max_arch_pfn = 0x400000000
> > [ 0.000000] initial memory mapped : 0 - 20000000
> > [ 0.000000] Base memory trampoline at [ffff880000098000] 98000 size 20480
> > [ 0.000000] init_memory_mapping: 0000000000000000-00000000bf800000
> > [ 0.000000] 0000000000 - 00bf800000 page 2M
> > [ 0.000000] kernel direct mapping tables up to bf800000 @ 1fa00000-20000000
> > [ 0.000000] init_memory_mapping: 0000000100000000-0000000440000000
> > [ 0.000000] 0100000000 - 0440000000 page 2M
> > [ 0.000000] kernel direct mapping tables up to 440000000 @ bdaab000-bf4bd000
> > [ 0.000000] RAMDISK: 352c8000 - 3695c000
> >
Alright, moving the extra accounting to be inside of CONFIG_X86_32 works out.
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index e0e6990..63e6a5c 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
@@ -60,10 +60,10 @@ static void __init find_early_table_space(struct map_range *mr, unsigned long en
extra = end - ((end>>PMD_SHIFT) << PMD_SHIFT);
#ifdef CONFIG_X86_32
extra += PMD_SIZE;
-#endif
/* The first 2/4M doesn't use large pages. */
if (mr->start < PMD_SIZE)
extra += mr->end - mr->start;
+#endif
ptes = (extra + PAGE_SIZE - 1) >> PAGE_SHIFT;
} else
> BTW, can you please try our new init_memory_mapping clean up at
>
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git
> for-x86-mm
>
> hope it could make your kdump working.
I will give a try.
fbl
next prev parent reply other threads:[~2012-09-04 20:00 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 [this message]
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
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=20120904170007.5fa65d72@obelix.rh \
--to=fbl@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ianfang.cn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yinghai@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 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).