So . . .
ioctl(3, RTC_WIE_ON or RTC_WKALM_SET, {enabled=1, pending=0, {tm_sec=56, tm_min=20, tm_hour=5, tm_mday=4, tm_mon=4, tm$
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), …}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f0b000
write(1, “rtcwake: wakeup from “mem” using”…, 71) = 71
nanosleep({0, 10000000}, NULL) = 0
sync() = 0
open("/sys/power/state", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=4096, …}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb6f0a000
write(4, “mem\n”, 4****
rtcwake never finishes writing to /sys/power/state, which mean the file is never closed which means I bet the contents are not “mem”.
william@beaglebone:~$ cat /sys/power/state
freeze standby mem disk
Uh yeah, that looks borked . . .my first guess, this never gets changed, then rtcwake sees “freeze” and proceeds no further. Thus we’re stuck in la la land while the board sleeps forever.
Here is what I think I’ve noticed so far. Right after the board suspends to memory, I press the reset button on the beaglebone, and nothing happens. But after one minute, the reset button seems to work fine. Maybe I was not pressing the button just right, but I attempted several times before finally the board went into reset.
Darren, do you think you can get an strace of rtcwake from your 3.14.x system ? If you can, then we should be able to compare the differences and probably figure out how to fix this mess. Just remember to use the -o(oh) option with strace to sent stdout to a file.
root@beaglebone:/home/debian# strace -o ./test.txt rtcwake -m mem -s 60
is how I’ve been running strace . . .