Bug#477377: rsync: page allocation failure. order:1, mode:0x20
On Sun, Dec 21, 2008 at 01:01:50AM +0100, Moritz Muehlenhoff wrote:
> On Tue, Apr 22, 2008 at 08:40:45PM +0200, Kurt Roeckx wrote:
> > Package: linux-2.6
> > Version: 2.6.22-6
> >
> > Hi,
> >
> > I found this message today:
> > rsync: page allocation failure. order:1, mode:0x20
> >
> > Call Trace:
> > <IRQ> [<ffffffff8026d94d>] __alloc_pages+0x2a3/0x2bc
> > [<ffffffff80287a1a>] kmem_getpages+0x69/0x111
> > [<ffffffff80287a1a>] kmem_getpages+0x69/0x111
> > [<ffffffff80287f92>] fallback_alloc+0x115/0x180
> > [<ffffffff80287bf2>] kmem_cache_alloc_node+0x93/0xed
> > [<ffffffff80396ce5>] __alloc_skb+0x64/0x137
> > [<ffffffff803ca52c>] tcp_collapse+0x169/0x37a
> > [<ffffffff803ca8bc>] tcp_prune_queue+0x17f/0x27b
> > [<ffffffff803cab85>] tcp_data_queue+0x1cd/0xafd
> > [<ffffffff803cce04>] tcp_rcv_established+0x802/0x8da
> > [<ffffffff803d2591>] tcp_v4_do_rcv+0x30/0x36c
> > [<ffffffff803d4e30>] tcp_v4_rcv+0x98f/0xa23
> > [<ffffffff803b9c27>] ip_local_deliver+0x1c9/0x28e
> > [<ffffffff803b9a15>] ip_rcv+0x551/0x59a
> > [<ffffffff8039acfd>] netif_receive_skb+0x7d/0x392
> > [<ffffffff880abb21>] :tg3:tg3_poll+0x6ff/0x94d
> > [<ffffffff8039d20b>] net_rx_action+0xa8/0x1b6
> > [<ffffffff80237552>] __do_softirq+0x55/0xc3
> > [<ffffffff8021b7ff>] ack_apic_level+0x3a/0x4e
> > [<ffffffff8020af2c>] call_softirq+0x1c/0x28
> > [<ffffffff8020c855>] do_softirq+0x2c/0x7d
> > [<ffffffff8020ca8b>] do_IRQ+0xb6/0xd3
> > [<ffffffff8020a2b1>] ret_from_intr+0x0/0xa
> > <EOI> [<ffffffff8814cbcd>] :jbd:journal_dirty_metadata+0x8f/0x1be
> > [<ffffffff8816ccae>] :ext3:__ext3_journal_dirty_metadata+0x1e/0x46
> > [<ffffffff88160cdd>] :ext3:ext3_mark_iloc_dirty+0x2b0/0x339
> > [<ffffffff881610f4>] :ext3:ext3_mark_inode_dirty+0x28/0x31
> > [<ffffffff88163d7d>] :ext3:ext3_dirty_inode+0x63/0x7b
> > [<ffffffff802a9f5f>] __mark_inode_dirty+0x29/0x17d
> > [<ffffffff8815e7d1>] :ext3:ext3_new_blocks+0x5ec/0x7d3
> > [<ffffffff802ae8ec>] __bread+0x6/0x76
> > [<ffffffff8816182e>] :ext3:ext3_get_blocks_handle+0x405/0x8e6
> > [<ffffffff80287aa8>] kmem_getpages+0xf7/0x111
> > [<ffffffff88161ffb>] :ext3:ext3_get_block+0xc2/0xe4
> > [<ffffffff802addca>] __block_prepare_write+0x18a/0x441
> > [<ffffffff88161f39>] :ext3:ext3_get_block+0x0/0xe4
> > [<ffffffff802ae09b>] block_prepare_write+0x1a/0x25
> > [<ffffffff8816338a>] :ext3:ext3_prepare_write+0xb2/0x17b
> > [<ffffffff8026a432>] generic_file_buffered_write+0x288/0x61a
> > [<ffffffff8026ab07>] __generic_file_aio_write_nolock+0x343/0x3ad
> > [<ffffffff803901c8>] sock_aio_read+0x112/0x19a
> > [<ffffffff8026abd2>] generic_file_aio_write+0x61/0xc1
> > [<ffffffff8815f416>] :ext3:ext3_file_write+0x16/0x94
> > [<ffffffff8028d7f8>] do_sync_write+0xc9/0x10c
> > [<ffffffff80220d53>] do_page_fault+0x41f/0x78c
> > [<ffffffff80244a5a>] autoremove_wake_function+0x0/0x2e
> > [<ffffffff8028dfc9>] vfs_write+0xce/0x157
> > [<ffffffff8028e527>] sys_write+0x45/0x6e
> > [<ffffffff80209d9e>] system_call+0x7e/0x83
>
> Does this error still occur with more recent kernel versions?
It still occurs, but I'm now using a work around. I use this
setting in /etc/sysctl.conf:
vm.min_free_kbytes = 65536
See http://www.acc.umu.se/~maswan/linux-netperf.txt
Kurt
Reply to: