From: Bob Copeland <me@bobcopeland.com>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: linux-wireless@vger.kernel.org,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luca Coelho <luciano.coelho@intel.com>
Subject: Re: wireless-testing on 4.7
Date: Wed, 1 Jun 2016 08:54:53 -0400 [thread overview]
Message-ID: <20160601125453.GB12977@localhost> (raw)
In-Reply-To: <CAAA5faFNa1sQrj6Yfq+hrXfUOi0Lek4qL8Zzpdv27-4+Z4n6mQ@mail.gmail.com>
+ Luca, Emmanuel
On Tue, May 31, 2016 at 10:06:57PM -0600, Reinoud Koornstra wrote:
> Today I compiled 4.6+ and pulled sources today
> iwlwifi isn't super smooth.
I assume you mean wireless-testing, based on 4.7-rc1 (as this email is
in reply to my announcement of same).
>
> [ 112.345457] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> [ 112.349002] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> [ 112.349647] wlp4s0: authenticated
> [ 112.352456] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> [ 112.353764] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b (capab=0x11
> status=0 aid=3)
> [ 112.355035] wlp4s0: associated
> [ 112.355393] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
> [ 118.616327] wlp4s0: deauthenticated from 00:30:44:1d:cf:2b (Reason:
> 15=4WAY_HANDSHAKE_TIMEOUT)
> [ 128.673812] wlp4s0: authenticate with 00:30:44:1d:cf:2b
> [ 128.676997] wlp4s0: send auth to 00:30:44:1d:cf:2b (try 1/3)
> [ 128.677648] wlp4s0: authenticated
> [ 128.678691] wlp4s0: associate with 00:30:44:1d:cf:2b (try 1/3)
> [ 128.679807] wlp4s0: RX AssocResp from 00:30:44:1d:cf:2b (capab=0x11
> status=0 aid=3)
> [ 128.681198] wlp4s0: associated
>
> I never experienced the 4 way handshake 802.11i timeout in my home setup.
> With other setups plenty of times, especially with mediatek drivers. :)
> If you wish I can sniff and see which side is at fault.
I have not noticed any problems on my laptop with iwldvm on a 6205, with
latest wireless-testing. But maybe intel devs can weigh in.
--
Bob Copeland %% http://bobcopeland.com/
next prev parent reply other threads:[~2016-06-01 12:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 21:40 wireless-testing on 4.7 Bob Copeland
2016-06-01 4:06 ` Reinoud Koornstra
2016-06-01 12:54 ` Bob Copeland [this message]
2016-06-01 13:19 ` Coelho, Luciano
2016-06-01 22:08 ` Reinoud Koornstra
2016-06-02 4:27 ` Coelho, Luciano
2016-06-02 8:02 ` Reinoud Koornstra
2016-06-02 8:16 ` Luca Coelho
2016-06-03 5:09 ` Reinoud Koornstra
2016-06-03 5:59 ` Luca Coelho
2016-06-06 1:09 ` Reinoud Koornstra
2016-06-06 8:08 ` Luca Coelho
2016-06-04 14:57 ` wireless-drivers-next open for 4.8 Kalle Valo
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=20160601125453.GB12977@localhost \
--to=me@bobcopeland.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=reinoudkoornstra@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 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.