Wireless
Issues related to Intel® Wireless Adapters and technologies
Announcements
Bluetooth mouse lag problem on specific systems with 11th Gen Intel processors. See details here.

How to Enable Wi-Fi 6E/ 6GHz Band Using Intel® Wi-Fi 6E AX210 (Gig+)
5637 Discussions

Ubuntu – Wpa_supplicant CTRL-EVENT-SCAN-FAILED error

Wanderzhd
New Contributor I
1,646 Views

Hi, We are using Intel Celeron 4205U + Intel 9560 2×2ac+BT HW running Ubuntu 18.04 system. When I enable hotspot, it works well but /var/log/syslog is filled with wpa_supplicant errors every second as below. And once disabled Hotspot, error will disappeared. Would you please help check if there anything wrong?

Line 3: Dec 1 00:06:49 pacom-EDGE90 wpa_supplicant[872]: message repeated 2 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 11: Dec 1 00:06:50 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 12: Dec 1 00:17:00 pacom-EDGE90 wpa_supplicant[872]: message repeated 609 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 14: Dec 1 00:17:01 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 15: Dec 1 00:26:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 549 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 25: Dec 1 00:26:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 26: Dec 1 00:31:10 pacom-EDGE90 wpa_supplicant[872]: message repeated 298 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 28: Dec 1 00:31:11 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 29: Dec 1 00:36:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 299 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 31: Dec 1 00:36:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 32: Dec 1 00:40:49 pacom-EDGE90 wpa_supplicant[872]: message repeated 277 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 43: Dec 1 00:40:50 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 44: Dec 1 00:40:51 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 46: Dec 1 00:40:52 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 47: Dec 1 01:02:52 pacom-EDGE90 wpa_supplicant[872]: message repeated 1318 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 51: Dec 1 01:02:53 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 52: Dec 1 01:11:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 497 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 62: Dec 1 01:11:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 63: Dec 1 01:16:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 299 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 65: Dec 1 01:16:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 66: Dec 1 01:17:00 pacom-EDGE90 wpa_supplicant[872]: message repeated 48 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 68: Dec 1 01:17:01 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 69: Dec 1 01:20:51 pacom-EDGE90 wpa_supplicant[872]: message repeated 230 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 81: Dec 1 01:20:52 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 82: Dec 1 01:36:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 917 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 92: Dec 1 01:36:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 93: Dec 1 01:40:43 pacom-EDGE90 wpa_supplicant[872]: message repeated 271 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 105: Dec 1 01:40:44 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 106: Dec 1 01:46:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 326 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 116: Dec 1 01:46:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 117: Dec 1 01:50:46 pacom-EDGE90 wpa_supplicant[872]: message repeated 274 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 128: Dec 1 01:50:47 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 129: Dec 1 01:50:48 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 131: Dec 1 01:50:49 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 132: Dec 1 02:01:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 621 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 142: Dec 1 02:01:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 143: Dec 1 02:01:45 pacom-EDGE90 wpa_supplicant[872]: message repeated 33 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 147: Dec 1 02:01:46 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 148: Dec 1 02:06:04 pacom-EDGE90 wpa_supplicant[872]: message repeated 258 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 159: Dec 1 02:06:05 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 161: Dec 1 02:06:06 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 162: Dec 1 02:17:00 pacom-EDGE90 wpa_supplicant[872]: message repeated 653 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 164: Dec 1 02:17:01 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 165: Dec 1 02:21:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 249 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 175: Dec 1 02:21:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 176: Dec 1 02:25:43 pacom-EDGE90 wpa_supplicant[872]: message repeated 271 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 188: Dec 1 02:25:44 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 189: Dec 1 03:01:00 pacom-EDGE90 wpa_supplicant[872]: message repeated 2113 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 193: Dec 1 03:01:01 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 194: Dec 1 03:17:00 pacom-EDGE90 wpa_supplicant[872]: message repeated 957 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 196: Dec 1 03:17:01 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Line 197: Dec 1 03:26:11 pacom-EDGE90 wpa_supplicant[872]: message repeated 549 times: [ wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1]
Line 207: Dec 1 03:26:12 pacom-EDGE90 wpa_supplicant[872]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1

 

