From: "Arend van Spriel" <arend@broadcom.com>
To: "Ján Veselý" <jano.vesely@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4313 problems connecting to AP since 3.8
Date: Tue, 5 Mar 2013 18:00:39 +0100 [thread overview]
Message-ID: <513624B7.8010109@broadcom.com> (raw)
In-Reply-To: <CA+K+NcR9tExM9y-yjH_MB=ZpjeeakMW2GozECg4Pejp54nkCjA@mail.gmail.com>
On 03/04/13 22:47, Ján Veselý wrote:
> Hi,
>
> after upgrading to 3.8 I started running into a timeout problem on
> BCM4313 wifi using brcmsmac driver (compiled as module, x86_64).
> the card is unable to connect to ap after startup of resume.
> Although it eventually connects it takes a long time (several minutes)
> and dmesg log is spammed with:
>
> [ 144.725431] wlan0: authenticate with 00:23:f8:8f:29:14
> [ 144.727786] wlan0: capabilities/regulatory prevented using AP
> HT/VHT configuration, downgraded
> [ 144.727820] wlan0: direct probe to 00:23:f8:8f:29:14 (try 1/3)
> [ 144.930780] wlan0: direct probe to 00:23:f8:8f:29:14 (try 2/3)
> [ 145.133855] wlan0: direct probe to 00:23:f8:8f:29:14 (try 3/3)
> [ 145.336931] wlan0: authentication with 00:23:f8:8f:29:14 timed out
> [ 151.217245] wlan0: authenticate with 00:23:f8:8f:29:14
>
> (30+ times in some cases)
>
> I tested 3.8.0/1/2 as well as 3.9.0-rc1 and the problem is present in
> all of them.
> returning back to 3.7.10 fixes the problem and the card connects
> without a single timeout message.
>
> the AP is an older adsl modem/hotspot and runs in 802.11g mode, my
> other machine (x86) with atheros chipset connects without any problems
> to the same AP on 3.8 kernel.
>
> let me know if I can provide more info
Well, for starters the dmesg output before the first spam occurrence
would be good to have a look at. Could you provide that?
If you don't mind I changed Cc: to linux-wireless mailing list.
Gr. AvS
> Jan Vesely
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next parent reply other threads:[~2013-03-05 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+K+NcR9tExM9y-yjH_MB=ZpjeeakMW2GozECg4Pejp54nkCjA@mail.gmail.com>
2013-03-05 17:00 ` Arend van Spriel [this message]
2013-03-05 20:22 ` BCM4313 problems connecting to AP since 3.8 Ján Veselý
2013-03-05 23:06 ` Alexander Mezin
2013-03-06 10:20 ` Piotr Haber
[not found] ` <CADnvcf+Mub7DhGWNqSuRF9u2A5HMfqUv5GuYrYcrkGjbXx470A@mail.gmail.com>
2013-03-06 11:07 ` Piotr Haber
2013-03-06 20:00 ` Ján Veselý
2013-03-06 22:05 ` Ján Veselý
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=513624B7.8010109@broadcom.com \
--to=arend@broadcom.com \
--cc=jano.vesely@gmail.com \
--cc=linux-wireless@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).