Kernel crashes after resuming from Suspend (Intel Wireless LAN 3945 issue?)

[Muelli]

This might be the same issue as with bug 301874.

[ 6518.275305] Pid: 6405, comm: NetworkManager Not tainted 2.6.27-9-generic #1
[ 6518.275308] RIP: 0010:[<ffffffffa037f360>] [<ffffffffa037f360>] iwl_eeprom_query16+0x10/0x20 [iwlcore]
[ 6518.275324] RSP: 0018:ffff8800748c3738 EFLAGS: 00010046
[ 6518.275326] RAX: 7fff88007adea000 RBX: ffff88007ace1a00 RCX: 00000000800300f0
[ 6518.275329] RDX: ffffc2000491403c RSI: 0000000000000090 RDI: ffff88007ace1a00
[ 6518.275331] RBP: ffff8800748c3738 R08: 0000000000000001 R09: ffff8800748c370c
[ 6518.275334] R10: 0000000000000000 R11: ffff8800748c36f8 R12: ffff88007ace2448
[ 6518.275337] R13: 0000000000000246 R14: ffff88007ace2b50 R15: ffff88007ace0060
[ 6518.275340] FS: 00007f9c72b7c730(0000) GS:ffff88007d002880(0000) knlGS:0000000000000000
[ 6518.275343] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 6518.275345] CR2: 00007fa0bd81b000 CR3: 0000000074103000 CR4: 00000000000026a0
[ 6518.275348] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 6518.275351] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 6518.275354] Process NetworkManager (pid: 6405, threadinfo ffff8800748c2000, task ffff8800741859c0)
[ 6518.275356] Stack: ffff8800748c3778 ffffffffa03bb0ab ffffffff805026d8 0000000000000246
[ 6518.275362] 43ff88007ace1a00 0000000000000246 ffff88007ace1a00 ffff88007ace2448
[ 6518.275367] ffff8800748c37a8 ffffffffa037ddbb 0000000000000000 ffff88007ace1a00
[ 6518.275372] Call Trace:
[ 6518.275383] [<ffffffffa03bb0ab>] iwl4965_nic_config+0x7b/0x150 [iwlagn]
[ 6518.275390] [<ffffffff805026d8>] ? _spin_unlock_irqrestore+0x18/0x30
[ 6518.275401] [<ffffffffa037ddbb>] iwl_hw_nic_init+0x9b/0x160 [iwlcore]
[ 6518.275409] [<ffffffffa03b4e3a>] __iwl4965_up+0xba/0x2d0 [iwlagn]
[ 6518.275417] [<ffffffffa03b5544>] iwl4965_mac_start+0xe4/0x350 [iwlagn]
[ 6518.275422] [<ffffffff80485d58>] ? __nla_reserve+0x58/0x70
[ 6518.275437] [<ffffffffa02a76a2>] ieee80211_open+0x152/0x690 [mac80211]
[ 6518.275443] [<ffffffff8045c2ad>] ? skb_put+0xd/0xa0
[ 6518.275446] [<ffffffff80466c22>] dev_open+0xb2/0xf0
[ 6518.275450] [<ffffffff804662eb>] dev_change_flags+0x9b/0x1e0
[ 6518.275454] [<ffffffff80470654>] do_setlink+0x214/0x3b0
[ 6518.275457] [<ffffffff8046fe76>] ? rtnl_fill_ifinfo+0x2f6/0x420
[ 6518.275460] [<ffffffff8048617b>] ? nla_parse+0x3b/0x110
[ 6518.275463] [<ffffffff80470905>] rtnl_setlink+0x115/0x160
[ 6518.275468] [<ffffffff80234059>] ? __phys_addr+0x9/0x50
[ 6518.275471] [<ffffffff8046f8ce>] rtnetlink_rcv_msg+0x18e/0x240
[ 6518.275474] [<ffffffff8046f740>] ? rtnetlink_rcv_msg+0x0/0x240
[ 6518.275478] [<ffffffff804846a9>] netlink_rcv_skb+0x89/0xb0
[ 6518.275481] [<ffffffff8046f72c>] rtnetlink_rcv+0x2c/0x40
[ 6518.275484] [<ffffffff804843b5>] netlink_unicast+0x2c5/0x2e0
[ 6518.275488] [<ffffffff80485674>] netlink_sendmsg+0x204/0x2f0
[ 6518.275493] [<ffffffff803836f0>] ? aa_revalidate_sk+0x20/0xd0
[ 6518.275497] [<ffffffff80456cac>] sock_sendmsg+0x10c/0x140
[ 6518.275501] [<ffffffff80267050>] ? autoremove_wake_function+0x0/0x40
[ 6518.275505] [<ffffffff8045659c>] ? move_addr_to_kernel+0x5c/0x60
[ 6518.275509] [<ffffffff8045f434>] ? verify_iovec+0x44/0xd0
[ 6518.275512] [<ffffffff80456e6e>] sys_sendmsg+0x18e/0x320
[ 6518.275516] [<ffffffff802ea969>] ? fget_light+0x9/0xb0
[ 6518.275519] [<ffffffff802eb099>] ? fput+0x9/0x30
[ 6518.275522] [<ffffffff80457172>] ? sys_sendto+0x102/0x120
[ 6518.275527] [<ffffffff8021285a>] system_call_fastpath+0x16/0x1b
[ 6518.275529]
[ 6518.275531]
[ 6518.275532] Code: 47 33 e9 df 48 8b 47 18 48 8b 40 18 48 8b 00 ff 90 00 01 00 00 c9 c3 0f 1f 40 00 55 48 89 e5 e8 27 33 e9 df 48 8b 87 30 23 01 00 <0f> b6 54 30 01 0f b6 04 30 c9 c1 e2 08 09 d0 c3 55 48 89 e5 41
[ 6518.275574] RIP [<ffffffffa037f360>] iwl_eeprom_query16+0x10/0x20 [iwlcore]
[ 6518.275585] RSP <ffff8800748c3738>
[ 6518.275588] ---[ end trace f23d964e56cc0cfd ]---

