FS#37703 - [linux] 3.11: Wifi failed to resume after sleep
Attached to Project:
Arch Linux
Opened by Stanislaw Pitucha (viraptor) - Saturday, 09 November 2013, 00:21 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 March 2014, 00:03 GMT
Opened by Stanislaw Pitucha (viraptor) - Saturday, 09 November 2013, 00:21 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 March 2014, 00:03 GMT
|
Details
Description:
Wifi failed to become available after suspend (ram). Suspend could not be activated anymore after this issue. Additional info: * package version(s) linux 3.11.6-1 06:00.0 Network controller: Intel Corporation Centrino Wireless-N 2200 (rev c4) Subsystem: Intel Corporation Centrino Wireless-N 2200 BGN Flags: bus master, fast devsel, latency 0, IRQ 47 Memory at f1d00000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi * config and/or log files etc. [ 3553.470065] cfg80211: Calling CRDA to update world regulatory domain [ 3553.703515] PM: Syncing filesystems ... done. [ 3554.177415] PM: Preparing system for mem sleep [ 3724.975102] INFO: task kworker/u16:1:32503 blocked for more than 120 seconds. [ 3724.975106] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3724.975108] kworker/u16:1 D 0000000000000246 0 32503 2 0x00000000 [ 3724.975116] Workqueue: events_unbound async_run_entry_fn [ 3724.975118] ffff8802002d5c70 0000000000000046 0000000000014500 ffff8802002d5fd8 [ 3724.975122] ffff8802002d5fd8 0000000000014500 ffff8801c2e18000 ffff880213fc0000 [ 3724.975125] ffff8802002d5bd0 ffffffff810919c9 ffff880213fc0000 ffff88021f254500 [ 3724.975128] Call Trace: [ 3724.975134] [<ffffffff810919c9>] ? ttwu_do_wakeup+0x19/0x110 [ 3724.975137] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0 [ 3724.975141] [<ffffffff814e1029>] schedule+0x29/0x70 [ 3724.975144] [<ffffffff814e1463>] schedule_preempt_disabled+0x23/0x30 [ 3724.975149] [<ffffffff814df9d8>] __mutex_lock_slowpath+0x168/0x3b0 [ 3724.975152] [<ffffffff814dfc32>] mutex_lock+0x12/0x30 [ 3724.975156] [<ffffffff81388d03>] _request_firmware+0x3e3/0xa90 [ 3724.975159] [<ffffffff813893e4>] request_firmware+0x34/0x50 [ 3724.975162] [<ffffffff81389434>] __async_dev_cache_fw_image+0x34/0x100 [ 3724.975165] [<ffffffff8108ab47>] async_run_entry_fn+0x37/0x130 [ 3724.975169] [<ffffffff8107c6e7>] process_one_work+0x167/0x450 [ 3724.975172] [<ffffffff8107d0f1>] worker_thread+0x121/0x3a0 [ 3724.975174] [<ffffffff8107cfd0>] ? manage_workers.isra.23+0x2b0/0x2b0 [ 3724.975178] [<ffffffff81083960>] kthread+0xc0/0xd0 [ 3724.975181] [<ffffffff810838a0>] ? kthread_create_on_node+0x120/0x120 [ 3724.975184] [<ffffffff814ea52c>] ret_from_fork+0x7c/0xb0 [ 3724.975187] [<ffffffff810838a0>] ? kthread_create_on_node+0x120/0x120 [ 3724.975193] INFO: task kworker/u16:2:14505 blocked for more than 120 seconds. [ 3724.975195] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3724.975196] kworker/u16:2 D 0000000000000246 0 14505 2 0x00000000 [ 3724.975200] Workqueue: events_unbound async_run_entry_fn [ 3724.975201] ffff8801ae823c70 0000000000000046 0000000000014500 ffff8801ae823fd8 [ 3724.975204] ffff8801ae823fd8 0000000000014500 ffff88021243e540 ffff880212b2e540 [ 3724.975207] ffff8801ae823bd0 ffffffff810919c9 ffff880212b2e540 ffff88021f294500 [ 3724.975210] Call Trace: [ 3724.975213] [<ffffffff810919c9>] ? ttwu_do_wakeup+0x19/0x110 [ 3724.975216] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0 [ 3724.975218] [<ffffffff814e1029>] schedule+0x29/0x70 [ 3724.975221] [<ffffffff814e1463>] schedule_preempt_disabled+0x23/0x30 [ 3724.975224] [<ffffffff814df9d8>] __mutex_lock_slowpath+0x168/0x3b0 [ 3724.975227] [<ffffffff814dfc32>] mutex_lock+0x12/0x30 [ 3724.975230] [<ffffffff81388d03>] _request_firmware+0x3e3/0xa90 [ 3724.975233] [<ffffffff813893e4>] request_firmware+0x34/0x50 [ 3724.975236] [<ffffffff81389434>] __async_dev_cache_fw_image+0x34/0x100 [ 3724.975239] [<ffffffff8108ab47>] async_run_entry_fn+0x37/0x130 [ 3724.975241] [<ffffffff8107c6e7>] process_one_work+0x167/0x450 [ 3724.975244] [<ffffffff8107d0f1>] worker_thread+0x121/0x3a0 [ 3724.975246] [<ffffffff8107cfd0>] ? manage_workers.isra.23+0x2b0/0x2b0 [ 3724.975249] [<ffffffff81083960>] kthread+0xc0/0xd0 [ 3724.975252] [<ffffffff810838a0>] ? kthread_create_on_node+0x120/0x120 [ 3724.975254] [<ffffffff814ea52c>] ret_from_fork+0x7c/0xb0 [ 3724.975257] [<ffffffff810838a0>] ? kthread_create_on_node+0x120/0x120 Steps to reproduce: |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Wednesday, 12 March 2014, 00:03 GMT
Reason for closing: No response
Wednesday, 12 March 2014, 00:03 GMT
Reason for closing: No response
Comment by
Gerardo Exequiel Pozzi (djgera) -
Friday, 07 February 2014, 00:53 GMT
- Field changed: Summary (Wifi failed to resume after sleep → [linux] 3.11: Wifi failed to resume after sleep)
- Field changed: Status (Unconfirmed → Waiting on Response)
- Field changed: Category (Kernel → Upstream Bugs)
- Task assigned to Thomas Bächler (brain0), Tobias Powalowski (tpowa)
status with 3.12/3.13? If persist, please report to upstream.
Thanks.