[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20091222153936.269e8153.akpm@linux-foundation.org>
Date: Tue, 22 Dec 2009 15:39:36 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: linux-ext4@...r.kernel.org
Subject: Re: [Bug 14843] New: WARNING: at mm/page_alloc.c at ext4 root mount
On Sat, 19 Dec 2009 16:12:52 GMT
bugzilla-daemon@...zilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=14843
>
> Summary: WARNING: at mm/page_alloc.c at ext4 root mount
> Product: Memory Management
> Version: 2.5
> Kernel Version: 2.6.33-rc1
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Page Allocator
> AssignedTo: akpm@...ux-foundation.org
> ReportedBy: casteyde.christian@...e.fr
> Regression: Yes
>
>
> Kernel 2.6.33-rc1 64bits with kmemcheck and other debug options
> Athlon64 3GHz single core
> Acer Aspire 1511LMi
> Bluewhite 64 13 (32 bits port of Slackware)
>
> Since 2.6.33-rc1, I get the following warning at boot when the root ext4
> filesystem is mounted:
> kmemleak: Automatic memory scanning thread started
> EXT3-fs (hda2): error: couldn't mount because of unsupported optional features
> (240)
> EXT2-fs (hda2): error: couldn't mount because of unsupported optional features
> (240)
> ------------[ cut here ]------------
> WARNING: at mm/page_alloc.c:1220 get_page_from_freelist+0x6a4/0x6c0()
Can we please zap that __GFP_NOFAIL in journal_init_common()?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists