resuming arch linux from sleep is not working properly

seth · 2024-11-29 07:25:31

i dont have to do this on my original arch ssd

You're running this while the new disk is attached to the system?
Please post a journal from such boot covering a suspend cycle.

Omarz2012 · 2024-11-29 22:43:24

seth wrote:

i dont have to do this on my original arch ssd
You're running this while the new disk is attached to the system?
Please post a journal from such boot covering a suspend cycle.

what i mean is that the kernel version on my original arch install is the same as my new one so i don't think that it's a kernel issue.

Omarz2012 · 2024-11-30 01:35:32

BIG NEWS: After reinstalling all my packages, i got some more messages for what happens when i resume. output of

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

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

seth · 2024-11-30 07:06:06

i don't think that it's a kernel issue

No, I think it's a "new disk" issue since some dozen posts ago

The plan is to sleep/wake the system from the old disk and see whether - though everything seems working, the new disk acts up.
It'll likely be helpful if some partition of the new disk is mounted before sleeoing the system.

Omarz2012 · 2024-11-30 13:54:03

seth wrote:

i don't think that it's a kernel issue
No, I think it's a "new disk" issue since some dozen posts ago
The plan is to sleep/wake the system from the old disk and see whether - though everything seems working, the new disk acts up.
It'll likely be helpful if some partition of the new disk is mounted before sleeoing the system.

Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened? well the result is that it worked just fine. also there are some new things in the journal which i posted in my previous post which include the reading/poll/queues thing to be completed allowing there to be some more information such as the wifi/Bluetooth driver failing and getting stuck on getting stuck on

random: crng reseeded on system resumption

seth · 2024-11-30 18:00:41

Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened?

Almost. Not "tell", "show" - post the journal.
We're lookng for any signs of the nvme acting up (though not critically, since it's not the root device)

Omarz2012 · 2024-12-01 16:05:40

seth wrote:

Ok just to be clear you want me to sleep my original system with a partition of the new disk mounted and then tell what happened?
Almost. Not "tell", "show" - post the journal.
We're lookng for any signs of the nvme acting up (though not critically, since it's not the root device)

update: seemed to be fixed by just reinstalling. but now computer just does not resume and fails to detect my laptop lid opening every 2nd time with the last message being

 File systems sync

with some random message about the wifi 30 seconds after i open the lid. also every time i put it to sleep, the usb failing to suspend and the wifi failing to resume even though they work. i tried checking with hw-probe to see the firmware but it was not working.

Last edited by Omarz2012 (2024-12-01 17:19:24)

seth · 2024-12-03 05:45:37

with some random message about the wifi…

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for an affected boot, eg

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

for the previous (-1) one.

Omarz2012 · 2024-12-08 15:23:20

Turns out it is a kernel issue as booting from LTS seems to fix the problem, now because I reinstalled arch, the issue with the vanilla kernel is now a cointoss between the blinking cursor and "nvme nvme1: 16/0/0 default/read/poll queues".

Last edited by Omarz2012 (2024-12-08 15:38:05)

seth · 2024-12-08 20:15:16

16th Nov 2024 wrote:

everything has been going well until the 2 days ago

Nov 08, 2024: 6.11.7.arch1-1
Nov 10, 2024: config: Disable ZSWAP_DEFAULT_ON (zen kernel)
Nov 15, 2024: 6.11.8.arch1-1 / config: Enable MAXSMP / 6.11.8.arch1-2

seth also wrote:

Have you tried to downgrade the kernel to 6.11.6

Also check your pacman log what was actually updated (notably kernel-wise) from where ~Nov 14.

Omarz2012 · 2024-12-09 23:15:27

seth wrote:

16th Nov 2024 wrote:
everything has been going well until the 2 days ago
Nov 08, 2024: 6.11.7.arch1-1
Nov 10, 2024: config: Disable ZSWAP_DEFAULT_ON (zen kernel)
Nov 15, 2024: 6.11.8.arch1-1 / config: Enable MAXSMP / 6.11.8.arch1-2
seth also wrote:
Have you tried to downgrade the kernel to 6.11.6
Also check your pacman log what was actually updated (notably kernel-wise) from where ~Nov 14.

