Still present on 5.13.4-200.fc34.x86_64+debug
Now happened right after bug #1988131 while resuming from suspend.

[ 6292.301405] [drm] ib test on ring 5 succeeded
[ 6292.336373] usb 3-2.4.4: reset high-speed USB device number 7 using xhci_hcd
[ 6292.752511] usb 3-2.4.4.4: reset high-speed USB device number 9 using xhci_hcd
[ 6293.169234] usb 3-2.4.4.4.2: reset full-speed USB device number 10 using xhci_hcd
[ 6293.300786] BUG: sleeping function called from invalid context at net/core/sock.c:3071
[ 6293.300799] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 9991, name: kworker/u64:14
[ 6293.300801] 5 locks held by kworker/u64:14/9991:
[ 6293.300803]  #0: ffff947c00051948 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x21a/0x5c0
[ 6293.300814]  #1: ffffa4260513fe70 ((work_completion)(&entry->work)){+.+.}-{0:0}, at: process_one_work+0x21a/0x5c0
[ 6293.300823]  #2: ffff947c1068c238 (&dev->mutex){....}-{3:3}, at: device_resume+0x5f/0x200
[ 6293.300832]  #3: ffff947c1068c9c0 (&dev->mutex){....}-{3:3}, at: device_release_driver+0x1c/0x40
[ 6293.300840]  #4: ffffffffc0a9f400 (hci_sk_list.lock){++++}-{2:2}, at: hci_sock_dev_event+0x144/0x200 [bluetooth]
[ 6293.300866] CPU: 3 PID: 9991 Comm: kworker/u64:14 Not tainted 5.13.4-200.fc34.x86_64+debug #1
[ 6293.300869] Hardware name: ASUS System Product Name/TUF GAMING B550M-PLUS, BIOS 1401 12/03/2020
[ 6293.300871] Workqueue: events_unbound async_run_entry_fn
[ 6293.300874] Call Trace:
[ 6293.300877]  dump_stack+0x7f/0xa1
[ 6293.300881]  ___might_sleep.cold+0xb6/0xc6
[ 6293.300885]  lock_sock_nested+0x28/0x90
[ 6293.300889]  hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.300906]  hci_unregister_dev+0xda/0x500 [bluetooth]
[ 6293.300921]  ? _raw_spin_unlock_irq+0x24/0x40
[ 6293.300926]  ? usb_hcd_flush_endpoint+0x80/0x180
[ 6293.300932]  btusb_disconnect+0x63/0x150 [btusb]
[ 6293.300937]  usb_unbind_interface+0x8d/0x270
[ 6293.300943]  __device_release_driver+0x180/0x240
[ 6293.300947]  ? usb_dev_thaw+0x10/0x10
[ 6293.300949]  device_release_driver+0x26/0x40
[ 6293.300952]  usb_forced_unbind_intf+0x70/0xa0
[ 6293.300955]  unbind_marked_interfaces.isra.0+0x42/0x60
[ 6293.300958]  usb_resume+0x5d/0x70
[ 6293.300961]  dpm_run_callback+0x51/0xc0
[ 6293.300965]  device_resume+0xa9/0x200
[ 6293.300969]  async_resume+0x19/0x30
[ 6293.300972]  async_run_entry_fn+0x30/0x130
[ 6293.300975]  process_one_work+0x2b0/0x5c0
[ 6293.300984]  worker_thread+0x55/0x3c0
[ 6293.300986]  ? process_one_work+0x5c0/0x5c0
[ 6293.300990]  kthread+0x149/0x170
[ 6293.300993]  ? set_kthread_struct+0x40/0x40
[ 6293.300997]  ret_from_fork+0x22/0x30

[ 6293.301035] ======================================================
[ 6293.301035] WARNING: possible circular locking dependency detected
[ 6293.301036] 5.13.4-200.fc34.x86_64+debug #1 Tainted: G        W        
[ 6293.301036] ------------------------------------------------------
[ 6293.301037] kworker/u64:14/9991 is trying to acquire lock:
[ 6293.301037] ffff947c0fc7f130 (sk_lock-AF_BLUETOOTH-BTPROTO_HCI){+.+.}-{0:0}, at: hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.301054] 
               but task is already holding lock:
