[542.6274] WARNING: CPU: 0 PID: 20729 at /build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 _request_firmware+0x7c2/0xaf0() [542.6276] CPU: 0 PID: 20729 Comm: kworker/u17:0 Tainted: G OE 4.4.0-73-generic #94-Ubuntu [542.6277] Call Trace: [542.6277] [<ffffffff813f8493>] dump_stack+0x63/0x90 [542.6277] [<ffffffff81081302>] warn_slowpath_common+0x82/0xc0 [542.6277] [<ffffffff8108144a>] warn_slowpath_null+0x1a/0x20 [542.6277] [<ffffffff81571812>] _request_firmware+0x7c2/0xaf0 [542.6277] [<ffffffff81571b71>] request_firmware+0x31/0x50 [542.6278] [<ffffffffc07a5805>] btusb_setup_qca+0x185/0x3a0 [btusb] [542.6278] [<ffffffff8156906b>] ? __pm_runtime_resume+0x5b/0x70 [542.6278] [<ffffffffc07a4a49>] btusb_open+0x49/0x250 [btusb] [542.6278] [<ffffffffc0475cc2>] hci_dev_do_open+0x82/0x580 [bluetooth] [542.6278] [<ffffffff810ab70d>] ? ttwu_do_activate.constprop.90+0x5d/0x70 [542.6278] [<ffffffffc0477a60>] hci_power_on+0x40/0x1d0 [bluetooth] [542.6279] [<ffffffff810ecf04>] ? lock_timer_base.isra.22+0x54/0x70 [542.6279] [<ffffffff8109a555>] process_one_work+0x165/0x480 [542.6279] [<ffffffff8109a8bb>] worker_thread+0x4b/0x4c0 [542.6279] [<ffffffff8109a870>] ? process_one_work+0x480/0x480 [542.6279] [<ffffffff810a0be8>] kthread+0xd8/0xf0 [542.6279] [<ffffffff810a0b10>] ? kthread_create_on_node+0x1e0/0x1e0 [542.6279] [<ffffffff8183bd0f>] ret_from_fork+0x3f/0x70 [542.6279] [<ffffffff810a0b10>] ? kthread_create_on_node+0x1e0/0x1e0 [542.6279] ---[ end trace 4e3ab800f10b5115 ]--- [542.6279] bluetooth hci0: firmware: qca/rampatch_usb_00000302.bin will not be loaded [542.6279] Bluetooth: hci0: failed to request rampatch file: qca/rampatch_usb_00000302.bin (-11)
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1706833 Title: atheros bt failed after S3 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: [Impact] BT fails to load firmware after S3. On my system it's atheros' chip, but the same issue can be seen with broadcom's chip, too. [542.6274] WARNING: CPU: 0 PID: 20729 at /build/linux-MD8jsN/linux-4.4.0/drivers/base/firmware_class.c:1148 _request_firmware+0x7c2/0xaf0() The root cause of this issue is request_firmware() is being called at the wrong time. [Fix] The fix is from this old thread[1], but the patch didn't be accepted by the maintainer. It prevents the work queue from being re-created and calls request_firmware() immediately before usermodehelper is fully resumed. Making the workqueue freezable preserves the delay and will postpone the firmware loading time. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] From what I can see, I think this change should be safe, and after 240 times S3 test, the system and BT functions are still working. 1. http://lists.openwall.net/netdev/2015/05/06/3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1706833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
