Jetson Orin suddenly crashed. Error found when loading /etc/profile

[user133662]

I am getting this error message everytime I boot my Jetson Orin:

How can I fix this? What does that error mean?

[kayccc]

Are you using custom carrier board or devkit?
Have you tried to reflash your device with JetPack 5.0.2 SW?

[linuxdev]

I’ll add that if this is an SD card model, then it would be easy to post the actual “/etc/profile” file. Also, if there was an update before the failure, perhaps it was an incompatible library. Also, you should be able to still log in (in some cases) via serial console (the GUI files are not needed for consoles).

[user133662]

@kayccc I am using devkit. I am trying to avoid reflashing the Jetson.

@linuxdev I am posting the /etc/profile file below. There wasn’t any update. I was able to logged into the Jetson GUI normally by pressing Ctrl+Alt+F1 but everytime I reboot the device I get that error message.

# /etc/profile: system-wide .profile file for the Bourne shell (sh(1))
# and Bourne compatible shells (bash(1), ksh(1), ash(1), ...).

if [ "${PS1-}" ]; then
 if [ "${BASH-}" ] && [ "$BASH" != "/bin/sh" ]; then
   # The file bash.bashrc already sets the default PS1.
   # PS1='\h:\w\$ '
   if [ -f /etc/bash.bashrc ]; then
     . /etc/bash.bashrc
   fi
 else
   if [ "`id -u`" -eq 0 ]; then
     PS1='# '
   else
     PS1='$ '
   fi
 fi
fi

if [ -d /etc/profile.d ]; then
 for i in /etc/profile.d/*.sh; do
   if [ -r $i ]; then
     . $i
   fi
 done
 unset i
fi

[linuxdev]

I just noticed the relevance of the fact that the screenshot is of a GUI popup…you wouldn’t be able to see that popup or get a GUI screenshot if you couldn’t get into the GUI. Therefore, it seems that the problem is probably part of the startup of the GUI software and perhaps not “/etc/profile” (perhaps it is just a bad error message). Is it possible to show the dmesg output prior to starting the GUI, and the again after the GUI starts? Basically I’m trying to find what logged as a result of the GUI starting, and also to search for a similar error prior to the GUI starting. Knowing the timing of this showing up would make debugging much easier. It might be possible to find the line in “/etc/profile” is related to the GUI only.