TX2 module is freezed while I'm using it

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

Hello,

There is an issue as like this with Jetson TX2 module.

Jan 20 03:57:39 milab wpa_supplicant[1005]: wlan0: Failed to initiate sched scan
Jan 20 03:59:26 milab kernel: [18742.417867] CPU4: SError detected, daif=140, spsr=0x20000000, mpidr=80000102, esr=bf40c000
Jan 20 03:59:26 milab kernel: [18742.417870] CPU0: SError detected, daif=140, spsr=0x60000000, mpidr=80000100, esr=bf40c000
Jan 20 03:59:26 milab kernel: [18742.417872] CPU5: SError detected, daif=140, spsr=0x60000000, mpidr=80000103, esr=bf40c000
Jan 20 03:59:26 milab kernel: [18742.417875] CPU3: SError detected, daif=140, spsr=0x20000000, mpidr=80000101, esr=bf40c000
Jan 20 03:59:26 milab kernel: [18742.417916] CPU1: SError detected, daif=140, spsr=0x80000000, mpidr=80000000, esr=be000000
Jan 20 03:59:26 milab kernel: [18742.421911] **************************************
Jan 20 03:59:26 milab kernel: [18742.421912] Machine check error in JSR:MTS:
Jan 20 03:59:26 milab kernel: [18742.421913] Status = 0xb400000000000001
Jan 20 03:59:26 milab kernel: [18742.421914] Unknown error: 0x1
Jan 20 03:59:26 milab kernel: [18742.421914] Uncorrected (this is fatal)
Jan 20 03:59:26 milab kernel: [18742.421915] Error reporting enabled when error arrived
Jan 20 03:59:26 milab kernel: [18742.422919] ADDR = 0x27f8ae7a0
Jan 20 03:59:26 milab kernel: [18742.427950] **************************************
Jan 20 03:59:26 milab kernel: [18742.427952] **************************************
Jan 20 03:59:26 milab kernel: [18742.427952] Machine check error in JSR:MTS:
Jan 20 03:59:26 milab kernel: [18742.427953] Status = 0xb400000000000001
Jan 20 03:59:26 milab kernel: [18742.427954] Unknown error: 0x1
Jan 20 03:59:26 milab kernel: [18742.427955] Uncorrected (this is fatal)
Jan 20 03:59:26 milab kernel: [18742.427956] Error reporting enabled when error arrived
Jan 20 03:59:26 milab kernel: [18742.428960] ADDR = 0x27f8ae7a0
Jan 20 03:59:26 milab kernel: [18742.433995] **************************************
Jan 20 03:59:26 milab kernel: [18742.433998] **************************************
Jan 20 03:59:26 milab kernel: [18742.433998] Machine check error in JSR:MTS:
Jan 20 03:59:26 milab kernel: [18742.433999] Status = 0xb400000000000001
Jan 20 03:59:26 milab kernel: [18742.434001] Unknown error: 0x1
Jan 20 03:59:26 milab kernel: [18742.434002] Uncorrected (this is fatal)
Jan 20 03:59:26 milab kernel: [18742.434002] Error reporting enabled when error arrived
Jan 20 03:59:26 milab kernel: [18742.435006] ADDR = 0x27f8ae7a0
Jan 20 03:59:26 milab kernel: [18742.557774] **************************************
Jan 20 03:59:26 milab kernel: [18742.562563] **************************************
Jan 20 03:59:26 milab kernel: [18742.562563] Machine check error in JSR:MTS:
Jan 20 03:59:26 milab kernel: [18742.571516] Status = 0xb400000000000001
Jan 20 03:59:26 milab kernel: [18742.575429] Unknown error: 0x1
Jan 20 03:59:26 milab kernel: [18742.578561] Uncorrected (this is fatal)
Jan 20 03:59:26 milab kernel: [18742.582472] Error reporting enabled when error arrived
Jan 20 03:59:26 milab kernel: [18742.588688] ADDR = 0x27f8ae7a0
Jan 20 03:59:40 milab kernel: [18742.591822] **************************************
Jan 20 03:59:40 milab kernel: [18756.031309] Watchdog detected hard LOCKUP on cpu 1<4>[18756.036123] ------------[ cut here ]------------
Jan 20 03:59:40 milab kernel: [18756.040737] WARNING: at ffffffc000140808 [verbose debug info unavailable]
Jan 20 03:59:40 milab kernel: [18756.047516] Modules linked in: fuse xt_conntrack iptable_filter ip_tables uvcvideo videobuf2_vmalloc bcmdhd spidev pci_tegra bluedroid_pm

And it looks like these issues are very similar with following link.

Does it hardware issue?
And could I do the RMA process?

3

Which jetpack release are you using?

Is this NV devkit or you are not sure?

Is this always happened or intermittent?

4

We are using JetPack 3.3.
We’ve used same HW components and SW since 2020.
The carrier board is manufactured from Avidea.
300~400 products were manufactured and most products are working well.
and only 7 modules happen this problem.

5

It is working after re-installation of our application.
I’m not sure, it is HW issue or SW issue.
You can see the syslog.
syslog.zip (133.2 KB)

6

If only specific module would reproduce, please do the RMA.

7

Thank you for answer.

I have one more question about it.
Is there any screening solution that we could do by our side?
It can make the module will be sorted it has problem or not before shipment from factory.

8

Hi,

Honestly, the BSP you are using is too old to support. The real thing I would suggest is to upgrade your BSP here if you don’t want to do RMA.

Please be aware that even rel-32 is EOL. No need to mention the jetpack3 you are using there.

1 Like
9

Thanks for kindly support