Suspending fail: system back to lock screen

Hello!
I have problem with suspend: my PC trying to go to suspend mode, but after a few second tern back to lock screen.
I’m using desktop Fedora Workstation 37, Gnome 43.2, X11. My PC is Intel core i7, Nvidia GTX750ti (driver version: 525.60.11). I have tried X11 and Wayland — in both the same problem. I have tried to close all programs before suspend, and I’ve tried to logout from current user shell. It’s did not help too.

My journalctl has error:
systemd-sleep: Failed to put system to sleep. System resumed again: Device or resource busy

and dmesg has:

Freezing of tasks failed after 20.007 seconds (0 tasks refusing to freeze, wq_busy=1):
Showing busy workqueues and worker pools:
workqueue events: flags=0x0
  pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=18/256 refcnt=19
    in-flight: 4237:output_poll_execute
    pending: psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work, psi_avgs_work
workqueue events_freezable: flags=0x4
  pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/0 refcnt=2
    pending: pci_pme_list_scan
workqueue mm_percpu_wq: flags=0x8
  pwq 6: cpus=3 node=0 flags=0x0 nice=0 active=1/256 refcnt=2
    pending: vmstat_update

 <TASK>
 __schedule+0x332/0x12c0
 ? update_load_avg+0x7e/0x730
 schedule+0x5d/0xe0
 schedule_timeout+0xfa/0x140
 wait_for_completion+0x76/0x140
 __flush_work.isra.0+0x165/0x260
 ? flush_workqueue_prep_pwqs+0x110/0x110
 __lru_add_drain_all+0x15e/0x200
 khugepaged+0x5b/0x1790
 ? __schedule+0x33a/0x12c0
 ? ttwu_queue_wakelist+0xbf/0x110
 ? dequeue_task_stop+0x70/0x70
 ? _raw_spin_lock_irqsave+0x23/0x50
 ? collapse_pte_mapped_thp+0x3e0/0x3e0
 kthread+0xe6/0x110
 ? kthread_complete_and_exit+0x20/0x20
 ret_from_fork+0x1f/0x30
 </TASK>

I don’t understand what the problem: Is it system bug or my OS settings wrong?
Is any possibility to look more informative logs data to fix it?

Reinstall OS, problem has gone.