Hello, I’m currently experiments regarding sleep and wake-up functionalities on Jetson ORIN devices. I used the following command to put the device into suspend mode: sudo bash -c \"echo mem > /sys/power/state\".
After the device entered sleep mode, I woke it up using two methods:
Sending a WOL magic packet to wake it up from the LAN network.
Pressing the power button to wake it up.
However, when I use the power button, the Jetson wakes up but immediately goes back to sleep again. Therefore, I have to press the power button once more for it to wake up correctly. When using the WOL magic packet, the Jetson wakes up correctly.
I used this command to Log the ‘demsg’ output: sudo dmesg | grep -i 'suspend\|power\|button\|sleep\|wake
my purpose is put the Jetson device in sleep mode from inside a docker container so that sudo systemctl suspend will not work. i used sudo bash -c \"echo mem > /sys/power/state\" for the replace solution.
@mehmetdeniz maybe you might know what’s going wrong?
To summarise, we use sudo bash -c "echo mem > /sys/power/state" to put the device in suspend. We then encounter an issue when doing a short button press to wake the system where it wakes up for about 5 seconds and then goes back to suspend. We then do a second short press and this time it’s fine.
Hi @mehmetdeniz , thank for the reply. I’ve read your attached Link. So that, as i understand, after suspended and press short button, i must send 0x000000ED to memory address 0x0c2f1080 to make the system wake correctly?
We are not use the “systemctl suspend” to suspend the system. instead, we used " sudo bash -c "echo mem > /sys/power/state"
But after the system suspended by sudo bash -c "echo mem > /sys/power/state and we pressed short button to wake it up, but it wake up for about 5 seconds and then goes back again. We must press 1 more time, then the system will wake correct
Hi, yeh the systemctl suspend can work normally in our side. But because we want to trigger the suspend event inside the container so that we used " sudo bash -c "echo mem > /sys/power/state " instead
We notice you are using container. This is not something we ever tested.
Thus, we suggest to use sudo systemctl suspend instead of that echo command.
That echo mem > /sys/power/state command directly controls through kernel which does not inform userspace services. This may lead to uncertain behavior.