page allocation failure如何分析

[杨六]

order与mode分别表示什么含义，对问题定位是否有帮助
以下信息哪些需要关注，大致说明什么问题？或者有关以下信息的链接，请教一下

root@HSAN:/tmp#hostapd -ddd hostapd_wep.conf -t -e/tmp/myramdom -Boam_rx_queue: page allocation failure. order:0, mode:0x20
[<c002bdb8>] (unwind_backtrace+0x0/0xfc) from [<c006c77c>] (__alloc_pages_nodemask+0x4e4/0x59c)
[<c006c77c>] (__alloc_pages_nodemask+0x4e4/0x59c) from [<c008b900>] (__slab_alloc+0x374/0x394)
[<c008b900>] (__slab_alloc+0x374/0x394) from [<c008bcd8>] (kmem_cache_alloc+0xa8/0xb4)
[<c008bcd8>] (kmem_cache_alloc+0xa8/0xb4) from [<c021c9a8>] (__alloc_skb+0x30/0x100)
[<c021c9a8>] (__alloc_skb+0x30/0x100) from [<c021d478>] (skb_copy_expand+0x28/0xd0)
[<c021d478>] (skb_copy_expand+0x28/0xd0) from [<bf3f3818>] (sdt_drv_add_pkt_head+0x28/0x1ac [sdt])
[<bf3f3818>] (sdt_drv_add_pkt_head+0x28/0x1ac [sdt]) from [<bf247284>] (oam_upload_log_to_sdt+0x74/0xb8 [oam])
[<bf247284>] (oam_upload_log_to_sdt+0x74/0xb8 [oam]) from [<bf248468>] (oam_log_print_param_only+0x4a4/0xaec [oam])
[<bf248468>] (oam_log_print_param_only+0x4a4/0xaec [oam]) from [<bf248bec>] (oam_log_print1+0x44/0x4c [oam])
[<bf248bec>] (oam_log_print1+0x44/0x4c [oam]) from [<bf3f362c>] (sdt_drv_send_data_down+0x170/0x224 [sdt])
[<bf3f362c>] (sdt_drv_send_data_down+0x170/0x224 [sdt]) from [<bf3f37b0>] (sdt_drv_netlink_recv+0xd0/0x110 [sdt])
[<bf3f37b0>] (sdt_drv_netlink_recv+0xd0/0x110 [sdt]) from [<c023d050>] (netlink_unicast+0x290/0x2dc)
[<c023d050>] (netlink_unicast+0x290/0x2dc) from [<bf3f349c>] (sdt_drv_push_wifi_log_work+0x20/0x40 [sdt])
[<bf3f349c>] (sdt_drv_push_wifi_log_work+0x20/0x40 [sdt]) from [<c0049aa4>] (worker_thread+0xf8/0x188)
[<c0049aa4>] (worker_thread+0xf8/0x188) from [<c004cedc>] (kthread+0x7c/0x84)
[<c004cedc>] (kthread+0x7c/0x84) from [<c0026e44>] (kernel_thread_exit+0x0/0x8)
Mem-info:
Normal per-cpu:
CPU 0: hi: 42, btch: 7 usd: 8
active_anon:1205 inactive_anon:779 isolated_anon:0
active_file:447 inactive_file:1407 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
free:124 slab_reclaimable:164 slab_unreclaimable:21644
mapped:332 shmem:908 pagetables:26 bounce:0
Normal free:496kB min:1360kB low:1700kB high:2040kB active_anon:4820kB inactive_anon:3116kB active_file:1788kB inactive_file:5628kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:115824kB mlocked:0kB dirty:0kB writeback:0kB mapped:1328kB shmem:3632kB slab_reclaimable:656kB slab_unreclaimable:86576kB kernel_stack:280kB pagetables:104kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
lowmem_reserve[]: 0 0 0
Normal: 34*4kB 9*8kB 6*16kB 0*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 496kB
2762 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
29184 pages of RAM
185 free pages
1262 reserved pages
19865 slab pages
1229 pages shared
0 pages swap cached
SLUB: Unable to allocate memory on node -1 (gfp=0x20)
cache: kmalloc-192, object size: 192, buffer size: 192, default order: 0, min order: 0
node 0: slabs: 0, objs: 0, free: 0

[杨六]

引用 1 楼 Huntercao 的回复:

能否介绍一下问题背景？

驱动代码，与app侧消息交互，该问题就是接收到app的消息后回复app，在申请内存时报错了；目前走读代码确实发现一些内存处理的异常，但不知道是否与这个打印里提示信息是否一致了。

[曹大夯]

能否介绍一下问题背景？

[jianmin09]

能否介绍下问题的背景？

[ck550460]

你的问题解决了吗？