All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: ARMADA-XP cpu1 .. cpu3 does not come online
Date: Thu, 18 Jun 2015 16:28:35 +0200	[thread overview]
Message-ID: <20150618142835.GF312@lunn.ch> (raw)
In-Reply-To: <20150618142233.GL7557@n2100.arm.linux.org.uk>

On Thu, Jun 18, 2015 at 03:22:33PM +0100, Russell King - ARM Linux wrote:
> On Thu, Jun 18, 2015 at 03:36:07PM +0200, Andrew Lunn wrote:
> > > Uncompressing Linux... done, booting the kernel.                               
> > > [    0.000000] Booting Linux on physical CPU 0x0                               
> > > [    0.000000] Linux version 4.0.5-00001-g8b87c3c (peter at t440) (gcc version 4.95
> > > [    0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d 
> > > [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache 
> > > [    0.000000] Machine model: AXP-TEST-BOARD 
> > > [    0.000000] bootconsole [earlycon0] enabled
> > > [    0.000000] Truncating RAM at 0x00000000-0xffffffff to -0x2f800000 
> > > 
> > > ^^ This is worrying to me, firstly because memory is being truncated down, secondly because my dts file only specifies memory from 0x00000000 to 0xf000000 (see attached dts file)
> > 
> > 0x2f800000 suggests you have an old boot loader, with IO at
> > 0xd000,0000. Upgrading to a newer uboot will allow you to use more of
> > the 4G of RAM. It might also fix your SMP issue.
> 
> No.  The 0x2f800000 comes from having more than 0x2f800000 bytes of memory
> and having highmem disabled.  It's got nothing to do with boot loaders at
> all.
> 
> The way this works is that sanity_check_meminfo() looks at the base of
> the vmalloc() area.  If PAGE_OFFSET + memory_size results in memory above
> the vmalloc() area, and highmem is disabled, sanity_check_meminfo()
> truncates the memory to that limit and reports the above message.

Hi Russell

Thanks for the explanation.

I think at one point x86 used to print a hint about enabling HIGHMEM.
Is it worth adding something similar?

   Andrew

  reply	other threads:[~2015-06-18 14:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 12:38 ARMADA-XP cpu1 .. cpu3 does not come online Peter Morrow
2015-06-18 13:36 ` Andrew Lunn
2015-06-18 14:04   ` Thomas Petazzoni
2015-06-18 14:10     ` Peter Morrow
2015-06-18 14:22   ` Russell King - ARM Linux
2015-06-18 14:28     ` Andrew Lunn [this message]
2015-06-18 15:01       ` Russell King - ARM Linux
2015-06-18 14:12 ` Thomas Petazzoni
2015-06-18 14:25   ` Peter Morrow

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=20150618142835.GF312@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=linux-arm-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.