[SOLVED] Suspend won't suspend for longer then a second

seth · 2024-11-04 13:55:02

I would not have enough fan ports for my case fans and so I would lose their functionality

This is primarily to identify the cause, not so much a long-term solution.

You can also just ass·u·me that it's the cause and look into its configuration abilities (eg. can you disable the USB hub) but while my gut says it's the problem, this might easily just make an Ass out of U and Me…

HangedFool · 2024-11-04 18:47:37

Oh wait, I'm stupid and can't read. I do have enough fan slots; the extras were in a different location from the rest of them, I'll try it. But just to clarify, the plan is: unplug all the fans from the cooler hub and plug them directly into the board, but what about the hub itself? Do I keep it plugged in? Because, while I'm not sure, I think it does more for my cooler then just spinning the fans.

Also, just to clarify because I never explicitly stated, this is my exact cooler

On a separate note, I'm going to have a pretty busy week and so I'll try doing this on the weekend, maybe thursday if I get done with my work earlier then expected.

Last edited by HangedFool (2024-11-04 18:47:55)

seth · 2024-11-04 20:36:06

I'm going to have a pretty busy week

You're the only one w/ stakes in this, so this runs at your pace anyway.

what about the hub itself? Do I keep it plugged in

No. You don't have to dismount it, but the plan is to get it out of the equation and that notably means "detached from the board" - the USB connections are actually the most interesting/worrysome ones.

HangedFool · 2024-11-04 21:55:03

I said that I would be taking a break from this but I'll be honest I couldn't step away from it when their was work to be done (I may be addiction to linux)

But anyway, after disconnecting the cooler hub and booting I hit suspend and the screen went black. I had to hard reset my monitor and cut power to my pc to fix it, so that was scary. But, after that first weird instance, consecutive suspends exhibited the same problem as usual. Here is a log from when my computer wasn't frozen. So I guess the primary suspect, the cooler, is out.

Oh, also, while I was at it I tried disconnecting the case usb ports. I don't think that was something we were suspecting but I decided to try it while I was at it.

Last edited by HangedFool (2024-11-04 21:58:22)

seth · 2024-11-05 07:53:40

Does/did the wakeup table still have all those doublettes w/o the cooler controller?

HangedFool · 2024-11-05 08:51:11

Looks like it.

cat /proc/acpi/wakeup

