From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: RCU init call bootmem allocation after slub us ready.
Date: Mon, 6 May 2013 12:06:11 -0700 [thread overview]
Message-ID: <20130506190611.GE3501@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAE9FiQUTV_e9De-6zCPs6OQrVAUJV2VLZDBmxFpJtnjNO3rKfw@mail.gmail.com>
On Mon, May 06, 2013 at 11:53:56AM -0700, Yinghai Lu wrote:
> [ 0.000000] SLUB: Genslabs=15, HWalign=64, Order=0-3, MinObjects=0,
> CPUs=160, Nodes=8
> [ 0.000000] Hierarchical RCU implementation.
> [ 0.000000] RCU restricting CPUs from NR_CPUS=4096 to nr_cpu_ids=160.
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING: at mm/nobootmem.c:234
> ___alloc_bootmem_nopanic+0x3a/0x7d()
> [ 0.000000] Modules linked in:
> [ 0.000000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
> 3.9.0-yh-10495-gfc7ffbc-dirty #1543
> [ 0.000000] Hardware name: Oracle Corporation Sun Fire X4800 M2 /
> , BIOS 15013200 04/19/2012
> [ 0.000000] 0000000000000009 ffffffff82a01e58 ffffffff8209dc61
> ffffffff82a01e98
> [ 0.000000] ffffffff8108a9d0 0000000000000000 0000000000000000
> 0000000000000200
> [ 0.000000] ffffffffffffffff 0000000000000040 0000000000000000
> ffffffff82a01ea8
> [ 0.000000] Call Trace:
> [ 0.000000] [<ffffffff8209dc61>] dump_stack+0x19/0x1b
> [ 0.000000] [<ffffffff8108a9d0>] warn_slowpath_common+0x70/0xa0
> [ 0.000000] [<ffffffff8108aa1a>] warn_slowpath_null+0x1a/0x20
> [ 0.000000] [<ffffffff82dd54cd>] ___alloc_bootmem_nopanic+0x3a/0x7d
> [ 0.000000] [<ffffffff82dd5695>] __alloc_bootmem+0x12/0x38
> [ 0.000000] [<ffffffff82de976a>] alloc_bootmem_cpumask_var+0x1a/0x21
> [ 0.000000] [<ffffffff82dce4da>] rcu_init+0x66/0x283
> [ 0.000000] [<ffffffff82dd15ed>] ? perf_event_init+0x136/0x15f
> [ 0.000000] [<ffffffff82dabf95>] start_kernel+0x24a/0x423
> [ 0.000000] [<ffffffff82dababe>] ? repair_env_string+0x5e/0x5e
> [ 0.000000] [<ffffffff820936b6>] ? __memblock_reserve+0x81/0x89
> [ 0.000000] [<ffffffff82dab5a8>] x86_64_start_reservations+0x2f/0x31
> [ 0.000000] [<ffffffff82dab79e>] x86_64_start_kernel+0x1f4/0x1fc
> [ 0.000000] ---[ end trace 53ae8bb075006d8f ]---
Do you have commit fa0f93cd6a (rcu: Don't allocate bootmem from rcu_init())?
If not, could you please try applying it?
Thanx, Paul
next prev parent reply other threads:[~2013-05-06 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 18:53 RCU init call bootmem allocation after slub us ready Yinghai Lu
2013-05-06 19:06 ` Paul E. McKenney [this message]
2013-05-06 20:00 ` Yinghai Lu
2013-05-06 20:06 ` Paul E. McKenney
2013-05-06 20:13 ` Yinghai Lu
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=20130506190611.GE3501@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@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 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.