RTX 4060 when Leaving Suspend, Screen Blanks for 3 times (Bluetooth USB Kernel bug?) (LG Ultragear DisplayPort)

NVIDIA Open GPU Kernel Modules Version

590.48.01-1

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.

• I confirm that this does not happen with the proprietary driver package.

Operating System and Version

EndeavourOS Linux

Kernel Release

Linux john-ryzen 6.12.63-1-lts

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.

-Yes, I am running on a stable kernel release.

Hardware: GPU

RTX 4060

Describe the bug

When I leave suspend. Firefox is unresponsive when resumed.

Also, when I leave suspend sometimes the screen reblanks, goes back to suspend.

It looks like maybe my bluetooth dongle may be causing it somehow?

[john@john-ryzen ~]$ journalctl -r -p 3 -b 0
Jan 02 14:31:10 john-ryzen kernel: hwmon hwmon4: update_ec_sensors() failure
Jan 02 14:31:10 john-ryzen kernel: hwmon hwmon4: update_ec_sensors() failure
Jan 02 14:31:05 john-ryzen bluetoothd[1001]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 02 14:31:05 john-ryzen gdm[1103]: GLib: Source ID 186 was not found when attempting to remove it
Jan 02 14:30:42 john-ryzen kernel: hwmon hwmon4: update_ec_sensors() failure
Jan 02 14:30:42 john-ryzen kernel: hwmon hwmon4: update_ec_sensors() failure
Jan 02 14:30:35 john-ryzen gdm[1103]: GLib: Source ID 182 was not found when attempting to remove it
Jan 02 14:30:35 john-ryzen bluetoothd[1001]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Jan 02 12:54:04 john-ryzen gdm[1103]: GLib: Source ID 160 was not found when attempting to remove it
Jan 02 12:54:03 john-ryzen bluetoothd[1001]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters

To Reproduce

Let your computer suspend, and intermittently the screen will blank when resuming. May be related to USB bluetooth dongle.

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

[john@john-ryzen ~]$ sudo nvidia-bug-report.sh

nvidia-bug-report.sh will now collect information about your
system and create the file 'nvidia-bug-report.log.gz' in the current
directory. It may take several seconds to run. In some
cases, it may hang trying to capture data generated dynamically
by the Linux kernel and/or the NVIDIA kernel module. While
the bug report log file will be incomplete if this happens, it
may still contain enough data to diagnose your problem.

If nvidia-bug-report.sh hangs, consider running with the --safe-mode
and --extra-system-data command line arguments.

Please include the 'nvidia-bug-report.log.gz' log file when reporting
your bug via the NVIDIA Linux forum (see forums.developer.nvidia.com)
or by sending email to 'linux-bugs@nvidia.com'.

By delivering 'nvidia-bug-report.log.gz' to NVIDIA, you acknowledge
and agree that personal information may inadvertently be included in
the output. Notwithstanding the foregoing, NVIDIA will use the
output only for the purpose of investigating your reported issue.

Running nvidia-bug-report.sh...
Detected driver type: Running RM Driver on GPUs
complete.

Summary of Skipped Sections:

Skipped Component | Details

ibstat output | ibstat not found

acpidump output | acpidump not found

mst output | mst not found

nvlsm-bug-report.sh output | nvlsm-bug-report.sh not found

Summary of Errors:

Error Component | Details | Resolution

More Info

I think this is a GDM/bluetooth bug. But I don't see why it would affect my DisplayPort screen.

Start with the reported suspend/resume symptoms, the Linux 6.12.63-1-lts journal entries, and the generated nvidia-bug-report.log.gz. First establish whether the issue reproduces with the proprietary driver and whether the Bluetooth dongle is involved; done requires a reproducible, driver-specific failure with sufficient logs to identify the affected component.