From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Jeff V. Merkey" <jmerkey@drdos.com>
Cc: linux-kernel@vger.kernel.org, jmerkey@comcast.net
Subject: Re: 2.6.8.1 mempool subsystem sickness
Date: Wed, 15 Sep 2004 08:59:54 +1000 [thread overview]
Message-ID: <414777EA.5080406@yahoo.com.au> (raw)
In-Reply-To: <4147555C.7010809@drdos.com>
Jeff V. Merkey wrote:
>
> Hi Jeff,
>
>> Can you give us a few more details please? Post the allocation failure
>> messages in full, and post /proc/meminfo, etc. Thanks.
>> -
>>
> Here you go.
>
Thanks.
> Jeff
>
> Sep 14 14:18:59 datascout4 kernel: if_regen2: page allocation failure.
> order:3, mode:0x20
> Sep 14 14:18:59 datascout4 kernel: [<80106c7e>] dump_stack+0x1e/0x30
> Sep 14 14:18:59 datascout4 kernel: [<80134aac>] __alloc_pages+0x2dc/0x350
> Sep 14 14:18:59 datascout4 kernel: [<80134b42>] __get_free_pages+0x22/0x50
> Sep 14 14:18:59 datascout4 kernel: [<80137d9f>] kmem_getpages+0x1f/0xd0
> Sep 14 14:18:59 datascout4 kernel: [<8013897a>] cache_grow+0x9a/0x130
> Sep 14 14:18:59 datascout4 kernel: [<80138b4b>]
> cache_alloc_refill+0x13b/0x1e0
> Sep 14 14:18:59 datascout4 kernel: [<80138fa4>] __kmalloc+0x74/0x80
> Sep 14 14:18:59 datascout4 kernel: [<80299298>] alloc_skb+0x48/0xf0
> Sep 14 14:18:59 datascout4 kernel: [<f8972e67>]
> create_xmit_packet+0x57/0x100 [dsfs]
> Sep 14 14:18:59 datascout4 kernel: [<f8973150>] regen_data+0x60/0x1d0
> [dsfs]
> Sep 14 14:18:59 datascout4 kernel: [<80104355>]
> kernel_thread_helper+0x5/0x10
> Sep 14 14:18:59 datascout4 kernel: printk: 12 messages suppressed.
>
> MemTotal: 1944860 kB
> MemFree: 200008 kB
Wow. You have 200MB free, and can't satisfy an order 3 allocation (although it
is atomic).
Now it just so happens that I have a couple of patches that are supposed to fix
exactly this. Unfortunately I haven't had the hardware to properly test them
(they're pretty stable though). Want to give them a try? :)
next prev parent reply other threads:[~2004-09-14 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <091420042058.15928.41475B8000002BA100003E382200763704970A059D0A0306@comcast.net>
2004-09-14 20:32 ` 2.6.8.1 mempool subsystem sickness Jeff V. Merkey
2004-09-14 22:59 ` Nick Piggin [this message]
[not found] ` <20040914223122.GA3325@galt.devicelogics.com>
2004-09-14 23:51 ` Nick Piggin
2004-09-15 0:51 ` Gene Heskett
2004-09-15 17:27 ` Jeff V. Merkey
2004-09-15 17:33 ` Jeff V. Merkey
2004-09-16 1:46 ` Nick Piggin
2004-09-16 5:56 ` Jens Axboe
2004-09-08 16:48 jmerkey
2004-09-08 23:05 ` 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=414777EA.5080406@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=jmerkey@comcast.net \
--cc=jmerkey@drdos.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