Originally Posted by pmul
Tried it again this morning, about 8 hours since the last try. SSH'd in first, then did the wake-up. It came up immediately. Damn. Is it because I SSH'd or is it because of the active usbNetwork? Updates to follow.
One or the other or both.
Neither of those work without the kernel being awake, so it had to wake up before you could see any response.
You can connect to the operator's console serial port and (receive only) monitor that while the kernel is asleep. The console port is re-initialized very early in both the boot sequence and in the wake-up sequence.