resuming arch linux from sleep is not working properly

Omarz2012 · 2024-11-16 15:30:27

i have recently installed arch linux with plasma, network manager and nvidia-open driver setup on an acer nitro 5 (AN515-45) with an RTX 3050 and everything has been going well until the 2 days ago, whenever i set my computer to sleep and then wake it up, it kind of works but alot of things are broken like the wifi and the ability to turn off/reboot the computer without using the physical button. this is the output of

journalctl -r | grep "Nov 16 10:19"

(November 16 10:19 is the time of resume):

Nov 16 10:19:15 omarsarchernitro5 kernel: nvme nvme1: 16/0/0 default/read/poll queues
Nov 16 10:19:15 omarsarchernitro5 kernel: amdgpu 0000:06:00.0: amdgpu: PSP is resuming...
Nov 16 10:19:15 omarsarchernitro5 kernel: [drm] PTB located at 0x000000F41FC00000
Nov 16 10:19:15 omarsarchernitro5 kernel: [drm] PCIE GART of 1024M enabled.
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: event unblocked
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: interrupt unblocked
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: PM: Waking up from system sleep state S3
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU15 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00F: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU14 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00E: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU13 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00D: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU12 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00C: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU11 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00B: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU10 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C00A: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU9 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C009: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU8 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C008: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU7 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C007: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU6 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C006: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU5 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C005: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU4 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C004: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU3 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C003: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU2 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C002: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Nov 16 10:19:15 omarsarchernitro5 kernel: CPU1 is up
Nov 16 10:19:15 omarsarchernitro5 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: \_SB_.PLTF.C001: Found 3 idle states
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Nov 16 10:19:15 omarsarchernitro5 kernel: Enabling non-boot CPUs ...
Nov 16 10:19:15 omarsarchernitro5 kernel: LVT offset 0 assigned for vector 0x400
Nov 16 10:19:15 omarsarchernitro5 kernel: AMD-Vi: Virtual APIC enabled
Nov 16 10:19:15 omarsarchernitro5 kernel: AMD-Vi: Virtual APIC enabled
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: PM: Restoring platform NVS memory
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: EC started
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: PM: Low-level resume complete
Nov 16 10:19:15 omarsarchernitro5 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 1 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 2 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 3 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 4 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 5 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 6 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 7 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 8 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 9 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 10 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 11 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 12 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 13 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 14 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: smpboot: CPU 15 is now offline
Nov 16 10:19:15 omarsarchernitro5 kernel: Disabling non-boot CPUs ...
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: PM: Saving platform NVS memory
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: EC stopped
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: event blocked
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: PM: Preparing to enter system sleep state S3
Nov 16 10:19:15 omarsarchernitro5 kernel: ACPI: EC: interrupt blocked
Nov 16 10:19:15 omarsarchernitro5 kernel: NVRM: nvAssertFailedNoLog: Assertion failed: rmapiLockIsOwner() @ mem_mgr.c:465
Nov 16 10:19:15 omarsarchernitro5 kernel: queueing ieee80211 work while going to suspend
Nov 16 10:19:15 omarsarchernitro5 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Nov 16 10:19:15 omarsarchernitro5 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Nov 16 10:19:15 omarsarchernitro5 kernel: Freezing remaining freezable tasks
Nov 16 10:19:15 omarsarchernitro5 kernel: OOM killer disabled.
Nov 16 10:19:15 omarsarchernitro5 kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Nov 16 10:19:15 omarsarchernitro5 kernel: Freezing user space processes

edit: i have disabled Preserving video memory and fbdev as it caused a black screen when waking up

Last edited by Omarz2012 (2024-11-16 17:09:09)

seth · 2024-11-16 16:32:30

Because it is like top posting.
Why not?
Please don't "-r".

Also don't grep - the system wakes up but not much else is logged - the breakage might also have occurred when falling asleep.

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Omarz2012 · 2024-11-16 17:10:09

whats top posting

seth wrote:

Because it is like top posting.
Why not?
Please don't "-r".
Also don't grep - the system wakes up but not much else is logged - the breakage might also have occurred when falling asleep.
sudo journalctl -b | curl -F 'file=@-' 0x0.st

