From: "Piotr Haber" <phaber@broadcom.com>
To: "Alexander Mezin" <mezin.alexander@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BCM4313 problems connecting to AP since 3.8
Date: Wed, 6 Mar 2013 12:07:00 +0100 [thread overview]
Message-ID: <51372354.50901@broadcom.com> (raw)
In-Reply-To: <CADnvcf+Mub7DhGWNqSuRF9u2A5HMfqUv5GuYrYcrkGjbXx470A@mail.gmail.com>
On 03/06/13 11:24, Alexander Mezin wrote:
> 2013/3/6 Piotr Haber <phaber@broadcom.com>:
>> On 03/06/13 00:06, Alexander Mezin wrote:
>>> Arend van Spriel <arend@...> writes:
>>>
>>>>
>>>> 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)
>>>
>>> Had the same problem.
>>> It seems that this commit introduces the bug:
>>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?
>>> id=b6fc28a158076ca2764edc9a6d1e1402f56e1c0c
>>> I reverted it and now I have successful connection on first attempt. Linux
>>> 3.8.2, BCM4313 802.11b/g/n Wireless LAN Controller.
>>>
>> Hi,
>> that's disturbing.
>> I wonder what hardware version you have.
>> Could you share the contents of this debugfs file:
>> <debugfs_mount>/brcmsmac/bcma0:0/hardware
>>
>> Piotr
>>
>>
>>
>
> board vendor: 103c
> board type: 1483
> board revision: 2410
> board flags: 8402a01
> board flags2: 880
> firmware revision: 262032c
>
Thanks,
we had reports of poor performance of 4313/BT combo boards, but did not connect it to 4313iPA
support added by that problematic patch.
Will investigate.
Piotr
next prev parent reply other threads:[~2013-03-06 11:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 21:47 BCM4313 problems connecting to AP since 3.8 Ján Veselý
2013-03-05 17:00 ` Arend van Spriel
2013-03-05 20:22 ` 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 [this message]
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=51372354.50901@broadcom.com \
--to=phaber@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mezin.alexander@gmail.com \
/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.