From: Sven Eckelmann <sven.eckelmann@gmx.de>
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 gateway lock ups
Date: Mon, 8 Sep 2008 09:08:28 +0200 [thread overview]
Message-ID: <200809080908.31586.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <5635aa0d0809050801k1c5f0bd5wa366574efedd910f@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1742 bytes --]
On Friday 05 September 2008 17:01:24 Outback Dingo wrote:
> [...]
> http://www.pastebin.ca/1194874
>
> pertinent info
> dmesg | grep 'batgat loaded'
> batgat: [init_module:96] batgat loaded rv1025
> uname -a
> Linux nightwing 2.6.23.16 #16 Tue Apr 22 20:00:17 ART 2008 mips unknown
> root@nightwing:~# batmand -v
> WARNING: You are using the unstable batman branch. If you are interested in
> *using* batman get the latest stable release !
> B.A.T.M.A.N. 0.3-beta (compatibility version 5)
> [..]
Thx for your report. I looked a little bit at the the call stack but it is
really hard to guess the functions when you don't have the symbol table. It
looks a little bit like most of the functions are kernel thread/scheduling
related. Only one function <c00c8650> is from a module. Can you please send
the /proc/modules file so we can find in which module it is so we can check if
it could be a batgat related. Further investigations could be done by checking
the symbols of batgat.ko with nm - but this would not help very much because
it is stripped down. Maybe someone else has a good idea.
Now to something you said on the nightwing mailing list:
> i think the version of batgat being used has a bug as confirmed by someone in
> the batman irc room, note only gateways have this issue, clients do not
> crash at all.
If you mean me (Lazhur on irc) then I have to say that I am not a developer
nor a spokesman of b.a.t.m.a.n. and I never confirmed that it is batgat related
- only that something crashed/lock up.
I cannot find any crash related bug fixes in the batgat trunk directory - so it
doesn't seem to be a known problem (if it is a batgat problem at all).
Best regards
Sven Eckelmann
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-08 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 15:01 [B.A.T.M.A.N.] Batman gateway lock ups Outback Dingo
2008-09-08 7:08 ` Sven Eckelmann [this message]
2008-09-08 21:18 ` Sven Eckelmann
2008-09-08 21:45 ` Sven Eckelmann
2008-09-09 8:03 ` Sven Eckelmann
2008-09-09 11:26 ` Simon Wunderlich
2008-09-09 22:45 ` Sven Eckelmann
2008-09-10 9:50 ` Sven Eckelmann
2009-07-21 20:48 ` Simon Wunderlich
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=200809080908.31586.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox