System version: jetpack 5.1.2,
Dear nvidia,hi, in the recent period, my Jetson agx xavier will appear after a period of boot and running, it will automatically restart, the probability of occurrence will be relatively large, it is not sure what caused it for the time being, how do I check the log when it restarts abnormally, because the project has been deployed on the board, so it can not be re-flashed the system. I log in to the system via ssh, and the log displayed when rebooting abnormally is as follows:
Hi,
You may run sudo tegrastats to check the thermal condition. See if the system is in high temperature so it reboots.
Also if you have customization in rootfs, you can clone it out:
Flashing Support — Jetson Linux Developer Guide documentation
And then re-flash it to the same status. May try this method and see if it is more stable after re-flashing.
1 Like
Okay, thanks, I’ll try to re-flash first
@DaneLLL ,Hi,I re-refreshed the system according to your meaning, but there will still be a reboot and the kernel error in the screenshot above, I later tested and found that it was caused by us restarting the program used to capture MIPI camera for hardware encoding and decoding, our MIPI Camera driver is to use TP2854 to connect four AHD cameras, when testing, when constantly restarting a camera for hardware encoding, there will be no system restart and crash, But when I start four cameras at the same time for hardware encoding and decoding, three to five reboots will cause a system reboot.
My specific operation is as follows:
#!/bin/bash
delay=$1
gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! 'video/x-raw(memory:NVMM), format=UYVY, width=1920, height=1080, framerate=30/1' ! nvvidconv ! nvv4l2h264enc bitrate=2000000 ! h264parse ! qtmux ! filesink location=out0.mp4
sleep $delay
gst-launch-1.0 nvv4l2camerasrc device=/dev/video1 ! 'video/x-raw(memory:NVMM), format=UYVY, width=1920, height=1080, framerate=30/1' ! nvvidconv ! nvv4l2h264enc bitrate=2000000 ! h264parse ! qtmux ! filesink location=out1.mp4
sleep $delay
gst-launch-1.0 nvv4l2camerasrc device=/dev/video2 ! 'video/x-raw(memory:NVMM), format=UYVY, width=1920, height=1080, framerate=30/1' ! nvvidconv ! nvv4l2h264enc bitrate=2000000 ! h264parse ! qtmux ! filesink location=out2.mp4
sleep $delay
gst-launch-1.0 nvv4l2camerasrc device=/dev/video3 ! 'video/x-raw(memory:NVMM), format=UYVY, width=1920, height=1080, framerate=30/1' ! nvvidconv ! nvv4l2h264enc bitrate=2000000 ! h264parse ! qtmux ! filesink location=out2.mp4
exit 0
I use the GST tool to test, when I open four cameras at the same time, each camera opens the interval sleep 0, then there will be a system restart, but when I set the interval time to sleep 2, there will be no system restart, as long as each camera is turned on set a delay of more than 2 seconds will not trigger a restart, do you know what the reason is? Thank you.
Hi,
One idea from your description is that the power supply to simultaneously launching 4 cameras is insufficient. The sudden current may exceed limit, triggering instability and system reboots. It looks more like a constraint in hardware.
@DaneLLL ,Hi,thank you very much, then I am testing in the afternoon to see if there will be insufficient power supply if four cameras are turned on at the same time, resulting in a system restart. I don’t understand a little, is the system reboot caused by the kernel error in the screenshot above also caused by insufficient power supply? Because when I restart four cameras at the same time, there will be a reboot no kernel error and a reboot will appear …
Hi,
Rebooting without any error print looks to be an issue in hardware. Generally it shall have some error prints if something wrong in software. If you suspect it is a software issue, please try to reproduce it on developer kit. If it is present on developer kit, please share us the steps and we can check further.