All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: David Rientjes <rientjes@google.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hugh.dickins@tiscali.co.uk>
Subject: Re: 2.6.32.5 regression: page allocation failure. order:1,
Date: Wed, 27 Jan 2010 22:32:44 -0500	[thread overview]
Message-ID: <4B61055C.8040604@teksavvy.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1001271701170.17513@chino.kir.corp.google.com>

David Rientjes wrote:
> On Wed, 27 Jan 2010, Mark Lord wrote:
>> It's rock solid again with 2.6.31.12 on it now.
>>
> 
> Is there something specific about the workload that makes it easily 
> reproducible?  Are you saying that 2.6.31.12 is "rock solid" because it 
> has survived a certain workload that caused these page allocation failures 
> with 2.6.32.5, or simply because it has a longer uptime and hasn't shown 
> a problem?  It would be very helpful to describe the load so that we can 
> attempt to reproduce it locally without a sacrifice to your server.
..

Good questions, and I do "feel for you" here.  :)

That machine has a light workload.  Web server, email server,
dhcp for the small local network, name server, etc.

It sits at one end of a 6mb/1.5mb DSL connection, hardly busy at all.

But the logfile posted shows many of those "allocation failures"
within the first (only)36 hours of running 2.6.32.5:

  mirrordir (doing a backup to a USB drive)
  apcupsd  (UPS monitoring; hardly an intensive activity)
  apache2  (the web server receives rather light use, and no fancy php or anything)
  apache2  (again!)
  apache2  (and again)
  apache2  (another)
  apache2  (yet again)
  ...
  apache2  (and again again)
  vim      (hey, can't a guy edit his driver sources ??)
  cc1      (or compile them?)

So, not much happening, really.
It's a slow machine, a 600Mhz C7 ("VIA Samuel 2"), with only 512MB of RAM.

We've got 2.6.32.5 running on several other machines here with nary a glitch,
but all of those have 2-4GB of RAM.

Cheers

  reply	other threads:[~2010-01-28  3:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27  2:13 2.6.32.5 regression: page allocation failure. order:1, Mark Lord
2010-01-27 12:08 ` Mel Gorman
2010-01-27 22:39   ` Mark Lord
2010-01-28  1:04     ` David Rientjes
2010-01-28  3:32       ` Mark Lord [this message]
2010-01-28  4:17     ` Mark Lord
2010-01-28  4:34       ` Mark Lord
2010-01-28  9:01         ` Mike Galbraith
2010-01-28 10:52         ` Rafael J. Wysocki
2010-01-28 13:51           ` Mark Lord
2010-01-28 14:17             ` Mark Lord
2010-01-28 14:24               ` Mel Gorman
2010-01-29 13:56                 ` Mark Lord
2010-01-29 15:46                   ` Mel Gorman
2010-01-29 17:27                     ` Hugh Dickins
2010-01-29 17:34                       ` Mel Gorman
2010-01-29 17:46                         ` [PATCH] mm: fix migratetype bug which slowed swapping Hugh Dickins
2010-01-29 17:46                           ` Hugh Dickins

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=4B61055C.8040604@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --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.