From: Jesse Brandeburg <jesse.brandeburg@gmail.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: What to do with this message (2.6.30.1) ?
Date: Mon, 13 Jul 2009 22:40:39 -0700 [thread overview]
Message-ID: <4807377b0907132240g6f74c9cbnf1302d354a0e0a72@mail.gmail.com> (raw)
In-Reply-To: <20090713134621.124aa18e.skraw@ithnet.com>
On Mon, Jul 13, 2009 at 4:46 AM, Stephan von Krawczynski
<skraw@ithnet.com> wrote:
>
> Hello all,
>
> first day of using 2.6.30.1 on a box that mostly accepts rsync connections
> revealed this message. This is in fact not the only one of this type. Quite
> a lot from other processes follow. What can I do to prevent that? Is that
> a kind of a bug?
> I did not experience that on a box with the same job using tg3 instead of
> e1000e.
>
> Jul 13 01:10:57 backup kernel: swapper: page allocation failure. order:0, mode:0x20
> Jul 13 01:10:57 backup kernel: Pid: 0, comm: swapper Not tainted 2.6.30.1 #3
> Jul 13 01:10:57 backup kernel: Call Trace:
> Jul 13 01:10:57 backup kernel: <IRQ> [<ffffffff80269182>] ? __alloc_pages_internal+0x3df/0x3ff
> Jul 13 01:10:57 backup kernel: [<ffffffff802876cf>] ? cache_alloc_refill+0x25e/0x4a0
> Jul 13 01:10:57 backup kernel: [<ffffffff803eb067>] ? sock_def_readable+0x10/0x62
> Jul 13 01:10:57 backup kernel: [<ffffffff8028798a>] ? __kmalloc+0x79/0xa1
> Jul 13 01:10:57 backup kernel: [<ffffffff803ef98a>] ? __alloc_skb+0x5c/0x12a
> Jul 13 01:10:57 backup kernel: [<ffffffff803f0558>] ? __netdev_alloc_skb+0x15/0x2f
> Jul 13 01:10:57 backup kernel: [<ffffffffa000cda0>] ? e1000_alloc_rx_buffers+0x8c/0x248 [e1000e]
> Jul 13 01:10:57 backup kernel: [<ffffffffa000d262>] ? e1000_clean_rx_irq+0x2a2/0x2db [e1000e]
> Jul 13 01:10:57 backup kernel: [<ffffffffa000e8dc>] ? e1000_clean+0x70/0x219 [e1000e]
> Jul 13 01:10:57 backup kernel: [<ffffffff803f3adf>] ? net_rx_action+0x69/0x11f
> Jul 13 01:10:58 backup kernel: [<ffffffff802373eb>] ? __do_softirq+0x66/0xf7
> Jul 13 01:10:58 backup kernel: [<ffffffff8020bebc>] ? call_softirq+0x1c/0x28
> Jul 13 01:10:58 backup kernel: [<ffffffff8020d680>] ? do_softirq+0x2c/0x68
> Jul 13 01:10:58 backup kernel: [<ffffffff8020cf62>] ? do_IRQ+0xa9/0xbf
> Jul 13 01:10:58 backup kernel: [<ffffffff8020b793>] ? ret_from_intr+0x0/0xa
> Jul 13 01:10:58 backup kernel: <EOI> [<ffffffff802116d8>] ? mwait_idle+0x6e/0x73
> Jul 13 01:10:58 backup kernel: [<ffffffff802116d8>] ? mwait_idle+0x6e/0x73
> Jul 13 01:10:58 backup kernel: [<ffffffff8020a1cb>] ? cpu_idle+0x40/0x7c
> Jul 13 01:10:58 backup kernel: [<ffffffff805a7bb0>] ? start_kernel+0x31e/0x32a
> Jul 13 01:10:58 backup kernel: [<ffffffff805a737e>] ? x86_64_start_kernel+0xe5/0xeb
> Jul 13 01:10:58 backup kernel: DMA per-cpu:
> Jul 13 01:10:58 backup kernel: CPU 0: hi: 0, btch: 1 usd: 0
> Jul 13 01:10:58 backup kernel: CPU 1: hi: 0, btch: 1 usd: 0
> Jul 13 01:10:58 backup kernel: CPU 2: hi: 0, btch: 1 usd: 0
> Jul 13 01:10:58 backup kernel: CPU 3: hi: 0, btch: 1 usd: 0
> Jul 13 01:10:58 backup kernel: DMA32 per-cpu:
> Jul 13 01:10:58 backup kernel: CPU 0: hi: 186, btch: 31 usd: 130
> Jul 13 01:10:58 backup kernel: CPU 1: hi: 186, btch: 31 usd: 90
> Jul 13 01:10:59 backup kernel: CPU 2: hi: 186, btch: 31 usd: 142
> Jul 13 01:10:59 backup kernel: CPU 3: hi: 186, btch: 31 usd: 177
> Jul 13 01:10:59 backup kernel: Normal per-cpu:
> Jul 13 01:10:59 backup kernel: CPU 0: hi: 186, btch: 31 usd: 76
> Jul 13 01:10:59 backup kernel: CPU 1: hi: 186, btch: 31 usd: 160
> Jul 13 01:10:59 backup kernel: CPU 2: hi: 186, btch: 31 usd: 170
> Jul 13 01:10:59 backup kernel: CPU 3: hi: 186, btch: 31 usd: 165
> Jul 13 01:10:59 backup kernel: Active_anon:117688 active_file:169003 inactive_anon:22048
> Jul 13 01:10:59 backup kernel: inactive_file:1425813 unevictable:0 dirty:337125 writeback:4493 unstable:0
> Jul 13 01:10:59 backup kernel: free:8260 slab:297474 mapped:1475 pagetables:1685 bounce:0
> Jul 13 01:11:00 backup kernel: DMA free:11712kB min:12kB low:12kB high:16kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB present:10756kB pages_scanned:0 all_unreclaimable? yes
> Jul 13 01:11:00 backup kernel: lowmem_reserve[]: 0 3767 8059 8059
> Jul 13 01:11:00 backup kernel: DMA32 free:19060kB min:5364kB low:6704kB high:8044kB active_anon:180632kB inactive_anon:38496kB active_file:318456kB inactive_file:2581460kB unevictable:0kB present:3857440kB pages_scanned:0 all_unreclaimable? no
> Jul 13 01:11:00 backup kernel: lowmem_reserve[]: 0 0 4292 4292
> Jul 13 01:11:00 backup kernel: Normal free:2268kB min:6112kB low:7640kB high:9168kB active_anon:290120kB inactive_anon:49696kB active_file:357556kB inactive_file:3121792kB unevictable:0kB present:4395520kB pages_scanned:0 all_unreclaimable? no
> Jul 13 01:11:00 backup kernel: lowmem_reserve[]: 0 0 0 0
> Jul 13 01:11:00 backup kernel: DMA: 6*4kB 3*8kB 3*16kB 3*32kB 4*64kB 2*128kB 1*256kB 1*512kB 2*1024kB 0*2048kB 2*4096kB = 11712kB
> Jul 13 01:11:00 backup kernel: DMA32: 2720*4kB 2*8kB 1*16kB 0*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 1*4096kB = 19040kB
> Jul 13 01:11:00 backup kernel: Normal: 1*4kB 1*8kB 1*16kB 1*32kB 0*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 2236kB
> Jul 13 01:11:00 backup kernel: 1594864 total pagecache pages
> Jul 13 01:11:00 backup kernel: 9 pages in swap cache
> Jul 13 01:11:00 backup kernel: Swap cache stats: add 1047, delete 1038, find 0/0
> Jul 13 01:11:00 backup kernel: Free swap = 2100300kB
> Jul 13 01:11:00 backup kernel: Total swap = 2104488kB
Try increasing /proc/sys/vm/min_free_kbytes
can you show some more of the messages? I'm guessing you should
include linux-mm next time (I did this time)
are you running jumbo frames perhaps?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2009-07-14 5:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090713134621.124aa18e.skraw@ithnet.com>
2009-07-14 5:40 ` Jesse Brandeburg [this message]
2009-07-14 5:53 ` What to do with this message (2.6.30.1) ? David Rientjes
2009-07-14 9:21 ` Stephan von Krawczynski
2009-07-15 6:47 ` Stephan von Krawczynski
2009-07-15 8:18 ` David Rientjes
2009-07-15 8:31 ` Justin Piszcz
2009-07-15 9:37 ` Stephan von Krawczynski
2009-07-15 20:24 ` David Rientjes
2009-07-16 15:14 ` Justin Piszcz
2009-07-16 16:44 ` What to do with this message (2.6.30.1) ? (happened again) Justin Piszcz
2009-07-18 10:23 ` What to do with this message (2.6.30.1) ? Stephan von Krawczynski
2009-07-19 13:22 ` Stephan von Krawczynski
2009-07-20 12:15 ` Stephan von Krawczynski
2009-07-21 13:38 ` Stephan von Krawczynski
2009-07-22 11:53 ` Stephan von Krawczynski
2009-07-15 9:46 ` Stephan von Krawczynski
2009-07-15 20:22 ` David Rientjes
2009-07-16 13:19 ` Stephan von Krawczynski
2009-07-17 6:36 ` Stephan von Krawczynski
2009-07-14 9:16 ` Stephan von Krawczynski
2009-07-14 10:14 ` Stephan von Krawczynski
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=4807377b0907132240g6f74c9cbnf1302d354a0e0a72@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skraw@ithnet.com \
/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).