No login screen on wake from sleep after recent updates

Hello.

Since some recent updates ~3 days ago system has been unable to successfully wake from sleep. Each time system wake up from sleep I see a blank screen, its not dark, its just plain dark gray which means there is some input to monitor. I cannot even switch to tty using Ctrl+Alt+F3 or F2, which probably means the wake is not complete. So I end up hard rebooting the system each time this happens :cry: :cry: loosing all state and context of my work :cry:

I tried to look at dmesg but I only see messages from last boot not from when system was waking up.

FYI, I am a linux n00b, familiar with shell scripting and can follow instructions to diagnose the issue. So please help.

here is the garuda-inxi output

System:
  Kernel: 5.17.5-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=fbe68766-ca23-4bdd-9231-47009af87162 rw [email protected]
    cryptdevice=UUID=ec233d36-2eb5-4b54-a5f8-8db36ac50d51:luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
    root=/dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51 splash
    rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1
    resume=/dev/mapper/luks-d43f10c3-86bd-4231-a617-32e2520205fd loglevel=3
  Desktop: GNOME v: 42.0 tk: GTK v: 3.24.33 wm: gnome-shell dm: GDM v: 42.0
    Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: TRX40 AORUS MASTER v: -CF
    serial: <superuser required>
  Mobo: Gigabyte model: TRX40 AORUS MASTER serial: <superuser required>
    UEFI: American Megatrends LLC. v: FC date: 11/23/2021
