System malfunction and power failure occurred during use

Robotics & Edge Computing Jetson Systems Jetson Xavier NX
,
1

When I was using the Jetson nx, I encountered a situation where the device suddenly lost power.

The partial kernel log entries are as follows:

Dec  6 11:33:01 blst-pz-desktop kernel: [  892.755377] imx586 2-001a: imx586_set_exposure: imx586_set_coarse_time(nor) 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.755390] imx586_set_coarse_time: coarse_time(419) = val(3826) * pixel_clock(864000000) / exposure_factor{1000000} / line_length(7872).max_coarse_time is 4342, min_coarse_time is 6 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.755395] imx586_get_integ_coarse_time_regs, 419
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.755786] imx586 2-001a: imx586_set_group_hold: imx586_set_group_hold start, val :0 !!------------------
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.800382] imx586 2-001a: imx586_set_group_hold: imx586_set_group_hold start, val :1 !!------------------
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.800639] imx586_set_exposure: val: 3880, hdr_en: 0, 0, mode: 1
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.800654] imx586 2-001a: imx586_set_exposure: imx586_set_coarse_time(nor) 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.800667] imx586_set_coarse_time: coarse_time(425) = val(3880) * pixel_clock(864000000) / exposure_factor{1000000} / line_length(7872).max_coarse_time is 4342, min_coarse_time is 6 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.800672] imx586_get_integ_coarse_time_regs, 425
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.801057] imx586 2-001a: imx586_set_group_hold: imx586_set_group_hold start, val :0 !!------------------
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.835204] imx586 2-001a: imx586_set_group_hold: imx586_set_group_hold start, val :1 !!------------------
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.835767] imx586_set_exposure: val: 3874, hdr_en: 0, 0, mode: 1
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.835786] imx586 2-001a: imx586_set_exposure: imx586_set_coarse_time(nor) 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.835800] imx586_set_coarse_time: coarse_time(425) = val(3874) * pixel_clock(864000000) / exposure_factor{1000000} / line_length(7872).max_coarse_time is 4342, min_coarse_time is 6 
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.835804] imx586_get_integ_coarse_time_regs, 425
Dec  6 11:33:01 blst-pz-desktop kernel: [  892.836235] imx586 2-001a: imx586_set_group_hold: imx586_set_group_hold start, val :0 !!------------------
Dec  6 11:33:02 blst-pz-desktop kernel: [  892.924845] soctherm: OC ALARM 0x00000001
Dec  6 11:33:03 blst-pz-desktop kernel: [  894.025371] soctherm: OC ALARM 0x00000001
Dec  6 11:33:04 blst-pz-desktop kernel: [  895.080236] soctherm: OC ALARM 0x00000001
Dec  6 11:33:05 blst-pz-desktop kernel: [  896.123082] soctherm: OC ALARM 0x00000001
Dec  6 11:33:06 blst-pz-desktop kernel: [  897.153125] soctherm: OC ALARM 0x00000001
Dec  6 11:33:06 blst-pz-desktop kernel: [  897.623118] FAN rising trip_level:245 cur_temp:45300 trip_temps[246]:125600
Dec  6 11:33:07 blst-pz-desktop kernel: [  898.156672] soctherm: OC ALARM 0x00000001
Dec  6 11:33:07 blst-pz-desktop kernel: [  898.743103] FAN cooling trip_level:9 cur_temp:45150 trip_temps[10]:0
Dec  6 11:33:08 blst-pz-desktop kernel: [  899.188276] soctherm: OC ALARM 0x00000001
Dec  6 11:33:09 blst-pz-desktop kernel: [  900.201518] soctherm: OC ALARM 0x00000001
Dec  6 11:33:10 blst-pz-desktop kernel: [  901.224278] soctherm: OC ALARM 0x00000001
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] Booting Linux on physical CPU 0x0
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] Linux version 4.9.253 (root@ubuntu) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #3 SMP PREEMPT Fri May 30 16:35:57 CST 2025
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] Boot CPU: AArch64 Processor [4e0f0040]
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: fdt:memory scan node memory, reg size 48,
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: fdt: - 80000000 ,  2c000000
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: fdt: - ac200000 ,  44800000
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: fdt: - 100000000 ,  180000000
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] earlycon: tegra_comb_uart0 at MMIO32 0x000000000c168000 (options '')
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] bootconsole [tegra_comb_uart0] enabled
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: reserved mem: initialized node ramoops_carveout, compatible id nvidia,ramoops
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: reserved mem: initialized node vpr-carveout, compatible id nvidia,vpr-carveout
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] OF: reserved mem: initialized node grid-of-semaphores, compatible id nvidia,gosmem
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] cma: Reserved 64 MiB at 0x00000000c2000000
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] On node 0 totalpages: 2033152
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000]   DMA zone: 7192 pages used for memmap
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000]   DMA zone: 0 pages reserved
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000]   DMA zone: 460288 pages, LIFO batch:31
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000]   Normal zone: 24576 pages used for memmap
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000]   Normal zone: 1572864 pages, LIFO batch:31
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] psci: probing for conduit method from DT.

