Bluetooth: Wrong link type (-71) Bluetooth: hci7: link tx timeout Bluetooth: hci7: killing stalled connection 10:aa:aa:aa:aa:aa Bluetooth: hci7: link tx timeout Bluetooth: hci7: 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: 288, name: kworker/u5:5 preempt_count: 0, expected: 0 RCU nest depth: 1, expected: 0 3 locks held by kworker/u5:5/288: #0: ffff888019f76938 ((wq_completion)hci7#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770 #1: ffff888039dffd90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770 #2: ffffffff8560c3e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480 CPU: 1 PID: 288 Comm: kworker/u5:5 Not tainted 6.5.0-rc3-next-20230724 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: hci7 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-rc3-next-20230724 #1 Tainted: G W ----------------------------- kworker/u5:5/288 is trying to lock: ffff88801c3789b0 (&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:5/288: #0: ffff888019f76938 ((wq_completion)hci7#2){+.+.}-{0:0}, at: process_one_work+0x99d/0x1770 #1: ffff888039dffd90 ((work_completion)(&hdev->tx_work)){+.+.}-{0:0}, at: process_one_work+0x9d0/0x1770 #2: ffffffff8560c3e0 (rcu_read_lock){....}-{1:2}, at: __check_timeout+0x171/0x480 stack backtrace: CPU: 1 PID: 288 Comm: kworker/u5:5 Tainted: G W 6.5.0-rc3-next-20230724 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: hci7 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 Bluetooth: hci5: unexpected event 0x48 length: 29 > 3 Bluetooth: hci5: wrong event for mode 0 Bluetooth: hci6: unexpected event 0x48 length: 29 > 3 Bluetooth: hci6: wrong event for mode 0 Bluetooth: hci6: unexpected event for opcode 0x2024 Bluetooth: Wrong link type (-71) Bluetooth: Wrong link type (-71) Bluetooth: hci6: link tx timeout Bluetooth: hci6: killing stalled connection 10:aa:aa:aa:aa:aa Bluetooth: hci6: link tx timeout Bluetooth: hci6: killing stalled connection 11:aa:aa:aa:aa:aa Bluetooth: hci7: unexpected event 0x48 length: 29 > 3 Bluetooth: hci7: wrong event for mode 0 Bluetooth: hci7: unexpected event for opcode 0x2024 Bluetooth: Wrong link type (-71) Bluetooth: hci7: link tx timeout Bluetooth: hci7: killing stalled connection 10:aa:aa:aa:aa:aa Bluetooth: hci5: unexpected event 0x48 length: 29 > 3 Bluetooth: hci5: wrong event for mode 0 Bluetooth: Wrong link type (-71) Bluetooth: hci6: unexpected event 0x48 length: 29 > 3 Bluetooth: hci6: wrong event for mode 0 Bluetooth: hci6: unexpected event for opcode 0x2024 Bluetooth: hci7: unexpected event 0x48 length: 29 > 3 Bluetooth: hci7: wrong event for mode 0 Bluetooth: Wrong link type (-71) Bluetooth: Wrong link type (-71) Bluetooth: hci6: wrong event for mode 0 Bluetooth: Wrong link type (-71) cgroup: No subsys list or none specified cgroup: No subsys list or none specified cgroup: No subsys list or none specified cgroup: No subsys list or none specified cgroup: No subsys list or none specified cgroup: No subsys list or none specified cgroup: No subsys list or none specified Bluetooth: hci5: Controller not accepting commands anymore: ncmd = 0 Bluetooth: hci5: Injecting HCI hardware error event Bluetooth: hci5: hardware error 0x00 Bluetooth: hci7: Controller not accepting commands anymore: ncmd = 0 Bluetooth: hci7: Injecting HCI hardware error event Bluetooth: hci7: hardware error 0x00 Bluetooth: hci6: Controller not accepting commands anymore: ncmd = 0 Bluetooth: hci6: Injecting HCI hardware error event Bluetooth: hci6: hardware error 0x00 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: hci5: Opcode 0x c03 failed: -110 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: hci7: Opcode 0x c03 failed: -110 Bluetooth: hci6: Opcode 0x c03 failed: -110 UDC core: USB Raw Gadget: couldn't find an available UDC or it's busy 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 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 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 loop3: detected capacity change from 0 to 256