From: Lukas Hejtmanek <xhejtman@hell.sks3.muni.cz>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Lukas Hejtmanek <xhejtman@hell.sks3.muni.cz>,
Andrew Morton <akpm@osdl.org>,
zaphodb@zaphods.net, marcelo.tosatti@cyclades.com,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.9 Multiple Page Allocation Failures
Date: Wed, 8 Dec 2004 12:18:32 +0100 [thread overview]
Message-ID: <20041208111832.GA13592@mail.muni.cz> (raw)
In-Reply-To: <41B63738.2010305@cyberone.com.au>
On Wed, Dec 08, 2004 at 10:05:28AM +1100, Nick Piggin wrote:
> If you are able to test 2.6.10-rc3, that would be nice.
No better. min_free_kb is set by default to 3831 but I can still reproduce this:
swapper: page allocation failure. order:0, mode:0x20
[<c0135472>] __alloc_pages+0x1b7/0x35b
[<c013563b>] __get_free_pages+0x25/0x3f
[<c0138725>] kmem_getpages+0x21/0xc9
[<c0139253>] alloc_slabmgmt+0x55/0x5f
[<c01393d2>] cache_grow+0xab/0x14d
[<c01395f0>] cache_alloc_refill+0x17c/0x221
[<c0139932>] __kmalloc+0x85/0x8c
[<c02f49e9>] alloc_skb+0x47/0xe0
[<c0294b97>] e1000_alloc_rx_buffers+0x44/0xe3
[<c029489a>] e1000_clean_rx_irq+0x18e/0x447
[<c02f4c37>] __kfree_skb+0x83/0x107
[<c029447b>] e1000_clean+0x51/0xca
[<c02fabbe>] net_rx_action+0x77/0xf6
[<c011b8f7>] __do_softirq+0xb7/0xc6
[<c0104979>] do_softirq+0x4a/0x59
=======================
[<c012f909>] irq_exit+0x3a/0x3c
[<c0104875>] do_IRQ+0x4d/0x6a
[<c0102ed6>] common_interrupt+0x1a/0x20
[<c010050e>] default_idle+0x0/0x2c
[<c0100537>] default_idle+0x29/0x2c
[<c01005ac>] cpu_idle+0x3f/0x58
[<c043fa20>] start_kernel+0x14c/0x165
[<c043f4bd>] unknown_bootoption+0x0/0x1ab
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2004-12-08 11:19 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 22:24 Kernel 2.6.9 Multiple Page Allocation Failures (Part 2) Stefan Schmidt
2004-11-04 12:17 ` Marcelo Tosatti
2004-11-04 18:18 ` Stefan Schmidt
2004-11-09 16:41 ` Kernel 2.6.9 Multiple Page Allocation Failures Marcelo Tosatti
2004-11-09 22:35 ` Lukas Hejtmanek
2004-11-09 22:46 ` Andrew Morton
2004-11-09 22:44 ` Lukas Hejtmanek
2004-11-09 20:33 ` Marcelo Tosatti
2004-11-10 20:35 ` Lukas Hejtmanek
2004-11-10 21:09 ` Andrew Morton
2004-11-10 21:24 ` Lukas Hejtmanek
2004-11-10 21:47 ` Andrew Morton
2004-11-10 21:28 ` Lukas Hejtmanek
2004-11-10 18:11 ` Marcelo Tosatti
2004-11-11 1:04 ` Lukas Hejtmanek
2004-11-11 21:44 ` Lukas Hejtmanek
2004-11-12 12:09 ` Nick Piggin
2004-11-13 14:47 ` Stefan Schmidt
2004-11-16 9:33 ` Marcelo Tosatti
2004-11-16 17:05 ` Lukas Hejtmanek
2004-11-21 1:43 ` Stefan Schmidt
2004-11-21 2:42 ` Stefan Schmidt
2004-12-02 19:54 ` Lukas Hejtmanek
2004-12-02 20:25 ` Andrew Morton
2004-12-02 21:03 ` Lukas Hejtmanek
2004-12-02 22:31 ` Stefan Schmidt
2004-12-02 22:48 ` Lukas Hejtmanek
2004-12-02 22:56 ` Andrew Morton
2004-12-02 23:18 ` Lukas Hejtmanek
2004-12-03 0:18 ` Andrew Morton
2004-12-03 12:11 ` Lukas Hejtmanek
2004-12-03 12:17 ` Lukas Hejtmanek
2004-12-07 22:52 ` Nick Piggin
2004-12-07 22:59 ` Lukas Hejtmanek
2004-12-07 23:05 ` Nick Piggin
2004-12-08 11:18 ` Lukas Hejtmanek [this message]
2004-12-08 11:23 ` Nick Piggin
2004-12-08 11:46 ` Lukas Hejtmanek
2004-12-08 13:14 ` Lukas Hejtmanek
2004-12-09 8:52 ` Nick Piggin
2004-12-09 9:02 ` Lukas Hejtmanek
2004-12-09 10:29 ` Nick Piggin
2004-12-09 10:37 ` Lukas Hejtmanek
2004-12-03 6:18 ` Nathan Scott
2004-12-03 7:06 ` Andrew Morton
2004-12-07 11:17 ` Lukas Hejtmanek
2004-12-08 0:15 ` Nathan Scott
2004-12-08 0:36 ` Lukas Hejtmanek
2004-12-03 10:35 ` Christoph Hellwig
2004-12-03 10:58 ` P
2004-12-03 17:11 ` Andrew Morton
2004-11-09 23:52 ` Stefan Schmidt
2004-11-10 1:27 ` 2.6.10-rc1-mm4 -1 EAGAIN after allocation failure was: " Stefan Schmidt
2004-11-10 1:39 ` Andrew Morton
2004-11-10 2:03 ` Stefan Schmidt
2004-11-10 2:21 ` Andrew Morton
2004-11-10 4:24 ` Nick Piggin
2004-11-10 10:28 ` Stefan Schmidt
2004-11-10 12:06 ` Stefan Schmidt
2004-11-10 8:58 ` Marcelo Tosatti
2004-11-10 12:48 ` Stefan Schmidt
2004-11-10 10:56 ` Marcelo Tosatti
2004-11-11 1:23 ` Nick Piggin
2004-11-11 18:31 ` jhigdon
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=20041208111832.GA13592@mail.muni.cz \
--to=xhejtman@hell.sks3.muni.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=piggin@cyberone.com.au \
--cc=zaphodb@zaphods.net \
/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