linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Andreas Reis <andreas.reis@gmail.com>, linux-wireless@vger.kernel.org
Cc: ilw@linux.intel.com
Subject: Re: iwlwifi: FW error in SYNC CMD MAC_CONTEXT_CMD
Date: Tue, 08 Sep 2015 08:37:56 +0300	[thread overview]
Message-ID: <1441690676.27148.11.camel@coelho.fi> (raw)
In-Reply-To: <55ED93D0.4070509@gmail.com>

Hi Anreas,

On Mon, 2015-09-07 at 15:40 +0200, Andreas Reis wrote:
> Updated to
> net.git: 46cdc9b (ie. with mac80211 2015-09-04)
> + iwlwifi-next.git commits up to 5bff653
> iwlwifi firmware: 16.215201.0
> 
> now connecting to my WPA-802.1X with a Intel 7260 fails, see dmesg.
> 
>  From the wifi's wpa_supplicant file (actually wicd somehow
> accumulated 
> different ones for this SSID, but the following should be it):
>      proto=RSN
>      key_mgmt=WPA-EAP
>      pairwise=CCMP
>      eap=PEAP
>      phase2="auth=MSCHAPv2"
> 
> Meanwhile my WPA2-PSK at home still works.

According to the dmesg you attached, it seems that we're bouncing
between two APs:

[  214.644607] wlp2s0: authenticate with 9c:1c:12:c1:26:82
...
[  214.798595] wlp2s0: deauthenticated from 9c:1c:12:c1:26:82 (Reason: 3=DEAUTH_LEAVING)
...
[  218.001901] wlp2s0: authenticate with 18:64:72:26:de:22
...
[  218.054498] wlp2s0: deauthenticated from 18:64:72:26:de:22 (Reason: 3=DEAUTH_LEAVING)

It seems that your system is trying to connect to two different APs
forth and back.  After each association succeeds, the userspace seems
to trigger a deauth (DEAUTH_LEAVING) and goes to the other AP again...

This sometimes indicates that two instances of wpa_supplicant are
competing with each other.  Can you check whether you have more than
one wpa_supplicant instance running?

In any case, there seems to be a driver bug at some point, because we
get a firmware SYSASSERT.  To debug that, could you follow the
directions in our debugging wiki page [1] and create a bug in bugzilla?
Please provide trace-cmd logs (as explained in the wiki) so we can try
to figure out what is going on.

One final question, was this working before you upgraded to iwlwifi
-next 5bff6536f742?

Thanks for reporting!

[1] https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging

--
Cheers,
Luca.

  reply	other threads:[~2015-09-08  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-07 13:40 iwlwifi: FW error in SYNC CMD MAC_CONTEXT_CMD Andreas Reis
2015-09-08  5:37 ` Luca Coelho [this message]
2015-09-08  6:31   ` Luca Coelho
2015-09-09 14:09     ` Andreas Reis
2015-09-10 20:00       ` [linuxwifi] " Luca Coelho
2015-09-11 16:32         ` Andreas Reis

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=1441690676.27148.11.camel@coelho.fi \
    --to=luca@coelho.fi \
    --cc=andreas.reis@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).