Skip to contentSkip to conversation

batman-exp still has sometimes around 90% CPU load

B.A.T.M.A.N. Stephan Enderlein (Freifunk Dresden) 2 participants 3 messages Oct 25, 2008 – Oct 28, 2008

lore
Share & tools
lore
#0 lore raw

Hi,

I'm using batman-experimental rev1145. I test this release since 2 days. I found that a thread of batmand was consuming around 90% of cpu resources.

Mem: 15064K used, 15560K free, 0K shrd, 1152K buff, 5176K cached

CPU: 10.0% usr 90.0% sys  0.0% nice  0.0% idle  0.0% io  0.0% irq  0.0%
softirq
Load average: 0.98 1.00 0.97
  PID  PPID USER     STAT   VSZ %MEM %CPU COMMAND
 4464  1941 root     R     1216  3.9 84.1 /sbin/batmand -s 10.12.0.1  -a

10.12.10.16/28 -r 1 --t 63 --no-unreachable-rule --no-throw-rules
1151 1 root S 1216 3.9 0.0 /sbin/batmand -s 10.12.0.1 -a
10.12.10.16/28 -r 1 --t 63 --no-unreachable-rule --no-throw-rules
1941 1151 root S 1216 3.9 0.0 /sbin/batmand -s 10.12.0.1 -a
10.12.10.16/28 -r 1 --t 63 --no-unreachable-rule --no-throw-rules

it was not possibe to connect to the running batmand.
A call "batmand -c" just hangs without printing current parameters.

I had this error in previous revision where you disabled the debug task. Batmand was running without problems.Have you enabled the debug task again in current revision?

any idea or solution?
Regards
/Stephan

---------------------------------------
Dipl.Informatiker(FH) Stephan Enderlein
Freifunk Dresden

#1 lore raw

Hi,

On Samstag 25 Oktober 2008, Stephan Enderlein (Freifunk Dresden) wrote:
[...]

Quoted 3 lines

it was not possibe to connect to the running batmand.
A call "batmand -c" just hangs without printing current parameters.

grrr, I know that really ugly

Quoted 4 lines

I had this error in previous revision where you disabled the debug task. Batmand was running without problems.Have you enabled the debug task again in current revision?

Well, the debug functionality has never been disabled. It has just been moved to the main thread. Iam already thinking whether it makes sense to do the same with the tunnel thread - but not tonight. According to your debug output Iam sure its the tunnel thread. Just wondering why the same peace of code works since days on several mipsel and x86 devices here. Please test with r1146.

cheers,
axel

Quoted 15 lines

any idea or solution?
Regards
/Stephan

---------------------------------------
Dipl.Informatiker(FH) Stephan Enderlein
Freifunk Dresden

_______________________________________________
B.A.T.M.A.N mailing list
[email protected]
https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n

#2 lore raw

Hi,

I will try the release 1146. Just for information I use the following compile/linker switches:

CFLAGS = -Wall -O1 -DMEMORY_USAGE -DPROFILE_DATA -DDEBUG_MALLOC
LDFLAGS = -lpthread

Cheers,
Stephan