On Sat, Jul 21, 2012 at 6:38 PM, Antonio Quartulli ordex@autistici.org wrote:
Last week I came across this bug again, with the latest firm which includes the fixes mentioned, pushed by Marek. We were kinda in a hurry so i didn't have much time to check it thoroughly, so there's a *slim* chance it was just a coincidence, such as very poor signal giving erratic results. But if I recall correctly Nico Echaniz did stump on this too, using the latest firm.
How did you solve it then? Rebooting?
A reboot did, yes.
So, although i can't confirm it 100%, it seems so far the fixes didn't help :(
We'll keep an eye on it and try a "batctl l"
Yes, please. Remember to set the TT log level (batctl ll tt) before launching batctl l. Actually it would be very interesting to see the log of the involved nodes during the "wrong behaviour period".
This time it solved itself after some brief time (a minute) but the symptoms were the same. So I could catch some logs, http://pastebin.com/MEENj94i
sadly, i wasn't fast enough to get a live log from the node involved in the inconsistency as you suggested, so the report might be pretty useless. But at least now I got an idea where we are heading :)
Thank you very much!
Thanks a lot for your support people!
Gui