Re: [B.A.T.M.A.N.] Kernel crashes with batgat installed

[Nathan Wharton <naw@greptar.com>]

On Wed, May 20, 2009 at 11:10 AM, Marek Lindner <lindner_marek@yahoo.de> wrote:
> Ok, from your output plus the nvalid magic number we can say that it seems
> somewhat related to your HNA settings. A few more questions:
> * In this case the batgat module is not involved and still it crashes ?!
> * Is your network up & running ? Does batman receive messages from neighbor
> nodes (you can track that via debug log 4) ?
> * Does batman also crash in a disconnected environment ?

In this case, it does the same thing whether or not batgat is installed.

Debug level 4 gives:
========================================
WARNING: You are using the unstable batman branch. If you are
interested in *using* batman get the lat
est stable release !
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 66 - unknown)
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 66 - unknown)
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 65 - unknown)
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 65 - unknown)
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 67 - unknown)
Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 67 - unknown)
Interface activated: ath0
Using interface ath0 with address 10.0.1.3 and broadcast address 10.0.255.255
Interface activated: eth0
Using interface eth0 with address 10.255.1.3 and broadcast address
10.255.255.255
B.A.T.M.A.N. 0.3.2-beta rv1256 (compatibility version 5)
[        30] Adding throw route to 127.0.0.0/8 via 0.0.0.0 (table 68 - lo)
[        30] Adding throw route to 10.1.3.0/24 via 0.0.0.0 (table 68 - eth1)
[        30] Adding throw route to 10.0.0.0/16 via 0.0.0.0 (table 68 - ath0)
debug level: 4
routing class: 2
[        30] Adding throw route to 10.1.3.0/24 via 0.0.0.0 (table 65 - unknown)
[        30] Adding throw route to 10.1.3.0/24 via 0.0.0.0 (table 66 - unknown)
[        30] Adding throw route to 10.1.3.0/24 via 0.0.0.0 (table 67 - unknown)
[        30] Adding throw route to 10.1.3.0/24 via 0.0.0.0 (table 68 - unknown)
[        30] Error - can't add throw route to 10.1.3.0/24 via 0.0.0.0
(table 68): File exists
[        30] Error - can't add throw route to 10.1.3.0/24 via 0.0.0.0
(table 68): File exists
[        30] debugRealloc - invalid magic number in trailer: 78183456,
malloc tag = 15
[        30] debugRealloc - invalid magic number in trailer: 78183456,
malloc tag = 15
[        30] Deleting throw route to 127.0.0.0/8 via 0.0.0.0 (table 68 - lo)
[       100] Deleting throw route to 10.1.3.0/24 via 0.0.0.0 (table 68 - eth1)
[       130] Deleting throw route to 10.0.0.0/16 via 0.0.0.0 (table 68 - ath0)
========================================

It does this while not connected.

>> This is only happening when using the batgat module.
>> The kernel is crashing.  If it happens to not reboot, I see that
>> batman is in a device wait state and can't be killed.
>
> The log you just provided is not about a kernel crash - its "just" the batman
> daemon. Are we hunting 2 different bugs ?

If you consider 1 bug being the debug_malloc stuff not working, and
the other being batgat possibly crashing the kernel, then yes.
If I turn off debug malloc, then everything works fine, except using
batgat and going from gateway to routing class.