Search Linux Wireless

Re: AP mode my ath9k broke between 3.3 and 3.4-rc2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Apr 25, 2012, at 10:42 AM, Felix Fietkau wrote:

> On 2012-04-24 2:54 PM, John W. Linville wrote:
>> On Tue, Apr 24, 2012 at 12:00:11PM +0200, Andreas Hartmann wrote:
>>> Andrew Chant wrote:
>>>> 3.4-rc4 doesn't work either.
>>>> If I revert the patch on 3.4-rc4, the Intel card is able to associate again.
>>>> -Andrew
>>>> 
>>>> On Tue, Apr 24, 2012 at 12:11 AM, Andrew Chant <andrew.chant@xxxxxxxxx> wrote:
>>>>> Hello,
>>>>> my Atheros AR9300 PCIe card (168c:0030) stopped working as an AP on
>>>>> the 5GHz band between 3.3 and 3.4-rc2.
>>>>> After 14 git bisects, I believe I have narrowed it down to the following patch:
>>>>> 
>>>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=293702a3fb75832613e2af097bdc3ac8ef775b33
>>>>> 
>>>>> mac80211: use common radiotap code for cooked monitors
>>> 
>>> Same problem here with ar9285 / 2.4GHz / eap-tls / 802.11n / hostapd
>>> 0.7.3 / compat-wireless-3.4-rc3-1.tar.bz2
>>> 
>>> Removing "mac80211: use common radiotap code for cooked monitors" solves
>>> the problem here, too.
>>> 
>>> Using rt2860 as AP seems not to be a problem.
>> 
>> Sounds like we may need to revert it upstream.  Johannes, any comments?
> That's a known bug, which I submitted a fix for. When looking at the
> 3.4-rc4 log, I don't see my fix in there. It was submitted as
> "[PATCH] mac80211: fix truncated packets in cooked monitor rx"


Just as another data-point, I'm using ath9k for an AR9300 Rev:3 chipset
with compat-wireless-v3.4-rc3-1, and it doesn't work as an AP in any case:

Stock code:
  fails
Reverting [PATCH] mac80211: use common radiotap code for cooked monitors:
  fails
Leaving the above in place and applying Felix's radiotap patch:
  fails

I get a lot of these logs from hostapd:

1335397090.413064: Could not parse ProbeReq from 00:24:44:f5:e3:c2

I'm using hostapd 0.7.3.  If I rewind to an earlier "stable", it works -
at least the AP works; there is a bug in client mode when connecting to
a WEP AP, which is fixed in v3.4-rc3-1.

Should I try switching from "stable" to "next"?

--
-bp


--
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


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux