From: Dan Williams <dcbw@redhat.com>
To: Ryan Finnie <ryan.finnie@canonical.com>
Cc: Emmanuel Grumbach <egrumbach@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: Intel 7265 wireless performance unstable on Linux >= 3.19
Date: Tue, 31 Mar 2015 16:37:10 -0500 [thread overview]
Message-ID: <1427837830.6133.3.camel@redhat.com> (raw)
In-Reply-To: <551B045C.1030400@canonical.com>
On Tue, 2015-03-31 at 13:32 -0700, Ryan Finnie wrote:
> On 03/31/2015 02:15 AM, Emmanuel Grumbach wrote:
> >> Please open a bug on bugzilla.kernel.org and CC
> >> ilw@linux.intel.com to the bug. Attach your syslog output as
> >> well.
>
> Done: https://bugzilla.kernel.org/show_bug.cgi?id=95901
>
> >> It seems that the supplicant is deauthenticating. What is your
> >> supplicant version?
>
> wpasupplicant 2.1-0ubuntu7 from Ubuntu vivid. From the syslog output,
> it appears the wpa_supplicant output is reacting to the kernel event,
> with nothing relevant preceding it:
>
> Mar 31 13:15:11 linda systemd[1]: Started Stop ureadahead data collection.
> Mar 31 13:15:20 linda kernel: [ 72.442153] wlan0: deauthenticating
> from 38:2c:4a:5c:7f:e4 by local choice (Reason: 3=DEAUTH_LEAVING)
> Mar 31 13:15:20 linda kernel: [ 72.457967] cfg80211: Calling CRDA to
> update world regulatory domain
> Mar 31 13:15:20 linda wpa_supplicant[902]: wlan0:
> CTRL-EVENT-DISCONNECTED bssid=38:2c:4a:5c:7f:e4 reason=3
> locally_generated=1
> Mar 31 13:15:20 linda NetworkManager[815]: <warn> Connection
> disconnected (reason -3)
I've looked through the log for relevant NetworkManager stuff, since
reason=3/locally-generated disconnections are often a result of NM's
association attempt timing out or moving to a new network. In this
case, I cannot find any evidence of NetworkManager disconnecting
intentionally, it seems to come out of nowhere.
Dan
> > One idea came through my mind. Can you try this?
> >
> > diff --git a/drivers/net/wireless/iwlwifi/mvm/mac80211.c
> > b/drivers/net/wireless/iwlwifi/mvm/mac80211.c index
> > 302c8cc..7c12c9f 100644 ---
> > a/drivers/net/wireless/iwlwifi/mvm/mac80211.c +++
> > b/drivers/net/wireless/iwlwifi/mvm/mac80211.c @@ -525,7 +525,7 @@
> > int iwl_mvm_mac_setup_register(struct iwl_mvm *mvm) else
> > hw->wiphy->flags &= ~WIPHY_FLAG_PS_ON_BY_DEFAULT;
> >
> > - if (IWL_UCODE_API(mvm->fw->ucode_ver) >= 10) { + if
> > (IWL_UCODE_API(mvm->fw->ucode_ver) >= 10 && false) {
> > hw->wiphy->flags |= WIPHY_FLAG_SUPPORTS_SCHED_SCAN;
> > hw->wiphy->max_sched_scan_ssids = PROBE_OPTION_MAX;
> > hw->wiphy->max_match_sets = IWL_SCAN_MAX_PROFILES;
>
> Sorry, it didn't appear to have any effect; DEAUTH_LEAVING would still
> occur every ~60 seconds.
>
> RF
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-31 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 5:54 Intel 7265 wireless performance unstable on Linux >= 3.19 Ryan Finnie
2015-03-31 8:10 ` Emmanuel Grumbach
2015-03-31 9:15 ` Emmanuel Grumbach
2015-03-31 20:32 ` Ryan Finnie
2015-03-31 21:37 ` Dan Williams [this message]
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=1427837830.6133.3.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=ryan.finnie@canonical.com \
--cc=seth.forshee@canonical.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).