Console image stability affected by uninitiated reboot?

I am running a stretch console image[1] on a BBB industrial. After letting it run for about 24 hrs, the system rebooted. Inspecting syslog[2], it doesnt seemed to explain the reboot.

The only thing that could be suspicious is cron.hourly. Any thoughts?

Jan 10 02:08:56 beaglebone systemd[1]: Starting Cleanup of Temporary Directories…
Jan 10 02:08:56 beaglebone systemd[1]: Started Cleanup of Temporary Directories.
Jan 10 02:17:01 beaglebone CRON[992]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 7 22:19:43 beaglebone systemd-fsck[271]: rootfs: clean, 15515/54208 files, 88361/216576 blocks
Jan 7 22:19:43 beaglebone systemd[1]: Started Create Static Device Nodes in /dev.
Jan 7 22:19:43 beaglebone systemd[1]: Starting udev Kernel Device Manager…
Jan 7 22:19:43 beaglebone systemd[1]: Started Remount Root and Kernel File Systems.
Jan 7 22:19:43 beaglebone systemd[1]: Reached target Local File Systems (Pre).
Jan 7 22:19:43 beaglebone systemd[1]: Starting udev Coldplug all Devices…
Jan 7 22:19:43 beaglebone systemd[1]: Reached target Local File Systems.
Jan 7 22:19:43 beaglebone systemd-udevd[287]: Network interface NamePolicy= disabled on kernel command line, ignoring.
Jan 7 22:19:43 beaglebone systemd[1]: Starting Raise network interfaces…
Jan 7 22:19:43 beaglebone systemd[1]: Starting Flush Journal to Persistent Storage…

[1] https://rcn-ee.com/rootfs/bb.org/testing/2018-01-07/stretch-console/bone-debian-9.3-console-armhf-2018-01-07-1gb.img.xz
[2] https://gist.github.com/elfgoh/1f92b70c79555494f2053797ece1b936

On a related note, I will also be curious of the longest uptimes that you have for images based on Stretch. I have created images based on a console image in Sep last year, and I realised recently that these images typically dont have uptimes more than a week. Most will reboot once every few days. Thanks!

In the setup listed below, the BBB is only connected to a power supply and nothing else

What hardware are you running?
Where is power supply connected?
Which specific Stretch image are you running?

Thanks,
— Graham

First plug in a usb-serial adapter and log the serial port. When it
reboot's U-Boot will dump the "reset" flag on startup so please share
that with us.

Afterwards, downgrade to v4.4.x: and you should see the old reliability..

sudo /opt/scripts/tools/update_kernel.sh --ti-channel --lts-4_4

Regards,

What hardware are you running?

Beaglebone Black Industrial

Where is power supply connected?
5V 1.25 A power supply

Which specific Stretch image are you running?
https://rcn-ee.com/rootfs/bb.org/testing/2018-01-07/stretch-console/bone-debian-9.3-console-armhf-2018-01-07-1gb.img.xz

Afterwards, downgrade to v4.4.x: and you should see the old reliability…

Is 4.9 known to be unstable? I see it listed as long term stable on kernel.org

sudo /opt/scripts/tools/update_kernel.sh --ti-channel --lts-4_4

So above command is more preferable than installing linux-image-4.4.110-ti-r142 using apt?