Device	S-state	 Status   Sysfs node
GPP3	 S4	*disabled
GPP4	 S4	*disabled
GPP5	 S4	*disabled
GPP6	 S4	*disabled
GP17	 S4	*enabled   pci:0000:00:08.1
XHC0	 S4	*enabled   pci:0000:16:00.3
XHC1	 S4	*enabled   pci:0000:16:00.4
XHC2	 S4	*enabled   pci:0000:17:00.0
GPP0	 S4	*enabled   pci:0000:00:01.1
SWUS	 S4	*enabled   pci:0000:01:00.0
SWDS	 S4	*enabled   pci:0000:02:00.0
GPP1	 S4	*disabled
GPP2	 S4	*disabled
GPP7	 S4	*enabled   pci:0000:00:02.1
UP00	 S4	*enabled   pci:0000:04:00.0
DP00	 S4	*enabled   pci:0000:05:00.0
NV00	 S4	*disabled
DP08	 S4	*disabled
EP00	 S4	*disabled
DP10	 S4	*disabled
WN00	 S4	*disabled
DP18	 S4	*disabled
LN00	 S4	*disabled
DP20	 S4	*enabled   pci:0000:05:04.0
NV00	 S4	*disabled
DP28	 S4	*enabled   pci:0000:05:05.0
EP00	 S4	*disabled
DP30	 S4	*enabled   pci:0000:05:06.0
EP00	 S4	*disabled
DP38	 S4	*enabled   pci:0000:05:07.0
EP00	 S4	*disabled
DP40	 S4	*enabled   pci:0000:05:08.0
UP00	 S4	*enabled   pci:0000:0b:00.0
DP00	 S4	*enabled   pci:0000:0c:00.0
NV00	 S4	*disabled
DP08	 S4	*disabled
EP00	 S4	*disabled
DP10	 S4	*enabled   pci:0000:0c:02.0
WN00	 S4	*disabled  pci:0000:0e:00.0
DP18	 S4	*enabled   pci:0000:0c:03.0
LN00	 S4	*enabled   pci:0000:0f:00.0
DP20	 S4	*enabled   pci:0000:0c:04.0
NV00	 S4	*disabled
DP28	 S4	*disabled
EP00	 S4	*disabled
DP30	 S4	*disabled
EP00	 S4	*disabled
DP38	 S4	*disabled
EP00	 S4	*disabled
DP40	 S4	*enabled   pci:0000:0c:08.0
EP00	 S4	*disabled  pci:0000:11:00.0
DP48	 S4	*disabled
EP00	 S4	*disabled
DP50	 S4	*disabled
EP00	 S4	*disabled
DP58	 S4	*disabled
EP00	 S4	*disabled
DP60	 S4	*enabled   pci:0000:0c:0c.0
XH00	 S4	*enabled   pci:0000:12:00.0
DP68	 S4	*enabled   pci:0000:0c:0d.0
SA00	 S4	*disabled  pci:0000:13:00.0
DP48	 S4	*disabled
EP00	 S4	*disabled
DP50	 S4	*disabled
EP00	 S4	*disabled
DP58	 S4	*disabled
EP00	 S4	*disabled
DP60	 S4	*enabled   pci:0000:05:0c.0
XH00	 S4	*enabled   pci:0000:14:00.0
DP68	 S4	*enabled   pci:0000:05:0d.0
SA00	 S4	*disabled  pci:0000:15:00.0
GPP8	 S4	*disabled

seth · 2024-11-05 14:14:42

Fuck.
At least we didn't waste any time on researching it for the error.

What if you pretend to be windows?

acpi_osi=! acpi_osi="Windows 2022"

https://learn.microsoft.com/en-us/windo … inacpi-osi

echo XH00 | sudo tee /proc/acpi/wakeup
grep XH00 /proc/acpi/wakeup

does only flip one of them (and then both)?

HangedFool · 2024-11-05 16:59:00

╭─░▒▓    ~ ···································································· ✔  10:56:33 AM  ▓▒░
╰─ grep XH00 /proc/acpi/wakeup           
XH00	 S4	*enabled   pci:0000:12:00.0
XH00	 S4	*enabled   pci:0000:14:00.0

╭─░▒▓    ~ ···································································· ✔  10:56:41 AM  ▓▒░
╰─ acpi_osi=! acpi_osi="Windows 2022"    

╭─░▒▓    ~ ···································································· ✔  10:56:48 AM  ▓▒░
╰─ echo XH00 | sudo tee /proc/acpi/wakeup
XH00

╭─░▒▓    ~ ···································································· ✔  10:56:55 AM  ▓▒░
╰─ grep XH00 /proc/acpi/wakeup           
XH00	 S4	*disabled  pci:0000:12:00.0
XH00	 S4	*enabled   pci:0000:14:00.0

╭─░▒▓    ~ ···································································· ✔  10:57:00 AM  ▓▒░
╰─ echo XH00 | sudo tee /proc/acpi/wakeup
XH00

╭─░▒▓    ~ ···································································· ✔  10:57:02 AM  ▓▒░
╰─ grep XH00 /proc/acpi/wakeup           
XH00	 S4	*enabled   pci:0000:12:00.0
XH00	 S4	*enabled   pci:0000:14:00.0

seth · 2024-11-05 20:39:59

acpi_osi=! acpi_osi="Windows 2022"

is a https://wiki.archlinux.org/title/Kernel_parameters

HangedFool · 2024-11-05 21:16:39

