Here is an update of some tests i ran in the past 24h with the following build:
routers used: dlink dir 601a and tplink wr703n in "ng" mode. (atheros)
My current AA DISTRIB_REVISION="r39154" mac80211 r39150 from openwrt trunk hostapd r39155 from trunk
From batman-adv i am using the following patches:
ls feeds/routing/batman-adv/patches/ 0001-batman-adv-fix-batman-adv-header-overhead-calculatio.patch
From d72756b97529b3c6afa08933216aaa912bb16ce6 Mon Sep 17 00:00:00 2001
From: Marek Lindner mareklindner@neomailbox.ch Date: Wed, 15 Jan 2014 20:31:18 +0800 Subject: [PATCH] batman-adv: fix batman-adv header overhead calculation
batman-adv/Makefile # $Id: Makefile 5624 2006-11-23 00:29:07Z nbd $
include $(TOPDIR)/rules.mk
PKG_NAME:=batman-adv
PKG_VERSION:=2014.0.0 BATCTL_VERSION:=2014.0.0 PKG_RELEASE:=1 PKG_MD5SUM:=8d58ecaede17dc05aab1b549dc09fa7d BATCTL_MD5SUM:=b0bcf29fef80ddcc33769e13f5937d0a
I tried to find any memory leaks that could be causing reboots and i was unable to find any after having compiled the build with batman-adv-header-overhead-calculatio.patch. Before this patch i did get reboots caused by the leak.
I keep monitoring memory usage with top, htop, ps and /proc/meminfo since i was not able to install valgrind due to lack of available flash memory given the size of the valgrind package.
Got some tips from here: http://blog.thewebsitepeople.org/2011/03/linux-memory-leak-detection
Additionally i ran iperf tests on both routers against each other to force them under heavy load during 24h: iperf -c <ip> -t 99999 -i 5
The mtu is 1560 for the adhoc.
After 24h i still had 6 mb of ram and above on both routers. Once i stopped the tests; the ram increased.
Dmesh and logread output nothing wrong and or errors.
No reboots happened during this time which leads me to conclude that the problem might not be all from batman-adv side or maybe not even at all or maybe only happens when in use with something very specific.
I would like to run a few more tests to be more sure about possible leaks but are there any other tools that someone might recommend ?
@ daniel What did you use to find the leak and or how did you troubleshoot it ?
On 01/26/2014 11:13 AM, Antonio Quartulli wrote:
On 26/01/14 17:07, Antonio Quartulli wrote:Can you explain in what
This is a patch to fix the memleak we were discussing about. This bug appeared with and it is meant to be applied on batman-adv-2014.0.0 (regardless of the openwrt revision).
sorry, bad copy/paste.
The patch is for batman-adv-2014.0.0 (I don't know what version you have in AA). It fixes the memleak bug that we were discussing about.