[ 6293.301054] ffffffffc0a9f400 (hci_sk_list.lock){++++}-{2:2}, at: hci_sock_dev_event+0x144/0x200 [bluetooth]
[ 6293.301070] 
               which lock already depends on the new lock.

[ 6293.301070] 
               the existing dependency chain (in reverse order) is:
[ 6293.301071] 
               -> #1 (hci_sk_list.lock){++++}-{2:2}:
[ 6293.301072]        _raw_read_lock+0x3d/0xa0
[ 6293.301075]        hci_sock_sendmsg+0x9a9/0xa90 [bluetooth]
[ 6293.301089]        sock_sendmsg+0x5e/0x60
[ 6293.301091]        ____sys_sendmsg+0x22f/0x270
[ 6293.301093]        ___sys_sendmsg+0x81/0xc0
[ 6293.301094]        __sys_sendmsg+0x49/0x80
[ 6293.301095]        do_syscall_64+0x40/0x80
[ 6293.301096]        entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 6293.301098] 
               -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_HCI){+.+.}-{0:0}:
[ 6293.301099]        __lock_acquire+0x11c7/0x1de0
[ 6293.301101]        lock_acquire+0xc4/0x2e0
[ 6293.301102]        lock_sock_nested+0x70/0x90
[ 6293.301103]        hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.301117]        hci_unregister_dev+0xda/0x500 [bluetooth]
[ 6293.301131]        btusb_disconnect+0x63/0x150 [btusb]
[ 6293.301133]        usb_unbind_interface+0x8d/0x270
[ 6293.301134]        __device_release_driver+0x180/0x240
[ 6293.301136]        device_release_driver+0x26/0x40
[ 6293.301137]        usb_forced_unbind_intf+0x70/0xa0
[ 6293.301139]        unbind_marked_interfaces.isra.0+0x42/0x60
[ 6293.301140]        usb_resume+0x5d/0x70
[ 6293.301141]        dpm_run_callback+0x51/0xc0
[ 6293.301143]        device_resume+0xa9/0x200
[ 6293.301144]        async_resume+0x19/0x30
[ 6293.301146]        async_run_entry_fn+0x30/0x130
[ 6293.301147]        process_one_work+0x2b0/0x5c0
[ 6293.301148]        worker_thread+0x55/0x3c0
[ 6293.301150]        kthread+0x149/0x170
[ 6293.301151]        ret_from_fork+0x22/0x30
[ 6293.301153] 
               other info that might help us debug this:

[ 6293.301153]  Possible unsafe locking scenario:

[ 6293.301153]        CPU0                    CPU1
[ 6293.301154]        ----                    ----
[ 6293.301154]   lock(hci_sk_list.lock);
[ 6293.301155]                                lock(sk_lock-AF_BLUETOOTH-BTPROTO_HCI);
[ 6293.301156]                                lock(hci_sk_list.lock);
[ 6293.301157]   lock(sk_lock-AF_BLUETOOTH-BTPROTO_HCI);
[ 6293.301158] 
                *** DEADLOCK ***

[ 6293.301158] 5 locks held by kworker/u64:14/9991:
[ 6293.301159]  #0: ffff947c00051948 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x21a/0x5c0
[ 6293.301162]  #1: ffffa4260513fe70 ((work_completion)(&entry->work)){+.+.}-{0:0}, at: process_one_work+0x21a/0x5c0
[ 6293.301165]  #2: ffff947c1068c238 (&dev->mutex){....}-{3:3}, at: device_resume+0x5f/0x200
[ 6293.301168]  #3: ffff947c1068c9c0 (&dev->mutex){....}-{3:3}, at: device_release_driver+0x1c/0x40
[ 6293.301171]  #4: ffffffffc0a9f400 (hci_sk_list.lock){++++}-{2:2}, at: hci_sock_dev_event+0x144/0x200 [bluetooth]
[ 6293.301187] 
               stack backtrace:
