From: Christoph Lameter <cl@linux.com>
To: Peter Kruse <pk@q-leap.de>
Cc: eric.dumazet@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: I have a blaze of 353 page allocation failures, all alike
Date: Tue, 12 Apr 2011 13:08:09 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1104121306581.14692@router.home> (raw)
In-Reply-To: <4DA4692D.7080207@q-leap.de>
On Tue, 12 Apr 2011, Peter Kruse wrote:
> Hello,
>
> On 02/24/2011 01:01 PM, Peter Kruse wrote:
> > it took a while to find a date for a reboot... Unfortunately
> > it was not possible to get the early boot messages with the
> > kernel 2.6.32.23 since the compiled in log buffer is too
> > small. So we installed as you suggested a more recent kernel
> > 2.6.32.29 with a bigger log buffer, I attach the dmesg
> > of that, and hope that the information in there is useful.
> > We will keep an eye on that server with the newer kernel
> > to see if the allocation failures appear again.
>
> the server was running for a few without any more allocation
> failures with kernel 2.6.32.29 but at one point the server
> stopped responding, it was still possible for a while to
> get a login, and trying to kill some processes but that
> didn't succeed. But after that even login was
> no longer possible so we had to reset it.
> I attach the call trace, I hope you can find out what is
> the problem.
The problem maybe that you have lots and lots of SCSI devices which
consume ZONE_DMA memory for their control structures. I guess that is
oversubscribing the 16M zone.
next prev parent reply other threads:[~2011-04-12 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 15:03 I have a blaze of 353 page allocation failures, all alike Peter Kruse
2011-02-14 16:49 ` Christoph Lameter
2011-02-15 7:44 ` Peter Kruse
2011-02-15 17:30 ` Christoph Lameter
2011-02-16 12:22 ` Peter Kruse
2011-02-16 15:59 ` Christoph Lameter
2011-02-16 16:03 ` Peter Kruse
2011-02-16 16:14 ` Christoph Lameter
2011-02-17 7:31 ` Peter Kruse
2011-02-17 17:03 ` Christoph Lameter
2011-02-18 12:30 ` Peter Kruse
2011-02-24 12:01 ` Peter Kruse
2011-04-12 15:01 ` Peter Kruse
2011-04-12 18:08 ` Christoph Lameter [this message]
2011-04-13 1:34 ` David Rientjes
2011-04-13 7:13 ` Peter Kruse
2011-04-13 16:17 ` Christoph Lameter
2011-05-19 11:56 ` Peter Kruse
2011-05-19 16:00 ` Christoph Lameter
2011-05-23 6:34 ` Peter Kruse
[not found] ` <4E09BEA1.1080501@q-leap.de>
[not found] ` <alpine.DEB.2.00.1107051013500.16869@router.home>
2011-07-05 17:20 ` Mel Gorman
2011-07-06 4:16 ` Dave Chinner
2011-07-06 6:50 ` Peter Kruse
2011-07-06 14:31 ` Christoph Lameter
2011-07-06 15:15 ` Peter Kruse
2011-07-06 15:30 ` Christoph Lameter
2011-11-24 10:53 ` Peter Kruse
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.00.1104121306581.14692@router.home \
--to=cl@linux.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pk@q-leap.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.