Had a minute or two to try machinekit, loaded onto uSD. Unfortunately, it's
based on 3.8.x which doesn't support USB Hotplug so a non-starter. Also, it
froze after about 3 hours so I just shut it down for now.
On Tuesday, October 14, 2014 5:41:09 PM UTC-4, jmelson wrote:
On Monday, October
We still have the same issues with reboots as well. we have had to move our
project to bbw for now instead. the bbw with the same kernel and no reboots
for two weeks. The BBB reboots on an average og 1-2 times per 24 hours
independent of load.
No serial messages. No kernel messages, no oops. We
I've run into the BBB random reboot problem a while ago. We've eventually
found out the root cause is the USB-OTG detection. The USB-OTG periodical
probing actually caused the problem. Details and fix please the link below:
Hello,
I'm kind of a noob but willing to help investigate if needed.
I once had random reboots and traced it to an overheating problem. I don't
know if log files trap overheating messages or not. I had a blocked vent
and once it was cleared, no probem.
On a second point, my BBB is stable
On Monday, October 13, 2014 1:37:18 PM UTC-5, Greg Kelley wrote:
Mine is still resetting one to three times a day. I have moved both
processes I was running on it (CUPS and weewx) over to my RasPi so it is
just sitting idle except for CRON jobs. No events in serial debug logs,
just a
For the record, even with the watchdog package removed, my BBB rebooted on
me again after just 7 hours of uptime. :-(
Here http://pastebin.com/UwF2fsRB's the kernel config I used. Searching
for watchdog, there are only two entries. This is the one still enabled:
CONFIG_OMAP_REMOTEPROC_WATCHDOG=y
Did you check if memory usage is increasing ? Log file ?
Micka,
On Mon, Oct 13, 2014 at 10:49 AM, Sebastian H shos...@gmail.com wrote:
For the record, even with the watchdog package removed, my BBB rebooted on
me again after just 7 hours of uptime. :-(
Here http://pastebin.com/UwF2fsRB's the
I remember that once it was suggested to check the reboot reason from the
pmic. Definitely your issues are because of some hardware faults in the
pmic
13 Окт 2014 г. 12:55 пользователь Micka mickamus...@gmail.com написал:
Did you check if memory usage is increasing ? Log file ?
Micka,
On
@Micka:
I'm not sure how to check for increased memory usage as it's completely
unpredictable when it's going to reboot. Is there some kind of logging I
can enable for memory usage so it would get logged to my netconsole?
As for logs, the netconsole log has nothing before the reboot occurs (just
Searching around a bit, I wonder if an old u-boot version might have
anything to do with it? From what I can tell, I'm still using an u-boot
release from 2013.07 . Should I be updating this? If so, what would be the
safest way to do so?
In /boot/uboot/tools, I noticed a couple of scripts
Mine is still resetting one to three times a day. I have moved both
processes I was running on it (CUPS and weewx) over to my RasPi so it is
just sitting idle except for CRON jobs. No events in serial debug logs,
just a sudden reset and cold boot restart.
--
For more options, visit
The issue still happened even using the kernel compiled without any
watchdog support. The netconsole log didn't include any details. It just
rebooted again without any indication why. That was about 24 hours after
the last restart.
I still had the watchdog package installed (but with even the
I switched over from kernel 3.8.13 to 3.14.19-ti-r28 (compiled with
netconsole support) and after a little over 24 hours uptime, my BBB
rebooted without any entries in the netconsole log or any logs on the BBB
that I could find.
Did anyone have any luck in troubleshooting this issue any
Forget about claiming its a hardware issue. Because it is not. We've had
two beaglebone blacks for close to a year, and a half now. Both are rock
solid, running off barrel jack power, or USB( one of each ).
Ok well just stating facts that bbw is not rebooting and BBB is with the
same kernel
Short term, you can disable the hardware watchdog in kernel config. That
should temporarily fix your problem, and if it does not . . . bigger
mystery.
Long term, it would be good to figure out what is triggering the watchdog.
strace on the watchdog PID will not work - I tested this myself.
The
Well new and interesting discoveries on this problem.
Last night we set up 9 bbw as well as the blacks for control. during the
night all of the bbb has crashed at least once and none of the bbw. All
running the same kernel and software. 3.15.2-bone5.
This means that this is hw related on the bbb
I had a total of 5 resets yesterday one at 8am, 5pm, 9pm, 10pm, 11pm using
a switching power supply. Maybe I should go back to the cheapo power supply
as I was only resetting once or twice a day with that one. I'll wait and
see what Thomas comes up with before ordering the serial debug cable.
I didn't follow all the conversation, but I had a reboot several time every
day.
I found out that the bandwidth of the Network was too much for the
BeagleBone black and the watchdog decided to reboot the beagle every time.
On Wed, Sep 17, 2014 at 1:34 PM, Greg Kelley suekkel...@gmail.com wrote:
you have to activate the watchdog, normally it's not activated by default.
I'm talking about the software watchdog.
On Wed, Sep 17, 2014 at 3:29 PM, Thomas Olofsson skjor...@gmail.com wrote:
Micka that sounds interesting. which watchdog are you talking about? is
this a hardware watchdog on
*As stated i now have 9 black all rebooting and nine white not rebooting.
Same kernel. same network same network load. *
Forget about claiming its a hardware issue. Because it is not. We've had
two beaglebone blacks for close to a year, and a half now. Both are rock
solid, running off barrel
On Wed, Sep 17, 2014 at 2:18 PM, William Hermans yyrk...@gmail.com wrote:
As stated i now have 9 black all rebooting and nine white not rebooting.
Same kernel. same network same network load.
Forget about claiming its a hardware issue. Because it is not. We've had two
beaglebone blacks for
Update: I changed power supplies back to the 5v2a and removed wicd
yesterday at 3:20pm. Ran fine until 8:42am and reset after 16hrs. This
time, it didn't bring up eth0 and was unreachable. I pulled the power and
powered back up, booted normally. Interesting thing is that syslog only
shows the
One other note, current Debian distro that comes with BBB has ntpdate
installed. I have removed ntpdate and installed ntp in it's place.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
I just changed over to the Switching Power Supply and eth0 failed to come
up on boot. I hit the reset button and a reboot brought it up. So now it
seems there are eth0 issues as well as resets. Going from bad to worse.
--
For more options, visit http://beagleboard.org/discuss
---
You received
Greg we are experiencing the same issues as well with reset not bringing up
the eth0 interface. we were trying to do a hw watchdog that would reset the
board and when we press reset the eth0 interface fails as well. We are also
setting the interface config static in /etc/network/interfaces.
On Tue, Sep 16, 2014 at 11:42 AM, Thomas Olofsson skjor...@gmail.com wrote:
Greg we are experiencing the same issues as well with reset not bringing up
the eth0 interface. we were trying to do a hw watchdog that would reset the
board and when we press reset the eth0 interface fails as well. We
I plan to address this on the Ethernet issue in the next revision of the
board in the form of a GPIO based recovery mechanism that will allow SW to
reset the Ethernet PHY.
Gerald
On Tue, Sep 16, 2014 at 11:53 AM, Chris Morgan chmor...@gmail.com wrote:
On Tue, Sep 16, 2014 at 11:42 AM, Thomas
On Tue, Sep 16, 2014 at 11:53 AM, Chris Morgan chmor...@gmail.com wrote:
On Tue, Sep 16, 2014 at 11:42 AM, Thomas Olofsson skjor...@gmail.com wrote:
Greg we are experiencing the same issues as well with reset not bringing up
the eth0 interface. we were trying to do a hw watchdog that would
Well. That would be nice to have everywhere.
Gerald
On Tue, Sep 16, 2014 at 12:00 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Sep 16, 2014 at 11:53 AM, Chris Morgan chmor...@gmail.com wrote:
On Tue, Sep 16, 2014 at 11:42 AM, Thomas Olofsson skjor...@gmail.com
wrote:
Greg we
On Tue, Sep 16, 2014 at 12:56 PM, Gerald Coley ger...@beagleboard.org wrote:
Well. That would be nice to have everywhere.
It is all the bone branches, except in the new 3.14-ti tree... It
was one of those, I was just tagging a new release, oh crap, should
have added that. But was in a race to
Thank you!
Gerald
On Tue, Sep 16, 2014 at 12:59 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Sep 16, 2014 at 12:56 PM, Gerald Coley ger...@beagleboard.org
wrote:
Well. That would be nice to have everywhere.
It is all the bone branches, except in the new 3.14-ti tree... It
31 matches
Mail list logo
