> 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 <https://www.google.com/url?q=https%3A%2F%2Frcn-ee.com%2Frootfs%2Fbb.org%2Ftesting%2F2018-01-07%2Fstretch-console%2Fbone-debian-9.3-console-armhf-2018-01-07-1gb.img.xz&sa=D&sntz=1&usg=AFQjCNHgsyeX9jx-FOzpFQLo-VtlG1UklA> On Friday, January 12, 2018 at 2:01:35 AM UTC+8, Graham wrote: > > What hardware are you running? > Where is power supply connected? > Which specific Stretch image are you running? > > Thanks, > --- Graham > > == > > On Thursday, January 11, 2018 at 12:23:15 AM UTC-6, Luther Goh Lu Feng > wrote: >> >> 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 >> >> On Thursday, January 11, 2018 at 11:48:45 AM UTC+8, Luther Goh Lu Feng >> wrote: >>> >>> 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 >>> >> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/3f60ced7-6fcd-4f46-9919-5f5f7f8ccc5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
