On Wed, Jan 4, 2023 at 9:02 PM Varakh <varakh@xxxxxxxxx> wrote:
Not sure if it's related, but I also ran into suspend issues recently,
namely that my desktop machine wakes up directly after reaching
suspend.target, turning off displays for a short amount of time (like
two seconds) and then turning them on again. I tried network WoL
settings and BIOS settings. Downgrading kernel to 6.0.12 or linux-lts,
and even linux-git didn't work out either. I need to admit though, that
I don't use suspend very frequently, so that slipped for a while I guess.
What solved it for me was adding specific udev rules, e.g. to
/etc/udev/rules.d/10-wakeup.rules.
ACTION="" SUBSYSTEM=="pci", ATTR{vendor}=="0x1022",
ATTR{subsystem_device}=="0x1484", ATTR{subsystem_vendor}=="0x1022",
ATTR{power/wakeup}="disabled"
In my case, two PCI devices caused it. I hunted it down by changing all
devices to disabled in /proc/acpi/wakeup and enabling them one by one again.
Still not sure if that should happen at all, if it's wrong behavior of
hardware or of the kernel.
Cheers
On 02.01.23 15:08, SET wrote:
> Le lundi 2 janvier 2023 14:41:17 CET Paul Dann a écrit :
>> Have you tried configuring the kernel to use deep sleep instead?
>
> Yes, I have already tried 'mem_sleep_default=deep' in /etc/default/grub,
> followed by grub-mkconfig. It did not help at all.
>
>
>
>
Also this may be relevant: https://www.phoronix.com/news/AMD-s2idle-Check-FW
--
mike c
