From: Luca Coelho <luca@coelho.fi>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Kazior <michal.kazior@tieto.com>,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix channel switch for chanctx-based drivers
Date: Mon, 18 Aug 2014 16:59:25 +0300 [thread overview]
Message-ID: <1408370365.20137.11.camel@dubbel> (raw)
In-Reply-To: <CA+55aFy4X9+o3u=gPcsVfO8VHLcdzifefdjMDoH+uB0xKzym9Q@mail.gmail.com>
Hi Linus,
On Mon, 2014-08-18 at 08:53 -0500, Linus Torvalds wrote:
> On Mon, Aug 18, 2014 at 6:19 AM, Michal Kazior <michal.kazior@tieto.com> wrote:
> >
> > I've verified this fix with iwlmvm & 7260.
>
> So I'm running a kernel with this manually applied, and so far so
> good. But I don't know what actually triggered the problem, and it
> definitely didn't happen all the time, so my testing of this is
> dubious. But the patch certainly seems to match the symptoms. Thanks,
What triggers this is a "Channel Switch Announcement" on which the
access point tells the clients to move to another channel at a specified
time. This is not very common, but some enterprise APs use it to
improve the operating radio conditions, for instance.
Previously, as a client, we would simply disconnect from the current
channel and reconnect on the new channel after the time specified by the
AP. Now we implemented a more advanced switch where we don't lose
connectivity, but "simply" switch channels.
Hope this clarifies a bit.
--
Cheers,
Luca.
next prev parent reply other threads:[~2014-08-18 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 4:01 More wireless problems Linus Torvalds
2014-08-18 4:37 ` Linus Torvalds
2014-08-18 8:50 ` Luca Coelho
2014-08-18 11:19 ` [PATCH] mac80211: fix channel switch for chanctx-based drivers Michal Kazior
2014-08-18 13:40 ` Luca Coelho
2014-08-18 13:53 ` Linus Torvalds
2014-08-18 13:59 ` Luca Coelho [this message]
[not found] ` <1408360749-10233-1-git-send-email-michal.kazior-++hxYGjEMp0AvxtiuMwx3w@public.gmane.org>
2014-08-18 13:59 ` Linus Torvalds
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=1408370365.20137.11.camel@dubbel \
--to=luca@coelho.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=michal.kazior@tieto.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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