Xavier suddenly cuts its own power

As it has been with the previous Jetson’s, MAX-N mode is intended for engineering development and not deployment, unless that is something you desire and your application can handle the TDP. For deployment we ship the 10/15/30W modes. You will get the best efficiency out of 15W mode, which is the default mode enabled after flashing JetPack-L4T. You can see the efficiency and power consumption measurements for inference in the DL benchmarks here:

[url]https://developer.nvidia.com/embedded/jetson-agx-xavier-dl-inference-benchmarks[/url]
[url]https://devblogs.nvidia.com/nvidia-jetson-agx-xavier-32-teraops-ai-robotics/[/url]

BTW, Xavier should consume 1.6W while in 15W mode, and around 3W while idle in MAX-N mode. But if you have run the ~/jetson_clocks.sh script, this will lock the clocks to maximum regardless of processing load, disabling the clock governors and DVFS.