linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Huan Wang <alison.wang@freescale.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Jin Jason <Jason.Jin@freescale.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Fabio Estevam <festevam@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>
Subject: RE: [PATCH v4] ARM: configs: Add Freescale LS1021A defconfig
Date: Mon, 2 Nov 2015 03:19:42 +0000	[thread overview]
Message-ID: <BN3PR0301MB0867A9DA25D6D192EDAACB3BFE2C0@BN3PR0301MB0867.namprd03.prod.outlook.com> (raw)
In-Reply-To: <3938714.zt8Y4X5ull@wuerfel>

> On Tuesday 27 October 2015 14:40:21 Huan Wang wrote:
> > >
> > > Ok. What I was suggesting above though was to try to pinpoint
> > > exactly where it goes wrong. You have verified that it does not
> > > crash before the page tables are enabled, but that is very early.
> > > You have also shown that the kernel crashes before the point at
> > > which the 'Booting Linux on physical CPU 0xf00' message is printed
> > > to the kernel, but that is *much*
> > > later: setup_arch() calls parse_early_param(), which in turn sets up
> > > early_console_write(). This means the 'Booting Linux on physical CPU
> > > 0xf00'
> > > is still stuck in the log buffer and you may have crashed someone
> > > inbetween.
> > >
> > > If you can call printascii(), you can try to do that just after
> > > enabling the page tables to see if that was the problem like you
> > > suspect, or otherwise add more printascii() statements between
> > > __turn_mmu_on and
> > > parse_early_param() to pinpoint the exact code that breaks.
> > [Alison Wang] Thank you very much for your help. The issue is fixed.
> >
> 
> Ah, very good. I'm curious what caused the problem in the end.
[Alison Wang] The problem is caused by the wrong fdt_high setting (0xcfffffff).
When 3G/1G user/kernel memory split is used, U-Boot relocates the device tree
blob into high memory when booting the kernel and the kernel is unable to access
the blob.

Best Regards,
Alison Wang

      reply	other threads:[~2015-11-02  3:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  9:03 [PATCH v4] ARM: configs: Add Freescale LS1021A defconfig Alison Wang
2015-09-17 10:34 ` Russell King - ARM Linux
2015-09-18  7:38   ` Huan Wang
2015-09-18 15:45     ` Fabio Estevam
2015-09-24  7:27       ` Huan Wang
2015-09-24  7:34         ` Arnd Bergmann
2015-10-14 10:18           ` Huan Wang
2015-10-14 12:54             ` Arnd Bergmann
2015-10-15  2:11               ` Huan Wang
2015-10-15 12:12                 ` Arnd Bergmann
2015-10-27 14:40                   ` Huan Wang
2015-10-30 13:46                     ` Arnd Bergmann
2015-11-02  3:19                       ` Huan Wang [this message]

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=BN3PR0301MB0867A9DA25D6D192EDAACB3BFE2C0@BN3PR0301MB0867.namprd03.prod.outlook.com \
    --to=alison.wang@freescale.com \
    --cc=Jason.Jin@freescale.com \
    --cc=arnd@arndb.de \
    --cc=festevam@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=shawnguo@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).