On Mon, Feb 18, 2013 at 09:17:13PM -0800, Eric Dumazet wrote:
> > chrome: page allocation failure: order:1, mode:0x4020
> > Pid: 8730, comm: chrome Tainted: G O 3.7.8-amd64-preempt-20121226-fixwd #1
> > Call Trace:
> > <IRQ> [<ffffffff810d5f38>] warn_alloc_failed+0x117/0x12c
> > [<ffffffff810d8cfd>] __alloc_pages_nodemask+0x66a/0x702
> > [<ffffffff8108a948>] ? arch_local_irq_save+0x15/0x1b
> > [<ffffffff811064af>] alloc_pages_current+0xcd/0xee
> > [<ffffffffa039b579>] iwl_rx_allocate+0x8c/0x271 [iwlwifi]
> > [<ffffffffa039c24e>] iwl_irq_tasklet+0x7e5/0x91c [iwlwifi]
> > [<ffffffff8104805e>] tasklet_action+0x80/0xd2
> > [<ffffffff81047c99>] __do_softirq+0xdf/0x1c5
> > [<ffffffff814c1ed6>] ? _raw_spin_lock+0x1b/0x1f
> > [<ffffffff810a7f37>] ? handle_irq_event+0x4d/0x62
> > [<ffffffff814c7f5c>] call_softirq+0x1c/0x30
> > [<ffffffff8101104e>] do_softirq+0x41/0x7f
> > [<ffffffff81047e52>] irq_exit+0x3f/0xa7
> > [<ffffffff81010d40>] do_IRQ+0x88/0x9f
> > [<ffffffff814c246d>] common_interrupt+0x6d/0x6d
> > <EOI> Mem-Info:
>
> You could try to load iwlwifi with amsdu_size_8K set to 0 (disable)
>
> It should hopefully use order-0 pages
>
> Some drivers cant fallback to low order page allocations.
>
> mlx4 is another example (it uses order-2 pages )
Well, now that I changed NFS to 32K buffering, I won't have the problem
anyway, so the problem is effectively fixed enough for me.
But because the default behaviour is so bad, I wanted to help fix the
defaults so that it doesn't happen to others if possible.
I haven't been following the NFS world recently, so I don't know if the code
is known broken beyond fixing, or if I did find an unusual problem that is
worth looking into.
If somehow I'm the only one, then let's not worry about it :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
