From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batman-exp still has sometimes around 90% CPU load
Date: Mon, 27 Oct 2008 06:03:18 +0200 [thread overview]
Message-ID: <200810270503.18516.axel@open-mesh.net> (raw)
In-Reply-To: <24eb75fd8a048d4b908387e3bfbce04f.squirrel@webmail.ddmesh.de>
Hi,
On Samstag 25 Oktober 2008, Stephan Enderlein (Freifunk Dresden) wrote:
[...]
>
> 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
>
> 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
>
> any idea or solution?
> Regards
> /Stephan
>
>
> ---------------------------------------
> Dipl.Informatiker(FH) Stephan Enderlein
> Freifunk Dresden
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
next prev parent reply other threads:[~2008-10-27 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 15:30 [B.A.T.M.A.N.] batman-exp still has sometimes around 90% CPU load Stephan Enderlein (Freifunk Dresden)
2008-10-27 4:03 ` Axel Neumann [this message]
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=200810270503.18516.axel@open-mesh.net \
--to=axel@open-mesh.net \
--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.