All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Andrew Chant <andrew.chant@gmail.com>
Cc: Johannes Berg <johannes.berg@intel.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: AP mode my ath9k broke between 3.3 and 3.4-rc2
Date: Tue, 24 Apr 2012 12:00:11 +0200	[thread overview]
Message-ID: <4F9679AB.6010103@01019freenet.de> (raw)
In-Reply-To: <CANugF37wdS3=u7grT3H6WAJM=XxTukZoWdj70SXLL8k_6t1b6A@mail.gmail.com>

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@gmail.com> 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.


Regards,
Andreas Hartmann

  reply	other threads:[~2012-04-24 10:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  7:11 AP mode my ath9k broke between 3.3 and 3.4-rc2 Andrew Chant
2012-04-24  7:44 ` Andrew Chant
2012-04-24 10:00   ` Andreas Hartmann [this message]
2012-04-24 12:54     ` John W. Linville
2012-04-25 17:42       ` Felix Fietkau
2012-04-25 20:47         ` Andreas Hartmann
2012-04-25 23:46         ` Bryan Phillippe
2012-05-16 22:55           ` Bryan Phillippe
2012-04-26  3:33         ` Andrew Chant
2012-04-26  6:36         ` Andreas Hartmann

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=4F9679AB.6010103@01019freenet.de \
    --to=andihartmann@01019freenet.de \
    --cc=andrew.chant@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.