From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Marek Lindner <mareklindner@neomailbox.ch>,
netdev <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Kalle Valo <kvalo@codeaurora.org>,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [B.A.T.M.A.N.] ibss.c backtrace when batman-adv adds wireless interface
Date: Wed, 03 Feb 2016 18:09:40 +0100 [thread overview]
Message-ID: <9390290.k4UIzlfAE4@bentobox> (raw)
In-Reply-To: <1454514090.3083.8.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]
On Wednesday 03 February 2016 16:41:30 Johannes Berg wrote:
> On Wed, 2016-02-03 at 10:26 -0500, Josh Boyer wrote:
> > On Wed, Feb 3, 2016 at 10:24 AM, Josh Boyer <jwboyer@fedoraproject.or
> > g> wrote:
> > > Hi All,
> > >
> > > We've had a user report the backtrace below when loading batman-adv
> > > on
> > > his machine. It looks like the cfg80211 layer is complaining about
> > > a
> > > null bss returned, but I cannot tell if the rtlwifi driver or
> > > batman-adv is in error here.
> > >
> > > Thoughts?
> >
> > Sorry, forgot to include the link to the actual bug report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1304428
> >
> > Reporter says this is new with 4.3.y and did not happen on e.g.
> > 4.2.8.
> >
>
> AFAICT this should be a driver (or perhaps mac80211) issue, but I don't
> see any information about the driver used.
It doesn't really look like it is batman-adv specific. batman-adv also doesn't
be active because the message "batman_adv: bat0: Adding interface: " is
missing.
batman-adv is also not responsible for the underlying device. So it will not
join IBSS and thus should not trigger the "wlp0s26u1u4: Selected IBSS BSSID"
seen in the log.
But that said, I already saw weirder things happen because of memory
corruptions. So I will not say that batman-adv cannot be the culprit but right
now I don't see how.
The user can also try (when he thinks that batman-adv is to blame) to bisect
the batman-adv versions via the git of the out-of-tree module [1]. The version [2]
from 4.1 should be roughly v2015.0 (b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf),
v4.2 should be v2015.1 (95b64b1cef38340f48f4eba99689e0fb1feddcd0) and v4.3 should
not be newer than v2015.2 (e25bd38b0f8b4aeca85ef24884fa5eadd6270709). So bisecting
between b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf and
e25bd38b0f8b4aeca85ef24884fa5eadd6270709 (~6 steps) should cover it. I personally
would recommend to start on 4.2.8 with v2015.2
(e25bd38b0f8b4aeca85ef24884fa5eadd6270709)
Kind regards,
Sven
[1] https://git.open-mesh.org/batman-adv.git
[2] https://www.open-mesh.org/projects/open-mesh/wiki/Download#batman-adv-in-the-Linux-tree
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Josh Boyer <jwboyer@fedoraproject.org>,
Larry Finger <Larry.Finger@lwfinger.net>,
Marek Lindner <mareklindner@neomailbox.ch>,
Kalle Valo <kvalo@codeaurora.org>,
Simon Wunderlich <sw@simonwunderlich.de>,
netdev <netdev@vger.kernel.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [B.A.T.M.A.N.] ibss.c backtrace when batman-adv adds wireless interface
Date: Wed, 03 Feb 2016 18:09:40 +0100 [thread overview]
Message-ID: <9390290.k4UIzlfAE4@bentobox> (raw)
In-Reply-To: <1454514090.3083.8.camel@sipsolutions.net>
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]
On Wednesday 03 February 2016 16:41:30 Johannes Berg wrote:
> On Wed, 2016-02-03 at 10:26 -0500, Josh Boyer wrote:
> > On Wed, Feb 3, 2016 at 10:24 AM, Josh Boyer <jwboyer@fedoraproject.or
> > g> wrote:
> > > Hi All,
> > >
> > > We've had a user report the backtrace below when loading batman-adv
> > > on
> > > his machine. It looks like the cfg80211 layer is complaining about
> > > a
> > > null bss returned, but I cannot tell if the rtlwifi driver or
> > > batman-adv is in error here.
> > >
> > > Thoughts?
> >
> > Sorry, forgot to include the link to the actual bug report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1304428
> >
> > Reporter says this is new with 4.3.y and did not happen on e.g.
> > 4.2.8.
> >
>
> AFAICT this should be a driver (or perhaps mac80211) issue, but I don't
> see any information about the driver used.
It doesn't really look like it is batman-adv specific. batman-adv also doesn't
be active because the message "batman_adv: bat0: Adding interface: " is
missing.
batman-adv is also not responsible for the underlying device. So it will not
join IBSS and thus should not trigger the "wlp0s26u1u4: Selected IBSS BSSID"
seen in the log.
But that said, I already saw weirder things happen because of memory
corruptions. So I will not say that batman-adv cannot be the culprit but right
now I don't see how.
The user can also try (when he thinks that batman-adv is to blame) to bisect
the batman-adv versions via the git of the out-of-tree module [1]. The version [2]
from 4.1 should be roughly v2015.0 (b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf),
v4.2 should be v2015.1 (95b64b1cef38340f48f4eba99689e0fb1feddcd0) and v4.3 should
not be newer than v2015.2 (e25bd38b0f8b4aeca85ef24884fa5eadd6270709). So bisecting
between b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf and
e25bd38b0f8b4aeca85ef24884fa5eadd6270709 (~6 steps) should cover it. I personally
would recommend to start on 4.2.8 with v2015.2
(e25bd38b0f8b4aeca85ef24884fa5eadd6270709)
Kind regards,
Sven
[1] https://git.open-mesh.org/batman-adv.git
[2] https://www.open-mesh.org/projects/open-mesh/wiki/Download#batman-adv-in-the-Linux-tree
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven-KaDOiPu9UxWEi8DpZVb4nw@public.gmane.org>
To: b.a.t.m.a.n-ZwoEplunGu2X36UT3dwllkB+6BGkLq7r@public.gmane.org
Cc: Josh Boyer
<jwboyer-rxtnV0ftBwyoClj4AeEUq9i2O/JbrIOy@public.gmane.org>,
Marek Lindner
<mareklindner-rVWd3aGhH2z5bpWLKbzFeg@public.gmane.org>,
netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
Kalle Valo <kvalo-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
Larry Finger
<Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Subject: Re: ibss.c backtrace when batman-adv adds wireless interface
Date: Wed, 03 Feb 2016 18:09:40 +0100 [thread overview]
Message-ID: <9390290.k4UIzlfAE4@bentobox> (raw)
In-Reply-To: <1454514090.3083.8.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2203 bytes --]
On Wednesday 03 February 2016 16:41:30 Johannes Berg wrote:
> On Wed, 2016-02-03 at 10:26 -0500, Josh Boyer wrote:
> > On Wed, Feb 3, 2016 at 10:24 AM, Josh Boyer <jwboyer@fedoraproject.or
> > g> wrote:
> > > Hi All,
> > >
> > > We've had a user report the backtrace below when loading batman-adv
> > > on
> > > his machine. It looks like the cfg80211 layer is complaining about
> > > a
> > > null bss returned, but I cannot tell if the rtlwifi driver or
> > > batman-adv is in error here.
> > >
> > > Thoughts?
> >
> > Sorry, forgot to include the link to the actual bug report:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1304428
> >
> > Reporter says this is new with 4.3.y and did not happen on e.g.
> > 4.2.8.
> >
>
> AFAICT this should be a driver (or perhaps mac80211) issue, but I don't
> see any information about the driver used.
It doesn't really look like it is batman-adv specific. batman-adv also doesn't
be active because the message "batman_adv: bat0: Adding interface: " is
missing.
batman-adv is also not responsible for the underlying device. So it will not
join IBSS and thus should not trigger the "wlp0s26u1u4: Selected IBSS BSSID"
seen in the log.
But that said, I already saw weirder things happen because of memory
corruptions. So I will not say that batman-adv cannot be the culprit but right
now I don't see how.
The user can also try (when he thinks that batman-adv is to blame) to bisect
the batman-adv versions via the git of the out-of-tree module [1]. The version [2]
from 4.1 should be roughly v2015.0 (b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf),
v4.2 should be v2015.1 (95b64b1cef38340f48f4eba99689e0fb1feddcd0) and v4.3 should
not be newer than v2015.2 (e25bd38b0f8b4aeca85ef24884fa5eadd6270709). So bisecting
between b6ff92aa334083dee8a1f5f0c5aa0f7c4c2584cf and
e25bd38b0f8b4aeca85ef24884fa5eadd6270709 (~6 steps) should cover it. I personally
would recommend to start on 4.2.8 with v2015.2
(e25bd38b0f8b4aeca85ef24884fa5eadd6270709)
Kind regards,
Sven
[1] https://git.open-mesh.org/batman-adv.git
[2] https://www.open-mesh.org/projects/open-mesh/wiki/Download#batman-adv-in-the-Linux-tree
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-03 17:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 15:24 [B.A.T.M.A.N.] ibss.c backtrace when batman-adv adds wireless interface Josh Boyer
2016-02-03 15:24 ` Josh Boyer
2016-02-03 15:24 ` Josh Boyer
2016-02-03 15:26 ` [B.A.T.M.A.N.] " Josh Boyer
2016-02-03 15:26 ` Josh Boyer
2016-02-03 15:26 ` Josh Boyer
2016-02-03 15:41 ` [B.A.T.M.A.N.] " Johannes Berg
2016-02-03 15:41 ` Johannes Berg
2016-02-03 15:49 ` [B.A.T.M.A.N.] " Josh Boyer
2016-02-03 15:49 ` Josh Boyer
2016-02-03 17:09 ` Sven Eckelmann [this message]
2016-02-03 17:09 ` Sven Eckelmann
2016-02-03 17:09 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-02-03 17:35 ` Sven Eckelmann
2016-02-03 17:35 ` Sven Eckelmann
2016-02-03 17:14 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-02-03 17:14 ` Sven Eckelmann
2016-02-03 17:14 ` [B.A.T.M.A.N.] " Sven Eckelmann
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=9390290.k4UIzlfAE4@bentobox \
--to=sven@narfation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@fedoraproject.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.