Currently, the work I’m doing on the equipment is merely to activate two cameras, conduct AI recognition, and control the pan-tilt device for tracking.

However, during the tracking process, the device suddenly lost its response. Upon inspection, it was found that the device had shut down. Therefore, we had to power it off and then power it on again to restart it.

I am using a 12V power supply (currently the customer can only use it). Could you please tell me what caused this problem?

3

Hi darius-yuan,

Are you using the devkit or custom board for Xavier NX?
What’s the Jetpack version in use?

Could you share the full serial console log before and after the issue happens?

Do you have any reproduce steps for this issue?

4

The custom motherboard for Xavier NX is being used.

Currently, we are using version 4.6.1 of Jetpack.

During use, the device loses power and there are no fixed procedures.

I will share the complete kernel log

kern.log (64.3 MB)

5

Could you point out the lines when you hit post loss issue?

Dec  6 11:33:10 blst-pz-desktop kernel: [  901.224278] soctherm: OC ALARM 0x00000001
Jul 11 22:37:48 blst-pz-desktop kernel: [    0.000000] Booting Linux on physical CPU 0x0

Is above one?

Would you hit the similar issue if your don’t use camera?
Currently, I saw many imx586 related log printed.

6

It starts at line 532525 and ends at line 547786. The part I have shown is on line 547786.

Because we had previously debugged the imx586 driver and used these print statements, we did not encounter this problem during the debugging process. However, this issue only occurred when we assembled the entire set of equipment (including the camera, pan-tilt unit, and temperature sensor).

7 
Dec  6 11:33:05 blst-pz-desktop kernel: [  896.123082] soctherm: OC ALARM 0x00000001
Dec  6 11:33:06 blst-pz-desktop kernel: [  897.153125] soctherm: OC ALARM 0x00000001
Dec  6 11:33:06 blst-pz-desktop kernel: [  897.623118] FAN rising trip_level:245 cur_temp:45300 trip_temps[246]:125600
Dec  6 11:33:07 blst-pz-desktop kernel: [  898.156672] soctherm: OC ALARM 0x00000001
Dec  6 11:33:07 blst-pz-desktop kernel: [  898.743103] FAN cooling trip_level:9 cur_temp:45150 trip_temps[10]:0
Dec  6 11:33:08 blst-pz-desktop kernel: [  899.188276] soctherm: OC ALARM 0x00000001
Dec  6 11:33:09 blst-pz-desktop kernel: [  900.201518] soctherm: OC ALARM 0x00000001
Dec  6 11:33:10 blst-pz-desktop kernel: [  901.224278] soctherm: OC ALARM 0x00000001

I saw there’re multiple OC alarm before the power loss at line 5477XX.

Is the issue happening on specific device? (i.e only one or few devices hit the power loss issue)

Could you monitor if there’s any OC count when you are using the camera?

$ sudo su
# grep "" /sys/class/hwmon/hwmon*/oc*

Do you have the devkit to reproduce the similar issue?

8

Yes, this is a problem that only occurs on this specific device.

OK, I will monitor to see if there is an overclock value when using the camera.

The development kit did not detect this issue.

9

I am currently monitoring overclocking. So far, there has been no issue of power loss. However, the error message “soctherm: OC ALARM 0x00000001” has been constantly being reported, and I have noticed that /sys/class/hwmon/hwmon3/oc1_irq_cnt:0 keeps increasing. Will this cause any problems?

I will continue to observe it until it stops functioning.

image
image1710×848 67 KB

10

This count should not be increasing or there may be the OC throttling.

What’s the power mode you are using? Is it the same as the devkit?
Please compare the behavior between the devkit and your custom board.

11

We are using a 20W 6-core configuration, with a 12V voltage supply and a maximum current of 5A. Is this power supply setup acceptable?

Do you have any minimum voltage requirements for the 20W 6-core mode?

77f6e58ca618f32adb25b89067790de5
77f6e58ca618f32adb25b89067790de51903×808 21.2 KB

12

The OC1 event means the instantaneous high power usage.The threshold is 5A for 20W power mode to trigger instantaneous OC throttling, you could find more details here.
It means there’s pulse over this threshold so that you get the OC warning during you using the camera.

We suggest creating the custom power mode configuration for your use case. Or please check if you would hit the similar issue with MODE_20W_4CORE.

14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.