BRs.

Dong

0 Kudos
1 Solution
Wanderzhd
New Contributor I
1,603 Views
5 Replies
Sebastian_M_Intel
Moderator
1,630 Views

Hello Wanderzhd,  

 

Thank you for posting on the Intel® communities.    

  

In order to better assist you, please provide the following:  

  

1. Provide the Intel® System Support Utility for the Linux* Operating System for more details: https://downloadcenter.intel.com/download/26735/Intel-System-Support-Utility-for-the-Linux-Operating... 

2. Is this the original adapter that came pre-installed on your computer or did you change/install the adapter to this one?   

3. Besides the errors in /var/log/syslog, do you receive any other issue?  

4. Run the following commands and send us the outcome:  

  • modinfo iwlwifi > If there is no output, then the module isn’t installed this is the distribution installation issue.  
  • lsmod | grep iwlwifi > If the result is empty, the driver hasn't been loaded. Most likely to be a distribution issue.  
  • To verify, please type: dmesg | grep iwlwifi > If the result is empty, the driver wasn’t initialized and this is a distribution issue. If there is a result populated, proceed with the next step.   
  • dmesg | grep “no suitable firmware found!” > If the result is not empty, it means you don't have a suitable FW (api mentioned in the dmesg).  
  • Please visit here: h ttps://wireless.wiki.kernel.org/en/users/drivers/iwlwifi  for supported FW,  or here https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ for the latest versions.  

  

5. If the above steps don't work, collect the debug data:  

  

Type: dmesg | grep ASSERT    

  

If the output is empty, please follow this wiki: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging  to extract dmesg and trace-cmd.  

  

If the output has value, please collect from the wiki FW dump too.  

  

Regards,  

  

Sebastian M  

Intel Customer Support Technician   


Wanderzhd
New Contributor I
1,624 Views

Hi Sebastian,

We buy the devices from Lenovo,  you can get detailed info in below link:

https://www.lenovo.com/us/en/desktops-and-all-in-ones/thinkcentre/m-series-tiny/ThinkCentre-M90n-IoT...

WiFi works well in Client and Hotspot mode. The reason why we noticed these errors is that recently we enabled hotspot and Bluetooth together, we found that the BT connection is not stable, it will disconnected randomly. But if we disable Hotspot mode, BT works well.  We are wondering if the error logs are related with the issue.

pacom@pacom-EDGE90:/data$ modinfo iwlwifi
filename: /lib/modules/4.15.0-1043-oem/kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko
license: GPL
author: Copyright(c) 2003- 2015 Intel Corporation <linuxwifi@intel.com>
description: Intel(R) Wireless WiFi driver for Linux
firmware: iwlwifi-100-5.ucode
firmware: iwlwifi-1000-5.ucode
firmware: iwlwifi-135-6.ucode

pacom@pacom-EDGE90:/data$ lsmod | grep iwlwifi
iwlwifi 290816 1 iwlmvm
cfg80211 622592 3 iwlmvm,iwlwifi,mac80211

BRs.

Dong

Sebastian_M_Intel
Moderator
1,610 Views

Hello Wanderzhd,   

 

Thank you for your reply. 

 

Please let me review this behavior internally. In the meantime, can you check this forum and see if the response here helps you with this issue?  https://askubuntu.com/questions/1255634/wpa-supplicant-ctrl-event-scan-failed-error  

 

Once we have an update, we will post it on this thread. Kindly wait for a response.  

 

Regards,   

   

Sebastian M   

Intel Customer Support Technician 

 

Links to third-party sites and references to third-party trademarks are provided for convenience and illustrative purposes only. Unless explicitly stated, Intel® is not responsible for the contents of such links, and no third-party endorsement of Intel or any of its products is implied.  


Wanderzhd
New Contributor I
1,604 Views
Sebastian_M_Intel
Moderator
1,563 Views

Hello Wanderzhd,    

  

Thank you for the update. 

 

I am glad to hear that it worked, based on that, we will proceed to close this inquiry. 

 

If you need further assistance, please create a new thread and we will gladly assist you. 

  

Regards,    

    

Sebastian M    

Intel Customer Support Technician  


Reply