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.] Segmentation fault and log errors, expermimental Rev.756
Date: Thu, 25 Oct 2007 16:01:39 +0200 [thread overview]
Message-ID: <200710251601.39789.axel@open-mesh.net> (raw)
In-Reply-To: <47207A74.3060005@ddmesh.de>
Hello,
On Donnerstag 25 Oktober 2007, Freifunk Dresden wrote:
> Hi,
>
> I'm using experimental batmand Rev 756.
Just to be sure, Where does it show Rev 756 ? Because this reveision has never
been committed for batmand-exp. Do you mean rv752 ? Have you experienced this
with previous revisions?
> After a while the batmand is
> crashing. with "Segmentation fault". the crashing batmand is running on
> i386 (debian 2.6.22.1). All routers are running the same batmand version. I
> have not checked if also the batmand crashs on the routers.
can you check that? To be honest, I am usually not testing it a lot on i386.
I'll do so now. But on the mipsel devices which Iam mostly using for testing
it runs since weeks without problems.
>
> /usr/bin/batmand -g 1024/200 -a 104.61.0.0/16 -s 10.12.0.1
> --no-unreachable-rule --no-throw-rules --no-prio-rules
> --resist-blocked-send wlan0 bbs /t 1 /i /A bbc /t 1 /i /A -d 4
> >/tmp/batman-chrash
can you send me that batman-crash file, and even better also a core dump? (if
its to large send it private).
thanks,
axel
prev parent reply other threads:[~2007-10-25 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 11:13 [B.A.T.M.A.N.] Segmentation fault and log errors, expermimental Rev.756 Freifunk Dresden
2007-10-25 14:01 ` Axel Neumann [this message]
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=200710251601.39789.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.