From: Christoph Lameter <cl@linux.com>
To: Peter Kruse <pk@q-leap.de>
Cc: Dave Chinner <david@fromorbit.com>, Mel Gorman <mel@csn.ul.ie>,
David Rientjes <rientjes@google.com>,
eric.dumazet@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: I have a blaze of 353 page allocation failures, all alike
Date: Wed, 6 Jul 2011 09:31:45 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1107060931190.17202@router.home> (raw)
In-Reply-To: <4E1405C3.20904@q-leap.de>
On Wed, 6 Jul 2011, Peter Kruse wrote:
> Ok then I think we will schedule a kernel update and if the
> server then runs for more than 40 days we could say that
> the problem is fixed.
Note that this is *not* the original problem you reported. I do not see
page alloc failures in your latest logs.
next prev parent reply other threads:[~2011-07-06 14:31 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
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 [this message]
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.1107060931190.17202@router.home \
--to=cl@linux.com \
--cc=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=pk@q-leap.de \
--cc=rientjes@google.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 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.