linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2.6.33] mac80211: fix skb buffering issue
Date: Tue, 05 Jan 2010 23:30:48 -0600	[thread overview]
Message-ID: <4B442008.2040207@lwfinger.net> (raw)
In-Reply-To: <1262710858.28653.5.camel@johannes.local>

On 01/05/2010 11:00 AM, Johannes Berg wrote:
> Since I removed the master netdev, we've been
> keeping internal queues only, and even before
--snip--

> Reported-by: Lennert Buytenhek <buytenh@marvell.com>
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> Cc: stable@kernel.org [2.6.32]
> ---
> I know it's late, and large, but still would be good to have in .33
> since the issue is fairly serious.

I'm not sure this is ready for prime time. After I installed it, my b43 was
never able to reconnect after any kind of disconnect. The log is uninformative:

===========================================
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
wlan0: direct probe to 00:14:bf:85:49:fa (try 1)
wlan0: direct probe responded
wlan0: authenticate with 00:14:bf:85:49:fa (try 1)
wlan0: authenticated
wlan0: associate with 00:14:bf:85:49:fa (try 1)
wlan0: RX AssocResp from 00:14:bf:85:49:fa (capab=0x411 status=0 aid=1)
wlan0: associated
b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac:
00:14:bf:85:49:fa
b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac:
00:14:bf:85:49:fa
wlan0: deauthenticating from 00:14:bf:85:49:fa by local choice (reason=3)
===========================================

Reauthentication fails with a pop-up to reenter the WPA2 secret as I'm using
NetworkManager. I can only reconnect if b43 (and mac80211) are unloaded and
reloaded. I pulled the patch and confirmed that proper behavior is returned.

Larry

  parent reply	other threads:[~2010-01-06  5:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 17:00 [PATCH 2.6.33] mac80211: fix skb buffering issue Johannes Berg
2010-01-05 17:16 ` John W. Linville
2010-01-05 18:36   ` Lennert Buytenhek
2010-01-05 19:07   ` Felix Fietkau
2010-01-05 19:36     ` Lennert Buytenhek
2010-01-06 11:32   ` Lennert Buytenhek
2010-01-06  5:30 ` Larry Finger [this message]
2010-01-06 11:05   ` Johannes Berg
2010-01-06 18:16     ` Larry Finger
2010-01-06 11:33 ` Lennert Buytenhek
2010-01-06 21:26 ` Thomas Backlund
2010-01-06 21:51   ` Johannes Berg
2010-01-06 22:03     ` Felix Fietkau
2010-01-06 22:39       ` Thomas Backlund
2010-01-06 23:19         ` Thomas Backlund
2010-01-07  6:57           ` Johannes Berg
2010-01-07 10:41             ` Thomas Backlund
2010-01-06 22:31 ` Sedat Dilek
2010-01-07  4:10   ` Lennert Buytenhek
2010-01-07  9:24     ` Sedat Dilek
2010-01-07 14:01 ` mac80211: fix queue selection for packets injected via monitor interface Lennert Buytenhek
2010-01-07 15:45   ` Luis R. Rodriguez
2010-01-07 15:47     ` Lennert Buytenhek

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=4B442008.2040207@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=buytenh@wantstofly.org \
    --cc=johannes@sipsolutions.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).