Hi,
We are using Jetson AGX Xavier module with customized BSP (Based on L4T 32.4.3) with our custom Carrier Board.
We are observing Post Shutdown auto Reboot problem. We have checked EFM microcontroller and firmware, they look fine.
(1) set to the max power
On Linux,
$ sudo nvpmodel -m -0
(2) reproduction of the auto reboot problem
Case 1
*Run the check program.
*check the power consumption
12V 1.3A through 2min till the program stops
*immediately shutdowm the sysmtem
OS shutdown, status LEDs are still ON
Power IN => ON
Power ON => ON
*after a few minutes, OS reboots unexpectedly
Case 2
*Run the check program.
*check the power consumption
12V 1.3A through 2min till the program stops
*10 sec or more seconds after the finish of the check program,
shutdowm the sysmtem
OS shutdown, Power IN status LED is still ON
Power IN => ON
Power ON => OFF
*unexpected OS reboot DOES NOT HAPPEN
It seems GPU temperature is related to this.
We can see the current flowing to the Jetson/Stevie at shutdown.
After the successful shutdown, the current is 0.03A,
while post shutdown auto-reboot happens, the current
once goes up to 1A, then stays 0.31A, then reboot happens. Please help resolving the issue.
hello venkatraman.bhat,
please gather kernel level logs while the system reboot.
you may enable a terminal and running with $ dmesg --follow to catch the logs immediately.
note, Jetson AGX Xavier DevKit is taking 19V power supply.
Here is the dmsg log, will this gives any hint?
dmesg-1.log (77.6 KB)
hello venkatraman.bhat,
according to the logs, I’ve only see the normal kernel init procedure,
dose it report errors, when did the system rebooted?
I will ask the engg team to recheck that
Hi,
Can you please check this log?
dmesg-1.log (77.6 KB)
hello venkatraman.bhat,
besides some i2c no acknowledge failures while register camera node at the beginning.
I don’t see system level error to reboot the system.
[ 6.317508] tegra-i2c 3180000.i2c: no acknowledge from address 0x70
[ 6.317957] tegra-i2c 3180000.i2c: no acknowledge from address 0x70
there’re no related error messages from the kernel logs.
it looks kernel has boot-up successfully and display monitor power-off at 39sec.
for example,
[ 39.181994] tegradc 15200000.nvdisplay: unblank
[ 39.182005] tegradc 15210000.nvdisplay: blank - powerdown
could you please examine this from the hardware side.
for example, please check whether you have power shortage.
thanks
Hi,
We have checked for power shortage and seems no problem with that.
Here I am attaching few more logs.
dmesg –follow
Xorg.0.log
tegraststs
Will this help to diagnose any further?
dmesg-06012021 (77.2 KB)
tegrastats-06012021 (1.3 KB)
Xorg.0.log (17.7 KB)
hello venkatraman.bhat,
no, still cannot see anything suspect.
could you please setup serial console with J501, it’s micro-USB connector provides access to the UART console.
please gather the details to reproduce the failure.
Hi Another observation I found with 32GB module, we have around 4 LEDs to indicate Power IN, POWER ON and another 2 user LEDs for on board Micro controller and another for System Boot.
If we put the module in MODE_30W_ALL and powered off the board, the board turned off but all the 4 LEDs are ON even after power down(Power supply is connected so Power IN should be ON, but all other LEDs go off). Any suggestion for this behavior? LEDs work normal in other modes.
Attached is the block diagram, and LED position
