From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Lukas Hejtmanek <xhejtman@mail.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: E1000 - page allocation failure - saga continues :(
Date: Mon, 18 Apr 2005 14:10:31 +0200 [thread overview]
Message-ID: <4263A3B7.6010702@univ-nantes.fr> (raw)
In-Reply-To: <20050414214828.GB9591@mail.muni.cz>
Lukas Hejtmanek a écrit :
>Hello,
>
>today I tried 2.6.11.7 kernel with hoping that allocation failures disappear.
>Unfortunately they did not.
>
>Default min_free_kb is 3200kB.
>
>Here is stack trace:
>
>swapper: page allocation failure. order:0, mode:0x20
> [<c0139783>] __alloc_pages+0x2b3/0x420
> [<c013c4f1>] kmem_getpages+0x31/0xa0
> [<c013d22e>] cache_grow+0xae/0x160
> [<c0342b50>] ip_rcv_finish+0x0/0x280
> [<c013d45b>] cache_alloc_refill+0x17b/0x230
> [<c013d7d8>] __kmalloc+0x88/0xa0
> [<c0327ce7>] alloc_skb+0x47/0xf0
> [<c02bff97>] e1000_alloc_rx_buffers+0x57/0x100
> [<c02bfc3f>] e1000_clean_rx_irq+0x1bf/0x4c0
>
>
I have those problems too. The (temporary ?) fix is to raise the
min_free_kb to an higher value.
echo 65535 > /proc/sys/vm/min_free_kbytes
Maybe such an high value is totally silly, but at least I don't have
those messages.
Sincerely yours,
--
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-18 12:10 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 [this message]
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
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=4263A3B7.6010702@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=linux-kernel@vger.kernel.org \
--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®