From: Nick Piggin <nickpiggin@yahoo.com.au>
To: linuxkernel2.20.sandos@spamgourmet.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: E1000 - page allocation failure - saga continues :(
Date: Tue, 10 May 2005 18:19:44 +1000 [thread overview]
Message-ID: <42806EA0.2070501@yahoo.com.au> (raw)
In-Reply-To: <42806B78.2020708@home.se>
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?
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2005-05-10 8:19 UTC|newest]
Thread overview: 18+ 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 [this message]
2005-05-10 9:32 ` E1000 - page allocation failure - saga continues :( message 1 of 20) linuxkernel2.20.sandos@spamgourmet.com
2005-05-10 9:44 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 21:48 E1000 - page allocation failure - saga continues :( Lukas Hejtmanek
2005-04-18 12:10 ` Yann Dupont
2005-04-18 12:22 ` Lukas Hejtmanek
2005-04-18 12:24 ` Yann Dupont
2005-04-18 12:34 ` Lukas Hejtmanek
2005-04-18 12:39 ` Yann Dupont
2005-04-19 7:23 ` Yann Dupont
2005-04-19 8:03 ` Nick Piggin
2005-04-19 8:15 ` Yann Dupont
2005-04-19 8:24 ` Nick Piggin
2005-04-19 9:34 ` Lukas Hejtmanek
2005-04-19 8:04 ` Lukas Hejtmanek
2005-04-20 3:42 ` Nuno Silva
2005-04-20 7:12 ` Yann Dupont
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=42806EA0.2070501@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxkernel2.20.sandos@spamgourmet.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.