idk if that will work as I recently reinstalled arch. after I reinstalled, it would only successfully resume once per boot. then I switched to the LTS kernel and when I updated yesterday it then instead of working once and not again each boot, it was now a coin toss between the blinking cursor and "nvme nvme1: 16/0/0 default/read/poll queues" on the vanilla kernel. also how do you get pacman logs

Last edited by Omarz2012 (2024-12-09 23:16:14)

seth · 2024-12-10 10:08:58

How "recently"?
The log is in /var/log

Omarz2012 · 2024-12-10 23:10:29

seth wrote:

How "recently"?
The log is in /var/log

10 days ago. i can also confirm it is a kernel issue as it has now started happening in my original arch install. according to the pacman log on my original arch install(not my new one as I reinstalled it, destroying all trace of old pacman logs) by grepping with the keyword linux, the only notable logs were

[2024-12-10T17:30:21-0500] [ALPM] upgraded linux (6.12.1.arch1-1 -> 6.12.4.arch1-1)
[2024-12-10T17:30:22-0500] [ALPM] upgraded linux-headers (6.12.1.arch1-1 -> 6.12.4.arch1-1)

seth · 2024-12-11 08:18:39

So please confirm that 6.12.1 works reliably but 6.12.4 won't - then test which of the kernels inbetween breaks it.
However, both versions post-date your original report!
Also 6.12 < 6.12.3 "broke" the system for many users by running it on the simpledrm device.
Next question: you're running nvidia-open, but is the binary nvidia driver also affected?

Omarz2012 · 2024-12-11 20:31:09

seth wrote:

So please confirm that 6.12.1 works reliably but 6.12.4 won't - then test which of the kernels inbetween breaks it.
However, both versions post-date your original report!
Also 6.12 < 6.12.3 "broke" the system for many users by running it on the simpledrm device.
Next question: you're running nvidia-open, but is the binary nvidia driver also affected?

yes, the binary Nvidia driver has the same issues. I don't know what's going on now, this is a table of the whole situation embed error aw man
NE stands for it never got the update due to it being created too late or deleted too early, dash means that it was not tested due to miscellaneous reasons. 1 stands for the resume only working once per session before you have to restart and 2 means the coinflip between the blinking cursor and the nvme thing. I didn't keep track of what update I was on so some of this is just an estimate on what update I was on. when I created this thread, it was on the second install update 2. Shenanigans started in the Middle of November with the whole Nvidia issue. update 1, second install is just a speculation as I am pretty sure the reason I have no memory of it being broken was that I forgot so take that result with a small pebble. next post will be what each hypothetical update correlates to a real update. also the goofy ahh font on update 3 second install is because I had to correct it through imgurs editor. tests on which update breaks what are coming out later today. also when downgrading kernel, is it mandatory to downgrade all kernel modules.

Last edited by Omarz2012 (2024-12-11 21:42:59)

Omarz2012 · 2024-12-11 21:57:41

original install:
6.11.9 works moving on to 6.12.1
6.12.1 works moving to 6.12.4
6.12.4 works? retrying.
6.12.4 works again!
New 1tb install: nothing in my cache works
Edit: Ignore this, I forgot to test if it sleeps a second time per boot.

Last edited by Omarz2012 (2024-12-12 23:58:18)

Omarz2012 · 2024-12-14 02:42:04

