From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Wolfgang Breyha <wbreyha@gmx.net>, johannes.berg@intel.com
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi havoc on some APs (rekeying?)
Date: Fri, 09 Dec 2011 09:23:56 -0800 [thread overview]
Message-ID: <1323451436.13074.158.camel@wwguy-huron> (raw)
In-Reply-To: <4EE24DF4.4020301@gmx.net>
Johannes,
Anything changed in this area?
Thanks
Wey
On Fri, 2011-12-09 at 10:05 -0800, Wolfgang Breyha wrote:
> On 09/12/11 17:02, Guy, Wey-Yi wrote:
> > Hi Wolfgang,
> >
> > I don't have the similar AP here for testing. by looking at the log,
> > looks like there is a issue while you scan.
> >
> > Could you please try this patch and see if make any different? it is a
> > long shot, but I just like to see if it make any different at all
> >
> > once you apply the patch, please make sure P2P is disabled in .config
>
> Done that... iwlwifi says...
> > [ 833.360213] iwlwifi 0000:43:00.0: CONFIG_IWLWIFI_DEBUG enabled
> > [ 833.360215] iwlwifi 0000:43:00.0: CONFIG_IWLWIFI_DEBUGFS enabled
> > [ 833.360217] iwlwifi 0000:43:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled
> > [ 833.360219] iwlwifi 0000:43:00.0: CONFIG_IWLWIFI_DEVICE_SVTOOL enabled
> > [ 833.360222] iwlwifi 0000:43:00.0: CONFIG_IWLWIFI_P2P disabled
> > [ 833.360228] iwlwifi 0000:43:00.0: Detected Intel(R) Centrino(R) Advanced-N 6200 AGN, REV=0x74
>
> But it still occurs. This time it started again right after the 2.
> rekeying event. wpa_supplicant logged.
> > Associated with 00:80:48:xx:xx:xx
> > WPA: Key negotiation completed with 00:80:48:xx:xx:xx [PTK=CCMP GTK=TKIP]
> > CTRL-EVENT-CONNECTED - Connection to 00:80:48:xx:xx9:xx completed (reauth) [id=0 id_str=]
> > WPA: Group rekeying completed with 00:80:48:xx:xx:xx [GTK=TKIP]
> > WPA: Group rekeying completed with 00:80:48:xx:xx:xx [GTK=TKIP]
>
> I failed to mention that I used F14 with compat-wireless from arround
> march of 2011 before I upgraded to F16 in my first mail. With this
> version I had no troubles with the exactly same AP and my 2540p.
>
> Greetings, Wolfgang
> ..
>
>
>
> >
> > Thanks
> > Wey
next prev parent reply other threads:[~2011-12-09 18:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 14:50 iwlwifi havoc on some APs (rekeying?) Wolfgang Breyha
2011-12-09 16:02 ` Guy, Wey-Yi
2011-12-09 18:05 ` Wolfgang Breyha
2011-12-09 17:23 ` Guy, Wey-Yi [this message]
2011-12-09 18:26 ` Johannes Berg
2011-12-09 17:44 ` Guy, Wey-Yi
2011-12-10 13:02 ` Wolfgang Breyha
2011-12-12 9:04 ` Johannes Berg
2011-12-12 10:09 ` Wolfgang Breyha
2011-12-12 10:12 ` Johannes Berg
2011-12-12 11:21 ` Wolfgang Breyha
2011-12-12 17:48 ` Johannes Berg
2011-12-12 18:17 ` Wolfgang Breyha
2011-12-13 15:38 ` Johannes Berg
2011-12-14 14:22 ` Wolfgang Breyha
2011-12-14 22:10 ` Johannes Berg
2011-12-14 22:51 ` Daniel Halperin
2011-12-14 22:55 ` Johannes Berg
2011-12-14 23:07 ` Wolfgang Breyha
2011-12-15 0:46 ` Wolfgang Breyha
2011-12-15 13:01 ` Johannes Berg
2011-12-15 19:47 ` Wolfgang Breyha
2011-12-12 19:39 ` Wolfgang Breyha
2012-02-18 13:09 ` Johannes Berg
2012-02-24 7:25 ` 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=1323451436.13074.158.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wbreyha@gmx.net \
/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.