From: Andrew Morton <akpm@osdl.org>
To: "Alexander Y. Fomichev" <gluk@php4.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Call Trace: page allocation failure - is it normal behaviour?
Date: Tue, 3 Feb 2004 16:10:55 -0800 [thread overview]
Message-ID: <20040203161055.47596de4.akpm@osdl.org> (raw)
In-Reply-To: <200402031806.15439.gluk@php4.ru>
"Alexander Y. Fomichev" <gluk@php4.ru> wrote:
>
> Hello,
>
> I noticed some call trace when testing box under heavy load.
> To create a load following jobs have been running simultaneously.
>
> ab2 -c 200 -n 10000000 http://192.168.114.239/
> fsx-linux -l 900000000 fsx-data3
> dbench 100
>
> adt root # w
> 19:24:32 up 14:58, 6 users, load average: 90.92, 83.97, 84.28
>
> Some times after dmesg has shown multiple call traces of two types:
>
> swapper: page allocation failure. order:2, mode:0x20
> Call Trace:
> [<c014059c>] __alloc_pages+0x30c/0x350
> [<c0140605>] __get_free_pages+0x25/0x40
> [<c01435a7>] cache_grow+0xc7/0x310
> [<c01438fe>] cache_alloc_refill+0x10e/0x2c0
> [<c0143e01>] __kmalloc+0x71/0x80
> [<c0266697>] alloc_skb+0x47/0xe0
> [<c0294e7e>] tcp_fragment+0x5e/0x340
> [<c02975b8>] tcp_write_wakeup+0xe8/0x280
> [<c0298870>] tcp_write_timer+0x0/0x130
> [<c029776d>] tcp_send_probe0+0x1d/0x110
> [<c0298933>] tcp_write_timer+0xc3/0x130
> [<c01298f7>] run_timer_softirq+0xe7/0x1d0
> [<c0124e2a>] do_softirq+0xca/0xd0
>
> ...
> bwt I've noticed no visible harm to system and question ruther is
> whether this behaviour is normal under such circumstances?
Yes, it is expected and the networking stack will recover. We'll remove
that debug code at some point.
prev parent reply other threads:[~2004-02-04 0:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 15:06 Call Trace: page allocation failure - is it normal behaviour? Alexander Y. Fomichev
2004-02-04 0:10 ` Andrew Morton [this message]
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=20040203161055.47596de4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=gluk@php4.ru \
--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