Bluetooth: hci4: Received unexpected HCI Event 0x00
Bluetooth: hci4: Received unexpected HCI Event 0x00
Bluetooth: hci4: link tx timeout
Bluetooth: hci4: killing stalled connection 11:aa:aa:aa:aa:aa
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:580
in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 278, name: kworker/u5:0
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:0/278:
#0: ffff888014bcd938 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88800d8afd90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c2e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
CPU: 0 PID: 278 Comm: kworker/u5:0 Not tainted 6.5.0-rc4-next-20230804 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
dump_stack_lvl+0xc1/0xf0
__might_resched+0x2f9/0x510
__mutex_lock+0x9e/0x1a30
hci_cmd_sync_submit+0x3b/0x2d0
hci_cmd_sync_queue+0x7b/0xb0
hci_disconnect+0x1c2/0x450
__check_timeout+0x2cc/0x480
hci_tx_work+0x7cb/0x1a70
process_one_work+0xabf/0x1770
worker_thread+0x64f/0x12a0
kthread+0x33f/0x440
ret_from_fork+0x2f/0x70
ret_from_fork_asm+0x1b/0x30
=============================
[ BUG: Invalid wait context ]
6.5.0-rc4-next-20230804 #1 Tainted: G W
-----------------------------
kworker/u5:0/278 is trying to lock:
ffff8880152e49b0 (&hdev->unregister_lock){+.+.}-{3:3}, at: hci_cmd_sync_submit+0x3b/0x2d0
other info that might help us debug this:
context-{4:4}
3 locks held by kworker/u5:0/278:
#0: ffff888014bcd938 ((wq_completion)hci4#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
#1: ffff88800d8afd90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
#2: ffffffff8560c2e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
stack backtrace:
CPU: 0 PID: 278 Comm: kworker/u5:0 Tainted: G W 6.5.0-rc4-next-20230804 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
dump_stack_lvl+0x91/0xf0
__lock_acquire+0x1605/0x6340
lock_acquire+0x19a/0x4c0
__mutex_lock+0x12a/0x1a30
hci_cmd_sync_submit+0x3b/0x2d0
hci_cmd_sync_queue+0x7b/0xb0
hci_disconnect+0x1c2/0x450
__check_timeout+0x2cc/0x480
hci_tx_work+0x7cb/0x1a70
process_one_work+0xabf/0x1770
worker_thread+0x64f/0x12a0
kthread+0x33f/0x440
ret_from_fork+0x2f/0x70
ret_from_fork_asm+0x1b/0x30
autofs4:pid:7158:validate_dev_ioctl: invalid path supplied for cmd(0xc0189374)
autofs4:pid:7158:validate_dev_ioctl: invalid path supplied for cmd(0xc0189374)
UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_register_driver returned -16
UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_register_driver returned -16
UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy
misc raw-gadget: fail, usb_gadget_register_driver returned -16
Bluetooth: hci4: command 0x0406 tx timeout