From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Oliver O'Halloran <oohall@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Cc: linux-mm@kvack.org
Subject: Re: [v2,2/2] powerpc/mm: Ensure "special" zones are empty
Date: Wed, 11 May 2016 17:11:55 +1000 [thread overview]
Message-ID: <1462950715.20338.3.camel@gmail.com> (raw)
In-Reply-To: <3r3fQw4Xbnz9t79@ozlabs.org>
On Tue, 2016-05-10 at 09:55 +1000, Michael Ellerman wrote:
> On Thu, 2016-05-05 at 07:54:09 UTC, Oliver O'Halloran wrote:
> >A
> > The mm zone mechanism was traditionally used by arch specific code to
> > partition memory into allocation zones. However there are several zones
> > that are managed by the mm subsystem rather than the architecture. Most
> > architectures set the max PFN of these special zones to zero, however on
> > powerpc we set them to ~0ul. This, in conjunction with a bug in
> > free_area_init_nodes() results in all of system memory being placed in
> > ZONE_DEVICE when enabled. Device memory cannot be used for regular kernel
> > memory allocations so this will cause a kernel panic at boot.
> This is breaking my freescale machine:
>A
> A Sorting __ex_table...
> A Unable to handle kernel paging request for data at address 0xc000000101e28020
> A Faulting instruction address: 0xc0000000009ab698
> A cpu 0x0: Vector: 300 (Data Access) at [c000000000acbb30]
> A A A A A A pc: c0000000009ab698: .reserve_bootmem_region+0x64/0x8c
> A A A A A A lr: c0000000009883d0: .free_all_bootmem+0x70/0x200
> A A A A A A sp: c000000000acbdb0
> A A A A A msr: 80021000
> A A A A A dar: c000000101e28020
> A A A dsisr: 800000
> A A A A current = 0xc000000000a07640
> A A A A pacaA A A A = 0xc00000003fff5000 A softe: 0 A irq_happened: 0x01
> A A A A A A pidA A A = 0, comm = swapper
> A Linux version 4.6.0-rc3-00160-gc09920947f23 (michael@ka1) (gcc version 5.3.0 (GCC) ) #5 SMP Tue May 10 09:44:11 AEST 2016
> A enter ? for help
> A [link registerA A A ] c0000000009883d0 .free_all_bootmem+0x70/0x200
> A [c000000000acbdb0] c000000000988398 .free_all_bootmem+0x38/0x200 (unreliable)
> A [c000000000acbe80] c00000000097b700 .mem_init+0x5c/0x7c
> A [c000000000acbef0] c000000000971a0c .start_kernel+0x28c/0x4e4
> A [c000000000acbf90] c000000000000544 start_here_common+0x20/0x5c
> A 0:mon> ?A
>A
> I can give you access some time if you need to debug it.
>A
Could you also please post the bits on the boot containing the zone
and node information. That would provide some information about what
is broken. Or you could just send the whole dmesg
Thanks,
Balbir Singh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-11 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 7:54 [PATCH v2 1/2] powerpc/mm: define TOP_ZONE as a constant Oliver O'Halloran
2016-05-05 7:54 ` [PATCH v2 2/2] powerpc/mm: Ensure "special" zones are empty Oliver O'Halloran
2016-05-09 23:55 ` [v2,2/2] " Michael Ellerman
2016-05-11 7:11 ` Balbir Singh [this message]
2016-05-11 9:22 ` [PATCH v2] " Oliver O'Halloran
2016-06-21 0:40 ` [v2] " Michael Ellerman
2016-05-10 21:48 ` [v2,1/2] powerpc/mm: define TOP_ZONE as a constant Michael Ellerman
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=1462950715.20338.3.camel@gmail.com \
--to=bsingharora@gmail.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@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).