linux-kernel - BCM4313 problems connecting to AP since 3.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CA+K+NcR9tExM9y-yjH_MB=ZpjeeakMW2GozECg4Pejp54nkCjA@mail.gmail.com>
Date:	Mon, 4 Mar 2013 22:47:24 +0100
From:	Ján Veselý <jano.vesely@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: BCM4313 problems connecting to AP since 3.8

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

Jan Vesely
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/