Bluetooth: Wrong link type (-22)
Bluetooth: hci5: link tx timeout
Bluetooth: hci5: 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: 283, name: kworker/u5:4
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
3 locks held by kworker/u5:4/283:
 #0: ffff88801f914138 ((wq_completion)hci5#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
 #1: ffff88804034fdb0 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
 #2: ffffffff8560b6c0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
CPU: 0 PID: 283 Comm: kworker/u5:4 Not tainted 6.4.0-next-20230703 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci5 hci_tx_work
Call Trace:
 <TASK>
 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+0x2c/0x50
 </TASK>

=============================
[ BUG: Invalid wait context ]
6.4.0-next-20230703 #1 Tainted: G        W         
-----------------------------
kworker/u5:4/283 is trying to lock:
ffff8880426789b0 (&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:4/283:
 #0: ffff88801f914138 ((wq_completion)hci5#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770
 #1: ffff88804034fdb0 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770
 #2: ffffffff8560b6c0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480
stack backtrace:
CPU: 0 PID: 283 Comm: kworker/u5:4 Tainted: G        W          6.4.0-next-20230703 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci5 hci_tx_work
Call Trace:
 <TASK>
 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+0x2c/0x50
 </TASK>
Bluetooth: Wrong link type (-22)
Bluetooth: hci5: link tx timeout
Bluetooth: hci5: killing stalled connection 11:aa:aa:aa:aa:aa
loop7: detected capacity change from 0 to 40
FAT-fs (loop7): bogus number of reserved sectors
FAT-fs (loop7): Can't find a valid FAT filesystem
Bluetooth: hci5: command 0x0406 tx timeout
Bluetooth: Wrong link type (-22)
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: 7087, name: kworker/u5:0
preempt_count: 0, expected: 0
RCU nest depth: 1, expected: 0
INFO: lockdep is turned off.
CPU: 1 PID: 7087 Comm: kworker/u5:0 Tainted: G        W          6.4.0-next-20230703 #1
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: hci4 hci_tx_work
Call Trace:
 <TASK>
 dump_stack_lvl+0xc1/0xf0
 __might_resched+0x2f9/0x510
 __mutex_lock+0x9e/0x1a30
loop7: detected capacity change from 0 to 40
 hci_cmd_sync_submit+0x3b/0x2d0
 hci_cmd_sync_queue+0x7b/0xb0
 hci_disconnect+0x1c2/0x450
FAT-fs (loop7): bogus number of reserved sectors
 __check_timeout+0x2cc/0x480
FAT-fs (loop7): Can't find a valid FAT filesystem
 hci_tx_work+0x7cb/0x1a70
 process_one_work+0xabf/0x1770
 worker_thread+0x64f/0x12a0
 kthread+0x33f/0x440
 ret_from_fork+0x2c/0x50
 </TASK>
Bluetooth: hci5: ACL packet for unknown connection handle 175
Bluetooth: hci5: ACL packet for unknown connection handle 175
Bluetooth: Wrong link type (-22)
Bluetooth: hci4: link tx timeout
Bluetooth: hci4: killing stalled connection 11:aa:aa:aa:aa:aa