... I knew that... (I didn't)

Anyway, putting in both of those kernal parameters resulted in being stuck on the boot screen. Putting in just acpi_osi=! also got me stuck. However I did manage to boot with just acpi_osi="Windows 2022" however, no updates with suspend, nothing with XH00 or LN00

╭─░▒▓    ~ ···································································· ✔  03:08:09 PM  ▓▒░
╰─ echo XH00 | sudo tee /proc/acpi/wakeup
XH00

╭─░▒▓    ~ ···································································· ✔  03:08:16 PM  ▓▒░
╰─ grep XH00 /proc/acpi/wakeup           
XH00	 S4	*disabled  pci:0000:12:00.0
XH00	 S4	*enabled   pci:0000:14:00.0

╭─░▒▓    ~ ···································································· ✔  03:13:18 PM  ▓▒░
╰─ echo LN00 | sudo tee /proc/acpi/wakeup
LN00

╭─░▒▓    ~ ···································································· ✔  03:13:44 PM  ▓▒░
╰─ grep LN00 /proc/acpi/wakeup           
LN00	 S4	*disabled
LN00	 S4	*enabled   pci:0000:0f:00.0

seth · 2024-11-05 22:16:29

boot with just acpi_osi="Windows 2022"

unfortunately deosn't do anything.
Do you have more luck w/

acpi_osi=! acpi_osi="Windows 2015"

(windows 10, see the MS link for more windows versions)

HangedFool · 2024-11-05 22:53:26

Having tried "Windows 2022," "Windows 2021", "Windows 2015", and "Windows 2013" I got in with 2013. However, that being said,

╭─░▒▓    ~ ··························································································································································································· ✔  04:50:17 PM  ▓▒░
╰─ echo XH00 | sudo tee /proc/acpi/wakeup
XH00

╭─░▒▓    ~ ··························································································································································································· ✔  04:50:33 PM  ▓▒░
╰─ echo LN00 | sudo tee /proc/acpi/wakeup
LN00

╭─░▒▓    ~ ··························································································································································································· ✔  04:50:40 PM  ▓▒░
╰─ grep XH00 /proc/acpi/wakeup           
XH00	 S4	*disabled  pci:0000:12:00.0
XH00	 S4	*enabled   pci:0000:14:00.0

╭─░▒▓    ~ ··························································································································································································· ✔  04:50:45 PM  ▓▒░
╰─ grep LN00 /proc/acpi/wakeup         
LN00	 S4	*disabled
LN00	 S4	*enabled   pci:0000:0f:00.0

Also, suspend still didn't work.

Last edited by HangedFool (2024-11-05 22:55:10)

seth · 2024-11-06 07:00:21

You're trying to get rid of the redundant wakeup table entries.
If there's a BIOS update available and you get some stable power supply, that'd be my last best guess.

You could briefly check whether a different/older kernel (the LTS kernel or a completely different stack like https://grml.org ) produces them and/or lets you suspend the system.
Also

cat /sys/power/mem_sleep

, if it's "deep" you might have more luck w/ "s2idle"

HangedFool · 2024-11-06 07:10:01

In regard to a bios update, I will probably buy a UPS eventually. So I'll try that at some point.

As for the kernal, I can give the LTS a try.

And finally

cat /sys/power/mem_sleep

gives

s2idle [deep]

... I'm not sure what that means but both of the words you said are in that output

seth · 2024-11-06 07:24:50

echo s2idle | sudo tee /sys/power/mem_sleep
sudo systemctl suspend

HangedFool · 2024-11-06 07:40:12

Finally we got something different, it still isn't working proper but with the line you gave it is now exhibiting a different behavior.

When I ran suspend in the past what would happen is that the monitor's would lose input and all the lights would go off for a second and then the lights and monitor would immediately come back. However now the lights are staying on with the exception of my keyboard which turns off until I click it. Also the monitor does still lose it's input. That being said the factor that is making it annoying to test is that I can't get back in, I am unsure if it is just that their is no monitor input or if it is stuck asleep or what but I need to power off and back on to restore.

seth · 2024-11-06 07:44:54

https://wiki.archlinux.org/title/Power_ … _hibernate - but apparently it gets immediately broken as well and the system wakes up again.
It basically works less

HangedFool · 2024-11-06 07:46:32

At least it's different

HangedFool · 2024-11-06 19:14:47

Switching the kernel to linux-lts seems to work even less. All the lights stay on except my keyboard which just flickers off then back on and my monitor just freezes for an instant.

I also tried linux-zen, that exhibited the normal behavior.

So unless you have any more ideas I suppose the only thing left that I can try is a bios update.

Last edited by HangedFool (2024-11-06 19:19:54)

mwillems · 2024-11-06 19:43:08

Just chiming in to say that I have a similar issue with a gigabyte Aorus B650 motherboard and an AMD GPU. It's not exactly the same MoBo, but similar. I see attempts to suspend immediately resume, and I see a similar doubling of certain pci entries, and am unable to disable all of the wake entries. I have updated my BIOS to latest, but see no change in the behavior.

I've been troubleshooting the issue on and off for a year with no real progress except that I discovered that (for mysterious reasons) hibernation works correctly, it's just suspend that fails in my case. You might want to try and see if hibernation works for you as that could be a good alternative (as a workaround)

Last edited by mwillems (2024-11-06 19:44:38)

HangedFool · 2024-11-06 20:23:19

Thanks for telling me, that's awesome to hear. I wanted to set up hibernate but I was planning on waiting until I figured out suspend because I figured the same issue would persist into hibernate as well. So while I (obviously) am still hopeful that we can figure out the issue with suspend I am very appreciative of you for telling me that hibernate has a good shot of working.

Also, while it is sad to hear someone else has this problem, I won't lie, it is comforting hearing I am not the only one.

Last edited by HangedFool (2024-11-06 20:27:27)

seth · 2024-11-07 15:09:47

mwillems wrote:

hibernation works correctly

cat /proc/acpi/wakeup

https://bbs.archlinux.org/viewtopic.php … 1#p2206741 has them all at S4, is that the case for you as well? Or are there S3 specific ones?

mwillems · 2024-11-07 15:23:07

Mine are all also at S4:

Device	S-state	  Status   Sysfs node
GPP3	  S4	*disabled
GPP4	  S4	*disabled
GPP5	  S4	*disabled
GPP6	  S4	*disabled
GP17	  S4	*enabled   pci:0000:00:08.1
XHC0	  S4	*enabled   pci:0000:12:00.3
XHC1	  S4	*enabled   pci:0000:12:00.4
XHC2	  S4	*enabled   pci:0000:13:00.0
GPP0	  S4	*enabled   pci:0000:00:01.1
SWUS	  S4	*enabled   pci:0000:01:00.0
SWDS	  S4	*enabled   pci:0000:02:00.0
GPP1	  S4	*disabled
GPP2	  S4	*disabled
GPP7	  S4	*enabled   pci:0000:00:02.1
UP00	  S4	*enabled   pci:0000:04:00.0
DP00	  S4	*enabled   pci:0000:05:00.0
NV00	  S4	*disabled
DP08	  S4	*enabled   pci:0000:05:01.0
EP00	  S4	*disabled
DP10	  S4	*enabled   pci:0000:05:02.0
WN00	  S4	*disabled
DP18	  S4	*enabled   pci:0000:05:03.0
LN00	  S4	*disabled  pci:0000:09:00.0
DP20	  S4	*enabled   pci:0000:05:04.0
NV00	  S4	*disabled
DP28	  S4	*enabled   pci:0000:05:05.0
EP00	  S4	*disabled
DP30	  S4	*enabled   pci:0000:05:06.0
EP00	  S4	*disabled
DP38	  S4	*enabled   pci:0000:05:07.0
EP00	  S4	*disabled
DP40	  S4	*enabled   pci:0000:05:08.0
EP00	  S4	*disabled  pci:0000:0e:00.0
DP48	  S4	*disabled
EP00	  S4	*disabled
DP50	  S4	*disabled
EP00	  S4	*disabled
DP58	  S4	*disabled
EP00	  S4	*disabled
DP60	  S4	*enabled   pci:0000:05:0c.0
XH00	  S4	*enabled   pci:0000:0f:00.0
DP68	  S4	*enabled   pci:0000:05:0d.0
SA00	  S4	*disabled  pci:0000:10:00.0
GPP8	  S4	*enabled   pci:0000:00:02.2

sylv256 · 2025-02-20 00:22:47

I have reason to suspect this issue is similar to the one I was having.

Try adding this to your kernel parameters:

acpi_osi="!Windows 2015"

HangedFool · 2025-02-20 01:47:43

sylv256 wrote:

I have reason to suspect this issue is similar to the one I was having.
Try adding this to your kernel parameters:
acpi_osi="!Windows 2015"

I would like to preempt by saying, I did recently update my bios, so I can confirm that wasn't the issue.

That being said I am happy to say that the curse has been lifted! Thank you graciously sylv256, as your proposed solution has proven successful! When the bios update didn't solve it I gave up all hope so I am ecstatic at the fact that you have so graciously appeared to solve my problem. <3

Last edited by HangedFool (2025-02-20 01:48:13)

Arch Linux

#26 2024-11-04 13:55:02

Re: [SOLVED] Suspend won't suspend for longer then a second

#27 2024-11-04 18:47:37

Re: [SOLVED] Suspend won't suspend for longer then a second

#28 2024-11-04 20:36:06

Re: [SOLVED] Suspend won't suspend for longer then a second

#29 2024-11-04 21:55:03

Re: [SOLVED] Suspend won't suspend for longer then a second

#30 2024-11-05 07:53:40

Re: [SOLVED] Suspend won't suspend for longer then a second

#31 2024-11-05 08:51:11

Re: [SOLVED] Suspend won't suspend for longer then a second

#32 2024-11-05 14:14:42

Re: [SOLVED] Suspend won't suspend for longer then a second

#33 2024-11-05 16:59:00

Re: [SOLVED] Suspend won't suspend for longer then a second

#34 2024-11-05 20:39:59

Re: [SOLVED] Suspend won't suspend for longer then a second

#35 2024-11-05 21:16:39

Re: [SOLVED] Suspend won't suspend for longer then a second

#36 2024-11-05 22:16:29

Re: [SOLVED] Suspend won't suspend for longer then a second

#37 2024-11-05 22:53:26

Re: [SOLVED] Suspend won't suspend for longer then a second

#38 2024-11-06 07:00:21

Re: [SOLVED] Suspend won't suspend for longer then a second

#39 2024-11-06 07:10:01

Re: [SOLVED] Suspend won't suspend for longer then a second

#40 2024-11-06 07:24:50

Re: [SOLVED] Suspend won't suspend for longer then a second

#41 2024-11-06 07:40:12

Re: [SOLVED] Suspend won't suspend for longer then a second

#42 2024-11-06 07:44:54

Re: [SOLVED] Suspend won't suspend for longer then a second

#43 2024-11-06 07:46:32

Re: [SOLVED] Suspend won't suspend for longer then a second

#44 2024-11-06 19:14:47

Re: [SOLVED] Suspend won't suspend for longer then a second

#45 2024-11-06 19:43:08

Re: [SOLVED] Suspend won't suspend for longer then a second

#46 2024-11-06 20:23:19

Re: [SOLVED] Suspend won't suspend for longer then a second

#47 2024-11-07 15:09:47

Re: [SOLVED] Suspend won't suspend for longer then a second

#48 2024-11-07 15:23:07

Re: [SOLVED] Suspend won't suspend for longer then a second

#49 2025-02-20 00:22:47

Re: [SOLVED] Suspend won't suspend for longer then a second

#50 2025-02-20 01:47:43

Re: [SOLVED] Suspend won't suspend for longer then a second

Board footer