CPU:
  Info: model: AMD Ryzen Threadripper 3970X bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x31 (49) stepping: 0 microcode: 0x8301055
  Topology: cpus: 1x cores: 32 tpc: 2 threads: 64 smt: enabled cache:
    L1: 2 MiB desc: d-32x32 KiB; i-32x32 KiB L2: 16 MiB desc: 32x512 KiB
    L3: 128 MiB desc: 8x16 MiB
  Speed (MHz): avg: 3803 high: 4371 min/max: 2200/4549 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3582 2: 3482
    3: 3243 4: 3710 5: 3821 6: 3481 7: 3864 8: 4102 9: 3690 10: 4083 11: 3978
    12: 4349 13: 3563 14: 4349 15: 4366 16: 4001 17: 3538 18: 3578 19: 3551
    20: 3570 21: 3569 22: 3494 23: 4368 24: 3717 25: 4346 26: 3620 27: 3759
    28: 3807 29: 3486 30: 3715 31: 3819 32: 3497 33: 3484 34: 3354 35: 3482
    36: 4366 37: 4349 38: 3546 39: 4126 40: 3700 41: 3627 42: 4201 43: 3931
    44: 3958 45: 4134 46: 3770 47: 4306 48: 4074 49: 3596 50: 3602 51: 3548
    52: 3528 53: 3461 54: 3585 55: 3788 56: 3728 57: 4371 58: 3717 59: 3655
    60: 4364 61: 3440 62: 3628 63: 4349 64: 3566 bogomips: 473802
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2
    mitigation: Retpolines, IBPB: conditional, STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia
    v: 510.68.02 alternate: nouveau,nvidia_drm pcie: gen: 3 speed: 8 GT/s
    lanes: 8 link-max: lanes: 16 bus-ID: 02:00.0 chip-ID: 10de:1c82
    class-ID: 0300
  Device-2: Logitech C920 HD Pro Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: 046d:0892
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.1
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: nvidia
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x572mm (40.00x22.52")
    s-diag: 1166mm (45.9")
  Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 140
    size: 697x392mm (27.44x15.43") diag: 800mm (31.48") modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 8
    link-max: lanes: 16 bus-ID: 02:00.1 chip-ID: 10de:0fb9 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 22:00.4 chip-ID: 1022:1487
    class-ID: 0403
  Device-3: Logitech C920 HD Pro Webcam type: USB
    driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: 046d:0892
    class-ID: 0102 serial: <filter>
  Device-4: Giga-Byte USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-6:6 chip-ID: 0414:a000
    class-ID: 0300
  Device-5: Giga-Byte USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-5:3 chip-ID: 0414:a001
    class-ID: 0300
  Sound Server-1: ALSA v: k5.17.5-arch1-1 running: yes
  Sound Server-2: PulseAudio v: 15.0 running: no
  Sound Server-3: PipeWire v: 0.3.51 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 9000 bus-ID: 44:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp68s0 state: down mac: <filter>
  Device-2: Aquantia AQC111 NBase-T/IEEE 802.3bz Ethernet [AQtion]
    vendor: Gigabyte driver: atlantic v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 1 port: N/A bus-ID: 45:00.0 chip-ID: 1d6a:11b1 class-ID: 0200
  IF: enp69s0 state: down mac: <filter>
  Device-3: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 46:00.0 chip-ID: 8086:2723 class-ID: 0280
  IF: wlo2 state: up mac: <filter>
  Device-4: Realtek RTL8153 Gigabit Ethernet Adapter type: USB
    driver: r8152 bus-ID: 6-3.1:3 chip-ID: 0bda:8153 class-ID: 0000
    serial: <filter>
  IF: enp71s0f1u3u1 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 5-4.1:8 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 3.92 TiB used: 391.28 GiB (9.7%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 43.9 C scheme: MBR
  ID-2: /dev/nvme1n1 maj-min: 259:3 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3B2QEXM7 temp: 40.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Seagate
    model: Ultra Slim MT size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B type: N/A serial: <filter> rev: 0304 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 type: USB vendor: PQI model: Traveling Disk
    size: 984 MiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: 0.00 scheme: GPT
  ID-5: /dev/sde maj-min: 8:64 type: USB vendor: SanDisk
    model: Cruzer Glide 3.0 size: 233.25 GiB block-size: physical: 512 B
    logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: GPT
  ID-6: /dev/sdf maj-min: 8:80 type: USB vendor: PNY model: DUO LINK Type-C
    size: 57.8 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: PMAP scheme: MBR
Partition:
  ID-1: / raw-size: 315.27 GiB size: 315.27 GiB (100.00%)
    used: 82 GiB (26.0%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
    used: 720 KiB (0.1%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
  ID-3: /home raw-size: 546.87 GiB size: 546.87 GiB (100.00%)
    used: 203.23 GiB (37.2%) fs: btrfs dev: /dev/dm-2 maj-min: 254:2
    mapped: luks-7dba079f-5147-443c-9093-19db969dcc49
  ID-4: /var/log raw-size: 315.27 GiB size: 315.27 GiB (100.00%)
    used: 82 GiB (26.0%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
  ID-5: /var/tmp raw-size: 315.27 GiB size: 315.27 GiB (100.00%)
    used: 82 GiB (26.0%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 62.71 GiB used: 1.2 MiB (0.0%)
    priority: 100 dev: /dev/zram0
  ID-2: swap-2 type: partition size: 68.36 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 254:1
    mapped: luks-d43f10c3-86bd-4231-a617-32e2520205fd
Sensors:
  System Temperatures: cpu: 16.8 C mobo: N/A gpu: nvidia temp: 42 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30%
Info:
  Processes: 983 Uptime: 38m wakeups: 0 Memory: 62.71 GiB
  used: 9.57 GiB (15.3%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.2.0 clang: 13.0.1 Packages: 1947 pacman: 1928 lib: 432 flatpak: 19
  Shell: Zsh v: 5.8.1 running-in: terminator inxi: 3.3.15
Garuda (2.6.2-1):
  System install date:     2021-10-02
  Last full system update: 2022-05-04
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Timeshift (maybe)
  Failed units:            shadow.service systemd-guest-user.service 

2 Likes

Welcome to the Forums!

What is the output of say

journalctl -r -b -1?

Assuming you boot ONCE since the gray screen. If you booted twice, change the above number to 2 and so on depending on your number of reboots since.

EDIT: You can also take a look at this Troubleshooting System Stutter, Lags, Freezes, and Hangs

There is more than you need in there but hopefully a couple of tips on where and how to troubleshoot, althought it's not a freeze or hang, it's still close enough.

4 Likes

Another thing you could do (but I agree you should start from the journal), if you remember the day this issue started, could be to check the pacman log to see waht was installed/updated.
Normally I use something like:

cat /var/log/pacman.log | grep '2022-05-02' | egrep 'installed|upgraded|removed'

I'm afraid that your current nvidia driver version might have arrived there, and I'd not be able to suggest anything in that case.
In case you upgraded the kernel (but this was last updated a few days earlier), you could consider trying the linux-lts kernel.

4 Likes

@FGD I tried the following command without the -b option

May 05 08:09:28 big-machine kernel: SMBIOS 3.3.0 present.
May 05 08:09:28 big-machine kernel: efi: ACPI=0x9a06d000 ACPI 2.0=0x9a06d014 TPMFinalLog=0x9a032000 SMBIOS=0x9ae59000 SMBIOS 3.0=0x9ae58000 MEMATTR=0x91b39018 ESRT=0x96240698 
May 05 08:09:28 big-machine kernel: efi: EFI v2.70 by American Megatrends
May 05 08:09:28 big-machine kernel: NX (Execute Disable) protection: active
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000069730000000-0x00000697403fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000003cbb0000000-0x000003cbc03fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000003cb80000000-0x000003cb903fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000010000000000-0x00000100103fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000105f200000-0x000000105fffffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000100000000-0x000000105f1fffff] usable
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000feefffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fedd4000-0x00000000fedd5fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fedc2000-0x00000000fedcffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000fea00000-0x00000000feafffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000ab100000-0x00000000ab280fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000aa300000-0x00000000aa3fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000aa180000-0x00000000aa200fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000a3580000-0x00000000a3600fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000a2500000-0x00000000a2580fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000009c000000-0x000000009fffffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000009afff000-0x000000009bffffff] usable
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000009af72000-0x000000009affefff] type 20
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000009a085000-0x000000009af71fff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000099981000-0x000000009a084fff] ACPI NVS
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000009991c000-0x0000000099980fff] ACPI data
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000982c4000-0x000000009991bfff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000000a000000-0x00000000982c3fff] usable
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000009df2000-0x0000000009ffffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x000000000400d000-0x0000000009df1fff] usable
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000004000000-0x000000000400cfff] ACPI NVS
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000003ffffff] usable
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
May 05 08:09:28 big-machine kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
May 05 08:09:28 big-machine kernel: BIOS-provided physical RAM map:
May 05 08:09:28 big-machine kernel: signal: max sigframe size: 1776
May 05 08:09:28 big-machine kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
May 05 08:09:28 big-machine kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 05 08:09:28 big-machine kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 05 08:09:28 big-machine kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 05 08:09:28 big-machine kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 05 08:09:28 big-machine kernel: Command line: BOOT_IMAGE=/@/boot/vmlinuz-linux root=UUID=fbe68766-ca23-4bdd-9231-47009af87162 rw [email protected] cryptdevice=UUID=ec233d36-2eb5-4b54-a5f8-8db36ac50d51:luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51 root=/dev/mapper/luks-ec233d36-2eb5-4b54-a5f8-8db36ac50d51 splash rd.udev.log_priority=3 vt.global_cursor_default=0 systemd.unified_cgroup_hierarchy=1 resume=/dev/mapper/luks->
May 05 08:09:28 big-machine kernel: Linux version 5.17.5-arch1-1 ([email protected]) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Wed, 27 Apr 2022 20:56:11 +0000
-- Boot 3b6e64f092324e06a7e3302f90d41f74 --
May 04 19:28:26 big-machine wpa_supplicant[2881]: wlo2: CTRL-EVENT-DSCP-POLICY clear_all
May 04 19:28:26 big-machine /usr/lib/gdm-x-session[1591]: (**) Option "fd" "43"
May 04 19:28:26 big-machine /usr/lib/gdm-x-session[1591]: (II) event1  - Power Button: device removed
May 04 19:28:26 big-machine /usr/lib/gdm-x-session[1591]: (**) Option "fd" "40"
May 04 19:28:26 big-machine gsd-media-keys[6633]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
May 04 19:28:26 big-machine kernel: Filesystems sync: 0.043 seconds
May 04 19:28:26 big-machine wpa_supplicant[2881]: wlo2: CTRL-EVENT-DSCP-POLICY clear_all
May 04 19:28:26 big-machine kernel: PM: suspend entry (deep)
May 04 19:28:26 big-machine systemd-sleep[3698245]: Entering sleep state 'suspend'...
May 04 19:28:26 big-machine systemd[1]: Starting System Suspend...
May 04 19:28:26 big-machine wpa_supplicant[2881]: nl80211: deinit ifname=p2p-dev-wlo2 disabled_11b_rates=0
May 04 19:28:26 big-machine wpa_supplicant[2881]: p2p-dev-wlo2: CTRL-EVENT-DSCP-POLICY clear_all
May 04 19:28:26 big-machine wpa_supplicant[2881]: p2p-dev-wlo2: CTRL-EVENT-DSCP-POLICY clear_all
May 04 19:28:26 big-machine wpa_supplicant[2881]: wlo2: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
May 04 19:28:26 big-machine gnome-calendar[6747]: Failed to measure available space: Error resolving “sam.nl.tab.digital”: Name or service not known
May 04 19:28:26 big-machine systemd[1]: Reached target Sleep.
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5314] device (wlo2): set-hw-addr: reset MAC address to 34:C9:3D:01:06:A3 (unmanage)
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5273] device (wlo2): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5270] device (wlo2): supplicant interface state: completed -> disconnected
May 04 19:28:26 big-machine avahi-daemon[1420]: Interface wlo2.IPv4 no longer relevant for mDNS.
May 04 19:28:26 big-machine avahi-daemon[1420]: Leaving mDNS multicast group on interface wlo2.IPv4 with address 192.168.1.124.
May 04 19:28:26 big-machine avahi-daemon[1420]: Withdrawing address record for 192.168.1.124 on wlo2.
May 04 19:28:26 big-machine avahi-daemon[1420]: Registering new address record for 192.168.1.124 on wlo2.IPv4.
May 04 19:28:26 big-machine avahi-daemon[1420]: New relevant interface wlo2.IPv4 for mDNS.
May 04 19:28:26 big-machine avahi-daemon[1420]: Joining mDNS multicast group on interface wlo2.IPv4 with address 192.168.1.124.
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5242] device (wlo2): set-hw-addr: set MAC address to CA:2D:85:F9:08:ED (scanning)
May 04 19:28:26 big-machine avahi-daemon[1420]: Withdrawing address record for 192.168.1.124 on wlo2.
May 04 19:28:26 big-machine avahi-daemon[1420]: Leaving mDNS multicast group on interface wlo2.IPv4 with address 192.168.1.124.
May 04 19:28:26 big-machine avahi-daemon[1420]: Interface wlo2.IPv4 no longer relevant for mDNS.
May 04 19:28:26 big-machine gnome-shell[5969]: An active wireless connection, in infrastructure mode, involves no access point?
May 04 19:28:26 big-machine gnome-shell[5969]: An active wireless connection, in infrastructure mode, involves no access point?
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5211] dhcp4 (wlo2): state changed no lease
May 04 19:28:26 big-machine avahi-daemon[1420]: Interface wlo2.IPv6 no longer relevant for mDNS.
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5210] dhcp4 (wlo2): activation: beginning transaction (timeout in 45 seconds)
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5210] dhcp4 (wlo2): canceled DHCP transaction
May 04 19:28:26 big-machine avahi-daemon[1420]: Leaving mDNS multicast group on interface wlo2.IPv6 with address fe80::6ce8:5ca4:7c3:198.
May 04 19:28:26 big-machine avahi-daemon[1420]: Withdrawing address record for fe80::6ce8:5ca4:7c3:198 on wlo2.
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.5201] device (wlo2): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 04 19:28:26 big-machine wpa_supplicant[2881]: wlo2: CTRL-EVENT-DSCP-POLICY clear_all
May 04 19:28:26 big-machine wpa_supplicant[2881]: wlo2: CTRL-EVENT-DISCONNECTED bssid=28:80:88:36:d3:28 reason=3 locally_generated=1
May 04 19:28:26 big-machine kernel: wlo2: deauthenticating from 28:80:88:36:d3:28 by local choice (Reason: 3=DEAUTH_LEAVING)
May 04 19:28:26 big-machine kernel: audit: type=1130 audit(1651710506.329:500): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 04 19:28:26 big-machine audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 04 19:28:26 big-machine systemd[1]: Started Network Manager Script Dispatcher Service.
May 04 19:28:26 big-machine dbus-daemon[1427]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 04 19:28:26 big-machine systemd[1]: Starting Network Manager Script Dispatcher Service...
May 04 19:28:26 big-machine dbus-daemon[1427]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.6' (uid=0 pid=1452 comm="/usr/bin/NetworkManager --no-daemon")
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.2683] device (wlo2): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.2682] manager: NetworkManager state is now ASLEEP
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.2680] device (38:E3:9F:98:F3:A5): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 04 19:28:26 big-machine NetworkManager[1452]: <info>  [1651710506.2678] device (p2p-dev-wlo2): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')

