Bugzilla – Bug 1861
ifconfig: page allocation failure. order:5, mode:0x8020
Last modified: 2009-02-02 22:45:08
You need to log in before you can comment on or make changes to this bug.
Test Environment: Platform : Intel SDV M3M31 Wireless Card : Intel(R) WiFi Link 4965 OS : Redhat Fedora release 8 (Werewolf) 64bit AP : Cisco 1250 uCode : iwlwifi-4965-2.ucode 228.57.2.23 Source : commit c87eacfd5ad8aaf14c644176af4f5e59dd86b406 Peer : Intel SDV M3M31 Issues: debug our scripts and automation testing leading to kernel panic and log has calltrace. "ifconfig: page allocation failure. order:5, mode:0x8020" It's hard to reproduce it. I **suspect** that this calltrace maybe is related with memory allocation. iwlagn 0000:01:00.0: firmware: requesting iwlwifi-4965-2.ucode iwlagn loaded firmware version 228.57.2.23 ifconfig: page allocation failure. order:5, mode:0x8020 Pid: 13792, comm: ifconfig Not tainted 2.6.28-rc8-wl #1 Call Trace: [<ffffffff810810bb>] __alloc_pages_internal+0x3b5/0x3ce [<ffffffff8101098b>] dma_generic_alloc_coherent+0xa3/0x130 [<ffffffffa0205013>] iwl_mac_start+0xa15/0x14ea [iwlagn] [<ffffffffa018a9fc>] ieee80211_open+0x2b0/0x701 [mac80211] [<ffffffff810593a2>] mark_held_locks+0x51/0x6f [<ffffffff8103e4cd>] local_bh_enable_ip+0xc0/0xc3 [<ffffffff8121fe95>] dev_open+0x6b/0x9e [<ffffffff8121e2e4>] dev_change_flags+0x9d/0x154 [<ffffffff81263234>] devinet_ioctl+0x242/0x58a [<ffffffff810a24f8>] check_bytes_and_report+0x37/0xc9 [<ffffffff81213575>] sock_ioctl+0x1d8/0x1ff [<ffffffff810b51a2>] vfs_ioctl+0x21/0x6b [<ffffffff810b5562>] do_vfs_ioctl+0x376/0x3bd [<ffffffff810a3ef0>] kmem_cache_free+0xc1/0xd0 [<ffffffff8100bd6c>] sysret_check+0x27/0x62 [<ffffffff81059535>] trace_hardirqs_on_caller+0xf0/0x113 [<ffffffff810b55fa>] sys_ioctl+0x51/0x70 [<ffffffff8100bd3b>] system_call_fastpath+0x16/0x1b Mem-Info: Node 0 DMA per-cpu: CPU 0: hi: 0, btch: 1 usd: 0 CPU 1: hi: 0, btch: 1 usd: 0 Node 0 DMA32 per-cpu: CPU 0: hi: 186, btch: 31 usd: 125 CPU 1: hi: 186, btch: 31 usd: 158 Active_anon:7909 active_file:23142 inactive_anon:7167 ....... Call Trace: [<ffffffffa018a9fc>] ? ieee80211_open+0x2b0/0x701 [mac80211] [<ffffffff810593a2>] ? mark_held_locks+0x51/0x6f [<ffffffff8103e4cd>] ? local_bh_enable_ip+0xc0/0xc3 [<ffffffff8121fe95>] ? dev_open+0x6b/0x9e [<ffffffff8121e2e4>] ? dev_change_flags+0x9d/0x154 [<ffffffff81263234>] ? devinet_ioctl+0x242/0x58a [<ffffffff810a24f8>] ? check_bytes_and_report+0x37/0xc9 [<ffffffff81213575>] ? sock_ioctl+0x1d8/0x1ff [<ffffffff810b51a2>] ? vfs_ioctl+0x21/0x6b [<ffffffff810b5562>] ? do_vfs_ioctl+0x376/0x3bd [<ffffffff810a3ef0>] ? kmem_cache_free+0xc1/0xd0 [<ffffffff8100bd6c>] ? sysret_check+0x27/0x62 [<ffffffff81059535>] ? trace_hardirqs_on_caller+0xf0/0x113 [<ffffffff810b55fa>] ? sys_ioctl+0x51/0x70 [<ffffffff8100bd3b>] ? system_call_fastpath+0x16/0x1b Code: 48 89 c6 4d 89 e9 49 c7 c0 8e d1 21 a0 89 d9 48 c7 c7 41 ee 21 a0 31 c0 e8 a1 56 e3 e0 48 8b bd 20 0b 00 00 fc 4c 89 fe 4c 89 e9 <f3> a4 f6 85 54 34 01 00 01 0f 84 c8 05 00 00 4c 8b a5 28 0b 00 RIP [<ffffffffa020546d>] iwl_mac_start+0xe6f/0x14ea [iwlagn] RSP <ffff88000357dc78> CR2: 0000000000000000 ---[ end trace 08f8c922809617a3 ]---
Created an attachment (id=1756) [details] this is netconsole detailed log.
Created an attachment (id=1757) [details] this is screen log
Created an attachment (id=1800) [details] fix patch This patch should fix the (second) oops. For the first call trace, it is due to the system DMA memory is low. The reason why the system is short of DMA-able memory is unknown.
mark as fixed
I can't reproduce it currently and mark is as verified.