Linux wireless drivers development
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh.dickins@tiscali.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-wireless@vger.kernel.org
Subject: 2.6.31-git wireless broken
Date: Thu, 24 Sep 2009 18:18:20 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0909241737390.20846@sister.anvils> (raw)

I've noticed for a while that wireless is broken in linux-next, on both
the machines I use it on (a Fujitsu Siemens laptop using iwl3945 and an
Acer Aspire One using ath5k: both running openSUSE 11.1, with WPA):
I hoped to find it fixed later, but no, Linus's git is broken now.

Only found time to bisect it a couple of days ago (on the Aspire One:
guess the other would show the same, but that's no more than a guess).
It arrived at the commit below as the culprit, which from your own
words doesn't seem like a very hopeful place to land :-(

That commit does give me a "WARNING: at net/mac80211/mlme.c:1904",
followed by "WARNING: at net/mac80211/mlme.c:2308" every few seconds;
and those do get fixed later on (don't appear with latest git).
But I think there's another problem that comes in later, because
at this commit iwconfig does show my ESSID, whereas with later
git it just says "ESSID:off/any" (I have not bisected when that
change comes in).

I expect you'll need a lot more info from me: please do ask
(but bear in mind that I'm wireless and network ignorant).

Thanks,
Hugh

77fdaa12cea26c204cc12c312fe40bc0f3dcdfd8 is first bad commit
commit 77fdaa12cea26c204cc12c312fe40bc0f3dcdfd8
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Tue Jul 7 03:45:17 2009 +0200

    mac80211: rework MLME for multiple authentications
    
    Sit tight. This shakes up the world as you know
    it. Let go of your spaghetti tongs, they will no
    longer be required, the horrible statemachine in
    net/mac80211/mlme.c is no more...
    
    With the cfg80211 SME mac80211 now has much less
    to keep track of, but, on the other hand, for FT
    it needs to be able to keep track of at least one
    authentication being in progress while associated.
    So convert from a single state machine to having
    small ones for all the different things we need to
    do. For real FT it will still need work wrt. PS,
    but this should be a good step.
    
    Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>

:040000 040000 437301807c7c27495cee7692f293dac1ca56ed78 02520ec555c0873050318af669dade9e066f479d M	net

             reply	other threads:[~2009-09-24 17:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 17:18 Hugh Dickins [this message]
2009-09-24 17:35 ` 2.6.31-git wireless broken Johannes Berg
2009-09-24 18:14   ` Hugh Dickins
2009-09-24 18:23     ` Johannes Berg
2009-09-24 19:45       ` Hugh Dickins
2009-09-25  5:20         ` Johannes Berg
2009-09-25  8:06           ` Hugh Dickins
2009-09-25  8:43             ` Johannes Berg
2009-09-25 14:15               ` Hugh Dickins
2009-09-26 13:00                 ` Johannes Berg
2009-09-26 14:03                   ` Johannes Berg
2009-09-26 15:06                     ` Sven-Haegar Koch
2009-09-26 15:33                     ` Hugh Dickins
2009-09-27 11:08                       ` Johannes Berg
2009-09-27 11:15                       ` Johannes Berg
2009-09-26 15:31                   ` Hugh Dickins
2009-09-26 15:58                     ` Larry Finger
2009-09-25  8:45             ` Holger Schurig
2009-09-25 14:56               ` Christian Lamparter

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=Pine.LNX.4.64.0909241737390.20846@sister.anvils \
    --to=hugh.dickins@tiscali.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rjw@sisk.pl \
    /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