Suspend/hibernation broken on my machine after installing updates

I had already upgraded my system from 9.3 to 9.4. Suspend/sleep was working fine. I installed some more updates yesterday and found that suspend is now broken. It reboots as soon as I press the power button to run it again. I suspended it and sure enough it reboots the server. Anybody else seeing this situation. I should have kept a list of updates that it found, but did not. Is there anyway I can check the database for all the updates that it did after the last update I ran? Thanks.

I have attached the logs from the point that I suspended it to check it out



May 31 23:19:28 mainServerRyzen systemd-logind[1276]: The system will suspend now!
May 31 23:19:28 mainServerRyzen ModemManager[1326]: <info>  [sleep-monitor-systemd] system is about to suspend
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.1774] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.1778] device (enp6s0f1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen gnome-shell[4129]: [4122:4151:0531/231928.178349:ERROR:connection_factory_impl.cc(483)] ConnectionHandler failed with net error: -2
May 31 23:19:28 mainServerRyzen kernel: e1000e 0000:06:00.1 enp6s0f1: NIC Link is Down
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.3316] device (enp7s0f0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen kernel: e1000e 0000:07:00.0 enp7s0f0: NIC Link is Down
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.4844] manager: NetworkManager state is now ASLEEP
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.4846] device (enp42s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.4854] device (enp7s0f1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen kernel: device enp7s0f1 left promiscuous mode
May 31 23:19:28 mainServerRyzen kernel: br0: port 1(enp7s0f1) entered disabled state
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.4987] device (br0): detached bridge port enp7s0f1
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.4987] device (enp7s0f1): released from master device br0
May 31 23:19:28 mainServerRyzen systemd[1]: Starting Network Manager Script Dispatcher Service...
May 31 23:19:28 mainServerRyzen systemd[1]: Started Network Manager Script Dispatcher Service.
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5176] device (enp42s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Withdrawing address record for fe80::67c:16ff:fe77:2f44 on enp42s0.
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Leaving mDNS multicast group on interface enp42s0.IPv6 with address fe80::67c:16ff:fe77:2f44.
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5180] dhcp4 (enp42s0): canceled DHCP transaction
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Interface enp42s0.IPv6 no longer relevant for mDNS.
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5180] dhcp4 (enp42s0): activation: beginning transaction (timeout in 45 seconds)
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5181] dhcp4 (enp42s0): state changed no lease
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Withdrawing address record for 10.10.1.10 on enp42s0.
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Leaving mDNS multicast group on interface enp42s0.IPv4 with address 10.10.1.10.
May 31 23:19:28 mainServerRyzen avahi-daemon[1264]: Interface enp42s0.IPv4 no longer relevant for mDNS.
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5337] policy: set 'br0' (br0) as default for IPv4 routing and DNS
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5353] device (enp7s0f1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5363] device (enp42s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen kernel: r8169 0000:2a:00.0 enp42s0: Link is Down
May 31 23:19:28 mainServerRyzen NetworkManager[1397]: <info>  [1717215568.5453] device (enp7s0f1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 31 23:19:28 mainServerRyzen kernel: e1000e 0000:07:00.1 enp7s0f1: NIC Link is Down
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:19:28 mainServerRyzen gnome-shell[3071]: Timelines with detached actors are not supported
May 31 23:20:20 mainServerRyzen kernel: The list of certified hardware and cloud instances for Enterprise Linux 9 can be viewed at the Red Hat Ecosystem Catalog, https://catalog.redhat.com.
May 31 23:20:20 mainServerRyzen kernel: Command line: BOOT_IMAGE=(hd5,gpt2)/vmlinuz-5.14.0-427.18.1.el9_4.x86_64 root=/dev/mapper/rl_system-root ro crashkernel=1G-4G:192M,4G-64G:256M,64G-:512M resume=/dev/mapper/rl_system-swap rd.lvm.lv=rl_system/root rd.lvm.lv=rl_system/swap rhgb quiet rd.driver.blacklist=nouveau
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: xstate_offset[9]:  832, xstate_sizes[9]:    8
May 31 23:20:20 mainServerRyzen kernel: x86/fpu: Enabled xstate features 0x207, context size is 840 bytes, using 'compacted' format.
May 31 23:20:20 mainServerRyzen kernel: signal: max sigframe size: 3376
May 31 23:20:20 mainServerRyzen kernel: BIOS-provided physical RAM map:
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009e01fff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1fffff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000000a20e000-0x000000000affffff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000000b000000-0x000000000b01ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000000b020000-0x00000000db117fff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000db118000-0x00000000db497fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000db498000-0x00000000db4fbfff] ACPI data
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000db4fc000-0x00000000dcbfafff] ACPI NVS
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000dcbfb000-0x00000000ddbfefff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000ddbff000-0x00000000deffffff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000df000000-0x00000000dfffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x0000000100000000-0x000000101f37ffff] usable
May 31 23:20:20 mainServerRyzen kernel: BIOS-e820: [mem 0x000000101f380000-0x000000101fffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: NX (Execute Disable) protection: active
May 31 23:20:20 mainServerRyzen kernel: extended physical RAM map:
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x0000000000100000-0x0000000009e01fff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x0000000009e02000-0x0000000009ffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000000a000000-0x000000000a1fffff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000000a200000-0x000000000a20dfff] ACPI NVS
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000000a20e000-0x000000000affffff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000000b000000-0x000000000b01ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000000b020000-0x00000000d774c017] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000d774c018-0x00000000d776ba57] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000d776ba58-0x00000000d776c017] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000d776c018-0x00000000d777a057] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000d777a058-0x00000000db117fff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000db118000-0x00000000db497fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000db498000-0x00000000db4fbfff] ACPI data
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000db4fc000-0x00000000dcbfafff] ACPI NVS
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000dcbfb000-0x00000000ddbfefff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000ddbff000-0x00000000deffffff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000df000000-0x00000000dfffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fd200000-0x00000000fd2fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fd600000-0x00000000fd7fffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fea00000-0x00000000fea0ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fec30000-0x00000000fec30fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x0000000100000000-0x000000101f37ffff] usable
May 31 23:20:20 mainServerRyzen kernel: reserve setup_data: [mem 0x000000101f380000-0x000000101fffffff] reserved
May 31 23:20:20 mainServerRyzen kernel: efi: EFI v2.7 by American Megatrends
May 31 23:20:20 mainServerRyzen kernel: efi: ACPI=0xdcbe4000 ACPI 2.0=0xdcbe4014 SMBIOS=0xdd9fd000 MEMATTR=0xd8b30298 MOKvar=0xdda2a000 RNG=0xdb4e8018 
May 31 23:20:20 mainServerRyzen kernel: efi: Remove mem308: MMIO range=[0xf0000000-0xf7ffffff] (128MB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Remove mem309: MMIO range=[0xfd200000-0xfd2fffff] (1MB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Remove mem310: MMIO range=[0xfd600000-0xfd7fffff] (2MB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem311: MMIO range=[0xfea00000-0xfea0ffff] (64KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Remove mem312: MMIO range=[0xfeb80000-0xfec01fff] (0MB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem313: MMIO range=[0xfec10000-0xfec10fff] (4KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem314: MMIO range=[0xfec30000-0xfec30fff] (4KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem315: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem316: MMIO range=[0xfed40000-0xfed44fff] (20KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem317: MMIO range=[0xfed80000-0xfed8ffff] (64KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem318: MMIO range=[0xfedc2000-0xfedcffff] (56KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Not removing mem319: MMIO range=[0xfedd4000-0xfedd5fff] (8KB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: efi: Remove mem320: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
May 31 23:20:20 mainServerRyzen kernel: secureboot: Secure boot disabled
May 31 23:20:20 mainServerRyzen kernel: SMBIOS 2.8 present.
May 31 23:20:20 mainServerRyzen kernel: DMI: Micro-Star International Co., Ltd. MS-7C56/B550-A PRO (MS-7C56), BIOS A.F0 10/11/2023
May 31 23:20:20 mainServerRyzen kernel: tsc: Fast TSC calibration using PIT
May 31 23:20:20 mainServerRyzen kernel: tsc: Detected 3399.744 MHz processor
May 31 23:20:20 mainServerRyzen kernel: last_pfn = 0x101f380 max_arch_pfn = 0x400000000
May 31 23:20:20 mainServerRyzen kernel: total RAM covered: 3583M
May 31 23:20:20 mainServerRyzen kernel: Found optimal setting for mtrr clean up
May 31 23:20:20 mainServerRyzen kernel: gran_size: 64K #011chunk_size: 64M #011num_reg: 4  #011lose cover RAM: 0G
May 31 23:20:20 mainServerRyzen kernel: MTRR map: 8 entries (4 fixed + 4 variable; max 21), built from 9 variable MTRRs
May 31 23:20:20 mainServerRyzen kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
May 31 23:20:20 mainServerRyzen kernel: last_pfn = 0xdf000 max_arch_pfn = 0x400000000
May 31 23:20:20 mainServerRyzen kernel: Using GB pages for direct mapping
May 31 23:20:20 mainServerRyzen kernel: secureboot: Secure boot disabled
May 31 23:20:20 mainServerRyzen kernel: RAMDISK: [mem 0xcf558000-0xd2e92fff]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Early table checksum verification disabled
May 31 23:20:20 mainServerRyzen kernel: ACPI: RSDP 0x00000000DCBE4014 000024 (v02 ALASKA)
May 31 23:20:20 mainServerRyzen kernel: ACPI: XSDT 0x00000000DCBE3728 0000C4 (v01 ALASKA A M I    01072009 AMI  01000013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: FACP 0x00000000DB4ED000 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: DSDT 0x00000000DB4CA000 00721F (v02 ALASKA A M I    01072009 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: FACS 0x00000000DCBDE000 000040
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4F3000 008CE9 (v02 AMD    AmdTable 00000002 MSFT 04000000)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4EF000 003B86 (v02 AMD    AMD AOD  00000001 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4EE000 000221 (v02 ALASKA CPUSSDT  01072009 AMI  01072009)
May 31 23:20:20 mainServerRyzen kernel: ACPI: FIDT 0x00000000DB4E5000 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: MCFG 0x00000000DB4E4000 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: HPET 0x00000000DB4E3000 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
May 31 23:20:20 mainServerRyzen kernel: ACPI: IVRS 0x00000000DB4E2000 0000D0 (v02 AMD    AmdTable 00000001 AMD  00000001)
May 31 23:20:20 mainServerRyzen kernel: ACPI: FPDT 0x00000000DB4E1000 000044 (v01 ALASKA A M I    01072009 AMI  01000013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: PCCT 0x00000000DB4E0000 00006E (v02 AMD    AmdTable 00000001 AMD  00000001)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4DB000 004133 (v02 AMD    AmdTable 00000001 AMD  00000001)
May 31 23:20:20 mainServerRyzen kernel: ACPI: CRAT 0x00000000DB4DA000 000F10 (v01 AMD    AmdTable 00000001 AMD  00000001)
May 31 23:20:20 mainServerRyzen kernel: ACPI: CDIT 0x00000000DB4D9000 000029 (v01 AMD    AmdTable 00000001 AMD  00000001)
May 31 23:20:20 mainServerRyzen kernel: ACPI: BGRT 0x00000000DB4D8000 000038 (v01 ALASKA A M I    01072009 AMI  00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4D4000 0037DC (v02 AMD    ArticN   00000001 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: WSMT 0x00000000DB4D3000 000028 (v01 ALASKA A M I    01072009 AMI  00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: APIC 0x00000000DB4D2000 00015E (v04 ALASKA A M I    01072009 AMI  00010013)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4EC000 00007D (v02 AMD    ArticDIS 00000001 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4EA000 0010AF (v02 AMD    ArticC   00000001 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: SSDT 0x00000000DB4E9000 0000BF (v01 AMD    AmdTable 00001000 INTL 20120913)
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving FACP table memory at [mem 0xdb4ed000-0xdb4ed113]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving DSDT table memory at [mem 0xdb4ca000-0xdb4d121e]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving FACS table memory at [mem 0xdcbde000-0xdcbde03f]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4f3000-0xdb4fbce8]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4ef000-0xdb4f2b85]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4ee000-0xdb4ee220]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving FIDT table memory at [mem 0xdb4e5000-0xdb4e509b]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving MCFG table memory at [mem 0xdb4e4000-0xdb4e403b]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving HPET table memory at [mem 0xdb4e3000-0xdb4e3037]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving IVRS table memory at [mem 0xdb4e2000-0xdb4e20cf]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving FPDT table memory at [mem 0xdb4e1000-0xdb4e1043]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving PCCT table memory at [mem 0xdb4e0000-0xdb4e006d]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4db000-0xdb4df132]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving CRAT table memory at [mem 0xdb4da000-0xdb4daf0f]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving CDIT table memory at [mem 0xdb4d9000-0xdb4d9028]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving BGRT table memory at [mem 0xdb4d8000-0xdb4d8037]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4d4000-0xdb4d77db]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving WSMT table memory at [mem 0xdb4d3000-0xdb4d3027]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving APIC table memory at [mem 0xdb4d2000-0xdb4d215d]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4ec000-0xdb4ec07c]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4ea000-0xdb4eb0ae]
May 31 23:20:20 mainServerRyzen kernel: ACPI: Reserving SSDT table memory at [mem 0xdb4e9000-0xdb4e90be]
May 31 23:20:20 mainServerRyzen kernel: No NUMA configuration found
May 31 23:20:20 mainServerRyzen kernel: Faking a node at [mem 0x0000000000000000-0x000000101f37ffff]
May 31 23:20:20 mainServerRyzen kernel: NODE_DATA(0) allocated [mem 0x101f355000-0x101f37ffff]
May 31 23:20:20 mainServerRyzen kernel: Reserving 512MB of memory at 2800MB for crashkernel (System RAM: 65462MB)
May 31 23:20:20 mainServerRyzen kernel: Zone ranges:
May 31 23:20:20 mainServerRyzen kernel:  DMA      [mem 0x0000000000001000-0x0000000000ffffff]
May 31 23:20:20 mainServerRyzen kernel:  DMA32    [mem 0x0000000001000000-0x00000000ffffffff]

emphasized text

Check the dnf logs in ‘/var/log’. Look at the dates to confirm e.g. the most recent update.

Thank you Gerry. Appreciate it. Yes the whole list of updates for yesterday is in the dnf.log Thank you for your help.

I pulled the updates from the dnf.log (thanks gerry). I am not sure what broke the suspend/hibernation with this update. It was working perfectly until this update and now every time it goes to sleep, it restarts. Not sure which one broke it. The only other time sleep was broken with rocky was back when I updated to 8.5 from 8.4. That one got a patch in 2 weeks.

attached logs from yesterday’s update

2024-05-31T10:07:49-0500 DDEBUG Command: dnf upgrade --refresh 
2024-05-31T10:07:49-0500 DDEBUG Installroot: /
2024-05-31T10:07:49-0500 DDEBUG Releasever: 9
2024-05-31T10:07:49-0500 DEBUG cachedir: /var/cache/dnf
2024-05-31T10:07:49-0500 DDEBUG Base command: upgrade
2024-05-31T10:07:49-0500 DDEBUG Extra commands: ['upgrade', '--refresh']
2024-05-31T10:07:49-0500 DEBUG Unknown configuration option: autorefresh = 1 in /etc/yum.repos.d/brave-browser.repo
2024-05-31T10:07:49-0500 WARNING Repository vivaldi is listed more than once in the configuration
2024-05-31T10:07:49-0500 DEBUG User-Agent: constructed: 'libdnf (Rocky Linux 9.4; generic; Linux.x86_64)'
2024-05-31T10:07:49-0500 DEBUG reviving: 'brave-browser' can be revived - repomd matches.
2024-05-31T10:07:49-0500 DEBUG brave-browser: using metadata from Fri 24 May 2024 10:08:05 AM CDT.
2024-05-31T10:07:49-0500 DEBUG reviving: 'cuda-rhel9-x86_64' can be revived - repomd matches.
2024-05-31T10:07:49-0500 DEBUG cuda-rhel9-x86_64: using metadata from Wed 29 May 2024 02:09:59 PM CDT.
2024-05-31T10:07:49-0500 DEBUG countme: no event for epel: window already counted
2024-05-31T10:07:49-0500 DEBUG reviving: 'epel' can be revived - metalink checksums match.
2024-05-31T10:07:49-0500 DEBUG epel: using metadata from Thu 30 May 2024 08:04:03 PM CDT.
2024-05-31T10:07:49-0500 DEBUG reviving: 'epel-cisco-openh264' can be revived - metalink checksums match.
2024-05-31T10:07:49-0500 DEBUG epel-cisco-openh264: using metadata from Mon 22 May 2023 11:19:21 AM CDT.
2024-05-31T10:07:49-0500 DEBUG countme: no event for epel-next: window already counted
2024-05-31T10:07:49-0500 DEBUG reviving: 'epel-next' can be revived - metalink checksums match.
2024-05-31T10:07:49-0500 DEBUG epel-next: using metadata from Sat 25 May 2024 08:35:05 PM CDT.
2024-05-31T10:07:50-0500 DEBUG reviving: 'google-chrome' can be revived - repomd matches.
2024-05-31T10:07:50-0500 DEBUG google-chrome: using metadata from Thu 30 May 2024 03:59:08 PM CDT.
2024-05-31T10:07:50-0500 DEBUG reviving: 'microsoft-edge' can be revived - repomd matches.
2024-05-31T10:07:50-0500 DEBUG microsoft-edge: using metadata from Thu 30 May 2024 01:53:13 PM CDT.
2024-05-31T10:07:50-0500 DEBUG reviving: 'ookla_speedtest-cli' can be revived - repomd matches.
2024-05-31T10:07:50-0500 DEBUG ookla_speedtest-cli: using metadata from Wed 10 Aug 2022 03:10:35 PM CDT.
2024-05-31T10:07:51-0500 DEBUG reviving: 'ookla_speedtest-cli-source' can be revived - repomd matches.
2024-05-31T10:07:51-0500 DEBUG ookla_speedtest-cli-source: using metadata from Wed 31 Mar 2021 06:23:01 PM CDT.
2024-05-31T10:07:51-0500 DEBUG reviving: 'packages.microsoft.com_yumrepos_edge' can be revived - repomd matches.
2024-05-31T10:07:51-0500 DEBUG packages.microsoft.com_yumrepos_edge: using metadata from Thu 30 May 2024 01:53:13 PM CDT.
2024-05-31T10:07:51-0500 DEBUG countme: no event for baseos: window already counted
2024-05-31T10:07:51-0500 DEBUG reviving: 'baseos' can be revived - repomd matches.
2024-05-31T10:07:51-0500 DEBUG baseos: using metadata from Tue 28 May 2024 09:41:21 AM CDT.
2024-05-31T10:07:51-0500 DEBUG countme: no event for appstream: window already counted
2024-05-31T10:07:51-0500 DEBUG reviving: 'appstream' can be revived - repomd matches.
2024-05-31T10:07:51-0500 DEBUG appstream: using metadata from Tue 28 May 2024 09:41:43 AM CDT.
2024-05-31T10:07:51-0500 DEBUG countme: no event for crb: window already counted
2024-05-31T10:07:51-0500 DEBUG reviving: 'crb' can be revived - repomd matches.
2024-05-31T10:07:51-0500 DEBUG crb: using metadata from Tue 28 May 2024 09:42:19 AM CDT.
2024-05-31T10:07:51-0500 DEBUG countme: no event for extras: window already counted
2024-05-31T10:07:52-0500 DEBUG reviving: 'extras' can be revived - repomd matches.
2024-05-31T10:07:52-0500 DEBUG extras: using metadata from Fri 10 May 2024 09:45:43 AM CDT.
2024-05-31T10:07:52-0500 DEBUG reviving: 'rpmfusion-free-updates' can be revived - metalink checksums match.
2024-05-31T10:07:52-0500 DEBUG rpmfusion-free-updates: using metadata from Fri 24 May 2024 05:13:27 AM CDT.
2024-05-31T10:07:52-0500 DEBUG reviving: 'rpmfusion-nonfree-updates' can be revived - metalink checksums match.
2024-05-31T10:07:52-0500 DEBUG rpmfusion-nonfree-updates: using metadata from Fri 24 May 2024 05:20:24 AM CDT.
2024-05-31T10:07:52-0500 DEBUG reviving: failed for 'vivaldi', mismatched repomd.
2024-05-31T10:07:52-0500 DEBUG repo: downloading from remote: vivaldi
2024-05-31T10:07:53-0500 DEBUG vivaldi: using metadata from Fri 31 May 2024 08:42:41 AM CDT.
2024-05-31T10:07:54-0500 DEBUG reviving: 'vscode' can be revived - repomd matches.
2024-05-31T10:07:54-0500 DEBUG vscode: using metadata from Thu 30 May 2024 10:15:17 PM CDT.
2024-05-31T10:07:54-0500 DDEBUG timer: sack setup: 5526 ms
2024-05-31T10:07:54-0500 DEBUG Completion plugin: Generating completion cache...
2024-05-31T10:07:54-0500 DEBUG --> Starting dependency resolution
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-modules.x86_64 5.14.0-427.18.1.el9_4 will be installed
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-core.x86_64 5.14.0-427.18.1.el9_4 will be installed
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel.x86_64 5.14.0-427.18.1.el9_4 will be installed
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-modules-core.x86_64 5.14.0-427.18.1.el9_4 will be installed
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-devel.x86_64 5.14.0-427.18.1.el9_4 will be installed
2024-05-31T10:07:54-0500 DEBUG ---> Package brave-browser.x86_64 1.66.110-1 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package brave-browser.x86_64 1.66.115-1 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package cuda-drivers.x86_64 550.54.15-1 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package cuda-drivers.x86_64 555.42.02-1 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kmod-nvidia-latest-dkms.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package kmod-nvidia-latest-dkms.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-NVML.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-NVML.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-NvFBCOpenGL.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-NvFBCOpenGL.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-cuda.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-cuda.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-cuda-libs.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-cuda-libs.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-devel.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-devel.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-libs.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-driver-libs.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-kmod-common.noarch 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-kmod-common.noarch 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-libXNVCtrl.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-libXNVCtrl.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-libXNVCtrl-devel.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-libXNVCtrl-devel.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-modprobe.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-modprobe.x86_64 3:555.42.02-2.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-persistenced.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-persistenced.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-settings.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-settings.x86_64 3:555.42.02-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-xconfig.x86_64 3:550.54.15-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package nvidia-xconfig.x86_64 3:555.42.02-2.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package libaom.x86_64 3.8.2-1.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package libaom.x86_64 3.9.0-1.el9 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package google-chrome-stable.x86_64 125.0.6422.60-1 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package google-chrome-stable.x86_64 125.0.6422.141-1 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package microsoft-edge-stable.x86_64 125.0.2535.51-1 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package microsoft-edge-stable.x86_64 125.0.2535.79-1 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package python3-perf.x86_64 5.14.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package python3-perf.x86_64 5.14.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-tools-libs.x86_64 5.14.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-tools-libs.x86_64 5.14.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-tools.x86_64 5.14.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-tools.x86_64 5.14.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package bpftool.x86_64 7.3.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package bpftool.x86_64 7.3.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-langpack-en.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-langpack-en.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-gconv-extra.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-gconv-extra.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-common.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-common.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-all-langpacks.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-all-langpacks.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-headers.x86_64 5.14.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-headers.x86_64 5.14.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-devel-matched.x86_64 5.14.0-427.16.1.el9_4 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-devel-matched.x86_64 5.14.0-427.18.1.el9_4 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-headers.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-headers.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-devel.x86_64 2.34-100.el9 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package glibc-devel.x86_64 2.34-100.el9_4.2 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package vivaldi-stable.x86_64 6.7.3329.31-1 will be upgraded
2024-05-31T10:07:54-0500 DEBUG ---> Package vivaldi-stable.x86_64 6.7.3329.39-1 will be an upgrade
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel.x86_64 5.14.0-362.24.1.el9_3 will be erased
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-core.x86_64 5.14.0-362.24.1.el9_3 will be erased
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-devel.x86_64 5.14.0-362.24.1.el9_3 will be erased
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-modules.x86_64 5.14.0-362.24.1.el9_3 will be erased
2024-05-31T10:07:54-0500 DEBUG ---> Package kernel-modules-core.x86_64 5.14.0-362.24.1.el9_3 will be erased
2024-05-31T10:07:54-0500 DEBUG --> Finished dependency resolution
2024-05-31T10:07:54-0500 DDEBUG timer: depsolve: 34 ms
2024-05-31T10:07:54-0500 INFO Dependencies resolved.
2024-05-31T10:07:54-0500 INFO ============================================================================================================================
==============================
 Package                                     Architecture             Version                                   Repository                           Size
==========================================================================================================================================================
Installing:
 kernel                                      x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
     5.6 M
 kernel-core                                 x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
      20 M
 kernel-devel                                x86_64                   5.14.0-427.18.1.el9_4                     appstream                      
      21 M
 kernel-modules                              x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
      39 M
 kernel-modules-core                         x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
      33 M
Upgrading:
 bpftool                                     x86_64                   7.3.0-427.18.1.el9_4                      baseos                         
     6.4 M
 brave-browser                               x86_64                   1.66.115-1                                brave-browser                  
     115 M
 cuda-drivers                                x86_64                   555.42.02-1                               cuda-rhel9-x86_64              
     8.1 k
 glibc                                       x86_64                   2.34-100.el9_4.2                          baseos                         
     2.0 M
 glibc-all-langpacks                         x86_64                   2.34-100.el9_4.2                          baseos                         
      18 M
 glibc-common                                x86_64                   2.34-100.el9_4.2                          baseos                         
     301 k
 glibc-devel                                 x86_64                   2.34-100.el9_4.2                          appstream                      
      36 k
 glibc-gconv-extra                           x86_64                   2.34-100.el9_4.2                          baseos                         
     1.6 M
 glibc-headers                               x86_64                   2.34-100.el9_4.2                          appstream                      
     440 k
 glibc-langpack-en                           x86_64                   2.34-100.el9_4.2                          baseos                         
     557 k
 google-chrome-stable                        x86_64                   125.0.6422.141-1                          google-chrome                  
     106 M
 kernel-devel-matched                        x86_64                   5.14.0-427.18.1.el9_4                     appstream                      
     5.6 M
 kernel-headers                              x86_64                   5.14.0-427.18.1.el9_4                     appstream                      
     7.1 M
 kernel-tools                                x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
     5.9 M
 kernel-tools-libs                           x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
     5.6 M
 kmod-nvidia-latest-dkms                     x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      40 M
 libaom                                      x86_64                   3.9.0-1.el9                               epel                           
     1.8 M
 microsoft-edge-stable                       x86_64                   125.0.2535.79-1                           microsoft-edge                 
     162 M
 nvidia-driver                               x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     126 M
 nvidia-driver-NVML                          x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     606 k
 nvidia-driver-NvFBCOpenGL                   x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      77 k
 nvidia-driver-cuda                          x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     531 k
 nvidia-driver-cuda-libs                     x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      50 M
 nvidia-driver-devel                         x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     9.6 k
 nvidia-driver-libs                          x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     136 M
 nvidia-kmod-common                          noarch                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      12 k
 nvidia-libXNVCtrl                           x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      24 k
 nvidia-libXNVCtrl-devel                     x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      51 k
 nvidia-modprobe                             x86_64                   3:555.42.02-2.el9                         cuda-rhel9-x86_64              
      29 k
 nvidia-persistenced                         x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
      34 k
 nvidia-settings                             x86_64                   3:555.42.02-1.el9                         cuda-rhel9-x86_64              
     848 k
 nvidia-xconfig                              x86_64                   3:555.42.02-2.el9                         cuda-rhel9-x86_64              
      95 k
 python3-perf                                x86_64                   5.14.0-427.18.1.el9_4                     baseos                         
     5.7 M
 vivaldi-stable                              x86_64                   6.7.3329.39-1                             vivaldi                        
     104 M
Removing:
 kernel                                      x86_64                   5.14.0-362.24.1.el9_3                     @baseos                           
    0  
 kernel-core                                 x86_64                   5.14.0-362.24.1.el9_3                     @baseos                           
   63 M
 kernel-devel                                x86_64                   5.14.0-362.24.1.el9_3                     @appstream                        
   64 M
 kernel-modules                              x86_64                   5.14.0-362.24.1.el9_3                     @baseos                           
   31 M
 kernel-modules-core                         x86_64                   5.14.0-362.24.1.el9_3                     @baseos                           
   26 M

Transaction Summary
==========================================================================================================================================================
Install   5 Packages
Upgrade  34 Packages
Remove    5 Packages

2024-05-31T10:07:54-0500 INFO Total download size: 1.0 G
2024-05-31T10:07:57-0500 INFO Downloading Packages:
2024-05-31T10:08:09-0500 INFO ----------------------------------------------------------------------------------------------------------------------------
------------------------------
2024-05-31T10:08:09-0500 INFO Total

How much ram does the server have? How much swap space configured? I’ve had problems in the past, albeit with laptops rather than servers because not enough swap was configured. I got it to work by ensuring that my swap was double the ram, eg: if I had 16GB ram, I configured 32GB of swap.

I’m a bit confused about the original post.

I don’t really know what “suspend” and “sleep” means (disambiguate). Then of course there’s “hybernate”.

Those terms make sense for a laptop, but you say it’s a server.

Surely you don’t press the power button on a real server?

Can you clarify what the terms actually mean, and is there a way to trigger those operations using the command line (might help with logs, messages etc).

I notice the kernel is one above the original Rocky 9.4, did you try booting into an older kernel using grub?

Thanks Ian. I have plenty of RAM and swap space. I have 64gb RAM and about 15gb of swap space. I have about 5-6 VMs running at certain parts of the day but even then the memory usage is about 15+ gb and pretty stable at that and I have not seen it use any swap space yet even with the VMs running and db servers are running on those VMs. Other than that, I do development and may have about 3-4 instances of the browsers with about 6-8 tabs in each of the browser instance. I would say with all of that running simultaneously, I rarely see the free memory dip below 45gb and swap still unused.

[root@mainServerRyzen ~]# free -m
total used free shared buff/cache available
Mem: 63711 3476 59042 72 1877 60235
Swap: 15359 0 15359

Thanks Gerry. Well, “suspend” in gnome is what I keep referring to sleep and where I have set the bios to wake the system up only if I press the power button. So, I guess the sleep is referred to S3 sleep state (cpu idle, display off, kb/mouse not functional etc., unless I press the power button and gnome puts me back at the login screen). Its definitely not hibernate. So, I have to press the power button to get it out of that sleep state (or suspend). I use suspend and sleep interchangeably but I am referring to the same thing which is the “auto suspend” under power settings in gnome. I have not switched back to the older version (one before the current one yet). I will try that out this evening and update tomorrow. When you say the original 9.4, are you referring to .427.16.1. as the original? I will switch to that one and try it out. I have only two 9.4 kernels right now. The 16.1 and the current one that is running 18.1. Thank you for your time.

If your ram usage is more than 15gb (current swap space) then it won’t suspend. You would need to have at least 64gb swap if not more.

Well, it was doing just fine with that swap space. I guess the real usage could have been less than 15gb but sleep was just fine before the updates I made a couple of days ago. After it went to sleep, I was able to bring it up by pressing the power button and it did it just fine. I had set my idle time at 30 mins and did not see any issue prior to the update. Something changed with the updates of a couple days.

Forgot to mention: I switched to the original kernel .427.16.1 and it goes to sleep after 30 mins of idle time.

Checked out. Went back to the previous kernel .427.16.1 and it successfully went to sleep after 30 mins of idle. .427.18.1 is the problem or could be any of the other updates that may or may not include the kernel.

You could try doing an lsmod by booting the new and previous kernel to see if there are any difference in loaded modules. Could well be some change in the kernel though that has caused it, just no idea what would do that tbh.

Yes, I pointed out that you were “one above” the official 9.4 release. I wasn’t sure it was relevant at the time. Can’t see anything obvious in the changelog that would affect power settings. This type of problem is hard to pin down because it might only affect certain hardware with certain BIOS versions and settings.

It would be good to let the kernel guys know something changed, but we can’t prove where the issue lies.

Can you list each setting on the page “Gnome Settings : Power”.

The way you describe your power button is the opposite of how mine works. On my workstation, I have to press the power button to suspend, and have to press a key to wake up. It’s even more confusing that you have a BIOS setting telling it to use the power button to wake up.

My understanding of “sleep” is when the o/s is still running, but the screen goes black and some devices go into low power mode. My understanding of “suspend” is where the memory gets paged out to disk and then the o/s stops running, cpu fan goes off, but the power supply is still providing a tiny amount of power which can detect a key press and resume.