as you can see on May 05 08:09:28 the reboot

big-machine kernel: Linux version 5.17.5-arch1-1 ([email protected]) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Wed, 27 Apr 2022 20:56:11 +0000
-- Boot 3b6e64f092324e06a7e3302f90d41f74 --

so it would seem that there was no entry in the journal upon wake from sleep today morning around 08:06. Any idea why ?

here is the output in gist of the journalctl -r -b -1 command

@filo you were right the Nvidia driver did get upgraded recently

11:24AM ~ ➤ cat /var/log/pacman.log | grep '2022-05-02' | egrep 'installed|upgraded|removed' | ag -i nvidia                                                                                                                                                                                                                                                                                                                            
[2022-05-02T23:52:21-0500] [ALPM] upgraded nvidia-utils (510.60.02-1 -> 510.68.02-1)
[2022-05-02T23:52:25-0500] [ALPM] upgraded nvidia (510.60.02-16 -> 510.68.02-1)
[2022-05-02T23:52:25-0500] [ALPM] upgraded nvidia-settings (510.60.02-1 -> 510.68.02-1)
[2022-05-02T23:52:26-0500] [ALPM] upgraded opencl-nvidia (510.60.02-1 -> 510.68.02-1)
11:24AM ~ ➤                                                                                   

Can I downgrade it ? if yes, how ?

