Orin nano Using the power key to make the OS enter suspend/resume bug

In Settings, the power key is configured for suspend/resume behavior.

Issue:
During the process of pressing the power key to suspend or resume, if the power key is triggered multiple times, the system may freeze.
This issue has been reproduced multiple times with a high occurrence rate.

Attached are logs for both cases:

  • With a Wi-Fi card installed
  • Without a Wi-Fi card installed

Request:
Please assist in blocking repeated power key triggers during the suspend/resume process to prevent system freezes.
Thank you.

suspend_resume_wifi-card_bug.log (8.5 KB)
suspend_resume_not_wifi-card_bug.log (30.1 KB)

The following is the OS-related message (Jetson 6.2):
lsb-release
nv_tegra_release
os-release
user_release_version
root@ubuntu:/home/ubuntu# cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION=“Ubuntu 22.04.5 LTS”

R36 (release), REVISION: 4.3, GCID: 38968081, BOARD: generic, EABI: aarch64, DATE: Wed Jan 8 01:49:37 UTC 2025

KERNEL_VARIANT: oot

TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
PRETTY_NAME=“Ubuntu 22.04.5 LTS”
NAME=“Ubuntu”
VERSION_ID=“22.04”
VERSION=“22.04.5 LTS (Jammy Jellyfish)”
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL=“https://www.ubuntu.com/
SUPPORT_URL=“https://help.ubuntu.com/
BUG_REPORT_URL=“https://bugs.launchpad.net/ubuntu/
PRIVACY_POLICY_URL=“https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
UBUNTU_CODENAME=jammy

Hi frank_weng,

Are you using the devkit or custom board for Orin Nano?

What does the freeze mean you mentioned here?
Do you mean you can not interact with the board at this moment and it could only be recovered through a HW reset?

Is the issue relating to if the WiFi Card is connected?

Dear Kevin

suspend/resume issue
Verified using the “Jetson Orin Nano Super Developer Kit”

dear Kevin

The OS is flashed by SDKManager.

There’s no power key on Orin Nano devkit.
Do you just short PWR/GND instead?

Please also help to clarify this.

And how about the failed rate?

Yes, pull a wire from the Pwr pin in the pin header on the public board to connect to the GND trigger.

This will happen regardless of whether you have a wifi card or not, the only difference is the logs that appear. I have attached the logs for you.

ㄐpost:6, topic:331872"]
There’s no power key on Orin Nano devkit.
Do you just short PWR/GND instead?
[/quote]
Yes, pull a wire from the Pwr pin in the pin header on the public board to connect to the GND trigger.

This will happen regardless of whether you have a wifi card or not, the only difference is the logs that appear. I have attached the logs for you.

If you verify 5 times, 3 of them will happen, which is a very high probability.

Okay, we will verify it locally.

Do you just use power key to enter into suspend? And use power key to wake up?

Or you’ve also tried to enter into suspend through sudo systemctl suspend? and wake up through power key?

dear Kevin

Yes, use the power pin on the edge of the board to suspend and resume。

Use sudo systemctl suspend to enter, and before the system completely enters suspend, use the power button to trigger it multiple times. Test if it happens twice.

If you see the following information in console log, it means that the system has entered into suspend mode. After entering into suspend mode, use the power key to trigger the system to wake up multiple times. The system wakes up normally after 3 tests.
"===console log======
adc_suspend done
WAKE_MASK[31:0] = 0x21000000
WAKE_MASK[63:32] = 0x0
WAKE_MASK[95:64] = 0x17f200
TIER0[31:0] = 0x0
TIER0[63:32] = 0x0
TIER0[95:64] = 0x0
TIER1[31:0] = 0x0
TIER1[63:32] = 0x0
TIER1[95:64] = 0x0
TIER2[31:0] = 0x21000000
TIER2[63:32] = 0x0
TIER2[95:64] = 0x7f200
"

Do you mean that you use the power button to wake it up before it enters suspend?

Do you mean the system would still wake up instead of freeze?

What’s the exact reproduce steps to cause it freeze?

Do you connect the DP display during the test?

Dear kevin

When the following message appears on the console, it means that the system has entered suspend mode.
------------Complete suspend final message-----
adc_suspend done
WAKE_MASK[31:0] = 0x21000000
WAKE_MASK[63:32] = 0x0
WAKE_MASK[95:64] = 0x17f200
TIER0[31:0] = 0x0
TIER0[63:32] = 0x0
TIER0[95:64] = 0x0
TIER1[31:0] = 0x0
TIER1[63:32] = 0x0
TIER1[95:64] = 0x0
TIER2[31:0] = 0x21000000
TIER2[63:32] = 0x0
TIER2[95:64] = 0x7f200

Yes, enter suspend completely and you can resume smoothly

1: Connect to debug console porting
2: Before the following message appears in comsole, press the power key multiple times, and

adc_suspend done
WAKE_MASK[31:0] = 0x21000000
WAKE_MASK[63:32] = 0x0
WAKE_MASK[95:64] = 0x17f200

Yes, connect to DP screen

Would you hit the issue if you press power key after it enters into suspend correctly? (i.e. wait until you see those messages)

Would you hit the issue if DP display disconnected?

Please also share the full log when the freeze issue occurs. (I can not identify them in original logs)
I suppose there should be the watchdog triggering reset due to the system hangs.

Yes, if you enter suspend completely, you can wake up, and it will not freeze even if you press the power key multiple times during the wake-up process.

The same problem occurs when the DP monitor is not connected

suspend_resume_bug.log (104.6 KB)
suspend_resume_bug.log contains
1: Suspend/resume returns normally without triggering the power key multiple times
2: Before entering suspend mode, the system freezes if the power key is pressed multiple times.

===The following other logs==
alternatives.log (28.6 KB)
kern.log (4.4 MB)
oem-config.log (44.5 KB)
Xorg.0.log (24.0 KB)
ubuntu-advantage.log (88.6 KB)
Xorg.0.old.log (28 KB)
syslog.zip (12.9 MB)

dear @KevinFFF

How is the progress of the suspend/resume issue?
I’d be grateful for your assistance.