also what do i do after i run the command

Last edited by Omarz2012 (2024-11-16 17:10:49)

seth · 2024-11-16 17:15:11

"Bad style" - https://en.wikipedia.org/wiki/Posting_style#Top-posting
Share the url you get in return?

Omarz2012 · 2024-11-16 19:18:33

seth wrote:

"Bad style" - https://en.wikipedia.org/wiki/Posting_style#Top-posting
Share the url you get in return?

http://0x0.st/Xd8x.txt

Last edited by Omarz2012 (2024-11-16 19:21:28)

seth · 2024-11-16 22:20:46

That journal doesn't include a sleep cycle?
You can access older journals, eg

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous (-1) boot.

Omarz2012 · 2024-11-17 15:14:28

seth wrote:

That journal doesn't include a sleep cycle?
You can access older journals, eg
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
for the previous (-1) boot.

now the output is this

seth · 2024-11-17 15:38:27

Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Nov 17 10:09:43 omarsarchernitro5 kernel: nvme nvme1: 16/0/0 default/read/poll queues
Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme1n1: p1 p2 p3

Parallel windows? See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

So that journal stops abruptly after the wakeup, suggesting a hard reboot before the resumed session logged anything.
W/ these symptoms i'd first look into https://wiki.archlinux.org/title/Solid_ … leshooting and disable APST and ASPM and use the software IOMMU

Omarz2012 · 2024-11-20 00:39:10

seth wrote:

Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Nov 17 10:09:43 omarsarchernitro5 kernel: nvme nvme1: 16/0/0 default/read/poll queues
Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme1n1: p1 p2 p3
Parallel windows? See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
So that journal stops abruptly after the wakeup, suggesting a hard reboot before the resumed session logged anything.
W/ these symptoms i'd first look into https://wiki.archlinux.org/title/Solid_ … leshooting and disable APST and ASPM and use the software IOMMU

1. I have already disabled windows fast-start and hibernate back all away since i was trying out ubuntu
2. nvme0n1p1 is "Microsoft reserved", p2 is the boot partition of windows, p3 is windows, p4 is windows recovery, p5 is the boot partiton of my original arch install, p6 is my original arch install, nvme1n1p1 is "Microsoft reserved", p2 is my new arch installation boot partiton and p3 is my new arch install, both of these nvme drives are kingston with the omly difference that one was 512gb and came with the computer while the other one is 1tb and i bought it off amazon. I never had to do any of this when installing it on my original 512gb SSD. So is the 1tb NVMe defective, did I forgot to install some drivers or what is the problem with the SSD
3. is disabling APST and ASPM, setting the IOMMU to software safe? and also what are the side affects, also nothing in my log speaks of my nvme drive breaking.

Last edited by Omarz2012 (2024-11-20 05:01:42)

seth · 2024-11-20 07:49:03

also nothing in my log speaks of my nvme drive breaking

Nothing in your logs speaks of any problem, except that it abruptly ends and nothing has been logged after the wakeup.
That's primarily why we're looking at the storage and also because nvme's have this more frequently.

The settings are "safe" unless there's a horrible kernel bug and your house explodes when you add them.
They'll increase power consumption and cpu overhead and before you start to complain about that, we first and foremost want to know what the problem actually is. It's not the suggested final solution.

Omarz2012 · 2024-11-20 14:59:53

I will try doing that, also the log ending abruptly is probably because I had to hard poweroff because regular poweroff was broken from this whole fanatic

Last edited by Omarz2012 (2024-11-20 15:00:09)

Omarz2012 · 2024-11-21 22:22:53

Omarz2012 wrote:

seth wrote:
Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme0n1: p1 p2 p3 p4 p5 p6
Nov 17 10:09:43 omarsarchernitro5 kernel: nvme nvme1: 16/0/0 default/read/poll queues
Nov 17 10:09:43 omarsarchernitro5 kernel:  nvme1n1: p1 p2 p3
Parallel windows? See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodoo reasons.
So that journal stops abruptly after the wakeup, suggesting a hard reboot before the resumed session logged anything.
W/ these symptoms i'd first look into https://wiki.archlinux.org/title/Solid_ … leshooting and disable APST and ASPM and use the software IOMMU
1. I have already disabled windows fast start...3...nothing in my log speaks of my nvme drive breaking.

