From: Frans Pop <elendil@planet.nl>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-kernel@vger.kernel.org, Mel Gorman <mel@csn.ul.ie>
Subject: Re: Page alloc problems with 2.6.32-rc kernels
Date: Tue, 27 Oct 2009 11:38:00 +0100 [thread overview]
Message-ID: <200910271138.01624.elendil@planet.nl> (raw)
In-Reply-To: <20091027095014.GA22215@gibson.comsick.at>
Michael Guntsche wrote:
> I noticed that I get page alloc errors on one of my machines.
> It is an old server I use as a fileserver with 512MB RAM. Before
> 2.6.3[12] I did not see this problem at all.
> This only seems to happens when I use mutt on this machine.
> I know that it means I am running out of memory here, but I am wondering
> why I did not see this before....
>
> mutt: page allocation failure. order:1, mode:0x20
> Pid: 21746, comm: mutt Not tainted 2.6.32-rc5 #2
This is a known issue that's being heavily investigated, but is proving
very elusive. See http://lkml.org/lkml/2009/10/22/128 for an overview.
Can you easily reproduce the problem, or does it happen at random moments?
If you can reproduce it, it would be great if you could test the patches
mentioned in that mail.
Cheers,
FJP
next prev parent reply other threads:[~2009-10-27 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 9:50 Page alloc problems with 2.6.32-rc kernels Michael Guntsche
2009-10-27 10:38 ` Frans Pop [this message]
2009-10-27 14:00 ` Michael Guntsche
2009-10-27 14:00 ` Mel Gorman
2009-10-29 8:48 ` Michael Guntsche
2009-10-29 10:05 ` Michael Guntsche
2009-10-29 15:24 ` Michael Guntsche
2009-10-30 19:28 ` Michael Guntsche
2009-10-27 13:01 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2009-11-02 12:20 Michael Guntsche
2009-11-04 0:14 ` Frans Pop
2009-11-04 7:17 ` Michael Guntsche
2009-11-04 22:14 ` Frans Pop
2009-11-04 23:07 ` Michael Guntsche
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=200910271138.01624.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mike@it-loops.com \
/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