On 03/06/13 11:24, Alexander Mezin wrote: > 2013/3/6 Piotr Haber <phaber@xxxxxxxxxxxx>: >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
