From: Borislav Petkov <petkovbb@googlemail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.31-rc1: WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask
Date: Sun, 28 Jun 2009 12:05:03 +0200 [thread overview]
Message-ID: <20090628100503.GA8568@liondog.tnic> (raw)
In-Reply-To: <1246112143.21110.2.camel@localhost>
On Sat, Jun 27, 2009 at 04:15:43PM +0200, Thomas Meyer wrote:
> [ 1.516209] ------------[ cut here ]------------
> [ 1.516216] WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask+0x153/0x550()
> [ 1.516218] Hardware name: MS-7250
> [ 1.516219] Modules linked in:
> [ 1.516223] Pid: 1, comm: swapper Not tainted 2.6.31-rc1 #50
> [ 1.516225] Call Trace:
> [ 1.516232] [<ffffffff8106c182>] ? warn_slowpath_common+0x84/0xb2
> [ 1.516236] [<ffffffff81178fb8>] ? sysfs_ilookup_test+0x0/0x3b
> [ 1.516239] [<ffffffff810e5ea8>] ? __alloc_pages_nodemask+0x153/0x550
> [ 1.516245] [<ffffffff811131bd>] ? kmem_cache_create+0x1ac/0x30c
> [ 1.516249] [<ffffffff810e6346>] ? __get_free_pages+0x22/0x77
> [ 1.516253] [<ffffffff81cb5b8f>] ? dccp_init+0xeb/0x38e
> [ 1.516257] [<ffffffff81cb5aa4>] ? dccp_init+0x0/0x38e
> [ 1.516260] [<ffffffff8100908e>] ? do_one_initcall+0x60/0x144
> [ 1.516264] [<ffffffff810c0040>] ? register_irq_proc+0xac/0xdb
> [ 1.516268] [<ffffffff81c6a88f>] ? kernel_init+0x170/0x1dd
> [ 1.516272] [<ffffffff8102cf8a>] ? child_rip+0xa/0x20
> [ 1.516275] [<ffffffff81c6a71f>] ? kernel_init+0x0/0x1dd
> [ 1.516278] [<ffffffff8102cf80>] ? child_rip+0x0/0x20
> [ 1.516283] ---[ end trace 2e1baf37c897af4d ]---
Looks like DCCP is hitting the MAX_ORDER allocation sanity check, CCing relevant
people.
--
Regards/Gruss,
Boris.
prev parent reply other threads:[~2009-06-28 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 14:15 Thomas Meyer
2009-06-28 10:05 ` Borislav Petkov [this message]
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=20090628100503.GA8568@liondog.tnic \
--to=petkovbb@googlemail.com \
--cc=acme@ghostprotocols.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/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®