[ 6293.301187] CPU: 3 PID: 9991 Comm: kworker/u64:14 Tainted: G        W         5.13.4-200.fc34.x86_64+debug #1
[ 6293.301189] Hardware name: ASUS System Product Name/TUF GAMING B550M-PLUS, BIOS 1401 12/03/2020
[ 6293.301189] Workqueue: events_unbound async_run_entry_fn
[ 6293.301191] Call Trace:
[ 6293.301191]  dump_stack+0x7f/0xa1
[ 6293.301192]  check_noncircular+0xdf/0x100
[ 6293.301194]  ? save_trace+0x3f/0x2d0
[ 6293.301197]  __lock_acquire+0x11c7/0x1de0
[ 6293.301200]  lock_acquire+0xc4/0x2e0
[ 6293.301201]  ? hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.301215]  ? sched_clock_cpu+0xc/0xb0
[ 6293.301217]  ? lock_release+0x28a/0x400
[ 6293.301218]  lock_sock_nested+0x70/0x90
[ 6293.301220]  ? hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.301234]  hci_sock_dev_event+0x180/0x200 [bluetooth]
[ 6293.301248]  hci_unregister_dev+0xda/0x500 [bluetooth]
[ 6293.301262]  ? _raw_spin_unlock_irq+0x24/0x40
[ 6293.301263]  ? usb_hcd_flush_endpoint+0x80/0x180
[ 6293.301266]  btusb_disconnect+0x63/0x150 [btusb]
[ 6293.301268]  usb_unbind_interface+0x8d/0x270
[ 6293.301270]  __device_release_driver+0x180/0x240
[ 6293.301272]  ? usb_dev_thaw+0x10/0x10
[ 6293.301274]  device_release_driver+0x26/0x40
[ 6293.301276]  usb_forced_unbind_intf+0x70/0xa0
[ 6293.301277]  unbind_marked_interfaces.isra.0+0x42/0x60
[ 6293.301279]  usb_resume+0x5d/0x70
[ 6293.301280]  dpm_run_callback+0x51/0xc0
[ 6293.301282]  device_resume+0xa9/0x200
[ 6293.301284]  async_resume+0x19/0x30
[ 6293.301286]  async_run_entry_fn+0x30/0x130
[ 6293.301287]  process_one_work+0x2b0/0x5c0
[ 6293.301290]  worker_thread+0x55/0x3c0
[ 6293.301292]  ? process_one_work+0x5c0/0x5c0
[ 6293.301293]  kthread+0x149/0x170
[ 6293.301295]  ? set_kthread_struct+0x40/0x40
[ 6293.301296]  ret_from_fork+0x22/0x30
[ 6294.299328] r8169 0000:04:00.0 enp4s0: Link is Up - 1Gbps/Full - flow control off
[ 6294.923222] PM: resume devices took 3.484 seconds
[ 6295.125909] OOM killer enabled.
[ 6295.127058] Restarting tasks ... 
[ 6295.131759] usb 3-2.4.4.1: USB disconnect, device number 8
[ 6295.135864] done.
[ 6295.144310] PM: suspend exit
[ 6295.211504] r8169 0000:04:00.0 enp4s0: Link is Down
[ 6295.243995] RTL8226B_RTL8221B 2.5Gbps PHY r8169-400:00: attached PHY driver (mii_bus:phy_addr=r8169-400:00, irq=MAC)
[ 6295.367490] Bluetooth: hci0: BCM: chip id 63
[ 6295.368489] Bluetooth: hci0: BCM: features 0x07
[ 6295.384497] Bluetooth: hci0: BCM20702A
[ 6295.384509] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 6295.385812] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[ 6295.385819] Bluetooth: hci0: BCM: 'brcm/BCM20702A1-0b05-17cb.hcd'
[ 6295.385822] Bluetooth: hci0: BCM: 'brcm/BCM-0b05-17cb.hcd'
[ 6295.412313] r8169 0000:04:00.0 enp4s0: Link is Down

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Just got it again for Fedora 35:

[13019.844132] ======================================================
[13019.844134] WARNING: possible circular locking dependency detected
[13019.844135] 5.15.6-200.fc35.x86_64+debug #1 Not tainted
[13019.844138] ------------------------------------------------------
[13019.844139] krfcommd/12744 is trying to acquire lock:
[13019.844141] ffff9ed7c8b6b130 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x4d/0x110 [rfcomm]
[13019.844155] 
               but task is already holding lock:
[13019.844156] ffff9ed88db1e140 (&d->lock){+.+.}-{3:3}, at: rfcomm_run+0x1339/0x1820 [rfcomm]
[13019.844165] 
               which lock already depends on the new lock.

[13019.844167] 
               the existing dependency chain (in reverse order) is:
[13019.844168] 
               -> #2 (&d->lock){+.+.}-{3:3}:
