You are not logged in.
Hi,
I encountered a strange issue with suspend to ram while setting up a new small home server with an Asrock Q1900-ITX board. If I suspend the system and wake it within a few seconds everything works fine. However, if I wait a couple of minutes or even more, instead of resuming the system it takes a few seconds to think and then it reboots instead. It doesn't matter whether I resume via the power switch or with wake on lan. I tried several bios settings, the stock kernel as well as LTS and I even used an Ubuntu Live CD to check whether this is an arch issue. However, with the latter the system does not reboot it simply gets stuck. Power is on but nothing happens.
What is strange though that it works on all these platforms if there are only a few seconds between suspend and resume. Any ideas?
Best regards,
Karsten
Offline
Just to put some more numbers here. Apparently, waking up after 1 minute still works, 2 minutes doesn't. Is there any way to debug this further?
Whenever it does work I get messages like these.
ata3: softreset failed (device not ready)
ata4: softreset failed (device not ready)
However, everything seems to work as expected.
Offline
I just bought an Asrock Q1900-ITX last month. It seems to have issues when rebooting that may be part of your problem.
Overall the motherboard specs seem pretty good. It has 2x sata3, 2x rear usb3 ports, and an on board usb3 connector. The processor is an integrated quad core Celeron CPU J1900 @ 1.99GHz. I have added a 4G stick of memory, a 10/100 usb2 Ethernet adapter, and a 64 G usb3 thumb drive. It runs a headless setup of Arch's Simple stateful firewall; replacing my ancient WRT54GL Linksys router/firewall. I power it using an old 20 pin picoPSU plugged into the 24 pin power connector. It only draws 10 watts of power at the wall outlet.
There are a number of posts I found on the booting issue, including patches in the kernel mailing list, so hopefully better support will come soon. For me booting is at least consistent. I use the efi boot with csm bios option enabled. If I do a systemctl reboot the computer hangs after the grub loading kernel, initrd messages. Press the reset button and booting is successful. If I do a
systemctl poweroff followed by a wake-on-lan the computer will boot normally.
I thought at first the booting issue was because I had /boot/efi/EFI/boot/bootx64.efi and /boot/efi/EFI/arch_grub/archx64.efi files and the bios couldn't deal with that configuration; the bios would loose the 1st boot drive setting. I just went with only the /boot/efi/EFI/boot/bootx64.efi but still have the booting problem.
To get the wol function working I think I had to change the legacy options in the bios. Sorry, I can't remember exactly what they were. After getting the wol working I tested the suspend to ram which worked fine. I am not sure is these legacy options would fix your suspend problems but maybe. Could you check what journalctl -b -1 shows after you try to suspend to ram. Also do you run the nfs client? I had a problem with suspend on another computer that editing the nfsmount.conf file fixed.
Offline
I should have replied earlier, but I kinda lost track of this. Apparently, the reason for my problems was an incompatibility between the Q1900-ITX and the memory I bought. I changed to another brand and everything has been working smoothly for the past months now. Lesson learned: Even if memtest completes successfully, there might still be memory related issues left. ;-)
Offline