> > *Yeah, I think the transition to linear irq domain (added at 3.18) made > cpsw* > * a little extra flaky. Plus the new omap_8250 serial driver is not > bug-free;* > * just found a flow control bug in the h/w last week.* > > * I've had ssh shells go sideways on occasion, but not with that kind of* > * regularity or effect.* > > * Like I said, the right diagnostic method is bisecting the kernel.* > * It's going to take a while (multiple days) if several hours are required > to* > * distinguish good from bad kernel.* > > * Regards,* > * Peter Hurley*
Hi Peter. "bisecting the kernel" is unknown to me. As in the meaning, But I was wondering if some sort of remote, and very verbose logging might not help ? Currently I'm in the process of reading / learning advanced Linux programming, and have all these crazy ideas of what we could do. Just not sure what to "trap" and exactly 100% how to trap it. On Sun, Jul 12, 2015 at 1:29 PM, Peter Hurley <[email protected]> wrote: > On 07/12/2015 03:35 PM, Graham Haddock 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. > > Yeah, I think the transition to linear irq domain (added at 3.18) made cpsw > a little extra flaky. Plus the new omap_8250 serial driver is not bug-free; > just found a flow control bug in the h/w last week. > > I've had ssh shells go sideways on occasion, but not with that kind of > regularity or effect. > > Like I said, the right diagnostic method is bisecting the kernel. > It's going to take a while (multiple days) if several hours are required to > distinguish good from bad kernel. > > Regards, > Peter Hurley > > -- > 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.
