From: Michael Ellerman <mpe@ellerman.id.au>
To: Oliver O'Halloran <oohall@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: linux-mm@kvack.org, Oliver O'Halloran <oohall@gmail.com>
Subject: Re: [v2,2/2] powerpc/mm: Ensure "special" zones are empty
Date: Tue, 10 May 2016 09:55:51 +1000 (AEST) [thread overview]
Message-ID: <3r3fQw4Xbnz9t79@ozlabs.org> (raw)
In-Reply-To: <1462434849-14935-2-git-send-email-oohall@gmail.com>
On Thu, 2016-05-05 at 07:54:09 UTC, Oliver O'Halloran wrote:
> 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:
Sorting __ex_table...
Unable to handle kernel paging request for data at address 0xc000000101e28020
Faulting instruction address: 0xc0000000009ab698
cpu 0x0: Vector: 300 (Data Access) at [c000000000acbb30]
pc: c0000000009ab698: .reserve_bootmem_region+0x64/0x8c
lr: c0000000009883d0: .free_all_bootmem+0x70/0x200
sp: c000000000acbdb0
msr: 80021000
dar: c000000101e28020
dsisr: 800000
current = 0xc000000000a07640
paca = 0xc00000003fff5000 softe: 0 irq_happened: 0x01
pid = 0, comm = swapper
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
enter ? for help
[link register ] c0000000009883d0 .free_all_bootmem+0x70/0x200
[c000000000acbdb0] c000000000988398 .free_all_bootmem+0x38/0x200 (unreliable)
[c000000000acbe80] c00000000097b700 .mem_init+0x5c/0x7c
[c000000000acbef0] c000000000971a0c .start_kernel+0x28c/0x4e4
[c000000000acbf90] c000000000000544 start_here_common+0x20/0x5c
0:mon> ?
I can give you access some time if you need to debug it.
cheers
next prev parent reply other threads:[~2016-05-09 23:55 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 ` Michael Ellerman [this message]
2016-05-11 7:11 ` [v2,2/2] " Balbir Singh
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=3r3fQw4Xbnz9t79@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).