From: Christian Kujau <lists@nerdbynature.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: LKML <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, mingo@elte.hu,
jeremy.fitzhardinge@citrix.com
Subject: Re: WARNING: at mm/bootmem.c:535 alloc_arch_preferred_bootmem
Date: Tue, 30 Jun 2009 03:07:57 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.01.0906300300000.6439@bogon> (raw)
In-Reply-To: <1246351243.8014.14.camel@penberg-laptop>
On Tue, 30 Jun 2009, Pekka Enberg wrote:
> I think you're the first one to report this. The warning is harmless but
> the following patch should fix things up. Thanks!
Yes, your patch makes the warning go away, Thanks!
But, I think the patch description should read:
> Fixes the following boot-time warning:
> ------------[ cut here ]------------
> WARNING: at mm/bootmem.c:535 alloc_arch_preferred_bootmem+0x27/0x45()
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.30 #1
> Call Trace:
> [<ffffffff8102d6e3>] ? warn_slowpath_common+0x73/0xb0
> [<ffffffff810210d9>] ? pvclock_clocksource_read+0x49/0x90
> [<ffffffff812e522f>] ? alloc_arch_preferred_bootmem+0x27/0x45
> [<ffffffff812e5761>] ? ___alloc_bootmem_nopanic+0x39/0xc9
> [<ffffffff812e57fa>] ? ___alloc_bootmem+0x9/0x2f
> [<ffffffff812e9e21>] ? xen_init_IRQ+0x25/0x61
> [<ffffffff812d69ee>] ? start_kernel+0x1b5/0x29e
> ---[ end trace 4eaa2a86a8e2da22 ]---
[...]
(I myself forgot to put this warning into my initial message too)
Thanks for the fast response and the fix!
Christian.
--
BOFH excuse #65:
system needs to be rebooted
next prev parent reply other threads:[~2009-06-30 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 3:01 Christian Kujau
2009-06-30 8:40 ` Pekka Enberg
2009-06-30 10:07 ` Christian Kujau [this message]
2009-06-30 20:59 ` Jeremy Fitzhardinge
2009-07-01 5:58 ` Pekka Enberg
2009-07-01 8:40 ` Ingo Molnar
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=alpine.DEB.2.01.0906300300000.6439@bogon \
--to=lists@nerdbynature.de \
--cc=akpm@linux-foundation.org \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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
all inboxes | Powered by JetHome®