I'll attach the dmesg output after booting, suspending to RAM and resuming. I can use my system after that oopses, but I can't shutdown properly, because some processes can't get killed, e.g. ALSA.

Please let me know if I can provide further information.

[Andy Whitcroft (apw)]

This is not a bug in the linux-meta package, moving to the linux package.

[Jeremy Foshee (jeremyfoshee)]

Muelli,
      Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds .

Thanks in advance.

-JFo

[Muelli (ubuntu-bugs-auftrags-killer)]

Hm. Well. The WLAN stack doesn't actually crash anymore (2.6.31.11.22). From time to time I get these:

[42051.202443] rhythmbox: page allocation failure. order:2, mode:0x4020
[42051.202450] Pid: 31636, comm: rhythmbox Tainted: G WC 2.6.31-11-generic #36-Ubuntu
[42051.202454] Call Trace:
[42051.202457] <IRQ> [<ffffffff810db90c>] __alloc_pages_slowpath+0x4cc/0x4e0
[42051.202472] [<ffffffff810dba6e>] __alloc_pages_nodemask+0x14e/0x150
[42051.202478] [<ffffffff8110ce4a>] kmalloc_large_node+0x5a/0xb0
[42051.202483] [<ffffffff81110ff5>] __kmalloc_node_track_caller+0x135/0x180
[42051.202512] [<ffffffffa023e5c9>] ? iwl_rx_allocate+0x1a9/0x230 [iwlcore]
[42051.202519] [<ffffffff814290bb>] __alloc_skb+0x7b/0x180
[42051.202530] [<ffffffffa023e5c9>] iwl_rx_allocate+0x1a9/0x230 [iwlcore]
[42051.202536] [<ffffffff81018830>] ? nommu_map_page+0x0/0xb0
[42051.202548] [<ffffffffa023f966>] iwl_rx_replenish_now+0x16/0x30 [iwlcore]
[42051.202561] [<ffffffffa025c4ba>] iwl_rx_handle+0x24a/0x2f0 [iwlagn]
[42051.202569] [<ffffffffa025c767>] iwl_irq_tasklet_legacy+0x207/0x440 [iwlagn]
[42051.202575] [<ffffffff815235a9>] ? _spin_lock+0x9/0x10
[42051.202583] [<ffffffffa03354d7>] ? azx_interrupt+0x127/0x1a0 [snd_hda_intel]
[42051.202588] [<ffffffff8105ef30>] tasklet_action+0xd0/0xe0
[42051.202593] [<ffffffff810604ed>] __do_softirq+0xbd/0x200
[42051.202597] [<ffffffff8101318c>] call_softirq+0x1c/0x30
[42051.202601] [<ffffffff81014945>] do_softirq+0x55/0x90
[42051.202605] [<ffffffff81060255>] irq_exit+0x85/0x90
[42051.202608] [<ffffffff81014080>] do_IRQ+0x70/0xe0
[42051.202614] [<ffffffff810129d3>] ret_from_intr+0x0/0x11
[42051.202616] <EOI>
[42051.202618] Mem-Info:
[42051.202621] Node 0 DMA per-cpu:
[42051.202625] CPU 0: hi: 0, btch: 1 usd: 0
[42051.202628] CPU 1: hi: 0, btch: 1 usd: 0
[42051.202630] Node 0 DMA32 per-cpu:
[42051.202633] CPU 0: hi: 186, btch: 31 usd: 178
[42051.202636] CPU 1: hi: 186, btch: 31 usd: 36
[42051.202642] Active_anon:312037 active_file:20258 inactive_anon:104524
[42051.202643] inactive_file:20408 unevictable:13 dirty:2 writeback:1127 unstable:0
[42051.202645] free:4133 slab:17607 mapped:17452 pagetables:7476 bounce:0
[42051.202648] Node 0 DMA free:7876kB min:40kB low:48kB high:60kB active_anon:3000kB inactive_anon:3372kB active_file:384kB inactive_file:860kB unevictable:0kB present:15332kB pages_scanned:0 all_unreclaimable? no
[42051.202655] lowmem_reserve[]: 0 1963 1963 1963
[42051.202661] Node 0 DMA32 free:8656kB min:5648kB low:7060kB high:8472kB active_anon:1245148kB inactive_anon:414724kB active_file:80648kB inactive_file:80772kB unevictable:52kB present:2010592kB pages_scanned:0 all_unreclaimable? no
[42051.202669] lowmem_reserve[]: 0 0 0 0
[42051.202673] Node 0 DMA: 25*4kB 16*8kB 8*16kB 7*32kB 2*64kB 4*128kB 0*256kB 3*512kB 3*1024kB 1*2048kB 0*4096kB = 7876kB
[42051.202687] Node 0 DMA32: 1524*4kB 256*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 8656kB
[42051.202700] 96986 total pagecache pages
[42051.202703] 36762 pages in swap cache
[42051.202705] Swap cache stats: add 505638, delete 468876, find 215197/254358
[42051.202708] Free swap = 13616...

[Muelli (ubuntu-bugs-auftrags-killer)]

reopening as per last coment

[Jeremy Foshee (jeremyfoshee)]

While you have an issue with your wireless stack, that issue must be tracked in a new bug specifically for that. Can you confirm that you tested this on the current development version as requested in my comment above?

Regards,

-JFo

[Muelli (ubuntu-bugs-auftrags-killer)]

Hey Jeremy,

well, I guess this particular issue is gone by now. I don't know If it's fixed though, at least it doesn't appear anymore.

For my wireless issues: Well, I'll see if I'm the mood to report another bug which is ignored until a newer kernel gets released :-)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]