NCP Suspend-to-Ram/rtcwake

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
1

Hello
I recently set up NextCloudPlus/NextCloudPi on a Rock64. Now, I wanted to use rtcwake to automatically shut down or suspend my server during night. I tested the states off, suspend-to-disk and suspend-to-ram. The first two did not work at all (-m disk was not recognized and when completly switching off, it did not wake). Probably they are not supported by the device. Suspend-to-Ram (-m mem) did work, however, after my Rock64 woke, I wasn’t able to communicate with it. Both the web interface and ssh are unreachable, then until i manually restart the device using the power connection.

This is a short section out of my system log that I think is important (I think it is when rtcwake was launched, the command was sudo rtcwake -m mem -s 300, if I remember the time correctly):

Sep  2 12:38:10 nextcloudplus kernel: [  337.609188] PM: suspend entry 2018-09-02 12:38:10.024848212     UTC
Sep  2 12:40:11 nextcloudplus kernel: [  337.609205] PM: Syncing filesystems ... done.
Sep  2 12:40:11 nextcloudplus kernel: [  337.626475] PM: Preparing system for sleep (mem)
Sep  2 12:40:11 nextcloudplus kernel: [  337.626873] Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep  2 12:40:11 nextcloudplus kernel: [  337.628926] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep  2 12:40:11 nextcloudplus kernel: [  337.630351] PM: Suspending system (mem)
Sep  2 12:40:11 nextcloudplus kernel: [  337.630364] Suspending console(s) (use no_console_suspend to debug)
Sep  2 12:40:11 nextcloudplus kernel: [  337.665345] phy phy-ff470000.usb3-phy.2: u3phy u2 power off
Sep  2 12:40:11 nextcloudplus kernel: [  337.665374] phy phy-ff470000.usb3-phy.3: u3phy u3 power off
Sep  2 12:40:11 nextcloudplus kernel: [  337.687914] ------------[ cut here ]------------
Sep  2 12:40:11 nextcloudplus kernel: [  337.687925] WARNING: at drivers/clk/clk.c:681
Sep  2 12:40:11 nextcloudplus kernel: [  337.687968] Modules linked in: xt_multiport iptable_filter poly_hash_ce ip_tables x_tables autofs4 uas usb_storage
Sep  2 12:40:11 nextcloudplus kernel: [  337.687971] 
Sep  2 12:40:11 nextcloudplus kernel: [  337.687986] CPU: 1 PID: 2835 Comm: rtcwake Not tainted 4.4.131-rk3328 #2
Sep  2 12:40:11 nextcloudplus kernel: [  337.687992] Hardware name: Pine64 Rock64 (DT)
Sep  2 12:40:11 nextcloudplus kernel: [  337.688001] task: ffffffc0e4a56200 task.stack: ffffffc0f5504000
Sep  2 12:40:11 nextcloudplus kernel: [  337.688020] PC is at clk_core_disable+0x28/0x130
Sep  2 12:40:11 nextcloudplus kernel: [  337.688031] LR is at clk_disable+0x34/0x48
Sep  2 12:40:11 nextcloudplus kernel: [  337.688040] pc : [<ffffff800894e0dc>] lr : [<ffffff800894e450>] pstate: 600001c5

Does anybody know how to solve this issue?
Thanks in advance for any help

2

you would probably be better off asking for help in the Armbian forums. The image is a bit old though and it might already be fixed.

Hopefully they have a more stable build system for the rock64 now and we will be able to build more current images. You should try to update the kernel packages from Armbian probably to see if this has been fixed.

3

I have now posted the question in the Armbian forums, let’s see if it helps. I also checked out the Armbian changelog and found nothing that concerns my issue.