On Tuesday 17 November 2009, Karol Lewandowski wrote:
> On Tue, Nov 17, 2009 at 12:01:19AM +0100, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.30 and 2.6.31.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.30 and 2.6.31.  Please verify if it still should
> > be listed and let me know (either way).
> > 
> > 
> > Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=14265
> > Subject             : ifconfig: page allocation failure. order:5,
> mode:0x8020 w/ e100
> > Submitter   : Karol Lewandowski <karol.k.lewandowski@gmail.com>
> > Date                : 2009-09-15 12:05 (63 days old)
> > References  : http://marc.info/?l=linux-kernel&m=125301636509517&w=4
> 
> Bug is still present in 2.6.32-rc7.

This bug has been fixed in 2.6.32.x by 98468efddb101f8a29af974101c17ba513b07be1 and ee6bfc69e69474840cacb2f665831aff29bdbb40 (70abc8cb90e679d8519721e2761d8366a18212a6 upstream) and can be closed.

I am seeing the same problem on Ubuntu 10.04, amd86, kernel:

  2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux

Error message:

Jun 19 16:14:15 bigtom kernel: [ 4050.210948] ifconfig: page allocation failure. order:3, mode:0x4020
Jun 19 16:14:15 bigtom kernel: [ 4050.210951] Pid: 3115, comm: ifconfig Tainted: P           2.6.32-23-generic #37-Ubuntu
Jun 19 16:14:15 bigtom kernel: [ 4050.210953] Call Trace:
Jun 19 16:14:15 bigtom kernel: [ 4050.210960]  [<ffffffff810fad0e>] __alloc_pages_slowpath+0x56e/0x580
Jun 19 16:14:15 bigtom kernel: [ 4050.210964]  [<ffffffff8105b130>] ? default_wake_function+0x0/0x20
Jun 19 16:14:15 bigtom kernel: [ 4050.210966]  [<ffffffff810fae7e>] __alloc_pages_nodemask+0x15e/0x1a0
Jun 19 16:14:15 bigtom kernel: [ 4050.210969]  [<ffffffff81132de2>] kmalloc_large_node+0x62/0xb0
Jun 19 16:14:15 bigtom kernel: [ 4050.210972]  [<ffffffff81137475>] __kmalloc_node_track_caller+0x125/0x180
Jun 19 16:14:15 bigtom kernel: [ 4050.210975]  [<ffffffff81455276>] ? __netdev_alloc_skb+0x36/0x60
Jun 19 16:14:15 bigtom kernel: [ 4050.210977]  [<ffffffff81454f30>] __alloc_skb+0x80/0x190
Jun 19 16:14:15 bigtom kernel: [ 4050.210979]  [<ffffffff81455276>] __netdev_alloc_skb+0x36/0x60
Jun 19 16:14:15 bigtom kernel: [ 4050.210990]  [<ffffffffa00451ea>] rtl8169_rx_fill+0xba/0x250 [r8169]
Jun 19 16:14:15 bigtom kernel: [ 4050.210993]  [<ffffffff81019d60>] ? nommu_map_page+0x0/0xc0
Jun 19 16:14:15 bigtom kernel: [ 4050.210997]  [<ffffffffa0045d53>] rtl8169_init_ring+0x73/0xb0 [r8169]
Jun 19 16:14:15 bigtom kernel: [ 4050.211000]  [<ffffffffa0045fca>] rtl8169_open+0x14a/0x3d0 [r8169]
Jun 19 16:14:15 bigtom kernel: [ 4050.211004]  [<ffffffff81460c02>] dev_open+0xa2/0x100
Jun 19 16:14:15 bigtom kernel: [ 4050.211006]  [<ffffffff81460331>] dev_change_flags+0xa1/0x1e0
Jun 19 16:14:15 bigtom kernel: [ 4050.211009]  [<ffffffff814be3e3>] devinet_ioctl+0x593/0x5f0
Jun 19 16:14:15 bigtom kernel: [ 4050.211011]  [<ffffffff814bf710>] inet_ioctl+0x90/0xb0
Jun 19 16:14:15 bigtom kernel: [ 4050.211013]  [<ffffffff8144c72a>] sock_ioctl+0x7a/0x280
Jun 19 16:14:15 bigtom kernel: [ 4050.211016]  [<ffffffff81153cd2>] vfs_ioctl+0x22/0xa0
Jun 19 16:14:15 bigtom kernel: [ 4050.211018]  [<ffffffff81153f81>] do_vfs_ioctl+0x81/0x380
Jun 19 16:14:15 bigtom kernel: [ 4050.211021]  [<ffffffff81546118>] ? do_page_fault+0x158/0x3b0
Jun 19 16:14:15 bigtom kernel: [ 4050.211023]  [<ffffffff81154301>] sys_ioctl+0x81/0xa0
Jun 19 16:14:15 bigtom kernel: [ 4050.211026]  [<ffffffff810131b2>] system_call_fastpath+0x16/0x1b

Well that's a different problem.  r8169 doing an order-3 GFP_ATOMIC allocation.

Okay, shall I file a new bug?

Yes, you should.