Tx2 crashing.

background:TX2 JetPack4.2
Repeat the problem steps:
1.Cloning TX2 image
sudo ./flash.sh -r -k APP -G backup.img jetson-tx2 mmcblk0p1
2.Restoring the Image to another tx2

sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1 .This operation failed, it doesn’t restore the image
sudo ./flash.sh -r jetson-tx2 mmcblk0p1 .it’s works, i can start up the tx2.
3.Modify core clock
sudo /usr/bin/jetson_clocks
4.tx2 crashing
After a while, tx crashed and restarted automatically.
i can’t find any error information in dmesg log.and the TX2 used for backup is fine
questions:
Is there any way to solve this problem?I have no idea where to start

Hi,

Are you sure about following these steps?
https://devtalk.nvidia.com/default/topic/1058035/jetson-tx2/how-to-clone-a-tx2-get-a-unit-that-won-t-boot-after-/post/5372325/#5372325

Could you share the error you see when you restored the image?

sudo ./flash.sh -r -k APP jetson-tx2 mmcblk0p1 is works.but tx crashed and restarted automatically.
i have following these steps.
I will now reinstall a clean system.Without my application environment.I will follow this step again

It would be better if you could share the error log too.

I don’t know where to see the error log.Dmesg or system debug serial?.
I tried both methods to look at the error log, but the log was blank during the crash.Only log of the boot process and normal operation.
Is there any way view this error log you need?

The serial should dump the boot log including the cboot+uboot+kernel.

Yes serial port has these logs, I have attached it.Is it what you need?
serial_2019-09-23_16-42-43.log (162 KB)

Hi,

