Created attachment 277369 [details] dmesg and iwlwifi modinfo When connecting to WPA Wi-Fi networks, iwlwifi reports "No beacon heard and the time event is over already" 0.6 secs after wifi interface "authenticated". However connect to open networks works fine. Have tried to connect to different APs, reboot APs, and lower DTIM periods, none of them works. Related dmesg and modinfo of iwlwifi is attached. firmware-version: 38.c0e03d94.0 srcversion: A082116DEC439F44B0AAD63 vermagic: 4.17.6-1-ARCH SMP preempt mod_unload modversions
Please record tracing of this and if possible, an air sniffer capture with an external device. Information on how to do so: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
Created attachment 277377 [details] trace output Output trace.dat by `sudo trace-cmd record -e iwlwifi -e mac80211 -e cfg80211 -e iwlwifi_msg` attached. Sorry but I can't provide sniffing data now.
You can use your 9260 as an air sniffer. Of course you won't be able to associate to your AP but it'll help to see how your AP behaves. What is the model of the AP BTW?
Created attachment 277379 [details] 9260AC as sniffer Did a sniffer on my 9260AC. I used my OnePlus phone to connect and disconnect on the WiFi network, phone shows as OneplusT_37:8f:5f, AP shows as BelkinIn_96:0b:18. My AP is LINKSYS EA6400 running AsusWrt-Merlin.
Thanks. I'll try to take a look later.
Ok, I went to the wrong direction: Here is the lead to the problem: [ 93.262641] wlp2s0: authenticate with 94:10:3e:96:0b:18 [ 93.268848] wlp2s0: send auth to 94:10:3e:96:0b:18 (try 1/3) [ 93.306653] wlp2s0: authenticated [ 93.883282] iwlwifi 0000:02:00.0: No beacon heard and the time event is over already... We authenticate, but don't associate. The supplicant is in charge of moving to the association step. What supplicant do you use? Do you use the driver inside the kernel, or an out of tree driver? Can you share the logs from the supplicant?
I'm using wpa_supplicant v2.6, with nl80211. driver is in kernel, supplicant log here: Jul 18 00:29:03 Gyc-Arch-Linux systemd[1]: Starting WPA supplicant... Jul 18 00:29:03 Gyc-Arch-Linux wpa_supplicant[620]: Successfully initialized wpa_supplicant Jul 18 00:29:03 Gyc-Arch-Linux systemd[1]: Started WPA supplicant. Jul 18 02:13:37 Gyc-Arch-Linux wpa_supplicant[620]: wlp2s0: SME: Trying to authenticate with 94:10:3e:96:0b:18 (SSID='<ssid>' freq=5180 MHz) Jul 18 02:13:45 Gyc-Arch-Linux wpa_supplicant[620]: wlp2s0: SME: Trying to authenticate with 94:10:3e:96:0b:18 (SSID='<ssid>' freq=5180 MHz) Jul 18 02:13:53 Gyc-Arch-Linux wpa_supplicant[620]: wlp2s0: SME: Trying to authenticate with 94:10:3e:96:0b:18 (SSID='<ssid>' freq=5180 MHz) Jul 18 02:13:59 Gyc-Arch-Linux wpa_supplicant[620]: wlp2s0: Reject scan trigger since one is already pending
ok, we need to increase the log level of the supplicant
are you sure you don't have several instances of the supplicant fighting over the same wireless interface?
Oh! After some reboots, the bug fixes itself magically :) I think you may be right, maybe multiple supplicant instances were running. Thanka a lot, you are so helpful!
I'm glad I could help.