From: "linuxkernel2.20.sandos@spamgourmet.com" <majsetvger.100.sandos@spamgourmet.com>
To: linux-kernel@vger.kernel.org
Cc: +linuxkernel2+sandos+f66671bddc.linux-kernel#vger.kernel.org@spamgourmet.com
Subject: Re: E1000 - page allocation failure - saga continues :( message 1 of 20)
Date: Tue, 10 May 2005 11:32:54 +0200 [thread overview]
Message-ID: <42807FC6.10400@spamgourmet.com> (raw)
In-Reply-To: <42806EA0.2070501@yahoo.com.au>
Nick Piggin - nickpiggin@yahoo.com.au wrote:
> linuxkernel2.20.sandos@spamgourmet.com wrote:
>
>> >Anyway i'll try to catch THE option that make the kernel not so happy
>> >under heavy stress. Stay tuned
>>
>> How did this turn out? Any luck? Im seeing this same problem with my
>> e1000, now I did enable rx/tx flow control, I reniced kswapd and I
>> changed vm.min_free_kbytes to 65536, and the problem went away.
>>
>> It would be nice with a "cleaner" solution though.
>>
>
> What kernel are you using?
> Are you doing a lot of block IO as well?
I am using 2.6.11.8.
Yes, the server is a fileserver for both the internet (~10Mbit) and
internally (1Gbit e1000). Hardware is pretty old so is pretty heavily
loaded and with 256MB RAM.
---
John Bäckstrand
next prev parent reply other threads:[~2005-05-10 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 8:06 E1000 - page allocation failure - saga continues :( linuxkernel2.20.sandos
2005-05-10 8:19 ` Nick Piggin
2005-05-10 9:32 ` linuxkernel2.20.sandos@spamgourmet.com [this message]
2005-05-10 9:44 ` E1000 - page allocation failure - saga continues :( message 1 of 20) Nick Piggin
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=42807FC6.10400@spamgourmet.com \
--to=majsetvger.100.sandos@spamgourmet.com \
--cc=+linuxkernel2+sandos+f66671bddc.linux-kernel#vger.kernel.org@spamgourmet.com \
--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