Sep 23 16:43:30 opt-desktop kernel: [   17.938393] tegradc 15210000.nvdisplay: unblank
Sep 23 16:43:30 opt-desktop kernel: [   17.938406] tegradc 15220000.nvdisplay: blank - powerdown
Sep 23 16:43:32 opt-desktop kernel: [   19.835004] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Sep 23 16:43:32 opt-desktop kernel: [   19.835676] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sep 23 16:43:34 opt-desktop kernel: [   22.360361] fuse init (API version 7.26)
Sep 23 16:43:35 opt-desktop kernel: [   22.654298] tegradc 15210000.nvdisplay: unblank
Sep 23 16:43:35 opt-desktop kernel: [   22.654309] tegradc 15220000.nvdisplay: blank - powerdown
Sep 23 16:43:37 opt-desktop kernel: [   25.218370] serial-tegra c280000.serial: configured rate out of supported range by -0.2 %
Sep 23 16:43:37 opt-desktop kernel: [   25.231424] capability: warning: `MedicalScanner' uses 32-bit capabilities (legacy support in use)
Sep 23 16:43:49 opt-desktop kernel: [   37.086142] nvgpu: 17000000.gp10b             railgate_enable_store:343  [INFO]  railgate is disabled.
^C
opt@opt-desktop:~$

Where is the crash and reboot log? If it automatically reboots, it should at least have the next boot log.

I found the jetson of the two systems are different, the maximum clock is not the same,but I did use flash to clone it,
Can you tell anything by the frequency of this clock?

clone system jetson_clocks log:

opt@opt-desktop:~$ sudo /usr/bin/jetson_clocks --show
SOC family:tegra186 Machine:quill
Online CPUs: 0-5
CPU Cluster Switching: Disabled
cpu0: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0
cpu1: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c6=0 c7=0
cpu2: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c6=0 c7=0
cpu3: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0
cpu4: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0
cpu5: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0
GPU MinFreq=1517250000 MaxFreq=1517250000 CurrentFreq=1517250000
EMC MinFreq=40800000 MaxFreq=1866000000 CurrentFreq=1866000000 FreqOverride=1

original system jetson_clocks log:

opt@opt-desktop:~$ sudo /usr/bin/jetson_clocks --show
[sudo] password for opt:
SOC family:tegra186 Machine:quill
Online CPUs: 0-5
CPU Cluster Switching: Disabled
cpu0: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c7=0
cpu1: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c6=0 c7=0
cpu2: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c6=0 c7=0
cpu3: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c7=0
cpu4: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c7=0
cpu5: Online=1 Governor=schedutil MinFreq=2035200 MaxFreq=2035200 CurrentFreq=2035200 IdleStates: C1=0 c7=0
GPU MinFreq=1300500000 MaxFreq=1300500000 CurrentFreq=1300500000
EMC MinFreq=40800000 MaxFreq=1866000000 CurrentFreq=1866000000 FreqOverride=1
Can’t access Fan!
NV Power Mode: MAXN

Hi,

Are you cloning the image from different sku of tx2 modules? Could you check the serial number and sticker on those tx2 modules?

The two tx2 modules in the attachment are clone systems. They will crash. I took pictures of their stickers.The tx2 module of the original system was installed inside the machine, which need took a long time to see its serial number,i’ll post his serial number when I’m done

I cannot disassemble the device now. Can any software see the serial number of tx2 module?

Hi,

Sorry that the sitckers don’t have the information I want.
Is there any S/N sticker on the side of module?

Or could you share the flash log of these two modules? The flash script would read the eeprom and then use different dtb files if they are different sku.

I didn’t see the S/N sticker on the side of module.I can only share the flash log of this clone system.I can’t get the original system TX2 moudle.
1.Can I run the “sudo. /flash. sh-r-k kernel-dtb jetson-tx2 mmcblk0p1” command to get the log you need?
2.Can I use jetpack4.2 to reflash new system solve this problem? I guess I can’t apply for the original tx2 module which is normal
3.Where could S/N be?I have five tx2 modules waiting to clone the system because I cannot manually install the environment for each tx2 module

Hi,

We need to know the info for both tx2 modules. Only the cloned system is not enough for us to check.

1.Can I run the “sudo. /flash. sh-r-k kernel-dtb jetson-tx2 mmcblk0p1” command to get the log you need?

Please share the full flash log.

2.Can I use jetpack4.2 to reflash new system solve this problem? I guess I can’t apply for the original tx2 module which is normal

Yes, you can. But we will not know why your cloning failed.

i have reflash tx2 moudule with jetpack4.2.When I turned on the Max clock, it also crashed.Is there any problem with the tx2module I bought?or there’s something wrong with the way I use jetpack4.2?

serial_2019-09-25_10-44-05.log (451 KB)

I don’t get the exact error here.

Do you indicate that your system reboots by itself after you enable jetson_clocks?

opt@opt-desktop:~$ sudo /usr/bin/jetson_clocks  --show
SOC family:tegra186  Machine:quill
Online CPUs: 0-5
CPU Cluster Switching: Disabled
cpu0: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0 
cpu1: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c6=0 c7=0 
cpu2: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c6=0 c7=0 
cpu3: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0 
cpu4: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0 
cpu5: Online=1 Governor=schedutil MinFreq=2419200 MaxFreq=2419200 CurrentFreq=2419200 IdleStates: C1=0 c7=0 
GPU MinFreq=1517250000 MaxFreq=1517250000 CurrentFreq=1517250000
EMC MinFreq=40800000 MaxFreq=1866000000 CurrentFreq=1866000000 FreqOverride=1
Fan: speed=255
NV Power Mode: MAXN
opt@opt-desktop:~$ tail -f /[0000.252] I> Welcome to MB2(TBoot-BPMP)(version: 01.00.160913-t186-M-00.00-mobile-1b47d5d9)
[0000.260] I> bit @ 0xd480000
[0000.263] I> Boot-device: eMMC

yes,it reboots by itself after you enable jetson_clocks.Of course it will work for a while after jetson_clocks is enabled
That is all the information printed by serial port. When the machine crashes, the serial port will not work
Attached is the screenshot of jetpack I used

If only that module has this problem, I think it is a hardware issue. Could you try to change the dc power adapter of those devices and see if it is due to bad power supply?