the original install has started working again, but the new one is as worse as ever, 6.9 seemed to work but it was acting kind of weird after it resumed after going back to normal after about 20 seconds. 6.11.5 works once and cannot even sleep after that, it just says "device or resource busy" and 6.11.9 has the NVME thing, I am pretty sure it is because it is because I didn't downgrade properly as I am also supposed to downgrade all kernel modules and I don't know where to find what they all are ̶b̶u̶t̶ ̶e̶v̶e̶n̶ i̶f̶ ̶i̶ ̶d̶o̶ I̶ ̶c̶a̶n̶n̶o̶t̶ ̶p̶u̶l̶l̶ ̶m̶y̶s̶e̶l̶f̶ ̶t̶o̶ ̶d̶o̶ ̶t̶h̶a̶t̶ ̶a̶s̶ ̶I̶ ̶a̶m̶ ̶s̶l̶o̶w̶l̶y̶ ̶g̶o̶i̶n̶g̶ ̶i̶n̶s̶a̶n̶e̶ ̶f̶r̶o̶m̶ ̶t̶h̶i̶s̶ ̶a̶n̶d̶ ̶t̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶h̶a̶s̶ ̶i̶m̶p̶a̶c̶t̶e̶d̶ ̶m̶e̶ ̶m̶e̶n̶t̶a̶l̶l̶y̶ ̶s̶e̶v̶e̶r̶e̶l̶y̶ ̶a̶f̶t̶e̶r̶ ̶a̶n̶ ̶e̶n̶t̶i̶r̶e̶ ̶m̶o̶n̶t̶h̶ ̶o̶f̶ ̶p̶u̶l̶l̶i̶n̶g̶ ̶o̶u̶t̶ ̶m̶y̶ ̶h̶a̶i̶r̶s̶ ̶t̶o̶ ̶t̶h̶e̶ ̶p̶o̶i̶n̶t̶ ̶t̶h̶a̶t̶ ̶I̶ ̶c̶a̶n̶n̶o̶t̶ ̶g̶o̶ ̶n̶e̶a̶r̶ ̶a̶n̶y̶ ̶t̶e̶c̶h̶ ̶w̶h̶i̶c̶h̶ ̶I̶ ̶e̶v̶e̶n̶ ̶h̶a̶v̶e̶ ̶t̶h̶e̶ ̶s̶l̶i̶g̶h̶t̶e̶s̶t̶ ̶c̶o̶n̶t̶r̶o̶l̶ ̶o̶f̶ ̶w̶i̶t̶h̶o̶u̶t̶ ̶h̶a̶v̶i̶n̶g̶ ̶a̶ ̶g̶u̶t̶ ̶w̶r̶e̶n̶c̶h̶i̶n̶g̶ ̶p̶a̶i̶n̶.̶ ignore the last part, just a vent.

seth · 2024-12-14 14:45:55

Have you tried the "new" intallation w/ the 6.12.4 kernel?

as I am also supposed to downgrade all kernel modules and

The modules are part of the kernel package, you just need to make sure to have updated the initramfs into the proper location (what should™ happen automatically)

Omarz2012 · 2024-12-14 16:01:50

seth wrote:

Have you tried the "new" intallation w/ the 6.12.4 kernel?
as I am also supposed to downgrade all kernel modules and
The modules are part of the kernel package, you just need to make sure to have updated the initramfs into the proper location (what should™ happen automatically)

well that's weird? yes I have tested it with the new 6.12.4 kernel. so far, 6.9 does its job but it does not play nicely with my wifi card and sometimes straight up does not recognize it. 6.11.5 is the most broken of them all with it not being able to go to sleep a second time due to "device or resource busy". 6.11.9 has the classic stuck on nvme default/poll/queue thing and all later versions including 6.12.4 have either the same problem of 6.11.9 or does not even finish low level resume causing the blinking cursor. pls respond quickly if you can, this is the only day were I have free time on my hands as every other day is filled with either school or homework meaning that this conversation goes at 1 message per day and I have until December 31st which is when 6.12 becomes LTS.

Last edited by Omarz2012 (2024-12-14 16:04:17)

seth · 2024-12-14 16:29:24

https://man.archlinux.org/man/core/pacm … .conf.5.en
"IgnorePkg ="

If the installationsbehave differently on the same kernel, the difference is either
1. the user space
2. the root device => https://bbs.archlinux.org/viewtopic.php … 3#p2211363

Omarz2012 · 2024-12-14 16:39:16

seth wrote:

https://man.archlinux.org/man/core/pacm … .conf.5.en
"IgnorePkg ="
If the installationsbehave differently on the same kernel, the difference is either
1. the user space
2. the root device => https://bbs.archlinux.org/viewtopic.php … 3#p2211363

so maybe a recent kernel has introduced a bug where my specific nvme does not work correctly with the nvme? but that still wont explain the blinking cursor as journald does not say anything about the nvme when it comes to the nvme.

seth · 2024-12-14 16:41:11

My money would still be on DIPM or APST

but that still wont explain the blinking cursor as journald does not say anything about the nvme when it comes to the nvme.

The journal won't say anything when it cannot be written to the NVME, that's why it would be interesting to monitor the concerned nvme waking up from sleep when it's NOT the root device.

