Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) Subject: Re: [PATCH] Bluetooth: btmrvl: fix hung task warning dump From: Marcel Holtmann In-Reply-To: <1451391993-31195-1-git-send-email-akarwar@marvell.com> Date: Mon, 4 Jan 2016 10:26:36 -0800 Cc: linux-bluetooth@vger.kernel.org, Chin-Ran Lo Message-Id: <52AF759C-4DA2-43C1-A81A-4D12F2BBAB12@holtmann.org> References: <1451391993-31195-1-git-send-email-akarwar@marvell.com> To: Amitkumar Karwar Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Amitkumar, > It's been observed that when bluetooth driver fails to > activate the firmware, below hung task warning dump is > displayed after 120 seconds. > > [ 36.461022] Bluetooth: vendor=0x2df, device=0x912e, class=255, fn=2 > [ 56.512128] Bluetooth: FW failed to be active in time! > [ 56.517264] Bluetooth: Downloading firmware failed! > [ 240.252176] INFO: task kworker/3:2:129 blocked for more than 120 seconds. > [ 240.258931] Not tainted 3.18.0 #254 > [ 240.262972] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > [ 240.270751] kworker/3:2 D ffffffc000205760 0 129 2 0x00000000 > [ 240.277825] Workqueue: events request_firmware_work_func > [ 240.283134] Call trace: > [ 240.285581] [] __switch_to+0x80/0x8c > [ 240.290693] [] __schedule+0x540/0x7b8 > [ 240.295921] [] schedule+0x78/0x84 > [ 240.300764] [] __mmc_claim_host+0xe8/0x1c8 > [ 240.306395] [] sdio_claim_host+0x74/0x84 > [ 240.311840] [] 0xffffffbffc163d08 > [ 240.316685] [] 0xffffffbffc165104 > [ 240.321524] [] mwifiex_dnld_fw+0x98/0x110 [mwifiex] > [ 240.327918] [] mwifiex_remove_card+0x2c4/0x5fc [mwifiex] > [ 240.334741] [] request_firmware_work_func+0x44/0x80 > [ 240.341127] [] process_one_work+0x2ec/0x50c > [ 240.346831] [] worker_thread+0x350/0x470 > [ 240.352272] [] kthread+0xf0/0xfc > [ 240.357019] 2 locks held by kworker/3:2/129: > [ 240.361248] #0: ("events"){.+.+.+}, at: [] process_one_work+0x1f8/0x50c > [ 240.369562] #1: ((&fw_work->work)){+.+.+.}, at: [] process_one_work+0x1f8/0x50c > [ 240.378589] task PC stack pid father > [ 240.384501] kworker/1:1 D ffffffc000205760 0 40 2 0x00000000 > [ 240.391524] Workqueue: events mtk_atomic_work > [ 240.395884] Call trace: > [ 240.398317] [] __switch_to+0x80/0x8c > [ 240.403448] [] lock_acquire+0x128/0x164 > [ 240.408821] kworker/3:2 D ffffffc000205760 0 129 2 0x00000000 > [ 240.415867] Workqueue: events request_firmware_work_func > [ 240.421138] Call trace: > [ 240.423589] [] __switch_to+0x80/0x8c > [ 240.428688] [] __schedule+0x540/0x7b8 > [ 240.433886] [] schedule+0x78/0x84 > [ 240.438732] [] __mmc_claim_host+0xe8/0x1c8 > [ 240.444361] [] sdio_claim_host+0x74/0x84 > [ 240.449801] [] 0xffffffbffc163d08 > [ 240.454649] [] 0xffffffbffc165104 > [ 240.459486] [] mwifiex_dnld_fw+0x98/0x110 [mwifiex] > [ 240.465882] [] mwifiex_remove_card+0x2c4/0x5fc [mwifiex] > [ 240.472705] [] request_firmware_work_func+0x44/0x80 > [ 240.479090] [] process_one_work+0x2ec/0x50c > [ 240.484794] [] worker_thread+0x350/0x470 > [ 240.490231] [] kthread+0xf0/0xfc > > This patch adds missing sdio_release_host() call so that wlan driver > thread can claim sdio host. > > Fixes: 4863e4cc31d647e1 ("Bluetooth: btmrvl: release sdio bus after firmware is up") > Signed-off-by: Chin-Ran Lo > Signed-off-by: Amitkumar Karwar > --- > drivers/bluetooth/btmrvl_sdio.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) patch has been applied to bluetooth-next tree. Regards Marcel