> > > *Hi William:* > > *Doing nothing with the board. It is just sitting on the side connected > to +5V power and Ethernet.* > *So, for example, late last night (Central US time) I loaded > "bone-debian-8.1-lxqt-4gb-* > *armhf-2015-07-05-4gb.img"* > > *onto a trusted uSD card expanded the memory using gparted to the full > 16GB, and turned off the four blue* > > > *blinky lights. No other changes.* > > > *Then I went to bed.* > > *Reading syslog,* > > > *(Times are GMT, boot completion defined as systemd updating the time to > network time.* > > *the initial boot (completion) was at JUL 12, 05:09:27 * > > *the lab was quiet, lights off, nothing running.* > > > *The BBB automously rebooted at 08:25:33, 13:13:22, and 14:32:27* > *I am now rerunning with untouched reload of "bone-debian-8.1-lxqt-4gb-* > *armhf-2015-07-05-4gb.img"* > > > *Just load, install and boot. Talk to command line by SSH.* > *--- Graham*
OK. Well, my own personal feelings is that this could be related to systemd. Somehow. I have no proof so substantiate that. So, I'll work on the problem bottom to top. What I mean by this is that I'll start with a rootfs I know that works. In my case wheezy 7.8. I've got that running now with debian@beaglebone:~$ uname -a Linux beaglebone 4.1.0-rc8-bone9 #1 Tue Jun 16 23:45:22 UTC 2015 armv7l GNU/Linux. I'll let it sit and idle for a day or so. After that, I'll download and flash the Jessie image, install sysv, disable systemd. Then start the "test" over again. Oh and yeah if one of you can do me a favor and run one of your boards as is with *sudo cpufreq-set -g performance* and see if the problem clears up ? On Sun, Jul 12, 2015 at 12:35 PM, Graham Haddock <[email protected]> wrote: > Hi William: > Doing nothing with the board. It is just sitting on the side connected to > +5V power and Ethernet. > So, for example, late last night (Central US time) I loaded > "bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img" > onto a trusted uSD card expanded the memory using gparted to the full > 16GB, and turned off the four blue > blinky lights. No other changes. > > Then I went to bed. > > Reading syslog, > (Times are GMT, boot completion defined as systemd updating the time to > network time. > > the initial boot (completion) was at JUL 12, 05:09:27 > the lab was quiet, lights off, nothing running. > The BBB automously rebooted at 08:25:33, 13:13:22, and 14:32:27 > > I am now rerunning with untouched reload of > "bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img" > Just load, install and boot. Talk to command line by SSH. > > --- Graham > > == > > On Sun, Jul 12, 2015 at 2:22 PM, William Hermans <[email protected]> > wrote: > >> Anyway, guys, give me an idea of what you're doing on these boards. When >> you get random system reset, and I'll test here too. I have a couple free >> beaglebones I can run arbitrary tests on at the moment. >> >> On Sun, Jul 12, 2015 at 12:19 PM, William Hermans <[email protected]> >> wrote: >> >>> I've had this, or something similar happen to me a few times. When I did >>> apt-get update again right after, it succeeded. But I'm still not sure of >>> the cause. >>> >>> On Sun, Jul 12, 2015 at 11:48 AM, 'dl4mea' via BeagleBoard < >>> [email protected]> wrote: >>> >>>> If I look on one - but not the target "worst case" Beaglebone, I see >>>> only one package matching Robert's suggestion >>>> apt-cache search linux-image | grep ti | grep 4.1 >>>> linux-image-4.1.1-ti-r2 - Linux kernel, version 4.1.1-ti-r2 >>>> >>>> However, if I want to apt-get update on the two current worst case >>>> targets, I am getting >>>> >>>> Get:10 http://ftp.us.debian.org jessie-updates/non-free armhf Packages >>>> [20 B] >>>> Fetched 9247 kB in 20s (457 kB/s) >>>> W: Failed to fetch >>>> http://repos.rcn-ee.com/debian/dists/jessie/main/binary-armhf/Packages >>>> Hash Sum mismatch >>>> >>>> E: Some index files failed to download. They have been ignored, or old >>>> ones used instead. >>>> >>>> This system has installed >>>> uname -a >>>> Linux bb6c1f 4.1.0-rc8-bone9 #1 Wed Jun 17 00:05:43 UTC 2015 armv7l >>>> GNU/Linux >>>> >>>> Is this a temporary hickup or any other idea? >>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/lF1X1XINjDo/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
