From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Joonsoo Kim <js1304@gmail.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Linux MM <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>
Subject: Re: BUG: enable_cpucache failed for radix_tree_node, error 12 (was: Re: [PATCH v3 9/9] slab: remove BAD_ALIEN_MAGIC)
Date: Thu, 7 Aug 2014 14:53:54 +0200 [thread overview]
Message-ID: <CAMuHMdVC8aYwDEHnntshdVA24Nx3qAUXZfeRQNGqj=J6eExU-Q@mail.gmail.com> (raw)
In-Reply-To: <CAAmzW4MX2birtCOUxjDdQ7c3Y+RyVkBt383HEQ=XFgnhhOsQPw@mail.gmail.com>
Hi,
On Thu, Aug 7, 2014 at 2:36 PM, Joonsoo Kim <js1304@gmail.com> wrote:
>> With latest mainline, I'm getting a crash during bootup on m68k/ARAnyM:
>>
>> enable_cpucache failed for radix_tree_node, error 12.
>> kernel BUG at /scratch/geert/linux/linux-m68k/mm/slab.c:1522!
>> I bisected it to commit a640616822b2c3a8009b0600f20c4a76ea8a0025
>> Author: Joonsoo Kim <iamjoonsoo.kim@lge.com>
>> Date: Wed Aug 6 16:04:38 2014 -0700
>>
>> slab: remove BAD_ALIEN_MAGIC
> This patch only works for !NUMA. And if num_possible_nodes() is 1,
> then it doesn't have any effect, because alloc_alien_cache() call is always
> skipped. Is it possible !NUMA and num_possible_nodes() != 1?
>
> Could you check your config for CONFIG_NUMA and
> CONFIG_NODES_SHIFT?
$ grep CONFIG_NUMA .config
$ grep CONFIG_NODES_SHIFT .config
CONFIG_NODES_SHIFT=3
$
There are indeed multiple nodes:
On node 0 totalpages: 3584
free_area_init_node: node 0, pgdat 003659a4, node_mem_map 00402000
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3584 pages, LIFO batch:0
On node 1 totalpages: 65536
free_area_init_node: node 1, pgdat 00366294, node_mem_map 00426090
DMA zone: 576 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 65536 pages, LIFO batch:15
> And, could you check booting with boot param "noaliencache"?
That fixes the boot, too.
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
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:[~2014-08-07 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 11:52 Geert Uytterhoeven
2014-08-07 12:36 ` Joonsoo Kim
2014-08-07 12:53 ` Geert Uytterhoeven [this message]
2014-08-07 13:03 ` Joonsoo Kim
2014-08-08 7:19 ` Joonsoo Kim
2014-08-08 8:56 ` Geert Uytterhoeven
2014-08-08 11:50 ` Christoph Lameter
2014-08-08 12:06 ` Geert Uytterhoeven
2014-08-08 14:11 ` Christoph Lameter
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='CAMuHMdVC8aYwDEHnntshdVA24Nx3qAUXZfeRQNGqj=J6eExU-Q@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vdavydov@parallels.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