Closed DYSpider13 closed 10 months ago
rbonghi
commented
10 months ago Hi @DYSpider13
How did you install the Jetpack 6.0? Looking at your log, you have L4T=36.0.0 when should be L4T=36.2.0
Can you please share the output from:
jtop --error-logThis script generates a file jtop-error.log ready to be attached to your issue.
Best, Raffaello
DYSpider13
commented
10 months ago Hi @rbonghi ,
It came from the vendor himself.
Here is the output of jtop --error-log
--------------------- PLATFORM -------------------------
Machine: aarch64
System: Linux
Distribution: Ubuntu 22.04 Jammy Jellyfish
Release: 5.15.122-tegra
Python: 3.10.12
-------------------- RAW OUTPUT ------------------------
------------------
/etc/nv_tegra_release:
# R36 (release), REVISION: 0.0, GCID: 34507387, BOARD: generic, EABI: aarch64, DATE: Wed Oct 4 16:41:43 UTC 2023
------------------
/sys/firmware/devicetree/base/model:
NVIDIA Jetson AGX Orin Developer Kit
------------------
/proc/device-tree/nvidia,boardids:
No such file or directory
------------------
/proc/device-tree/compatible:
nvidia,p3737-0000+p3701-0004nvidia,p3701-0004nvidia,tegra234
------------------
/proc/device-tree/nvidia,dtsfilename:
No such file or directory
------------------
I2C-0-0x50:
02 00 FE 00 00 00 00 00 00 00 00 00 00 00 00 00 ..þ.............
00 00 00 0A 36 39 39 2D 31 33 37 30 31 2D 30 30 ....699-13701-00
30 34 2D 35 30 30 20 46 2E 30 00 00 00 00 00 00 04-500 F.0......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 B7 0C 95 2D B0 48 31 34 32 32 38 32 ....·..-°H142282
32 30 36 31 36 33 33 00 00 00 00 00 00 00 00 00 2061633.........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 4E 56 43 42 00 00 4D 31 00 00 ......NVCB..M1..
00 00 00 00 00 00 00 00 00 00 00 00 B7 0C 95 2D ............·..-
B0 48 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 °H..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 81 ................
------------------
I2C-0-0x56:
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
------------------
I2C-1:
FAIL
------------------
I2C-2:
FAIL
------------------
I2C-7:
FAIL
Log from jtop 4.2.4I'm figuring out which type of Jetpack you have; It's something else compared to the official NVIDIA release. I also noticed another issue: the GPU is not detected, and I would like to figure out where is locate the GPU.
Can you share the output from this script? This script (I hope) helps me to understand and fix jtop :-)
import os
igpu_path = "/sys/class/devfreq/"
for item in os.listdir(igpu_path):
item_path = os.path.join(igpu_path, item)
if os.path.isfile(item_path) or os.path.islink(item_path):
# Check name device
name_path = "{item}/device/of_node/name".format(item=item_path)
if os.path.isfile(name_path):
# Decode name
with open(name_path, 'r') as f:
name = f.readline().rstrip('\x00')
# path and file
print("Path: {}".format(name_path))
print("{}".format(name))Thank you in advance
DYSpider13
commented
10 months ago @rbonghi
It seems that it is a special release from the vendor.
The script does not return anything, since the "/sys/class/devfreq/" is empty.
rbonghi
commented
10 months ago Thank you! I was with the same feeling. Looks like some devices are missing or located in some folders that I don't know
Have you tried to run:
sudo tegrastatsIf there is an output, can you share here?
Thank you again
DYSpider13
commented
10 months ago Here is the output of tegrastats:
01-08-2024 17:20:20 RAM 4072/30697MB (lfb 641x4MB) CPU [8%@729,8%@729,6%@729,6%@729,10%@729,9%@729,8%@729,9%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.312C tdiode@42.75C soc2@48.437C soc0@48.812C tj@51.312C tboard@42.5C soc1@49.875C VDDQ_VDD2_1V8AO 700mW/700mW VDD_GPU_SOC 3167mW/3167mW VDD_CPU_CV 487mW/487mW VIN_SYS_5V0 3505mW/3505mW
01-08-2024 17:20:21 RAM 4072/30697MB (lfb 641x4MB) CPU [0%@729,0%@729,1%@729,1%@729,1%@729,0%@729,0%@729,2%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.093C tdiode@42.75C soc2@48.406C soc0@49.031C tj@51.093C tboard@42.375C soc1@49.75C VDDQ_VDD2_1V8AO 600mW/650mW VDD_GPU_SOC 2924mW/3045mW VDD_CPU_CV 243mW/365mW VIN_SYS_5V0 3405mW/3455mW
01-08-2024 17:20:22 RAM 4071/30697MB (lfb 641x4MB) CPU [10%@729,11%@729,8%@729,8%@729,9%@729,8%@729,10%@729,11%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.25C tdiode@43C soc2@48.343C soc0@49.062C tj@51.25C tboard@42.375C soc1@49.781C VDDQ_VDD2_1V8AO 700mW/666mW VDD_GPU_SOC 3167mW/3086mW VDD_CPU_CV 487mW/405mW VIN_SYS_5V0 3600mW/3503mW
01-08-2024 17:20:23 RAM 4071/30697MB (lfb 641x4MB) CPU [4%@2188,26%@2188,2%@2188,3%@2188,1%@729,42%@729,1%@729,1%@729] EMC_FREQ @2133 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.531C tdiode@42.875C soc2@48.406C soc0@49C tj@51.531C tboard@42.375C soc1@49.687C VDDQ_VDD2_1V8AO 800mW/700mW VDD_GPU_SOC 3409mW/3166mW VDD_CPU_CV 974mW/547mW VIN_SYS_5V0 3800mW/3577mW
01-08-2024 17:20:24 RAM 4086/30697MB (lfb 641x4MB) CPU [9%@729,52%@729,7%@729,9%@729,6%@960,9%@960,7%@960,9%@960] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.312C tdiode@42.875C soc2@48.406C soc0@49.125C tj@51.312C tboard@42.375C soc1@49.781C VDDQ_VDD2_1V8AO 900mW/740mW VDD_GPU_SOC 3409mW/3215mW VDD_CPU_CV 974mW/633mW VIN_SYS_5V0 3900mW/3642mW
01-08-2024 17:20:25 RAM 4068/30697MB (lfb 641x4MB) CPU [3%@729,2%@729,3%@729,0%@729,3%@729,2%@729,4%@729,1%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.218C tdiode@42.875C soc2@48.437C soc0@48.875C tj@51.218C tboard@42.375C soc1@49.531C VDDQ_VDD2_1V8AO 700mW/733mW VDD_GPU_SOC 3167mW/3207mW VDD_CPU_CV 243mW/568mW VIN_SYS_5V0 3405mW/3602mW
01-08-2024 17:20:26 RAM 4069/30697MB (lfb 641x4MB) CPU [5%@729,1%@729,3%@729,0%@729,4%@729,3%@729,1%@729,4%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.375C tdiode@42.75C soc2@48.468C soc0@48.906C tj@51.375C tboard@42.375C soc1@49.625C VDDQ_VDD2_1V8AO 700mW/728mW VDD_GPU_SOC 2924mW/3166mW VDD_CPU_CV 243mW/521mW VIN_SYS_5V0 3405mW/3574mW
01-08-2024 17:20:27 RAM 4069/30697MB (lfb 641x4MB) CPU [11%@729,3%@729,3%@729,6%@729,3%@729,4%@729,3%@729,1%@729] EMC_FREQ @204 GR3D_FREQ @[0,0] NVENC off NVDEC off NVJPG off NVJPG1 off VIC off NVDLA0 off NVDLA1 off PVA0_FREQ off APE 174 cpu@51.093C tdiode@42.875C soc2@48.375C soc0@48.843C tj@51.25C tboard@42.375C soc1@49.843C VDDQ_VDD2_1V8AO 700mW/725mW VDD_GPU_SOC 2924mW/3136mW VDD_CPU_CV 243mW/486mW VIN_SYS_5V0 3405mW/3553mW
There might be something strange with your flashed Jetson.
I suggest working with your vendor to reflash your device to the official Jetpack 6.0 DP, while I figure out how to fix other bugs.
DYSpider13
commented
10 months ago That's my feeling too. I'll check with him. Thanks @rbonghi !
rbonghi
commented
10 months ago I close this issue, if you've again bug on your device with jtop feel free to reopen it.
Describe the bug
jetson-stats not working on JP6. Service is not starting due to some files (entire directory) missing:
/sys/kernel/actmon_avg_activity/mc_all
Actually, it is not even detecting that Jetpack is installed.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Expected behavior
Shoud give the usual output of jtop
Board
Output from
jetson_release -v:Log from jtop.service
Attach here the output from:
journalctl -u jtop.service -n 100 --no-pagerLog from jetson-stats installation
Attach here the output from:
sudo -H pip3 install --no-cache-dir -U jetson-stats