NOPUFF
September 2, 2022, 8:22am
1
When using the power key to shut down, we found the following two situations in our test：
[ 129.138500] tegradc 15200000.nvdisplay: blank - powerdown
[ 129.168443] PM: suspend entry 2022-07-08 10:06:21.215640696 UTC
[ 129.174018] PM: Syncing filesystems ... done.
[ 129.174025] PM: Preparing system for sleep (mem)
[ 129.197031] extcon-disp-state external-connection:disp-state: cable 48 state 0
[ 129.197038] Extcon AUX2(HDMI) disable
[ 129.221055] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 129.222347] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 129.232077] tegradc 15200000.nvdisplay: unblank
[ 129.237146] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 129.237456] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 129.244216] Parent Clock set for DC plld3
[ 129.254495] tegradc 15200000.nvdisplay: hdmi: tmds rate:319890K prod-setting:prod_c_hdmi_300m_600m
[ 129.256365] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 129.292324] extcon-disp-state external-connection:disp-state: cable 48 state 1
[ 129.292326] Extcon AUX2(HDMI) enable
[ 129.343495] tegradc 15200000.nvdisplay: unblank
[ 129.343600] tegradc 15210000.nvdisplay: blank - powerdown
[ 129.343698] tegradc 15220000.nvdisplay: blank - powerdown
[ 129.376933] tegradc 15200000.nvdisplay: blank - powerdown
[ 129.439923] extcon-disp-state external-connection:disp-state: cable 48 state 0
[ 129.439926] Extcon AUX2(HDMI) disable
[ 129.465317] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
[ 129.466971] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
[ 129.467547] tegradc 15210000.nvdisplay: blank - powerdown
[ 129.467641] tegradc 15220000.nvdisplay: blank - powerdown
[ 129.479168] tegradc 15200000.nvdisplay: blank - powerdown
[ 129.479193] tegradc 15200000.nvdisplay: unblank
[ 129.480003] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 129.480101] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 129.481923] Parent Clock set for DC plld3
[ 129.490149] tegradc 15200000.nvdisplay: hdmi: tmds rate:319890K prod-setting:prod_c_hdmi_300m_600m
[ 129.491565] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
[ 129.527161] extcon-disp-state external-connection:disp-state: cable 48 state 1
[ 129.527164] Extcon AUX2(HDMI) enable
[ 129.541758] tegradc 15200000.nvdisplay: sync windows ret = 247
[ 129.589336] Freezing user space processes ... (elapsed 0.004 seconds) done.
[ 129.593873] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 129.595520] PM: Suspending system (mem)
[ 129.595612] Suspending console(s) (use no_console_suspend to debug)
spe entering sc7
tegra_clks_suspend
tegra_clks_suspend done
adc_suspend done
pg_suspend: disp pd is on (ext_pg_is_on=false)
pg_suspend: dispc pd is on (ext_pg_is_on=false)
pg_suspend: pciex1a pd is on (ext_pg_is_on=false)
fmon_suspend done
WAKE_MASK[31:0] = 0x21000000
WAKE_MASK[63:32] = 0x0
WAKE_MASK[95:64] = 0x1ff200
TIER0[31:0] = 0x0
TIER0[63:32] = 0x0
TIER0[95:64] = 0x0
TIER1[31:0] = 0x0
TIER1[63:32] = 0x0
TIER1[95:64] = 0x100000
TIER2[31:0] = 0x21000000
TIER2[63:32] = 0x0
TIER2[95:64] = 0xff200
（2）When the Xavier AGX is not connected to the HDMI screen, the system does not have any output. After 10s, the system is powered off directly
For the second situation above, is it normal? Why is there no output when the HDMI screen is not connected? Without any output, does it mean that the system has not done any exit processing before power down，If the HDMI screen is not connected, what should we do to power down the system normally?
kayccc
September 4, 2022, 11:12pm
2
These issues happened your custom carrier board or on devkit.
Trumany
September 4, 2022, 11:49pm
4
Power off with pressing power button for 10s is a hardware power off triggered by PMIC.
NOPUFF
September 5, 2022, 3:02am
5
Thank you very much for your answer. We use devkit. The following is the detailed version information：
root@nvidia:/home/nvidia#cat /etc/nv_tegra_release
# R32 (release), REVISION: 6.1, GCID: 27863751, BOARD: t186ref, EABI: aarch64, DATE: Mon Jul 26 19:36:31 UTC 2021
root@nvidia:/home/nvidia# apt-cache show nvidia-jetpack
Package: nvidia-jetpack
Version: 4.6-b199
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.6-b199), nvidia-opencv (= 4.6-b199), nvidia-cudnn8 (= 4.6-b199), nvidia-tensorrt (= 4.6-b199), nvidia-visionworks (= 4.6-b199), nvidia-container (= 4.6-b199), nvidia-vpi (= 4.6-b19)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6-b199_arm64.deb
Size: 29376
SHA256: d67b85293cade45d81dcafebd46c70a97a0b0d1379ca48aaa79d70d8ba99ddf8
SHA1: 74d9cbdfe9af52baa667e321749b9771101fc6de
MD5sum: cd1b3a0b651cd214b15fa76f6b5af2cd
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Package: nvidia-jetpack
Version: 4.6-b197
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.6-b197), nvidia-opencv (= 4.6-b197), nvidia-cudnn8 (= 4.6-b197), nvidia-tensorrt (= 4.6-b197), nvidia-visionworks (= 4.6-b197), nvidia-container (= 4.6-b197), nvidia-vpi (= 4.6-b19)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6-b197_arm64.deb
Size: 29372
SHA256: acec83ad0c1ef05caf9b8ccc6a975c4fb2a7f7830cbe63bbcf7b196a6c1f350e
SHA1: 3e11456cf0ec6b3a40d81b80ca1e14cebafa65ff
MD5sum: 72b2b7b280793bd4abdabe0d38b08535
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
NOPUFF
September 5, 2022, 3:20am
6
Thank you very much for your answer
[ 67.633983] tegradc 15200000.nvdisplay: blank - powerdown
[ 67.634101] tegradc 15210000.nvdisplay: blank - powerdown
[ 67.634197] tegradc 15220000.nvdisplay: blank - powerdown
[ 67.656383] tegradc 15200000.nvdisplay: blank - powerdown
[ 70.885041] android_work: did not send uevent (0 0 (null))
[ 70.885241] tegra-xudc-new 3550000.xudc: ep 0 disabled
[ 70.924782] device usb0 left promiscuous mode
[ 70.924893] l4tbr0: port 2(usb0) entered disabled state
[ 71.116779] device rndis0 left promiscuous mode
[ 71.116893] l4tbr0: port 1(rndis0) entered disabled state
[ 75.444770] systemd-shutdow: 42 output lines suppressed due to ratelimiting
[ 75.452646] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 75.464973] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 75.487534] systemd-journald[2544]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 75.517289] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 75.536728] systemd-shutdown[1]: Unmounting file systems.
[ 75.553895] EXT4-fs (mmcblk0p1): re-mounted. Opts: data=ordered
[ 75.560511] systemd-shutdown[1]: All filesystems unmounted.
[ 75.560727] systemd-shutdown[1]: Deactivating swaps.
[ 75.560919] systemd-shutdown[1]: All swaps deactivated.
[ 75.561024] systemd-shutdown[1]: Detaching loop devices.
[ 75.563056] systemd-shutdown[1]: All loop devices detached.
[ 75.563167] systemd-shutdown[1]: Detaching DM devices.
[ 76.176546] therm-fan-est: shutting down
[ 76.176930] nvgpu: 17000000.gv11b gk20a_pm_shutdown:983 [INFO] shutting down
[ 76.177075] nvgpu: 17000000.gv11b gk20a_pm_shutdown:1014 [INFO] shut down complete
[ 76.177234] tegra-xusb 3610000.xhci: exiting ELPG
[ 76.182771] tegra-xusb 3610000.xhci: Firmware timestamp: 2020-09-11 16:55:03 UTC, Version: 60.09 release
[ 76.184006] tegra-xusb 3610000.xhci: exiting ELPG done
[ 76.185321] i2c i2c-4: Bus is shutdown down...
[ 76.185486] late_shutdown started
[ 76.185666] tegra-i2c 31e0000.i2c: Bus is shutdown down..
[ 76.185771] tegra-i2c c250000.i2c: Bus is shutdown down..
[ 76.185863] tegra-i2c 31c0000.i2c: Bus is shutdown down..
[ 76.185956] tegra-i2c 31b0000.i2c: Bus is shutdown down..
[ 76.186047] tegra-i2c 3190000.i2c: Bus is shutdown down..
[ 76.186141] tegra-i2c 3180000.i2c: Bus is shutdown down..
[ 76.186231] tegra-i2c c240000.i2c: Bus is shutdown down..
[ 76.186319] tegra-i2c 3160000.i2c: Bus is shutdown down..
[ 76.186449] Disabling non-boot CPUs ...
[ 76.217249] ras_fhi_disable: FHI 476 disabled
[ 76.218083] CPU1: shutdown
[ 76.219232] psci: CPU1 killed (polled 0 ms)
[ 76.257219] ras_fhi_disable: FHI 477 disabled
[ 76.257757] CPU2: shutdown
[ 76.257836] psci: CPU2 killed (polled 0 ms)
[ 76.289092] ras_fhi_disable: FHI 478 disabled
[ 76.290419] CPU3: shutdown
[ 76.291566] psci: CPU3 killed (polled 0 ms)
[ 76.337013] ras_fhi_disable: FHI 479 disabled
[ 76.337513] CPU4: shutdown
[ 76.338604] psci: CPU4 killed (polled 0 ms)
[ 76.368969] ras_fhi_disable: FHI 480 disabled
[ 76.369834] CPU5: shutdown
[ 76.370966] psci: CPU5 killed (polled 0 ms)
[ 76.396908] ras_fhi_disable: FHI 481 disabled
[ 76.397407] CPU6: shutdown
[ 76.397486] psci: CPU6 killed (polled 0 ms)
[ 76.424815] ras_fhi_disable: FHI 482 disabled
[ 76.425977] CPU7: shutdown
[ 76.427138] psci: CPU7 killed (polled 0 ms)
[ 76.428046] reboot: Power
I think it’s normal to have this information. I checked its power down timing. I think the system is receiving that POWER_BTN_N goes low, some pre-processing will be done before power-off, such as bus exit and clock shutdown, and then wait for 10s. Finally, the power is really off, pulling down MODULE_POWER_ON and VIN_PWR_ON, but I don’t know why it works after I uninstall python3.6. Before uninstalling python3.6, Why didn’t it work before if it wasn’t connected to the HDMI screen?
Which version of jetpack release is this?
Are you sure this is a reproduced behavior with just fresh jp4.6 image + installed python3.6?
NOPUFF
September 5, 2022, 6:22am
11
The phenomenon I tested here is like this. If I uninstall python3.6, I can power down normally
Hi,
Sorry that I may miss some comments here. Are we talking about the device cannot power down just because of python3.6 or we are just talking about a log is printed or not here?
These two are quite different …
NOPUFF
September 5, 2022, 6:38am
13
Sorry, I may not have described it clearly. Before uninstalling python3.6, I must connect to the HDMI screen to see the log output when powering down. After uninstalling python3.6, I can see the log output even if I do not connect to the HDMI screen, and I think the log after uninstalling python3.6 is correct
You are saying to observe the log on the UART console, right?
