From: Ingo Molnar <mingo@elte.hu>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Yinghai Lu <yinghai@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
hannes@cmpxchg.org, mpm@selenic.com, npiggin@suse.de
Subject: Re: [GIT PULL v3] Early boot SLAB for 2.6.31
Date: Fri, 12 Jun 2009 00:03:07 +0200 [thread overview]
Message-ID: <20090611220307.GA16180@elte.hu> (raw)
In-Reply-To: <20090611214342.GA12762@elte.hu>
i also get this different warning, again:
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] WARNING: at mm/bootmem.c:537 alloc_arch_preferred_bootmem+0x2b/0x71()
[ 0.000000] Hardware name: System Product Name
[ 0.000000] Modules linked in:
[ 0.000000] Pid: 0, comm: swapper Tainted: G W 2.6.30-tip-03087-g0bb2618-dirty #52506
[ 0.000000] Call Trace:
[ 0.000000] [<81032588>] warn_slowpath_common+0x60/0x90
[ 0.000000] [<810325c5>] warn_slowpath_null+0xd/0x10
[ 0.000000] [<819d1bc0>] alloc_arch_preferred_bootmem+0x2b/0x71
[ 0.000000] [<819d1c31>] ___alloc_bootmem_nopanic+0x2b/0x9a
[ 0.000000] [<81050a0a>] ? lock_release+0xac/0xb2
[ 0.000000] [<819d1d4c>] ___alloc_bootmem+0xe/0x2d
[ 0.000000] [<819d1e9f>] __alloc_bootmem+0xa/0xc
[ 0.000000] [<819d7c63>] alloc_bootmem_cpumask_var+0x21/0x26
[ 0.000000] [<819d0cc8>] early_irq_init+0x15/0x10d
[ 0.000000] [<819bb75a>] start_kernel+0x167/0x326
[ 0.000000] [<819bb06b>] __init_begin+0x6b/0x70
[ 0.000000] ---[ end trace 4eaa2a86a8e2da23 ]---
[ 0.000000] NR_IRQS:2304 nr_irqs:424
[ 0.000000] CPU 0 irqstacks, hard=821e6000 soft=821e7000
Ingo
next prev parent reply other threads:[~2009-06-11 22:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 20:12 [GIT PULL] Early boot SLAB for 2.6.31 Pekka J Enberg
2009-06-10 20:32 ` Linus Torvalds
2009-06-10 20:30 ` Pekka Enberg
2009-06-10 20:43 ` Ingo Molnar
2009-06-10 20:47 ` Pekka Enberg
2009-06-10 20:50 ` Ingo Molnar
2009-06-10 20:57 ` Ingo Molnar
2009-06-10 20:58 ` Pekka Enberg
2009-06-10 21:07 ` Pekka Enberg
2009-06-11 0:54 ` Ingo Molnar
2009-06-10 21:00 ` Pekka J Enberg
2009-06-10 20:33 ` Linus Torvalds
2009-06-10 20:57 ` Pekka J Enberg
2009-06-11 11:17 ` [GIT PULL v2] " Pekka J Enberg
2009-06-11 11:35 ` Ingo Molnar
2009-06-11 11:40 ` Ingo Molnar
2009-06-11 11:42 ` Ingo Molnar
2009-06-11 11:48 ` Ingo Molnar
2009-06-11 11:56 ` Pekka Enberg
2009-06-11 11:49 ` Pekka J Enberg
2009-06-11 11:54 ` Ingo Molnar
2009-06-11 13:58 ` Christoph Lameter
2009-06-11 14:06 ` Pekka Enberg
2009-06-11 14:26 ` Christoph Lameter
2009-06-11 15:24 ` Pekka Enberg
2009-06-11 17:50 ` Yinghai Lu
2009-06-11 18:10 ` [GIT PULL v3] " Pekka J Enberg
2009-06-11 21:43 ` Ingo Molnar
2009-06-11 22:03 ` Ingo Molnar [this message]
2009-06-11 22:41 ` Yinghai Lu
2009-06-12 8:33 ` Pekka Enberg
2009-06-12 7:17 ` Ingo Molnar
2009-06-12 7:25 ` Li Zefan
2009-06-12 7:29 ` Pekka Enberg
2009-06-12 7:29 ` KAMEZAWA Hiroyuki
2009-06-12 7:33 ` Li Zefan
2009-06-12 7:51 ` Ingo Molnar
2009-06-11 23:14 ` Yinghai Lu
2009-06-12 8:37 ` Pekka Enberg
2009-06-10 21:00 ` [GIT PULL] " Ingo Molnar
2009-06-10 20:57 ` Pekka Enberg
2009-06-10 21:03 ` Yinghai Lu
2009-06-10 21:11 ` 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=20090611220307.GA16180@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox