From: "Stephan Enderlein (Freifunk Dresden)" <freifunk@ddmesh.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] batman-exp still has sometimes around 90% CPU load
Date: Sat, 25 Oct 2008 17:30:03 +0200 (CEST) [thread overview]
Message-ID: <24eb75fd8a048d4b908387e3bfbce04f.squirrel@webmail.ddmesh.de> (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
next reply other threads:[~2008-10-25 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 15:30 Stephan Enderlein (Freifunk Dresden) [this message]
2008-10-27 4:03 ` [B.A.T.M.A.N.] batman-exp still has sometimes around 90% CPU load Axel Neumann
2008-10-28 11:11 ` Stephan Enderlein (Freifunk Dresden)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24eb75fd8a048d4b908387e3bfbce04f.squirrel@webmail.ddmesh.de \
--to=freifunk@ddmesh.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.