I probably won’t be able to answer, but it is important to know if this is the AGX Orin developer’s kit from NVIDIA, or if it is a module and third party carrier board. The carrier board changes device tree requirements, and often odd behavior is from using the wrong device tree. You’d also want to include which L4T release (you can use “head -n 1 /etc/nv_tegra_release”). There is a possibility that if this is too old of a release (and Orin is new enough that most previous releases are too old even if relatively new), that there’ll just be a suggestion to flash the newer release and see if the problem still occurs.
Note that often serial console will still have logging output even when the rest of the machine is failing. Serial console has very few driver requirements, and so it might still output an error message when network and other parts are failing. The more interesting part is that if serial console does not output logging during that time, then this too is an important clue since a failing serial console requires a more severe error. If you could get a serial console full boot log I’m sure someone will find that useful. If you could get a serial console log before and during and after the error, then that would be a gold mine of information, so you might try to get a serial console log all the way from power on to past that error.
@WayneWWW I connected a different PC to the AGX Orin, but I see no output on the 4 ports that are detected. Set the baud to 115200 without any luck. Is there a setting on the jetson to enable serial console ? @linuxdev I’m using the nvidia devkit. The output of “head -n 1 /etc/nv_tegra_release ” is
# R35 (release), REVISION: 4.1, GCID: 33958178, BOARD: t186ref, EABI: aarch64, DATE: Tue Aug 1 19:57:35 UTC 2023