From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: linux-kernel@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: E1000 - page allocation failure - saga continues :(
Date: Wed, 20 Apr 2005 09:12:24 +0200 [thread overview]
Message-ID: <426600D8.5060900@univ-nantes.fr> (raw)
In-Reply-To: <20050419080424.GA28153@mail.muni.cz>
Lukas Hejtmanek a écrit :
>On Tue, Apr 19, 2005 at 09:23:46AM +0200, Yann Dupont wrote:
>
>
>>Do you have turned NAPI on ??? I tried without it off on e1000 and ...
>>surprise !
>>Don't have any messages since 12H now (usually I got those in less than 1H)
>>
>>
>
>I have NAPI on. I tried to turn it off but my test failed, I can see allocation
>failure again.
>
>
>
Well. forgives me :)
I have re turned NAPI On and my box is still happy 19H later...
So it's obviously not napi.
The problem is beetween the 2 incarnations of kernel (2.6.11.7 with
kswapd meesages on thoses who works well), I've changed some more options
Not exactly the best way to track bugs :(
Anyway i'll try to catch THE option that make the kernel not so happy
under heavy stress. Stay tuned,
--
Yann Dupont, Cri de l'université de Nantes
Tel: 02.51.12.53.91 - Fax: 02.51.12.58.60 - Yann.Dupont@univ-nantes.fr
next prev parent reply other threads:[~2005-04-20 7:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 21:48 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 [this message]
2005-05-10 8:06 linuxkernel2.20.sandos
2005-05-10 8:19 ` 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=426600D8.5060900@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=xhejtman@mail.muni.cz \
/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
all inboxes | Powered by JetHome®