Created attachment 283435 [details] dmesg Me again - this time not "STATISTICS_CMD" or "Got an HT RATE", but "BAD COMMAND" all of a sudden. Intel 8265 FW 36.9f0a2d68.0 Arch Linux 5.1.9 wpa_supplicant.conf: bgscan="simple:20:-70:60" autoscan=periodic:30 [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: FW Error notification: type 0x00000000 cmd_id 0xA7 [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: FW Error notification: seq 0x00F0 service 0x000000A7 [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: FW Error notification: timestamp 0x00000003EF1DBAEC [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000. [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: Start IWL Error Log Dump: [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: Status: 0x00000100, count: 6 [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: Loaded firmware version: 36.9f0a2d68.0 [Tue Jun 25 13:07:14 2019] iwlwifi 0000:01:00.0: 0x00000038 | BAD_COMMAND A little desperate by now - what are we doing wrong?! :-(
Why do you use TDLS? Looks like your user space is doing messy stuff. Anyway, this is already fixed. *** This bug has been marked as a duplicate of bug 203775 ***
>Why do you use TDLS? no idea what TDLS is. I'm generating a wpa_supplicant.conf: >ctrl_interface=DIR=/var/run/wpa_supplicant >bgscan="simple:20:-70:60" >network={ > ssid="yyyyyyyy" > scan_ssid=1 > key_mgmt=FT-PSK WPA-PSK > psk="xxxxxxxx" >} and firing it up with >wpa_supplicant -B -iwlp1s0 -c /opt/mmmmmmmm/tmp/wpa_supplicant.conf that's all I do.
Then I suggest you check the supplicant logs. Anyway, the new firmware has the fix: we don't advertise TDLS anymore.