Errors relating to Wilocity 60g WiFi module in Fedora 30

The following errors continuously repeat in my system log,

Aug 27 20:53:27 localhost.localdomain wpa_supplicant[2685]: wlp4s0: Reject scan trigger since one is already pending
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:e2:36:a4 RF = 0x0000 (status 0x0000) bband = 0x00000000
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_set_oob_mode: oob_mode to 0
Aug 27 20:58:42 localhost.localdomain NetworkManager[2596]: <info>  [1566903522.3817] device (wlp4s0): set-hw-addr: set MAC address to D2:68:B4:E5:51:05 (scanning)
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:e2:36:a4 RF = 0x0000 (status 0x0000) bband = 0x00000000
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_set_oob_mode: oob_mode to 0
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_reset: Use firmware <wil6210.fw> + board <wil6210.brd>
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wmi_evt_ready: FW ver. 5.2.0.18(SW 18); MAC dc:ef:ca:e2:36:a4; 0 MID's
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_wait_for_fw_ready: FW ready after 9 ms. HW version 0x00000001
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_TX_CNT_TRSH = 500 usec
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_TX_IDL_CNT_TRSH = 13 usec
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_RX_CNT_TRSH = 500 usec
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_RX_IDL_CNT_TRSH = 13 usec
Aug 27 20:58:42 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_refresh_fw_capabilities: keep_radio_on_during_sleep (0)
Aug 27 20:58:42 localhost.localdomain NetworkManager[2596]: <info>  [1566903522.4571] device (wlp4s0): supplicant interface state: inactive -> disabled
Aug 27 20:58:42 localhost.localdomain NetworkManager[2596]: <info>  [1566903522.4571] device (p2p-dev-wlp4s0): supplicant management interface state: inactive -> disabled
Aug 27 20:58:42 localhost.localdomain NetworkManager[2596]: <info>  [1566903522.4643] device (wlp4s0): supplicant interface state: disabled -> inactive
Aug 27 20:58:42 localhost.localdomain NetworkManager[2596]: <info>  [1566903522.4644] device (p2p-dev-wlp4s0): supplicant management interface state: disabled -> inactive

I did a search for wil6210 which was mentioned in the error message and found it was a module for supporting Wilocity 60g Wi-Fi see https://cateee.net/lkddb/web-lkddb/WIL6210.html

I’m currently running kernel 5.2.7-200.fc30.x86_64

I’m new to Fedora and Linux so any help is much appreciated.

thanks,

1 Like

Here is a segment of the system log which first mentions about the wil6210 module before the error message in the previous post starts continuously repeating,

Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:e2:36:a4 RF = 0x0000 (status 0x0000) bband = 0x00000000
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_set_oob_mode: oob_mode to 0
Aug 27 19:45:12 localhost.localdomain NetworkManager[2596]: <info>  [1566899112.3818] device (wlp4s0): set-hw-addr: set MAC address to 2A:CE:56:13:55:6F (scanning)
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect: disconnect bssid=(null), reason=3
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: _wil6210_disconnect_complete: disconnect_complete: bssid=(null), reason=3
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader struct v2: MAC = dc:ef:ca:e2:36:a4 RF = 0x0000 (status 0x0000) bband = 0x00000000
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_get_bl_info: Boot Loader build 255.255.0.6836
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_set_oob_mode: oob_mode to 0
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_reset: Use firmware <wil6210.fw> + board <wil6210.brd>
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wmi_evt_ready: FW ver. 5.2.0.18(SW 18); MAC dc:ef:ca:e2:36:a4; 0 MID's
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_wait_for_fw_ready: FW ready after 8 ms. HW version 0x00000001
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_TX_CNT_TRSH = 500 usec
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_TX_IDL_CNT_TRSH = 13 usec
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_RX_CNT_TRSH = 500 usec
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_configure_interrupt_moderation: set ITR_RX_IDL_CNT_TRSH = 13 usec
Aug 27 19:45:12 localhost.localdomain kernel: wil6210 0000:04:00.0 wlp4s0: wil_refresh_fw_capabilities: keep_radio_on_during_sleep (0)
Aug 27 19:45:12 localhost.localdomain NetworkManager[2596]: <info>  [1566899112.4558] device (wlp4s0): supplicant interface state: ready -> disabled
Aug 27 19:45:12 localhost.localdomain NetworkManager[2596]: <info>  [1566899112.4559] device (p2p-dev-wlp4s0): supplicant management interface state: ready -> disabled
1 Like

Hello @fedoraforadam! Welcome to the community! Please take a minute to go through the informative posts in #start-here if you’ve not had a chance to do so.

The logs seem to be merely informative, but not errors. Are you experiencing issues with your wifi?

The link you gave further links to this page for the kernel module:

https://wireless.wiki.kernel.org/en/users/Drivers/wil6210

From the looks of it, it may not be completely supported. Could you check the ID of your wireless hardware using:

sudo lspci -v

Hello @FranciscoD, thanks for replying.

I’m actually using the Qualcomm Atheros QCA6174 802.11ac wireless adapter not the Wilocity wil6210 802.11ad adapter. I am experiencing issues with wi-fi drop outs in my guest Fedora 30 virtual machines but that is a totally different matter (I think) from what is happening here. I’m still currently investigating the Fedora 30 wi-fi drop out issue on my own for now. The issue here is that my host Fedora 30 machine keeps writing those messages to the system log and I need it to stop because that will unnecessarily shorten the life span of the SSD I’m planning to install Fedora on.

The PCIe ID of the Wilocity network adapter in my computer is 1ae9:0310 which is what the page you’ve shown me states as being supported by the wil6210 module.

I don’t know much about that particular hardware, unfortunately. Sorry.

The most common reason for drops and such logging is the hardware driver that is provided in the kernel to support it. Your best bet will be to file a bug upstream (kernel) and while it is fixed use hardware from a company that provides better support for Linux—Intel does pretty well.

If it’s the hardware driver, by the way, you should see the same issue on all Linux distributions since they all use the same Linux kernel source. If you do not see this issue on another distribution, then that would imply it being a Fedora specific issue which we can help you look into.

1 Like

I think it is a hardware driver issue because in Ubuntu 18.04 I do get errors relating to the Wilocity wil6210 802.11ad wi-fi adapter that repeats but they are different from the ones in Fedora 30. The errors reported by Ubuntu 18.04 are much shorter and seem to happen at wider intervals.

Aug 29 14:34:50 adam-threadripper-1950x dnsmasq-dhcp[2754]: DHCPREQUEST(virbr0) 192.168.123.48 52:54:00:46:42:67
Aug 29 14:34:50 adam-threadripper-1950x dnsmasq-dhcp[2754]: DHCPACK(virbr0) 192.168.123.48 52:54:00:46:42:67 WIN-0RHL4FO3B32
Aug 29 14:38:31 adam-threadripper-1950x kernel: wil6210 0000:04:00.0 wlp4s0: wil_halp_vote: HALP vote timed out    
Aug 29 14:41:40 adam-threadripper-1950x kernel: wil6210 0000:04:00.0 wlp4s0: wil_halp_vote: HALP vote timed out

@FranciscoD I’ll file a a bug upstream (kernel) later. Thanks for the help.

That could be down to different kernel versions, or different kernel build configurations.

Thanks. Sorry we couldn’t help more here. The quick doc has some tips on filing bugs that are general enough for all bug trackers:

https://docs.fedoraproject.org/en-US/quick-docs/howto-file-a-bug/

1 Like