From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4 and 2.6.7 page allocation failure / e1000 related ?
Date: Wed, 30 Jun 2004 17:03:43 +1000 [thread overview]
Message-ID: <40E265CF.9040307@yahoo.com.au> (raw)
In-Reply-To: <003c01c45e6b$a2323ed0$0201a8c0@hawk>
Christopher S. Aker wrote:
> Hello,
>
> I've had this appear in dmesg a few times on a number of different systems, all
> identical hardware: SuperMicro 6013P-i dual Xeon, with 4GB of RAM, built-in e1000
> NICs connected via 100Mbit switch.
>
> It doesn't appear to cause any ill effects. I haven't provided all the variations
> of the messages, but the consistent thing between them are the e1000_* calls.
> This isn't an OOM situation, the machines are only a handful of MB into swap (if
> that).
>
It shouldn't cause any problems, although an order 0 failure
shouldn't be happening often.
It is possible we want to increase /proc/sys/vm/min_free_kbytes
a bit, or increase the amount of extra memory a __GFP_HIGH
allocation can get access to.
You could try the increasing former and see if that helps.
prev parent reply other threads:[~2004-06-30 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 6:29 2.6.4 and 2.6.7 page allocation failure / e1000 related ? Christopher S. Aker
2004-06-30 7:03 ` Nick Piggin [this message]
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=40E265CF.9040307@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=caker@theshore.net \
--cc=linux-kernel@vger.kernel.org \
/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