mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yisheng Xie <xieyisheng1@huawei.com>
To: <linux@armlinux.org.uk>, <matthias.bgg@gmail.com>,
	Al Viro <viro@zeniv.linux.org.uk>
Cc: <linux-arm-kernel@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Hanjun Guo <guohanjun@huawei.com>, <wangfangpeng1@huawei.com>,
	Yisheng Xie <xieyisheng1@huawei.com>
Subject: [BUG] boot fail with ARM_LPAE and VMSPLIT_3G_OPT
Date: Tue, 6 Jun 2017 19:08:00 +0800	[thread overview]
Message-ID: <e971a7f8-c05d-d6bd-a637-e8ba0b2d659e@huawei.com> (raw)

Hi all,

I find when both enable CONFIG_ARM_LPAE=y and CONFIG_VMSPLIT_3G_OPT=y,
which mean use PAGE_OFFSET=0xB0000000 with ARM_LPE, the kernel will boot fail.
it stop after uncompressed:
--------
  Starting kernel ...

  Uart base = 0x20001000
  watchdog reg = 0x20013000
  dtb addr = 0x80840308
  Uncompressing Linux... done, booting the kernel.

--------

Meanwhile, I also tried to use CONFIG_VMSPLIT_2G/CONFIG_VMSPLIT_1G with ARM_LPAE,
it can boot successfully.

Is that a limitation of ARM_LPAE, which I not do get any info about this from spec?
If it do have the limitation, then we should be:
--------
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 4c1a35f..c0fcab6 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -1416,6 +1416,7 @@ choice
        config VMSPLIT_3G
                bool "3G/1G user/kernel split"
        config VMSPLIT_3G_OPT
+               depends on !ARM_LPAE
                bool "3G/1G user/kernel split (for full 1G low memory)"
        config VMSPLIT_2G
                bool "2G/2G user/kernel split"



Any comment is more than welcome!

Thanks
Yisheng Xie

                 reply	other threads:[~2017-06-06 11:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=e971a7f8-c05d-d6bd-a637-e8ba0b2d659e@huawei.com \
    --to=xieyisheng1@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=matthias.bgg@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wangfangpeng1@huawei.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

all inboxes | Powered by JetHome®