Omarz2012 · 2024-12-14 16:53:04

ok ima try sleeping and resuming on my original install with my 1tb mounted, but also 6.9 and 6.11.5 both have errors saying "your system is too slow".

Omarz2012 · 2024-12-14 17:01:50

the 1tb nvme seems to be working perfectly fine, the only things it says when running

journalctl | grep "nvme1" | grep "Dec 14"

are

Dec 14 11:53:34 archlinux kernel: nvme nvme1: pci function 0000:03:00.0
Dec 14 11:53:34 archlinux kernel: nvme nvme1: allocated 64 MiB host memory buffer.
Dec 14 11:53:34 archlinux kernel: nvme nvme1: 16/0/0 default/read/poll queues
Dec 14 11:53:34 archlinux kernel:  nvme1n1: p1 p2 p3
Dec 14 11:53:48 archlinux kernel: block nvme1n1: No UUID available providing old NGUID
Dec 14 11:54:03 archlinux udisksd[1054]: Mounted /dev/nvme1n1p3 at /run/media/omarzakaria2012/9835908a-b90c-4942-9c64-311adc6c0beb on behalf of uid 1000
Dec 14 11:54:03 archlinux kernel: EXT4-fs (nvme1n1p3): mounted filesystem 9835908a-b90c-4942-9c64-311adc6c0beb r/w with ordered data mode. Quota mode: none.
Dec 14 11:55:08 archlinux kernel: nvme nvme1: 16/0/0 default/read/poll queues

Edit: the only output it has after waking up is

 Dec 14 11:55:08 archlinux kernel: nvme nvme1: 16/0/0 default/read/poll queues

, there still seems to be no problem with the nvme and i can perfectly acess it without any problems

Last edited by Omarz2012 (2024-12-14 17:14:36)

seth · 2024-12-14 17:18:14

Don't grep for random stuff, it's not even clear whether or when a sleep cycle happened there.

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

Arch Linux

#26 2024-11-29 07:25:31

Re: resuming arch linux from sleep is not working properly

#27 2024-11-29 22:43:24

Re: resuming arch linux from sleep is not working properly

#28 2024-11-30 01:35:32

Re: resuming arch linux from sleep is not working properly

#29 2024-11-30 07:06:06

Re: resuming arch linux from sleep is not working properly

#30 2024-11-30 13:54:03

Re: resuming arch linux from sleep is not working properly

#31 2024-11-30 18:00:41

Re: resuming arch linux from sleep is not working properly

#32 2024-12-01 16:05:40

Re: resuming arch linux from sleep is not working properly

#33 2024-12-03 05:45:37

Re: resuming arch linux from sleep is not working properly

#34 2024-12-08 15:23:20

Re: resuming arch linux from sleep is not working properly

#35 2024-12-08 20:15:16

Re: resuming arch linux from sleep is not working properly

#36 2024-12-09 23:15:27

Re: resuming arch linux from sleep is not working properly

#37 2024-12-10 10:08:58

Re: resuming arch linux from sleep is not working properly

#38 2024-12-10 23:10:29

Re: resuming arch linux from sleep is not working properly

#39 2024-12-11 08:18:39

Re: resuming arch linux from sleep is not working properly

#40 2024-12-11 20:31:09

Re: resuming arch linux from sleep is not working properly

#41 2024-12-11 21:57:41

Re: resuming arch linux from sleep is not working properly

#42 2024-12-14 02:42:04

Re: resuming arch linux from sleep is not working properly

#43 2024-12-14 14:45:55

Re: resuming arch linux from sleep is not working properly

#44 2024-12-14 16:01:50

Re: resuming arch linux from sleep is not working properly

#45 2024-12-14 16:29:24

Re: resuming arch linux from sleep is not working properly

#46 2024-12-14 16:39:16

Re: resuming arch linux from sleep is not working properly

#47 2024-12-14 16:41:11

Re: resuming arch linux from sleep is not working properly

#48 2024-12-14 16:53:04

Re: resuming arch linux from sleep is not working properly

#49 2024-12-14 17:01:50

Re: resuming arch linux from sleep is not working properly

#50 2024-12-14 17:18:14

Re: resuming arch linux from sleep is not working properly

Board footer