From: Phil Oester <kernel@linuxace.com>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"Andrew Morton" <akpm@linux-foundation.org>,
zsirmo@zsirmo.hu, LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>, netdev <netdev@vger.kernel.org>,
"Matt Carlson" <mcarlson@broadcom.com>,
"Michael Chan" <mchan@broadcom.com>,
"Brian Vowell" <brian.vowell@gmail.com>
Subject: Re: bug report
Date: Sat, 7 Jun 2008 08:09:48 -0700 [thread overview]
Message-ID: <20080607150948.GA4690@linuxace.com> (raw)
In-Reply-To: <6101e8c40806070550h62866816s1d8f8c1ba31f59f@mail.gmail.com>
On Sat, Jun 07, 2008 at 02:50:06PM +0200, Oliver Pinter wrote:
> [snip]
> Jun 6 14:04:11 www kernel: [ 6464.556309] clamscan: page allocation
> failure. order:3, mode:0x4020 <------------- this
"Me too". Lots of order 3 allocation failures on e1000 nics
since upgrading some heavy traffic boxes to 2.6.25 (though from 2.6.21,
so unclear on when it began).
Phil
Jun 2 11:11:24 px01 kernel: swapper: page allocation failure. order:3, mode:0x4020
Jun 2 11:11:24 px01 kernel: Pid: 0, comm: swapper Not tainted 2.6.25.2-x86_64.1 #1
Jun 2 11:11:24 px01 kernel:
Jun 2 11:11:24 px01 kernel: Call Trace:
Jun 2 11:11:24 px01 kernel: <IRQ> [<ffffffff8024ce51>] __alloc_pages+0x2dd/0x2f6
Jun 2 11:11:24 px01 kernel: [<ffffffff8026578d>] __slab_alloc+0x16e/0x4f9
Jun 2 11:11:24 px01 kernel: [<ffffffff80394e84>] tcp_collapse+0x164/0x394
Jun 2 11:11:25 px01 kernel: [<ffffffff802656d0>] __slab_alloc+0xb1/0x4f9
Jun 2 11:11:25 px01 kernel: [<ffffffff80394e84>] tcp_collapse+0x164/0x394
Jun 2 11:11:25 px01 kernel: [<ffffffff8026685d>] __kmalloc_track_caller+0x82/0xb8
Jun 2 11:11:25 px01 kernel: [<ffffffff8036a124>] __alloc_skb+0x5b/0x121
Jun 2 11:11:25 px01 kernel: [<ffffffff80394e84>] tcp_collapse+0x164/0x394
Jun 2 11:11:25 px01 kernel: [<ffffffff80395261>] tcp_prune_queue+0x1ad/0x21e
Jun 2 11:11:25 px01 kernel: [<ffffffff803954ba>] tcp_data_queue+0x1e8/0xbab
Jun 2 11:11:25 px01 kernel: [<ffffffff803974e8>] tcp_rcv_established+0x64c/0x6fc
Jun 2 11:11:25 px01 kernel: [<ffffffff8039c76f>] tcp_v4_do_rcv+0x2c/0x1b4
Jun 2 11:11:25 px01 kernel: [<ffffffff8039e43e>] tcp_v4_rcv+0x6b3/0x705
Jun 2 11:11:25 px01 kernel: [<ffffffff80384cdc>] ip_local_deliver_finish+0xf6/0x1b3
Jun 2 11:11:25 px01 kernel: [<ffffffff80384bc3>] ip_rcv_finish+0x2bf/0x2e2
Jun 2 11:11:25 px01 kernel: [<ffffffff8023ada3>] getnstimeofday+0x2f/0x83
Jun 2 11:11:25 px01 kernel: [<ffffffff8036e6b2>] netif_receive_skb+0x1af/0x21b
Jun 2 11:11:25 px01 kernel: [<ffffffff8032da6d>] e1000_clean_rx_irq+0x3f3/0x4e7
next prev parent reply other threads:[~2008-06-07 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48499731.1080807@gmail.com>
2008-06-07 1:44 ` bug report Oliver Pinter
2008-06-07 1:45 ` Oliver Pinter
2008-06-07 5:56 ` Andrew Morton
2008-06-07 8:47 ` Ilpo Järvinen
2008-06-07 12:50 ` Oliver Pinter
2008-06-07 15:09 ` Phil Oester [this message]
2008-06-07 18:53 ` Oliver Pinter
2008-06-08 11:56 ` Zsiros Attila
2008-06-09 17:04 ` Oliver Pinter
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=20080607150948.GA4690@linuxace.com \
--to=kernel@linuxace.com \
--cc=akpm@linux-foundation.org \
--cc=brian.vowell@gmail.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=zsirmo@zsirmo.hu \
/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;
as well as URLs for NNTP newsgroup(s).