so i add the kernel parameters

nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off iommu=soft

right?

Last edited by Omarz2012 (2024-11-22 00:11:59)

seth · 2024-11-21 22:44:05

Yes.
Please avoid bloating the thread w/ full quotes of previous posts.

Omarz2012 · 2024-11-22 00:29:14

seth wrote:

Yes.
Please avoid bloating the thread w/ full quotes of previous posts.

after putting in the kernel parameters, system does not even recognize waking up anymore, when i open up the laptop lid, it just gets stuck a blinking cursor. checking journalctl while chrooted from my original arch install to the new one shows no sign of the system detecting waking up and the last message being

Nov 21 19:18:53 omarsarchernitro5 kernel: Filesystems sync: 0.005 seconds
Nov 21 19:18:53 omarsarchernitro5 kernel: PM: suspend entry (deep)
Nov 21 19:18:53 omarsarchernitro5 systemd-sleep[3767]: Performing sleep operation 'suspend'...

with -r flag

seth · 2024-11-22 08:15:23

Interesting, skip "pcie_port_pm=off" (first, then try to add the 4 parameters one by one and see which one breaks the resume and whether just skipping that gets you a morefavorable outcome)

Omarz2012 · 2024-11-22 23:45:51

HUGE UPDATE

seth wrote:

Interesting, skip "pcie_port_pm=off" (first, then try to add the 4 parameters one by one and see which one breaks the resume and whether just skipping that gets you a morefavorable outcome)

when i was trying which kernel parameter was breaking the sleep, i found out that setting iommu to software fixed the original shenanigan. but also it turns out that the original sleep problem ONLY AFFECTED THE WIFI AND THE ABILITY TO TURN THE COMPUTER OFF after some testing. also using poweroff command freezes the system after sleep when not fixed.

Last edited by Omarz2012 (2024-11-23 01:05:08)

seth · 2024-11-23 05:58:30

For clarification: "iommu=soft" allows you to suspend and resume the system w/o further issues?
As for

original sleep problem ONLY AFFECTED THE WIFI AND THE ABILITY TO TURN THE COMPUTER OFF after some testing

: how is that different from

The OP wrote:

kind of works but alot of things are broken like the wifi and the ability to turn off/reboot the computer without using the physical button

Do you mean you "things … like" actually means "only these things" or that the problems emerge only after several sleep attempts/warm reboots?

Do you get away w/ either "iommu.strict=1" instead of "iommu=soft"?

Omarz2012 · 2024-11-23 13:50:15

seth wrote:

For clarification: "iommu=soft" allows you to suspend and resume the system w/o further issues?
As for
original sleep problem ONLY AFFECTED THE WIFI AND THE ABILITY TO TURN THE COMPUTER OFF after some testing
: how is that different from
The OP wrote:
kind of works but ...
Do you mean you "things … like" actually means "only these things" or that the problems emerge only after several sleep attempts/warm reboots?
Do you get away w/ either "iommu.strict=1" instead of "iommu=soft"?

i mean that it turns out that it ONLY effects these things and everything is working properly so i am a little confused how its related with the iommu. also what is iommu.strict=1 mean

Last edited by Omarz2012 (2024-11-23 15:31:59)

seth · 2024-11-23 13:54:54

also what is iommu.strict=1 mean

https://raw.githubusercontent.com/torva … meters.txt

Not lazy
It's the canonical version of the suggested alternative "amd_iommu=fullflush" (you can use that, too)

Sidebar: please refrain from bloating the thread with meaningless full-quotes.

Omarz2012 · 2024-11-23 16:04:10

seth wrote:

also what is iommu.strict=1 mean
https://raw.githubusercontent.com/torva … meters.txt
Not lazy
It's the canonical version of the suggested alternative "amd_iommu=fullflush" (you can use that, too)
Sidebar: please refrain from bloating the thread with meaningless full-quotes.

none of them work anymore . now its just a coin toss between a blinking cursor and nothing else or the original problem every time i put it to sleep

