From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev <b43-dev@lists.infradead.org>
Subject: Scanning regression since "cfg80211: use DS or HT operation IEs to determine BSS channel"
Date: Tue, 26 Mar 2013 19:38:38 +0100 [thread overview]
Message-ID: <1364323118.8319.13.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CACna6rwdAAsCX76=nwHpj-grVvQznbNCPVnpXL9kP2TkvhR-yw@mail.gmail.com> (sfid-20130326_181054_958567_0E045FFC)
On Tue, 2013-03-26 at 18:10 +0100, Rafa? Mi?ecki wrote:
> I've just finished bisecting wireless scanning regression I'm
> experiencing with my 14e4:432b (BCM4322) and b43 driver.
Hmmm.
> The problem is getting my network visible in scanning results (iw dev
> wlan0 scan). I've to repeat scanning dozens of time to notice my AP.
> It's also well visible when using wpa_supplicant. It takes from 20s to
> 100s before I get the "Trying to authenticate with".
That's strange.
> After going back to the kernel before that commit it takes
> wpa_supplicant less than 2 seconds to connect to my WiFi network.
> My network is at channel 13, I still have to verify if it matters.
>
> Any thought about that?
>
>
> The first bad commit (I've verified manually after bisecting) appears to be:
"verified manually" how? By reverting the commit? But anyway the commit
is clearly scanning related, so ...
Can you check your channel list? (iw list or iw phy0 info)
Also can you show the full data including beacon data from the AP (iw
wlan0 scan dump -b) please?
Does reverting just the mac80211 change fix it?
johannes
next prev parent reply other threads:[~2013-03-26 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 17:10 Scanning regression since "cfg80211: use DS or HT operation IEs to determine BSS channel" Rafał Miłecki
2013-03-26 18:38 ` Johannes Berg [this message]
2013-03-26 21:58 ` Rafał Miłecki
2013-03-26 22:13 ` Rafał Miłecki
2013-03-26 22:26 ` Johannes Berg
2014-01-26 14:37 ` Rafał Miłecki
2014-01-27 8:43 ` Johannes Berg
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=1364323118.8319.13.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).