You can. But it's very very risky.
You could use e g. the downgrade package, see
https://wiki.archlinux.org/title/Downgrading_packages#Automation
If you really can't stay without suspend for some time, I'd rather first try with a different kernel.
You could even restore a snapshot before and put the Nvidia packages on hold in pacman conf.
Or try downgrading... :wink:

3 Likes

Thanks, I won't downgrade Nvidia since its risky. Though I tried the LTS kernel 5.17.37 but the system would never finish booting i.e. did not show the Gnome login prompt here is the journalctl output in which the highlight is May 05 12:58:14 big-machine gdm[1400]: Gdm: GdmDisplay: Session never registered, failing

May 05 12:58:15 big-machine audit[20227]: USER_AUTH pid=20227 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:15 big-machine systemd-logind[1359]: Removed session 358.
May 05 12:58:15 big-machine systemd-logind[1359]: Session 358 logged out. Waiting for processes to exit.
May 05 12:58:15 big-machine systemd[1]: session-358.scope: Deactivated successfully.
May 05 12:58:15 big-machine gdm[1400]: Gdm: GdmDisplay: Session never registered, failing
May 05 12:58:15 big-machine audit[20214]: CRED_DISP pid=20214 uid=0 auid=1000 ses=358 msg='op=PAM:setcred grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine audit[20214]: USER_END pid=20214 uid=0 auid=1000 ses=358 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine gdm-autologin][20214]: pam_unix(gdm-autologin:session): session closed for user daya
May 05 12:58:15 big-machine ananicy-cpp[1338]: [2022-05-05 12:58:15.158] [info] Xorg(20225)
May 05 12:58:15 big-machine audit[20214]: USER_START pid=20214 uid=0 auid=1000 ses=358 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine gdm-autologin][20214]: gkr-pam: gnome-keyring-daemon started properly
May 05 12:58:15 big-machine gdm-autologin][20214]: pam_env(gdm-autologin:session): deprecated reading of user environment enabled
May 05 12:58:15 big-machine systemd[1]: Started Session 358 of User daya.
May 05 12:58:15 big-machine systemd-logind[1359]: New session 358 of user daya.
May 05 12:58:15 big-machine gdm-autologin][20214]: pam_unix(gdm-autologin:session): session opened for user daya(uid=1000) by (uid=0)
May 05 12:58:15 big-machine audit: PROCTITLE proctitle=67646D2D73657373696F6E2D776F726B6572205B70616D2F67646D2D6175746F6C6F67696E5D
May 05 12:58:15 big-machine audit[20214]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=a a1=7fffe59e96c0 a2=4 a3=0 items=0 ppid=1400 pid=20214 auid=1000 uid=0 gid=1001 euid=0 suid=0 fsuid=0 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=358 comm="gdm-session-wor" exe="/usr/lib/gdm-session-worker" key=(null)
May 05 12:58:15 big-machine audit[20214]: CRED_ACQ pid=20214 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:15 big-machine audit[20214]: USER_ACCT pid=20214 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:15 big-machine gdm-autologin][20214]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 05 12:58:15 big-machine dbus-daemon[1343]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
May 05 12:58:15 big-machine dbus-daemon[1343]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.1802' (uid=0 pid=20214 comm="gdm-session-worker [pam/gdm-autologin]")
May 05 12:58:15 big-machine audit[20214]: USER_AUTH pid=20214 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:15 big-machine systemd-logind[1359]: Removed session 357.
May 05 12:58:15 big-machine systemd-logind[1359]: Session 357 logged out. Waiting for processes to exit.
May 05 12:58:15 big-machine systemd[1]: session-357.scope: Deactivated successfully.
May 05 12:58:15 big-machine gdm[1400]: Gdm: GdmDisplay: Session never registered, failing
May 05 12:58:15 big-machine audit[20201]: CRED_DISP pid=20201 uid=0 auid=1000 ses=357 msg='op=PAM:setcred grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine audit[20201]: USER_END pid=20201 uid=0 auid=1000 ses=357 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine gdm-autologin][20201]: pam_unix(gdm-autologin:session): session closed for user daya
May 05 12:58:15 big-machine ananicy-cpp[1338]: [2022-05-05 12:58:15.012] [info] Xorg(20212)
May 05 12:58:14 big-machine audit[20201]: USER_START pid=20201 uid=0 auid=1000 ses=357 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:15 big-machine gdm-autologin][20201]: gkr-pam: gnome-keyring-daemon started properly
May 05 12:58:14 big-machine gdm-autologin][20201]: pam_env(gdm-autologin:session): deprecated reading of user environment enabled
May 05 12:58:14 big-machine systemd[1]: Started Session 357 of User daya.
May 05 12:58:14 big-machine systemd-logind[1359]: New session 357 of user daya.
May 05 12:58:14 big-machine gdm-autologin][20201]: pam_unix(gdm-autologin:session): session opened for user daya(uid=1000) by (uid=0)
May 05 12:58:14 big-machine audit: PROCTITLE proctitle=67646D2D73657373696F6E2D776F726B6572205B70616D2F67646D2D6175746F6C6F67696E5D
May 05 12:58:14 big-machine audit[20201]: SYSCALL arch=c000003e syscall=1 success=yes exit=4 a0=a a1=7ffdfcd674d0 a2=4 a3=0 items=0 ppid=1400 pid=20201 auid=1000 uid=0 gid=1001 euid=0 suid=0 fsuid=0 egid=1001 sgid=1001 fsgid=1001 tty=(none) ses=357 comm="gdm-session-wor" exe="/usr/lib/gdm-session-worker" key=(null)
May 05 12:58:14 big-machine audit[20201]: CRED_ACQ pid=20201 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:14 big-machine audit[20201]: USER_ACCT pid=20201 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:14 big-machine gdm-autologin][20201]: pam_systemd_home(gdm-autologin:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
May 05 12:58:14 big-machine dbus-daemon[1343]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.home1.service': Unit dbus-org.freedesktop.home1.service not found.
May 05 12:58:14 big-machine dbus-daemon[1343]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.1797' (uid=0 pid=20201 comm="gdm-session-worker [pam/gdm-autologin]")
May 05 12:58:14 big-machine audit[20201]: USER_AUTH pid=20201 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty1 res=success'
May 05 12:58:14 big-machine systemd-logind[1359]: Removed session 356.
May 05 12:58:14 big-machine systemd-logind[1359]: Session 356 logged out. Waiting for processes to exit.
May 05 12:58:14 big-machine systemd[1]: session-356.scope: Deactivated successfully.
May 05 12:58:14 big-machine gdm[1400]: Gdm: GdmDisplay: Session never registered, failing
May 05 12:58:14 big-machine audit[20188]: CRED_DISP pid=20188 uid=0 auid=1000 ses=356 msg='op=PAM:setcred grantors=pam_shells,pam_permit acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'
May 05 12:58:14 big-machine audit[20188]: USER_END pid=20188 uid=0 auid=1000 ses=356 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam_systemd_home,pam_limits,pam_unix,pam_permit,pam_mail,pam_systemd,pam_env,pam_gnome_keyring acct="daya" exe="/usr/lib/gdm-session-worker" hostname=big-machine addr=? terminal=/dev/tty2 res=success'

It's not that I can't live without Suspend/Sleep functionality working properly but its very annoying to keep the computer ON even when you are not using it say when you goto sleep.

Any suggestions on how I can fix this suspend problem? or how to fix the LTS kernel Gdm: GdmDisplay: Session never registered, failing ?

Try the linux-mainline kernel if you haven't tested it yet. It may be your best bet.

2 Likes

Couple of other ideas:

After following TBG's suggestion, if it still doesn't work, try disabling some features, like Networking and Bluetooth, but you can find more. Then go to sleep (not you! your machine) and wake it up. See if any changes.

Those issues are sometimes tricky to put your finger on what is causing it and you have to go by process elimination, especially when the logs don't talk much.

If you could find a way to go back to older NVIDIA driver without changing anything else, you could see if it's the driver or not. You could take a snapshot of your current system, boot into it, downgrade your nv driver and test it from the snapshot. I do stuff like that very often, but I'm not using Snapper or any software, so I can't say how risky that is with the default Garuda setup! Disclaimer here.
Can someone plz confirm if my idea would be risky with Garuda's default snapshot setup?

If you succeed in putting the finger on what is causing this, then it would be a lot easier to Google for a fix.

2 Likes

IIUC your logs, you probably use autologin. Is this correct?
You may try either disabling autologin, or replacing gdm with sddm (or lightdm), or both.

2 Likes

IMO the video driver is far more likely to be causing this rather than network components.

The rest of @FGD 's suggestions seem like very good methods to test out.

I would also search your mobo model online to see if you can find any kernel parameters known to help with sleep issues.

You could also test disabling the compositor as it can cause this issue.

2 Likes

I disabled auto-login but still got no login prompt with gdm. Then I installed lightdm first and tried to start it but after eabling lightdm.service still no luck even with startx command then installed sddm, uninstalled gdm and lightdm. Rebooted into mainline kernel but no prompt, not even a tty shell, then rebooted into 5.17.5-arch1-1 kernel this time got login prompt for sddm but nothing after that. Then from tty I did startx to write this message.

Not sure if this will fix the suspend issue but I am not sure how to proceed. As the current state is much worse than before. Hoping to see the light soon :pray:

Now you describe a really badly broken system, on which wake up from suspend seems the least of the problems. :face_with_head_bandage:
Check your pacman log to see what you have done (uninstalled important packages, failed update, etc) and try to undo/repair whatever.

Now this makes more sense. :point_up:

Update: I tried with lightdm after reboot I was able to login just fine but the wake from suspend still does not work. And mainline kernel does not work no matter if I use gdm or lightdm

@petsam I just found shadow.service is used to verify integrity of password and group files, but what does it mean it failed? even though the system booted fine as per that log.

Just thinking out loud. If video driver were the issue then on wake up from suspend the journalctl should have shown some entries around the wake up time, but there were none. I remember doing wake from sleep at 8:04am today and there was no entry in journal log around that time. The only entries I saw was for the last time I suspended the system and then rebooted it because the wake failed.

So my question is where should the log entries be when waking from sleep ? may be they will shed some light on the root cause

Not if a complete freeze occurs, in those cases the logs often show no entries.

1 Like

OK, then do we know the sequence of things that happen upon wake from sleep ? May be going thru that list one by one may help in debugging this issue.

Read status to find out

systemctl status shadow

IIRC there was an old issue with different/changed file/folder permissions that created such a failure.
I guess you would see if this is the case if you reinstall in terminal and watch for messages

sudo pacman -S shadow
2 Likes

Have you done ^^^ this