[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#580124: linux-image-2.6.32-4-amd64: kernel allocation failure in iwl_rx_allocate



On Sunday 09 May 2010 21:38:25 Ritesh Raj Sarraf wrote:
> On Thursday 06 May 2010 07:16:01 Ben Hutchings wrote:
> > On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-11
> > > Severity: normal
> > > 
> > > I often keep getting this allocation failure message. My gut feel is
> > > that it gets triggered when I do some I/O. Today, it got triggered when
> > > I was copying a couple of Gig data from my local encrypted backup
> > > partition to an external USB disk.
> > [...]
> > 
> > This is a bug/limitation in the iwlwifi drivers.  It appears to be fixed
> > in Linux 2.6.33, but it requires quite a large change.  The next release
> > of Debian will be based on Linux 2.6.32 and I don't know whether we will
> > be able to apply that change.
> > 
> 
> Too bad. There will be many users using this wifi device. :-(
> And the symptom is also not a good one. When the bug triggers, it seems to almost eat
> down all of your memory.
> 
> 


Ben,

I think this bug is more than the iwlwifi driver.

While this kernel message is from the 2.6.33 kernel, I think the bug is the same one.

May  9 22:07:07 champaran kernel: [34858.683705] Xorg: page allocation failure. order:1, mode:0x50d0
May  9 22:07:07 champaran kernel: [34858.683710] Pid: 2860, comm: Xorg Not tainted 2.6.33-2-amd64 #1
May  9 22:07:07 champaran kernel: [34858.683712] Call Trace:
May  9 22:07:07 champaran kernel: [34858.683724]  [<ffffffff810b5747>] ? __alloc_pages_nodemask+0x56d/0x5e2
May  9 22:07:07 champaran kernel: [34858.683728]  [<ffffffff810e154d>] ? new_slab+0x5b/0x1ca
May  9 22:07:07 champaran kernel: [34858.683731]  [<ffffffff810e18ac>] ? __slab_alloc+0x1f0/0x3a2
May  9 22:07:07 champaran kernel: [34858.683735]  [<ffffffff81205dba>] ? agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683739]  [<ffffffff810e2ceb>] ? __kmalloc+0xf1/0x141
May  9 22:07:07 champaran kernel: [34858.683741]  [<ffffffff81205dba>] ? agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683744]  [<ffffffff81205dba>] ? agp_alloc_page_array+0x2b/0x4a
May  9 22:07:07 champaran kernel: [34858.683746]  [<ffffffff81205e47>] ? agp_generic_alloc_user+0x6e/0xe2
May  9 22:07:07 champaran kernel: [34858.683749]  [<ffffffff81205fb0>] ? agp_allocate_memory+0x48/0xe8
May  9 22:07:07 champaran kernel: [34858.683802]  [<ffffffffa01018ad>] ? drm_agp_bind_pages+0x4e/0xd0 [drm]
May  9 22:07:07 champaran kernel: [34858.683817]  [<ffffffffa0147329>] ? i915_gem_object_bind_to_gtt+0x1c5/0x27a [i915]
May  9 22:07:07 champaran kernel: [34858.683825]  [<ffffffffa01473fc>] ? i915_gem_object_pin+0x1e/0x87 [i915]
May  9 22:07:07 champaran kernel: [34858.683834]  [<ffffffffa01481d1>] ? i915_gem_do_execbuffer+0x4aa/0xe89 [i915]
May  9 22:07:07 champaran kernel: [34858.683839]  [<ffffffff810d1788>] ? vmap_page_range_noflush+0x287/0x2ec
May  9 22:07:07 champaran kernel: [34858.683842]  [<ffffffff810d1812>] ? map_vm_area+0x25/0x36
May  9 22:07:07 champaran kernel: [34858.683845]  [<ffffffff810d1951>] ? __vmalloc_area_node+0x12e/0x152
May  9 22:07:07 champaran kernel: [34858.683848]  [<ffffffff810d19d4>] ? __vmalloc_node+0x5f/0x8e
May  9 22:07:07 champaran kernel: [34858.683856]  [<ffffffffa0148e65>] ? i915_gem_execbuffer+0x194/0x223 [i915]
May  9 22:07:07 champaran kernel: [34858.683861]  [<ffffffff812f35c4>] ? _lock_kernel+0x53/0x8a
May  9 22:07:07 champaran kernel: [34858.683870]  [<ffffffffa00fbef5>] ? drm_ioctl+0x260/0x32b [drm]
May  9 22:07:07 champaran kernel: [34858.683873]  [<ffffffff810c4c5a>] ? __do_fault+0x380/0x3c3
May  9 22:07:07 champaran kernel: [34858.683882]  [<ffffffffa0148cd1>] ? i915_gem_execbuffer+0x0/0x223 [i915]
May  9 22:07:07 champaran kernel: [34858.683887]  [<ffffffff81061b18>] ? __remove_hrtimer+0x74/0x80
May  9 22:07:07 champaran kernel: [34858.683892]  [<ffffffff810f5b4b>] ? vfs_ioctl+0x21/0x92
May  9 22:07:07 champaran kernel: [34858.683894]  [<ffffffff810f60c7>] ? do_vfs_ioctl+0x495/0x4d3
May  9 22:07:07 champaran kernel: [34858.683898]  [<ffffffff8104aa0e>] ? do_setitimer+0xbc/0x1d9
May  9 22:07:07 champaran kernel: [34858.683901]  [<ffffffff8104ab87>] ? sys_setitimer+0x5c/0x9a
May  9 22:07:07 champaran kernel: [34858.683903]  [<ffffffff810f6156>] ? sys_ioctl+0x51/0x70
May  9 22:07:07 champaran kernel: [34858.683908]  [<ffffffff81008ac2>] ? system_call_fastpath+0x16/0x1b
May  9 22:07:07 champaran kernel: [34858.683910] Mem-Info:
May  9 22:07:07 champaran kernel: [34858.683912] Node 0 DMA per-cpu:
May  9 22:07:07 champaran kernel: [34858.683915] CPU    0: hi:    0, btch:   1 usd:   0
May  9 22:07:07 champaran kernel: [34858.683917] CPU    1: hi:    0, btch:   1 usd:   0
May  9 22:07:07 champaran kernel: [34858.683918] Node 0 DMA32 per-cpu:
May  9 22:07:07 champaran kernel: [34858.683920] CPU    0: hi:  186, btch:  31 usd: 168
May  9 22:07:07 champaran kernel: [34858.683922] CPU    1: hi:  186, btch:  31 usd:   0
May  9 22:07:07 champaran kernel: [34858.683926] active_anon:282314 inactive_anon:90268 isolated_anon:0
May  9 22:07:07 champaran kernel: [34858.683927]  active_file:140695 inactive_file:158480 isolated_file:0
May  9 22:07:07 champaran kernel: [34858.683928]  unevictable:0 dirty:6 writeback:0 unstable:0
May  9 22:07:07 champaran kernel: [34858.683929]  free:7506 slab_reclaimable:30686 slab_unreclaimable:14882
May  9 22:07:07 champaran kernel: [34858.683930]  mapped:31957 shmem:84560 pagetables:10876 bounce:0
May  9 22:07:07 champaran kernel: [34858.683932] Node 0 DMA free:11656kB min:32kB low:40kB high:48kB active_anon:0kB inactive_anon:0kB active_file:1124kB inactive_file:2644kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15348kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:356kB slab_unreclaimable:140kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
May  9 22:07:07 champaran kernel: [34858.683941] lowmem_reserve[]: 0 2910 2910 2910
May  9 22:07:07 champaran kernel: [34858.683944] Node 0 DMA32 free:18368kB min:6884kB low:8604kB high:10324kB active_anon:1129256kB inactive_anon:361072kB active_file:561656kB inactive_file:631276kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:2979864kB mlocked:0kB dirty:24kB writeback:0kB mapped:127828kB shmem:338240kB slab_reclaimable:122388kB slab_unreclaimable:59388kB kernel_stack:3000kB pagetables:43504kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:138 all_unreclaimable? no
May  9 22:07:07 champaran kernel: [34858.683954] lowmem_reserve[]: 0 0 0 0
May  9 22:07:07 champaran kernel: [34858.683957] Node 0 DMA: 2*4kB 4*8kB 4*16kB 5*32kB 8*64kB 3*128kB 1*256kB 2*512kB 3*1024kB 3*2048kB 0*4096kB = 11656kB
May  9 22:07:07 champaran kernel: [34858.683965] Node 0 DMA32: 3884*4kB 60*8kB 43*16kB 22*32kB 11*64kB 2*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 18368kB
May  9 22:07:07 champaran kernel: [34858.683973] 391025 total pagecache pages
May  9 22:07:07 champaran kernel: [34858.683974] 7304 pages in swap cache
May  9 22:07:07 champaran kernel: [34858.683976] Swap cache stats: add 15029, delete 7725, find 264627/264699
May  9 22:07:07 champaran kernel: [34858.683977] Free swap  = 3162344kB
May  9 22:07:07 champaran kernel: [34858.683979] Total swap = 3219448kB
May  9 22:07:07 champaran kernel: [34858.694163] 760320 pages RAM
May  9 22:07:07 champaran kernel: [34858.694164] 13492 pages reserved
May  9 22:07:07 champaran kernel: [34858.694166] 320460 pages shared
May  9 22:07:07 champaran kernel: [34858.694167] 631156 pages non-shared
May  9 22:07:07 champaran kernel: [34858.694169] SLUB: Unable to allocate memory on node -1 (gfp=0x10d0)
May  9 22:07:07 champaran kernel: [34858.694172]   cache: kmalloc-8192, object size: 8192, buffer size: 8192, default order: 3, min order: 1
May  9 22:07:07 champaran kernel: [34858.694175]   node 0: slabs: 9, objs: 36, free: 0


This occured when I asked leafnode to give me the list on messages in the linux-kernel newsgroup (which is huge).

All these messages (this one and the previous one with iwlwifi) get triggered only when there is heavy I/O activity.
I don't think this bug is related to iwlwifi. What do you think ?


Regards,
Ritesh
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
"Necessity is the mother of invention."

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: