From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Andy Isaacson <adi@hexapodia.org>
Cc: Johannes Berg <johannes.berg@intel.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
Subject: Re: 3.10, iwlwifi 6200AGN: AP changed bandwidth in a way we can't support - disconnect
Date: Wed, 31 Jul 2013 10:59:56 +0200 [thread overview]
Message-ID: <20130731085956.GC1681@redhat.com> (raw)
In-Reply-To: <20130729163452.GA454@hexapodia.org>
On Mon, Jul 29, 2013 at 09:34:52AM -0700, Andy Isaacson wrote:
> After upgrading to 3.10.4 and traveling to Europe I'm often suffering
> from failures to associate with the following in dmesg:
>
> [ 37.351621] wlan0: authenticate with 64:70:02:e6:a6:ba
> [ 37.364701] wlan0: send auth to 64:70:02:e6:a6:ba (try 1/3)
> [ 37.366358] wlan0: authenticated
> [ 37.368543] wlan0: associate with 64:70:02:e6:a6:ba (try 1/3)
> [ 37.372765] wlan0: RX AssocResp from 64:70:02:e6:a6:ba (capab=0x431 status=0 aid=8)
> [ 37.380190] wlan0: associated
> [ 37.438935] wlan0: AP 64:70:02:e6:a6:ba changed bandwidth, new config is 2447 MHz, width 1 (2447/0 MHz)
> [ 37.438941] wlan0: AP 64:70:02:e6:a6:ba changed bandwidth in a way we can't support - disconnect
>
> I hacked the driver to do
>
> - "AP %pM changed bandwidth, new config is %d MHz, width %d (%d/%d MHz)\n",
> + "AP %pM changed bandwidth, new config is %d MHz, width %d (%d/%d MHz) flags %x/%x\n",
> ifmgd->bssid, chandef.chan->center_freq, chandef.width,
> - chandef.center_freq1, chandef.center_freq2);
> + chandef.center_freq1, chandef.center_freq2, flags, ifmgd->flags);
>
> and
>
> - if (flags != (ifmgd->flags & (IEEE80211_STA_DISABLE_HT |
> + if ((flags != 0x810 && ifmgd->flags != 0x804) && (
> + flags != (ifmgd->flags & (IEEE80211_STA_DISABLE_HT |
>
> and the result is a working link with
We have few reports about this. Johannes, proposed this patch
http://p.sipsolutions.net/9d1dd0734d2c3a7a.txt
Could you check if it fixes the problem for you?
Stanislaw
next prev parent reply other threads:[~2013-07-31 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 16:34 3.10, iwlwifi 6200AGN: AP changed bandwidth in a way we can't support - disconnect Andy Isaacson
2013-07-31 8:59 ` Stanislaw Gruszka [this message]
2013-07-31 14:57 ` Andy Isaacson
[not found] ` <20130731145737.GC31017-3HqRAUrWAWyGglJvpFV4uA@public.gmane.org>
2013-07-31 14:59 ` Johannes Berg
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=20130731085956.GC1681@redhat.com \
--to=sgruszka@redhat.com \
--cc=a.miskiewicz@gmail.com \
--cc=adi@hexapodia.org \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).