BeagleBone Black: v3.8.13-bone37 kernel flash slowly fills up

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:

Filesystem Size Used Avail Use% Mounted on
rootfs 1.7G 837M 753M 53% /
udev 10M 0 10M 0% /dev
tmpfs 50M 220K 50M 1% /run
/dev/disk/by-uuid/55f7d188-d284-4832-8d00-f68a649c8364 1.7G 837M 753M 53% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 100M 0 100M 0% /run/shm
/dev/mmcblk0p1 96M 72M 25M 75% /boot/uboot

With or without user activity the rootfs and /dev/disk/… grows to fill the available space. As shown:

Filesystem Size Used Avail Use% Mounted on
rootfs 1.7G 1.7G 0 100% /
udev 10M 0 10M 0% /dev
tmpfs 50M 220K 50M 1% /run
/dev/disk/by-uuid/55f7d188-d284-4832-8d00-f68a649c8364 1.7G 1.7G 0 100% /
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 100M 0 100M 0% /run/shm
/dev/mmcblk0p1 96M 72M 25M 75% /boot/uboot

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.

Help would be greatly appreciated.

Craig

Hi Craig,

It's /var/log/ but i've never seen it fill up so fast!

can you do a:

du -sh /var/log/* | pastebinit
dmesg | pastebinit

Did you enable systemd based boot or is this still the traditional one?

Yesterday i added a tweak so systemd only uses 8Mb's..
https://github.com/RobertCNelson/omap-image-builder/blob/master/scripts/chroot.sh#L368

sudo sed -i -e 's:#SystemMaxUse=:SystemMaxUse=8M:g'
/etc/systemd/systemd-journald.conf

Regards,

Hi Robert,

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.

Thank you for your attention,

Craig

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?

Regards,

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.

Regards,

Craig Mehan

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.

Regards,

Oops, sorry, I should have mentioned I am a newbie. After some googling:

http://paste.debian.net/79272/
http://paste.debian.net/79273/

Thank you for your help,

Craig Mehan

Ah crap.. i fixed that a year ago!

gen_ndis_query_resp: RNDIS_OID_GEN_RCV_NO_BUFFER

And then just unfixed it a couple weeks ago..
https://github.com/RobertCNelson/linux-dev/commit/3f61fc35d46cce0ee1a7543b666b2e9a99822b60

Regards,

So the fix is on the way.. (few hours of building..) to fix it now..

cd /opt/scripts/
git pull
./tools/update_kernel.sh --kernel v3.8.13-bone35

Then tomorrow just run:
cd /opt/scripts/
./tools/update_kernel.sh

Regards,

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 ?

cheers
Eric

Well, bone40 has been out with the /var/log/ overflow from driver fix.

Regards,

update done !
all fine :slight_smile:

Thank you for your quick reply :wink:
cheers
Eric

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

If your image is on the microSD, just stick it in and run
"./tools/install_kernel.sh"

If you've flashed it to the eMMC, well it's not that trival.

Regards,

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,
Brad

I'd like to get an image out today/tomorrow.. testing a few things..

But, you can upgrade the kernel today via:

cd /opt/script/
git pull
./tools/update_kernel.sh (it'll pull in bone40)

Regards,

I think this memory leak still exists in bone50.

Latest stable is bone67, so "update"..

I'll let you review:
https://github.com/RobertCNelson/bb-kernel/commits/am33x-v3.8

to find out when i actually fixed it..

Regards,

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.

Thank you.
James

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh

(reboot)

Regards,