Jetson nano rebooting every day at same time

Hi. I have a Jetson Nano that is rebooting at fixed times, after using the last reboot command I got this

reboot system boot 4.9.140-tegra Fri May 6 15:08 still running
reboot system boot 4.9.140-tegra Fri May 6 11:39 - 15:08 (03:29)
reboot system boot 4.9.140-tegra Fri May 6 08:37 - 15:08 (06:30)
reboot system boot 4.9.140-tegra Fri May 6 05:36 - 15:08 (09:31)
reboot system boot 4.9.140-tegra Fri May 6 02:35 - 15:08 (12:33)
reboot system boot 4.9.140-tegra Thu May 5 11:37 - 15:08 (1+03:30)
reboot system boot 4.9.140-tegra Thu May 5 08:36 - 15:08 (1+06:31)
reboot system boot 4.9.140-tegra Thu May 5 05:35 - 15:08 (1+09:33)
reboot system boot 4.9.140-tegra Thu May 5 02:33 - 15:08 (1+12:34)
reboot system boot 4.9.140-tegra Wed May 4 11:36 - 15:08 (2+03:32)
reboot system boot 4.9.140-tegra Wed May 4 08:34 - 15:08 (2+06:33)
reboot system boot 4.9.140-tegra Wed May 4 05:33 - 15:08 (2+09:34)
reboot system boot 4.9.140-tegra Wed May 4 02:31 - 15:08 (2+12:36)
reboot system boot 4.9.140-tegra Tue May 3 11:34 - 15:08 (3+03:34)
reboot system boot 4.9.140-tegra Tue May 3 08:32 - 15:08 (3+06:35)
reboot system boot 4.9.140-tegra Tue May 3 05:31 - 15:08 (3+09:36)
reboot system boot 4.9.140-tegra Tue May 3 02:30 - 15:08 (3+12:38)
reboot system boot 4.9.140-tegra Mon May 2 11:33 - 15:08 (4+03:35)
reboot system boot 4.9.140-tegra Mon May 2 08:31 - 15:08 (4+06:36)
reboot system boot 4.9.140-tegra Mon May 2 05:30 - 15:08 (4+09:37)
reboot system boot 4.9.140-tegra Mon May 2 02:28 - 15:08 (4+12:39)
reboot system boot 4.9.140-tegra Sun May 1 11:31 - 15:08 (5+03:36)
reboot system boot 4.9.140-tegra Sun May 1 08:29 - 15:08 (5+06:38)
reboot system boot 4.9.140-tegra Sun May 1 05:28 - 15:08 (5+09:39)
reboot system boot 4.9.140-tegra Sun May 1 02:26 - 15:08 (5+12:41)

For some reason, the Jeston is approximately rebooting at 2:30, 05:30, 08:30, and 11:30 every day and I want to know why? From the logs to me looks like that is some kind of error in the display but I am not sure. How can I get more information about this problem?

The log of the kernel before and after one of the boots is listed below.

May 1 07:31:27 omniflow-desktop kernel: [ 7386.607681] tegradc 15220000.nvdisplay: blank - powerdown
May 1 07:31:28 omniflow-desktop kernel: [ 7387.524295] fuse init (API version 7.26)
May 1 07:31:30 omniflow-desktop kernel: [ 7389.954031] tegradc 15200000.nvdisplay: blank - powerdown
May 1 07:31:30 omniflow-desktop kernel: [ 7390.006961] extcon-disp-state external-connection:disp-state: cable 48 state 0
May 1 07:31:30 omniflow-desktop kernel: [ 7390.006965] Extcon AUX2(HDMI) disable
May 1 07:31:30 omniflow-desktop kernel: [ 7390.028399] tegra_nvdisp_handle_pd_disable: Powergated Head1 pd
May 1 07:31:30 omniflow-desktop kernel: [ 7390.028859] tegra_nvdisp_handle_pd_disable: Powergated Head0 pd
May 1 07:31:30 omniflow-desktop kernel: [ 7390.029047] tegradc 15210000.nvdisplay: blank - powerdown
May 1 07:31:30 omniflow-desktop kernel: [ 7390.029054] tegradc 15220000.nvdisplay: blank - powerdown
May 1 07:31:30 omniflow-desktop kernel: [ 7390.057727] tegradc 15200000.nvdisplay: blank - powerdown
May 1 07:31:30 omniflow-desktop kernel: [ 7390.057740] tegradc 15200000.nvdisplay: unblank
May 1 07:31:30 omniflow-desktop kernel: [ 7390.058879] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
May 1 07:31:30 omniflow-desktop kernel: [ 7390.059027] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
May 1 07:31:30 omniflow-desktop kernel: [ 7390.061089] Parent Clock set for DC plld3
May 1 07:31:30 omniflow-desktop kernel: [ 7390.065239] tegradc 15200000.nvdisplay: hdmi: tmds rate:148500K prod-setting:prod_c_hdmi_111m_223m
May 1 07:31:30 omniflow-desktop kernel: [ 7390.066625] tegradc 15200000.nvdisplay: hdmi: get RGB quant from EDID.
May 1 07:31:30 omniflow-desktop kernel: [ 7390.066632] tegradc 15200000.nvdisplay: hdmi: get YCC quant from EDID.
May 1 07:31:30 omniflow-desktop kernel: [ 7390.164339] tegra_edid_read_block: remainder is 29 for the last 5 attempts. Assuming bad sink EDID and ignoring$May 1 07:31:30 omniflow-desktop kernel: [ 7390.168841] extcon-disp-state external-connection:disp-state: cable 48 state 1
May 1 07:31:30 omniflow-desktop kernel: [ 7390.168844] Extcon AUX2(HDMI) enable
May 1 07:31:30 omniflow-desktop kernel: [ 7390.169183] tegradc 15200000.nvdisplay: unblank
May 1 07:31:30 omniflow-desktop kernel: [ 7390.169195] tegradc 15210000.nvdisplay: blank - powerdown
May 1 07:31:30 omniflow-desktop kernel: [ 7390.169203] tegradc 15220000.nvdisplay: blank - powerdown
May 1 08:29:59 omniflow-desktop kernel: [ 0.000000] Booting Linux on physical CPU 0x0
May 1 08:29:59 omniflow-desktop kernel: [ 0.000000] Linux version 4.9.140-tegra (buildbrain@mobile-u64-4294) (gcc version 7.3.1 20180425 [linaro-7.3-20$May 1 08:29:59 omniflow-desktop kernel: [ 0.000000] Boot CPU: AArch64 Processor [4e0f0040]
May 1 08:29:59 omniflow-desktop kernel: [ 0.000000] OF: fdt:memory scan node memory, reg size 48,
May 1 08:29:59 omniflow-desktop kernel: [ 0.000000] OF: fdt: - 80000000 , 2c000000

please check if you set any cron jobs.

crontab -l

And actually, the log you provided does not help in tell what happened.

You can try to open UART console and see what would get printed during the time.

The difference is uart log will record some crash like kernel panic. But syslog will not record such event. And such event generally leads to system reboot.

Thanks for the idea but I don’t have any cronjob either in my user or the root.

Currently, I don’t have physical access to the jetson nano, is there any other way to get these logs?

Sorry, no.