Hi, thanks for your report. I am currently running some stress tests on x86 and mips and couldn't reproduce any such problems. So I have some questions regarding your configuration.
On Tuesday 19 May 2009 16:27:25 Nathan Wharton wrote:
I am using batman 1256 on a very recent openwrt (linux version 2.6.28.10) as well as a bit older one (linux version 2.6.26.8).
What is your target architecture in openwrt? Have you tried to reproduce that problem on another architecture?
With batgat installed, I have problems with the kernel crashing when turning the gateway on and off. I start batman with -r 2. If I detect an uplink, I issue -c -g 11000. If I lose the link, I issue -c -r 2. It is this final -c -r 2 that causes the kernel to either crash with a bad page on the next process that is created, have a null pointer error, or have a recursion error.
Can you create a readable kernel backtrace with ksymoops?
If I run batman without batgat, I don't get any crashes.
Everything works fine otherwise. Except one thing that just came to mind, I had to remove -DDEBUG_MALLOC -DMEMORY_USAGE because batman wouldn't do anything without crashing because of magic number problems. Could this be because I am on Big Endian hardware?
I am running it also on big endian hardware and it seems to work. Does it happen right after the start or were extra interaction needed? What was the error output?
Could anyone else see if they have the same problem? All you have to do is have batman running with batgat installed, start issuing batmand -c -g 11000 ; batmand -c -r 2 multiple times and see if their system stays stable.
I am running it in a while true loop since an hour on x86 and mips on isolated and non isolated (single partner) nodes and didn't get such problems.
Regards, Sven