PC Not Waking Up After Waking Up From Sleep

[thatcher]

Hey there fellow Manjaroers! Hope you’ll are doing great…

So I just upgraded my PC and did a fresh dual-boot UEFI install of Windows 11/Manjaro GNOME. I have a strange issue that makes my PC not wake up after it goes to sleep/suspend.

Things to note:

• PC wakes up from Windows normally.
• It’s a fresh install with just a few GNOME Extensions installed and some apps; in short, I haven’t touched the kernel or anything. No such app or extension installed that might inhibit wake-up.
• When the system is resumed, the screen is blank, the keyboard Numlock can not be toggled. Have to hard reset the system using the power button.

Things I’ve Tried:

• Kernel 5.15.48 (default kernel with Manjaro 21.3)
• Kernel 5.18.5

As far as the kernel buffer goes, I don’t know how I’m supposed to share when on one hand this forum won’t let me share the link to it and on the other, if pasted, it would become a messy post…

System Info:

System:
  Kernel: 5.18.5-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.0 Desktop: GNOME v: 42.2
    Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: B660M GAMING X DDR4 v: x.x serial: <superuser required>
    UEFI: American Megatrends LLC. v: F4b date: 03/28/2022
CPU:
  Info: 6-core model: 12th Gen Intel Core i5-12400 bits: 64 type: MT MCP arch: Alder Lake rev: 5
    cache: L1: 480 KiB L2: 7.5 MiB L3: 18 MiB
  Speed (MHz): avg: 4202 high: 4396 min/max: 800/5600 cores: 1: 4081 2: 4296 3: 4273 4: 4062
    5: 4283 6: 4208 7: 4201 8: 3928 9: 4396 10: 4200 11: 4134 12: 4364 bogomips: 59916
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel vendor: Gigabyte driver: i915 v: kernel bus-ID: 00:02.0
  Device-2: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Micro-Star MSI driver: amdgpu
    v: kernel arch: RDNA 2 bus-ID: 03:00.0
  Display: wayland server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.2 compositor: gnome-shell
    driver: gpu: amdgpu resolution: 2560x1080~75Hz
  OpenGL:
    renderer: AMD Radeon RX 6600 XT (dimgrey_cavefish LLVM 13.0.1 DRM 3.46 5.18.5-1-MANJARO)
    v: 4.6 Mesa 22.1.1 direct render: Yes
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3
  Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel bus-ID: 03:00.1
  Sound Server-1: ALSA v: k5.18.5-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.0 running: yes
  Sound Server-4: PipeWire v: 0.3.52 running: yes
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel port: 3000
    bus-ID: 06:00.0
  IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 7.98 TiB used: 3.59 TiB (44.9%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT500P5SSD8 size: 465.76 GiB temp: 43.9 C
  ID-2: /dev/sda vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
  ID-3: /dev/sdb vendor: Crucial model: CT275MX300SSD1 size: 256.17 GiB
Partition:
  ID-1: / size: 109.98 GiB used: 12.31 GiB (11.2%) fs: ext4 dev: /dev/nvme0n1p5
  ID-2: /boot/efi size: 96 MiB used: 27.3 MiB (28.4%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 42.0 C mobo: N/A gpu: amdgpu temp: 40.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
  Processes: 362 Uptime: 33m Memory: 31.13 GiB used: 4.68 GiB (15.0%) Init: systemd Compilers:
  gcc: 12.1.0 clang: 13.0.1 Packages: 1251 Client: gnome-shell v: 42.2 inxi: 3.3.19

Any help would be appreciated.

Thanks,
thatcher

[megavolt]

Hello @thatcher and welcome

This way you can get a clue what happens:

Not waking up from sleep - how to troubleshoot help request

Standby/Suspend journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p" Sleep/Hibernate journalctl --boot -1 | sed -n -r "/Starting.+Hibernate/,/Finished.+Hibernate/p" Here you can get a list of all boots with date and time: journalctl --list-boots --no-pager Then you can target the correct boot number (0, -1, -2, -3 etc.)

[thatcher]

$ journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"

Jun 21 12:56:57 mansion systemd[1]: Starting System Suspend...
Jun 21 12:56:57 mansion systemd-sleep[3989]: Entering sleep state 'suspend'...
Jun 21 12:56:57 mansion kernel: PM: suspend entry (deep)

journalctl --boot -1 | sed -n -r "/Starting.+Hibernate/,/Finished.+Hibernate/p"

this command does not product any output

journalctl --list-boots --no-pager

This only produces IDs of the last and current boots…

P.S: It won’t even let me upload images, great

[megavolt]

@thatcher

P.S: It won’t even let me upload images, great

It is because your are new. You need spend some time here, read things, answer some posts etc. Then you reach TL1 (Trust Level 1) quickly. Then you can post links and screenshots. It is “Spam Prevention”.

But at TL0 you use a trick. You can add links in a code block like:

`https://example.com`

https://example.com

However is is greatly discourage to send pictures of text here if avoidable.

---

Ok now the problem:

@thatcher

$ journalctl --boot -1 | sed -n -r "/Starting.+Suspend/,/Finished.+Suspend/p"

Jun 21 12:56:57 mansion systemd[1]: Starting System Suspend...
Jun 21 12:56:57 mansion systemd-sleep[3989]: Entering sleep state 'suspend'...
Jun 21 12:56:57 mansion kernel: PM: suspend entry (deep)

It just shows that it starts to suspend, normally it looks like that:

Jun 16 17:21:36 systemd[1]: Starting System Suspend...
Jun 16 17:21:36 systemd-sleep[13771]: Entering sleep state 'suspend'...
Jun 16 17:21:36 kernel: PM: suspend entry (deep)
Jun 16 17:21:36 kernel: Filesystems sync: 0.154 seconds
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "42"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event1  - Power Button: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "45"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event0  - Power Button: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "47"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event2  - Logitech USB Receiver: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "48"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event3  - Logitech USB Receiver Mouse: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "49"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "50"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event5  - Logitech USB Receiver System Control: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "51"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event18 - Eee PC WMI hotkeys: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "49"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event4  - Logitech USB Receiver Consumer Control: device removed
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (**) Option "fd" "65"
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) event19 - UVC Camera (046d:0825): device removed
Jun 16 17:21:36 pipewire-media-session[1062]: ms.mod.default-profile: device 'alsa_card.pci-0000_01_00.1': can't resto
re profile: No such device
Jun 16 17:21:36 gsd-media-keys[1202]: Unable to get default sink
Jun 16 17:21:36 gdm[685]: Gdm: GdmLocalDisplayFactory: received VT change event
Jun 16 17:21:36 gdm[685]: Gdm: GdmLocalDisplayFactory: VT changed from 2 to 63
Jun 16 17:21:36 gdm[685]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring
Jun 16 17:21:36 kernel: rfkill: input handler enabled
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:68
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:83
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:64
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:67
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:69
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:66
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:82
Jun 16 17:21:36 /usr/lib/gdm-x-session[806]: (II) systemd-logind: got pause for 13:65

So it hangs at the Filesystem sync?

[thatcher]

@megavolt

So it hangs at the Filesystem sync?

Umm, sorry but I don’t know about it…

and here’s the links to current and -1 and -2 boots…

I think the answer might be in the -2

Journalctl -b -2
https://cloudvyzor.com/logpad/?query&database=sandbox-fd15d49b0f7c4775f191f059f8c41289

Journalctl -b -1
https://cloudvyzor.com/logpad/?query&database=sandbox-82d945e469d1826c021435efc3578e6d

Journalctl -b 0
https://cloudvyzor.com/logpad/?query&database=sandbox-44ac348163165074b7a15a675f1fd24f

[megavolt]

@thatcher

Umm, sorry but I don’t know about it…

It just means: sync all filesystem operations which were not written and only exist in RAM at this moment.

It is the same as running sync at the terminal.

However…

@thatcher

journalctl --list-boots --no-pager

This only produces IDs of the last and current boots…

Did you try other boots? Is that all you get from the log?

[thatcher]

@megavolt

Did you try other boots? Is that all you get from the log?

Already pasted the links to correct boots in above code block

[megavolt]

@thatcher

https://cloudvyzor.com/logpad/?query&database=sandbox-fd15d49b0f7c4775f191f059f8c41289

Sorry, I am too dumb to use this “Logpad”… I don’t want to grep the text but switch to the position of the search result plus I cannot download it. Leave it as normal text here or I just leave the conversation. Someone else can deal with it.

Have a good day

[thatcher]

journalctl 0

https://0x0.st/ou52.txt

journalctl -1

https://0x0.st/ou51.txt

journalctl -2

https://0x0.st/ou5e.txt

[megavolt]

Ok thanks for text log @thatcher

After investigations I saw this post which should be related to your problem:

Suspend problems with LPSS on Alder Lake CPU

Hi folks, (my 1st post, please be gentle Currently running Release: 21.2.1 (Qonos) / with 5.15.12.1 kernel I’ve upgraded CPU and motherboard on my PC, to i7-12700kf and z690 (board: gigabyte z690 gaming x ddr4 with F6 bios which is the latest currently). Since the upgrade been having problems with resume from s3 suspend in Linux (tried 5.13, 5.14, 5.15 and couple of RC of 5.16). Simptoms: PC would start resuming - i.e. fans would start spinning, disk would blink once, but th…

He mentioned this:

@kiloba

After a lot of experimentation i found that resume starts working if i disable ‘IOAPIC 24-119’ in BIOS. Which got me thinking ‘noapic’ kernel parameter would help as well (and it did)… then i noticed that both approaches effectively lead to intel_lpss_pci failing to initialize… I.e. if intel_lpss_pci is failing then resume from suspend is working…

Even if pc boots with intel_lpss_pci (which properly initializes) and then rmmod it before suspend - resume still works.

Also here: https://unix.stackexchange.com/questions/688833/linux-wont-wake-up-from-suspend-on-intel-alder-latke-gigabyte-z690

1. try to disable IOAPIC 24-119 in the BIOS and kind of
2. If this module is loaded:

lsmod | grep intel_lpss_pci

remove/unload it before supending:

sudo rmmod -v intel_lpss_pci

3. You can also add: noapic to the kernel parameter at /etc/default/grub

Could you confirm that this is the problem?

[thatcher]

first off, thank you so much for going way and beyond in helping me out…
I solved it thanks to your pointer towards the culprit; intel_lpss_pci
Simply added module_blacklist=intel_lpss_pci to my kernel parameters

Thank you!