Last edited by Omarz2012 (2024-11-23 18:06:21)

seth · 2024-11-23 18:10:07

"coin toss" == "regardless of the iommu setting" or "depending on the iommu setting"?

Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft" again…

Omarz2012 · 2024-11-23 20:16:00

seth wrote:

"coin toss" == "regardless of the iommu setting" or "depending on the iommu setting"?
Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft" again…

1. when using hardware iommu. it has the original problem. with software iommu, it 75% of the time shows the blinking cursor after waking up and 25% has the original problem. 2. using those 3 kernel parameters causes a blinking cursor 100% of the time after waking up

Last edited by Omarz2012 (2024-11-23 20:16:55)

Omarz2012 · 2024-11-23 22:14:51

all of these shenanigans happened recently as it showed no problem the before.

seth · 2024-11-25 08:33:06

Have you tried to downgrade the kernel to 6.11.6 or the behavior of the LTS kernel?
There was https://bbs.archlinux.org/viewtopic.php … 6#p2209476 but I'm not sure how it would lead to this behavior.

Also

I had to hard poweroff because regular poweroff was broken from this whole fanatic

See whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) still works - it might get us a better journal (unless the nvme is actually dead, because then it cannot be synced)

Omarz2012 · 2024-11-28 23:30:53

seth wrote:

Have you tried to downgrade the kernel to 6.11.6 or the behavior of the LTS kernel?
There was https://bbs.archlinux.org/viewtopic.php … 6#p2209476 but I'm not sure how it would lead to this behavior.
Also
I had to hard poweroff because regular poweroff was broken from this whole fanatic
See whether https://wiki.archlinux.org/title/Keyboa … el_(SysRq) still works - it might get us a better journal (unless the nvme is actually dead, because then it cannot be synced)

i am going to try to use the lts kernel but also i dont have to do this on my original arch ssd even though i updated it after i updated the new install

Arch Linux

#1 2024-11-16 15:30:27

resuming arch linux from sleep is not working properly

#2 2024-11-16 16:32:30

Re: resuming arch linux from sleep is not working properly

#3 2024-11-16 17:10:09

Re: resuming arch linux from sleep is not working properly

#4 2024-11-16 17:15:11

Re: resuming arch linux from sleep is not working properly

#5 2024-11-16 19:18:33

Re: resuming arch linux from sleep is not working properly

#6 2024-11-16 22:20:46

Re: resuming arch linux from sleep is not working properly

#7 2024-11-17 15:14:28

Re: resuming arch linux from sleep is not working properly

#8 2024-11-17 15:38:27

Re: resuming arch linux from sleep is not working properly

#9 2024-11-20 00:39:10

Re: resuming arch linux from sleep is not working properly

#10 2024-11-20 07:49:03

Re: resuming arch linux from sleep is not working properly

#11 2024-11-20 14:59:53

Re: resuming arch linux from sleep is not working properly

#12 2024-11-21 22:22:53

Re: resuming arch linux from sleep is not working properly

#13 2024-11-21 22:44:05

Re: resuming arch linux from sleep is not working properly

#14 2024-11-22 00:29:14

Re: resuming arch linux from sleep is not working properly

#15 2024-11-22 08:15:23

Re: resuming arch linux from sleep is not working properly

#16 2024-11-22 23:45:51

Re: resuming arch linux from sleep is not working properly

#17 2024-11-23 05:58:30

Re: resuming arch linux from sleep is not working properly

#18 2024-11-23 13:50:15

Re: resuming arch linux from sleep is not working properly

#19 2024-11-23 13:54:54

Re: resuming arch linux from sleep is not working properly

#20 2024-11-23 16:04:10

Re: resuming arch linux from sleep is not working properly

#21 2024-11-23 18:10:07

Re: resuming arch linux from sleep is not working properly

#22 2024-11-23 20:16:00

Re: resuming arch linux from sleep is not working properly

#23 2024-11-23 22:14:51

Re: resuming arch linux from sleep is not working properly

#24 2024-11-25 08:33:06

Re: resuming arch linux from sleep is not working properly

#25 2024-11-28 23:30:53

Re: resuming arch linux from sleep is not working properly

Board footer