I have been running into an issue with the Jetson TX2. Here are the steps to reproduce it.
- The Jetson TX2 is off but physically connected to a monitor via HDMI and it is connected to my network via Ethernet.
- I power up the jetson and login via SSH. The monitor is still connected but I did not power it up.
- I power on the monitor (or select it’s HDMI input to the Jetson)
- My SSH session freezes. The Jetson no longer responds to pings and appears to be locked up.
- I hit the reset button on the Jetson and it comes back up and starts responding normally again (this time connected to my monitor)
The boot log shows the following:
qurrent pts/1 10.0.1.156 Thu Feb 20 22:21 - crash (00:02) runlevel (to lvl 5) 4.4.38-tegra Thu Feb 20 22:19 - 22:25 (00:06) nvidia ttyS0 Thu Feb 20 01:15 - crash (21:09) nvidia tty7 :0 Thu Feb 20 01:15 - crash (21:09)
I have reproduced this issue on 2 separate Jetson TX2s with very different hardware connections, they both exhibit the exact same behavior.
Ubuntu 18.04 does not reproduce the behavior. Although I am running Ubuntu 16.04 on the Jetsons so it is possible it is a bug in 16.04.
An SSH session is not required to cause the issue. If I am NOT connected via SSH and only sending pings I will see the pings start timing out.
I have looked all over on Google to try to find similar issues and I have found very little information about this. I suspect that the way we are using the Jetson is not common and therefore untested. One post I found indicated that it could be released to Ubuntu booting in low graphics mode.
Any help on this would be great.
Jonathan L Clark