Hi,

 > seems that your system is trying to connect to two different APs 
forth and back

Yes, this is a major network with multiple APs for each of its SSIDs 
always available. Unlike my single AP home network, unsurprisingly.

 > whether you have more than wpa_supplicant instance running

I disabled wicd, invoked wpa_supplicant manually and checked with pidof, 
there isn't. I also checked for changes with wpa_supplicant 2.3 vs git, 
none.

 > was this working before you upgraded to iwlwifi-next 5bff6536f742

That's the weird part, IIRC it and the 16er firmware actually were 
working fine *with* it (I had 4.2-RCs running with available 
iwlwifi-next commits for weeks), which is why I was inclined to blame 
net.git until I found out that it currently doesn't work with the 
vanilla Arch 4.2-3 kernel either. Honestly no idea why.

But I'll check with iwlwifi-next-for-kalle-2015-08-23 tomorrow.

 > directions in our debugging wiki page

Two remarks on that page:
iwlfwdump.sh should probably get a note about chmod +x
trace-cmd is not part of standard kernel packages and thus should get a 
note that it may need to be installed separately

Since I wasn't aware of the latter, I'll only be able to post a trace in 
a bugzilla report tomorrow–

– if that isn't bugged as well: "echo 1 > 
/sys/kernel/debug/iwlwifi/0000\:02\:00.0/iwlmvm/fw_dbg_collect" 
currently yields a "file exists", cat'ing it an invalid argument error, 
"echo 1 >>" ostensibly works but shows in dmesg as (1), see "excerpts" 
attachment.

(2) shows an example of what wpa_supplicant currently prints. This 
continues ad inf, and at some non-predictable point the driver bug(s?) 
and/or FW reset appear in dmesg. (3) shows two more variants I got with 
net.git (now at 7845989) and Arch's 4.2-3 kernel.

dmesg is also spammed with "r8169 0000:03:00.1 enp3s0f1: 
rtl_counters_cond == 1 (loop: 1000, delay: 10).", but that's prob an 
unrelated bug which has been there (but far) less frequent since early 4.2.

As for net.git kernel config, "grep IWLWIFI":
CONFIG_IWLWIFI=m
CONFIG_IWLWIFI_LEDS=y
CONFIG_IWLWIFI_OPMODE_MODULAR=y
CONFIG_IWLWIFI_BCAST_FILTERING=y
CONFIG_IWLWIFI_UAPSD=y
CONFIG_IWLWIFI_DEBUG=y
CONFIG_IWLWIFI_DEBUGFS=y
# CONFIG_IWLWIFI_DEBUG_EXPERIMENTAL_UCODE is not set
CONFIG_IWLWIFI_DEVICE_TRACING=y

-- Andreas

On 08.09.2015 08:31, Luca Coelho wrote:
> Adding our new list to CC.
>
>
> On Tue, 2015-09-08 at 08:37 +0300, Luca Coelho wrote:
>> 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.
>> --
>> 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