I am new in the software arena, so forgive me if I am missing something obvious. I have a BeagleBone Black. I have loaded Debian v3.8.13-bone37 from https://rcn-ee.net/deb/microsd/wheezy/bone-debian-7.3-2014-01-24-2gb.img.xz . I believe my flash slowly fills up without additional software being loaded.
After a fresh “flashing” of the eMMC a df -h shows:
I have tried executing apt-get clean, autoclean, remove and autoremove. Nothing seems to reduce the used flash. I have reflashed the eMMC with the above mentioned SD image three times. It has acted the same each time. I first noticed this problem when I tried to do an apt-get upgrade and received error messages of out of disk space. I then have reflashed two more times to make sure the problem is consistent.
I will perform your suggestions tonight. I took another troubleshooting step last night of loading the previous version (3.8.13-bone32). I am ashamed I did not think of it before posting. I have let it run all night and the older version has a more muted memory growth of 37 MB in ~12 hrs.
Your question: Did you enable systemd based boot or is this still the traditional one? I am sorry, I am not knowledgeable enough to answer your question (I have some google’ing to do). I am not aware of actively changing the booting process. I only copied the image to an SD card and then flashed the eMMC.
I will reload the newer (v3.8.13-bone37) system (from my PC harddrive) and post your suggestions tonight.
Okay, by default systemd isn't enabled on that particular image you
downloaded. It would be nice to catch what is causing the /var/log/
overload, do you have a specific usb device connected?
Ok I have done the pastebinits that you requested. Appears they sent ok. The memory usage was a bit more under control this flashing session, but still high and growing.
On usb devices connected, what started all this is trying to get the Asus USB-BT211 bluetooth dongle to work with the Beaglebone Black. I don’t really remember if the dongle was plugged in for my original email. The pastebinits that were sent, do not have the dongle plugged in. After I did the pastebinits, I did plug in the dongle and did not see any real change in the memory used or rate of memory used. Although with both the first email I sent and this email I have not installed the bluetooth or atheros modules.
On the bluetooth dongle subject, it appears I chose poorly from both experience and from the Google posts on this dongle. I did finally get the dongle to light up and pair with my phone after I did an aptitude install firmware-atheros. But, then the memory problem started rearing its head and I have not been back to that problem.
I appreciate your attention to this and am happy to provide anymore data or run any tests needed.
Ok I have done the pastebinits that you requested. Appears they sent ok.
The memory usage was a bit more under control this flashing session, but
still high and growing.
A little miss-communication. You kinda need to share the http links...
On usb devices connected, what started all this is trying to get the Asus
USB-BT211 bluetooth dongle to work with the Beaglebone Black. I don't
really remember if the dongle was plugged in for my original email. The
pastebinits that were sent, do not have the dongle plugged in. After I did
the pastebinits, I did plug in the dongle and did not see any real change in
the memory used or rate of memory used. Although with both the first email
I sent and this email I have not installed the bluetooth or atheros modules.
On the bluetooth dongle subject, it appears I chose poorly from both
experience and from the Google posts on this dongle. I did finally get the
dongle to light up and pair with my phone after I did an aptitude install
firmware-atheros. But, then the memory problem started rearing its head and
I have not been back to that problem.
I appreciate your attention to this and am happy to provide anymore data or
run any tests needed.
Hi Robert
I’ve (of course ) the same problem with my distro that is a 3.8.13-bone37
I did the bone35 kernel update and it worked perfectly. yet I’m wondering If I will have to “suffer” from any regression from 37 to 35 ?
Can someone tell me how to apply the built kernel on debian? I followed the above instructions to download from git and then compiled. I don’t know how to apply the built kernel. Thanks
Robert, when might you be releasing a bone40 flasher for the BBB? From this discussion it appears the bone37 has a memory leak (I’m using the bone37 flasher from your http://elinux.org/BeagleBoardDebian page.
Thanks, but I’m not really sure how to update from that. Can you advise me? The latest release on the beaglebone.org site is still the 5-14-2014 version with bone50.
Also, I can’t see in your github history that it is actually fixed, but I’ll be happy to test bone67 for you if you can tell me how to update it.