From: Eric Sandeen <sandeen@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Andreas Dilger <adilger@sun.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.33-rc6: ext4 triggers warning about high order allocations
Date: Wed, 03 Feb 2010 10:59:12 -0600 [thread overview]
Message-ID: <4B69AB60.5070609@redhat.com> (raw)
In-Reply-To: <20100203060854.GA12489@redhat.com>
Michael S. Tsirkin wrote:
> Hi!
> I got this warning at boot with 2.6.33-rc6:
>
> [ 12.374168] ------------[ cut here ]------------
> [ 12.375798] WARNING: at mm/page_alloc.c:1813 __alloc_pages_nodemask+0x180/0x666()
> [ 12.377401] Hardware name: 2241B48
> [ 12.378984] Modules linked in: [last unloaded: scsi_wait_scan]
> [ 12.380593] Pid: 1, comm: init Not tainted 2.6.33-rc6-aa-nopat #50
> [ 12.382194] Call Trace:
> [ 12.383781] [<ffffffff810b6b3e>] ? __alloc_pages_nodemask+0x180/0x666
> [ 12.385390] [<ffffffff81041cda>] warn_slowpath_common+0x77/0xa4
> [ 12.386996] [<ffffffff81041d16>] warn_slowpath_null+0xf/0x11
> [ 12.388577] [<ffffffff810b6b3e>] __alloc_pages_nodemask+0x180/0x666
> [ 12.390168] [<ffffffff81036a9b>] ? finish_task_switch+0x4b/0xb1
> [ 12.391758] [<ffffffff810b7036>] __get_free_pages+0x12/0x4f
> [ 12.393354] [<ffffffff810de892>] __kmalloc+0x42/0x116
> [ 12.394934] [<ffffffff812405bf>] match_number+0x35/0x98
> [ 12.396493] [<ffffffff8124064d>] match_int+0xb/0xd
> [ 12.398045] [<ffffffff81169c8c>] parse_options+0x5fe/0x733
> [ 12.399594] [<ffffffff811058c3>] ? __wait_on_buffer+0x1f/0x21
> [ 12.401157] [<ffffffff8116a2dc>] ext4_fill_super+0x373/0x2070
Are you mounting with any interesting options?
-Eric
next prev parent reply other threads:[~2010-02-03 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 6:08 2.6.33-rc6: ext4 triggers warning about high order allocations Michael S. Tsirkin
2010-02-03 16:59 ` Eric Sandeen [this message]
2010-02-03 17:58 ` Michael S. Tsirkin
2010-02-03 19:22 ` Eric Sandeen
2010-02-07 12:30 ` Michael S. Tsirkin
2010-02-07 19:00 ` Eric Sandeen
2010-02-07 21:26 ` Michael S. Tsirkin
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=4B69AB60.5070609@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).