[13019.844172]        __mutex_lock+0x92/0x8c0
[13019.844179]        rfcomm_run+0x1339/0x1820 [rfcomm]
[13019.844187]        kthread+0x149/0x170
[13019.844191]        ret_from_fork+0x22/0x30
[13019.844196] 
               -> #1 (rfcomm_mutex){+.+.}-{3:3}:
[13019.844199]        __mutex_lock+0x92/0x8c0
[13019.844203]        rfcomm_dlc_open+0x31/0x350 [rfcomm]
[13019.844209]        rfcomm_sock_connect+0xd3/0x130 [rfcomm]
[13019.844215]        __sys_connect+0x9f/0xd0
[13019.844218]        __x64_sys_connect+0x14/0x20
[13019.844221]        do_syscall_64+0x3b/0x90
[13019.844224]        entry_SYSCALL_64_after_hwframe+0x44/0xae
[13019.844227] 
               -> #0 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}:
[13019.844230]        __lock_acquire+0x11fe/0x1e00
[13019.844234]        lock_acquire+0xc4/0x2e0
[13019.844237]        lock_sock_nested+0x2e/0x80
[13019.844240]        rfcomm_sk_state_change+0x4d/0x110 [rfcomm]
[13019.844246]        rfcomm_run+0x1355/0x1820 [rfcomm]
[13019.844252]        kthread+0x149/0x170
[13019.844255]        ret_from_fork+0x22/0x30
[13019.844258] 
               other info that might help us debug this:

[13019.844259] Chain exists of:
                 sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM --> rfcomm_mutex --> &d->lock

[13019.844264]  Possible unsafe locking scenario:

[13019.844265]        CPU0                    CPU1
[13019.844266]        ----                    ----
[13019.844267]   lock(&d->lock);
[13019.844269]                                lock(rfcomm_mutex);
[13019.844271]                                lock(&d->lock);
[13019.844273]   lock(sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM);
[13019.844275] 
                *** DEADLOCK ***

[13019.844276] 2 locks held by krfcommd/12744:
[13019.844279]  #0: ffffffffc0f97130 (rfcomm_mutex){+.+.}-{3:3}, at: rfcomm_run+0x135/0x1820 [rfcomm]
[13019.844288]  #1: ffff9ed88db1e140 (&d->lock){+.+.}-{3:3}, at: rfcomm_run+0x1339/0x1820 [rfcomm]
[13019.844296] 
               stack backtrace:
[13019.844298] CPU: 0 PID: 12744 Comm: krfcommd Not tainted 5.15.6-200.fc35.x86_64+debug #1
[13019.844301] Hardware name: ASUS System Product Name/TUF GAMING B550M-PLUS, BIOS 1401 12/03/2020
[13019.844304] Call Trace:
[13019.844305]  <TASK>
[13019.844308]  dump_stack_lvl+0x57/0x72
[13019.844313]  check_noncircular+0xdf/0x100
[13019.844317]  ? __lock_acquire+0xfbd/0x1e00
[13019.844322]  __lock_acquire+0x11fe/0x1e00
[13019.844327]  ? rfcomm_run+0x1339/0x1820 [rfcomm]
[13019.844334]  lock_acquire+0xc4/0x2e0
[13019.844337]  ? rfcomm_sk_state_change+0x4d/0x110 [rfcomm]
[13019.844344]  ? mark_held_locks+0x50/0x80
[13019.844347]  ? rfcomm_run+0x1339/0x1820 [rfcomm]
[13019.844354]  lock_sock_nested+0x2e/0x80
[13019.844357]  ? rfcomm_sk_state_change+0x4d/0x110 [rfcomm]
[13019.844363]  rfcomm_sk_state_change+0x4d/0x110 [rfcomm]
[13019.844370]  rfcomm_run+0x1355/0x1820 [rfcomm]
[13019.844377]  ? __init_waitqueue_head+0x60/0x60
[13019.844381]  ? _raw_spin_unlock_irqrestore+0x37/0x40
[13019.844383]  ? rfcomm_check_accept+0xa0/0xa0 [rfcomm]
[13019.844390]  kthread+0x149/0x170
[13019.844393]  ? set_kthread_struct+0x40/0x40
[13019.844397]  ret_from_fork+0x22/0x30
[13019.844403]  </TASK>
[13020.166112] input: A605 (AVRCP) as /devices/virtual/input/input14

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.