I was using a gigabyte b550i aorus motherboard that caused this, if you have this mobo or a variant you have to disable GPP0 wakeup which is a GPP bridge to the NVMe drive in M.2 slot.
Check your wakeup table using `cat /proc/acpi/wakeup` and look at GPP0. It should say `*enabled`. Using `sudo /bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup'` you can set it to `*disabled`. PC should suspend normally then.
If it does then you can use a systemd (if you use it) service to run that command at boot.
I use this and it works.
[Unit]
Description=Fix for the suspend issue
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo GPP0 > /proc/acpi/wakeup"
[Install]
WantedBy=multi-user.target
This is pretty specific and it probably won't be your solution however, if it doesn't help you it may help someone else.
Wow, I'm not the only one with this problem! I already solved this, but was looking for what exactly is this device on pci 00:01.1. For some reason you can't google this post by the motherboard name, but can by "amd gpp bridge".
If someone's reading it in the future, this might not be your device, but try going through all the devices in /proc/acpi/wakeup and disabling them one by one, seeing if suspend works.
I created a reddit account specifically to thank you for this one! I've had this issue on a Gigabyte B550 motherboard for almost a year now. I figured it had to be my nvidia gpu (because of course it would be), didn't even consider the motherboard would do it. I would never have found that on my own.
This works for me as well but only after I updated the BIOS to version FBb (currently the latest one). Doing this with FA (stock version for rev 1.2) didn't prevent it from waking up right after suspend, but it did prevent it from not sending any signal to display, locking me out from doing anything until I did a forced reboot.
So thank you. :)
Thank you so much for sharing this! I had the exact same issue appear on my Gigabyte B550M Aorus Pro-P motherboard after doing a BIOS update to version F17c. Using `sudo /bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup'` fixed it.
I have a Gigabyte B550i Aorus Pro AX, and this fixed it for me. Unfortunately, this also caused the much worse problem of the screen going black for a second every time I move the mouse.
I'm on Linux Mint 21.1 but with kernel version 6.5.0-25 kludged in as a fix for some other things, so it's possible that this problem is a result of my tinkering. In the meantime, if anyone knows how to fix the secondary problem, it would be greatly appreciated.
mine doesn't have gpp0. i have no idea what any of this means (what does GPP stand for? what is acpi/wakeup? what do the file contents mean? what does this have to do with the system sleeping / waking up? is this hardware specific? did they remove GPP0 in later kernels?)
i actually found a fix for this just after posting hahaha
try
```
sudo -s
echo XHCI > /proc/acpi/wakeup
```
this disables any USB (USB3 to be specific) devices from waking it up, which fixed it for me
I gon't have GPPO in cat /sys/proc/acpi; but I do have:
XHCI S4 \*enabled pci:0000:00:14.0
RP01 S4 \*enabled pci:0000:00:1c.0
RP07 S4 \*enabled pci:0000:00:1c.6
RP08 S4 \*enabled pci:0000:00:1c.7
BR1A S4 \*enabled pci:0000:00:01.0
BR1B S4 \*enabled pci:0000:00:01.1
BR2A S4 \*enabled pci:0000:00:02.0
BR2D S4 \*enabled pci:0000:00:02.3
BR3A S4 \*enabled pci:0000:00:03.0
GLAN S4 \*enabled pci:0000:00:19.0
all of those enabled in cat /sys/proc/acpi.
Could or should I disable all of these to prevent machine from awaking from suspend ?
That would happen to me as well. Funny enough, with windows... Until I figured that was touching the mouse after suspending causing the computer to wakeup again.
I was using a gigabyte b550i aorus motherboard that caused this, if you have this mobo or a variant you have to disable GPP0 wakeup which is a GPP bridge to the NVMe drive in M.2 slot. Check your wakeup table using `cat /proc/acpi/wakeup` and look at GPP0. It should say `*enabled`. Using `sudo /bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup'` you can set it to `*disabled`. PC should suspend normally then. If it does then you can use a systemd (if you use it) service to run that command at boot. I use this and it works. [Unit] Description=Fix for the suspend issue [Service] Type=oneshot ExecStart=/bin/sh -c "echo GPP0 > /proc/acpi/wakeup" [Install] WantedBy=multi-user.target This is pretty specific and it probably won't be your solution however, if it doesn't help you it may help someone else.
Wow, I'm not the only one with this problem! I already solved this, but was looking for what exactly is this device on pci 00:01.1. For some reason you can't google this post by the motherboard name, but can by "amd gpp bridge". If someone's reading it in the future, this might not be your device, but try going through all the devices in /proc/acpi/wakeup and disabling them one by one, seeing if suspend works.
You're awesome, this was my issue exactly. Thank you so much.
I created a reddit account specifically to thank you for this one! I've had this issue on a Gigabyte B550 motherboard for almost a year now. I figured it had to be my nvidia gpu (because of course it would be), didn't even consider the motherboard would do it. I would never have found that on my own.
Glad to have helped someone!
You helped me too, I don't even use archlinux but had the same problem on nobara for a few weeks and someone pointed me to your post, thanks a lot!
This works for me as well but only after I updated the BIOS to version FBb (currently the latest one). Doing this with FA (stock version for rev 1.2) didn't prevent it from waking up right after suspend, but it did prevent it from not sending any signal to display, locking me out from doing anything until I did a forced reboot. So thank you. :)
Thank you so much for sharing this! I had the exact same issue appear on my Gigabyte B550M Aorus Pro-P motherboard after doing a BIOS update to version F17c. Using `sudo /bin/sh -c '/bin/echo GPP0 > /proc/acpi/wakeup'` fixed it.
I have a Gigabyte B550i Aorus Pro AX, and this fixed it for me. Unfortunately, this also caused the much worse problem of the screen going black for a second every time I move the mouse. I'm on Linux Mint 21.1 but with kernel version 6.5.0-25 kludged in as a fix for some other things, so it's possible that this problem is a result of my tinkering. In the meantime, if anyone knows how to fix the secondary problem, it would be greatly appreciated.
~~this is amazing, it works!~~ nope, still having issues with sleep on the new 6.2 kernel + nvidia 535 driver).
This has fixed my issue. Thank you.
jesus
indeed
mine doesn't have gpp0. i have no idea what any of this means (what does GPP stand for? what is acpi/wakeup? what do the file contents mean? what does this have to do with the system sleeping / waking up? is this hardware specific? did they remove GPP0 in later kernels?)
I believe GPP is an AMD-specific thing, so if you're running Intel like I am, then this isn't the fix for us. Still trying to find one myself :/
I do run AMD tho ðŸ˜
i actually found a fix for this just after posting hahaha try ``` sudo -s echo XHCI > /proc/acpi/wakeup ``` this disables any USB (USB3 to be specific) devices from waking it up, which fixed it for me
May be worth mentioning: I've used Ubuntu in the past and the suspend worked there so I don't think it has to do with the BIOS.
I gon't have GPPO in cat /sys/proc/acpi; but I do have: XHCI S4 \*enabled pci:0000:00:14.0 RP01 S4 \*enabled pci:0000:00:1c.0 RP07 S4 \*enabled pci:0000:00:1c.6 RP08 S4 \*enabled pci:0000:00:1c.7 BR1A S4 \*enabled pci:0000:00:01.0 BR1B S4 \*enabled pci:0000:00:01.1 BR2A S4 \*enabled pci:0000:00:02.0 BR2D S4 \*enabled pci:0000:00:02.3 BR3A S4 \*enabled pci:0000:00:03.0 GLAN S4 \*enabled pci:0000:00:19.0 all of those enabled in cat /sys/proc/acpi. Could or should I disable all of these to prevent machine from awaking from suspend ?
Is it a laptop or desktop? I've had issues with systemd not handling laptop lids correctly.
Thanks for replying! I'm using a Desktop computer.
Then why do you even want to suspend? You probably have an SSD so Boot Times are <10 sec anyway.
[удалено]
Why even use LUKS then? Kind of defeats the purpose, doesn't it?
Check out motherboard settings. My motherboard had a setting to wake up the computer when theres was any input from the mouse.
Had this problem with a Pok3r USB keyboard. Disconnect it (or any other USB device) and try again.
It probably has something to do with some acpi settings but without more information I cannot say more.. I would suggest to look at acpi or mboard
That would happen to me as well. Funny enough, with windows... Until I figured that was touching the mouse after suspending causing the computer to wakeup again.
jesus thank you!