public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: cmsv <cmsv@wirelesspt.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Batman-adv 2014.1.0 and 2014.0.0 issues with 3.10 and 3.8 kernels
Date: Mon, 31 Mar 2014 20:25:48 -0400	[thread overview]
Message-ID: <533A078C.7060803@wirelesspt.net> (raw)
In-Reply-To: <26865236.GIsAj78OZH@diderot>


[-- Attachment #1.1: Type: text/plain, Size: 2137 bytes --]

Inline:

On 03/31/2014 09:02 AM, Marek Lindner wrote:
> On Monday 31 March 2014 12:23:52 Bruno Antunes wrote:
>> root@Laguna1:/etc/config# wifi
>> [37620.920000] batman_adv: bat0: Interface deactivated: adhoc0
>> [37621.140000] batman_adv: bat0: Removing interface: adhoc0
>> [37621.250000] br-mesh: port 2(bat0) entered disabled state
>> [37621.250000] device bat0 left promiscuous mode
>> [37621.260000] br-mesh: port 2(bat0) entered disabled state
>> [37631.340000] unregister_netdevice: waiting for adhoc0 to become free.
>> Usage count = 1 [37641.390000] unregister_netdevice: waiting for adhoc0 to
>> become free. Usage count = 1 [37651.410000] unregister_netdevice: waiting
>> for adhoc0 to become free. Usage count = 1
> 
> This is a known 2014.1.0 regression which recently has been fixed. You can 
> either update your openwrt package to fetch these fixes or extract the patches 
> from our batman-adv git repository or wait for the next release.
> 
> 
>> And only restarting is possible to get the device back to work.
>>
>> Going back to 2014.0.0 it's worst with the system being very unstable and
>> continuously restarting.
>>
>> After following the instructions from cmsv <cmsv@wirelesspt.net>
>> and replacing the feeds.conf with
>> src-git routing https://github.com/libre-mesh/openwrt-routing-packages
> 
> Note that this is not the official openwrt-routing repository but a fork 
> maintained by 'people on the internet'. If you do experience problems with the 
> code coming from this repository, please contact the people maintaining this 
> fork.
> 

As far as i know; it is a clone of the batman-adv 2013.* without any
modification. Perhaps the maintainer could shed some light into this
subject.
https://github.com/libre-mesh/openwrt-routing-packages/tree/master/batman-adv
I have it fully working without any problems as a clone of batman-adv
2013.* without any modifications from "people on the internet".

There are also other ways to use the current official
openwrt-routing-packages repository and selecting only the 2013.* releases.

> 
> Cheers,
> Marek
> 

[-- Attachment #1.2: 0x15C4B382.asc --]
[-- Type: application/pgp-keys, Size: 36799 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-01  0:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 11:23 [B.A.T.M.A.N.] Batman-adv 2014.1.0 and 2014.0.0 issues with 3.10 and 3.8 kernels Bruno Antunes
2014-03-31 13:02 ` Marek Lindner
2014-04-01  0:25   ` cmsv [this message]
2014-04-01  2:54     ` Gui Iribarren
2014-04-01 11:16       ` Bastian Bittorf
2014-04-01 10:01   ` Bruno Antunes
2014-04-01 17:11     ` Marek Lindner

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=533A078C.7060803@wirelesspt.net \
    --to=cmsv@wirelesspt.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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