Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most see it every 1 second, not 10 seconds. I've tried numerous suggested solutions that were all ineffective (reboot after changes). These included:
- downgrading wpa_supplicant (none available) - downgrading NM (restored current) - eliminating all NM interfaces except the active one - eliminated the ethernet (wired) NM interface - several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most see it every 1 second, not 10 seconds. I've tried numerous suggested solutions that were all ineffective (reboot after changes). These included:
- downgrading wpa_supplicant (none available)
- downgrading NM (restored current)
- eliminating all NM interfaces except the active one
- eliminated the ethernet (wired) NM interface
- several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
Have you seen https://bugzilla.redhat.com/show_bug.cgi?id=1703745? This indicates the messages are due to wpa_supplicant not properly handling your wifi hardware, so you may want to check upstream. This could be an issue with the firmware version provided by Fedora.
My Fedora 33 system has wpa_supplicant messages in "the systemd(1) journal as written by systemd-journald.service(8)." so either Fedora 34 has changed logging for wpa_supplicant or you have a local wpa_supplicant version/configuration.
This sort of problem often appears across multiple linux distros, so it is worth checking for similar issues on other distros, in particular Ubuntu and Arch.
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most see it every 1 second, not 10 seconds. I've tried numerous suggested solutions that were all ineffective (reboot after changes). These included:
- downgrading wpa_supplicant (none available)
- downgrading NM (restored current)
- eliminating all NM interfaces except the active one
- eliminated the ethernet (wired) NM interface
- several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
Have you seen https://bugzilla.redhat.com/show_bug.cgi?id=1703745? This indicates the messages are due to wpa_supplicant not properly handling your wifi hardware, so you may want to check upstream. This could be an issue with the firmware version provided by Fedora.
My Fedora 33 system has wpa_supplicant messages in "the systemd(1) journal as written by systemd-journald.service(8)." so either Fedora 34 has changed logging for wpa_supplicant or you have a local wpa_supplicant version/configuration.
This sort of problem often appears across multiple linux distros, so it is worth checking for similar issues on other distros, in particular Ubuntu and Arch.
My bugzilla-foo is weak, I overlooked that one. Couple of things.
I'm not having connection problems at all.
Yes, most of the websearch results are Arch & Ubuntu In that bugzilla report the messages the messages end with "retries=1", as do most of the found reports. Mine do not.
Logging to /var/log/message is just my old school habit. systemD journal gets them too.
wpa_supplicant is totally stock. Never even tried to look at config before.
Does wifi work if wpa_supplicant service is disabled?
Jon
On 02/07/2021 00:40, Jon LaBadie wrote:
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most see it every 1 second, not 10 seconds. I've tried numerous suggested solutions that were all ineffective (reboot after changes). These included:
- downgrading wpa_supplicant (none available)
- downgrading NM (restored current)
- eliminating all NM interfaces except the active one
- eliminated the ethernet (wired) NM interface
- several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
Have you seen https://bugzilla.redhat.com/show_bug.cgi?id=1703745? This indicates the messages are due to wpa_supplicant not properly handling your wifi hardware, so you may want to check upstream. This could be an issue with the firmware version provided by Fedora.
My Fedora 33 system has wpa_supplicant messages in "the systemd(1) journal as written by systemd-journald.service(8)." so either Fedora 34 has changed logging for wpa_supplicant or you have a local wpa_supplicant version/configuration.
This sort of problem often appears across multiple linux distros, so it is worth checking for similar issues on other distros, in particular Ubuntu and Arch.
My bugzilla-foo is weak, I overlooked that one. Couple of things.
I'm not having connection problems at all.
Yes, most of the websearch results are Arch & Ubuntu In that bugzilla report the messages the messages end with "retries=1", as do most of the found reports. Mine do not.
Logging to /var/log/message is just my old school habit. systemD journal gets them too.
wpa_supplicant is totally stock. Never even tried to look at config before.
Does wifi work if wpa_supplicant service is disabled?
Well, what I would do in this case is to first do "lspci -v" and compare my hardware specs and driver in use with that reported in the BZ to see how they match up. It is not inconceivable that an error message may be the same while the underlying issue different than reported in a BZ.
On Fri, Jul 02, 2021 at 05:36:30AM +0800, Ed Greshko wrote:
On 02/07/2021 00:40, Jon LaBadie wrote:
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
A websearch shows this is not an uncommon problem though most see it every 1 second, not 10 seconds. I've tried numerous suggested solutions that were all ineffective (reboot after changes). These included:
- downgrading wpa_supplicant (none available)
- downgrading NM (restored current)
- eliminating all NM interfaces except the active one
- eliminated the ethernet (wired) NM interface
- several .conf changes for NM and wpa_supplicant
Still the messages keep coming (200K+).
Any suggestions?
Have you seen https://bugzilla.redhat.com/show_bug.cgi?id=1703745? This indicates the messages are due to wpa_supplicant not properly handling your wifi hardware, so you may want to check upstream. This could be an issue with the firmware version provided by Fedora.
My Fedora 33 system has wpa_supplicant messages in "the systemd(1) journal as written by systemd-journald.service(8)." so either Fedora 34 has changed logging for wpa_supplicant or you have a local wpa_supplicant version/configuration.
This sort of problem often appears across multiple linux distros, so it is worth checking for similar issues on other distros, in particular Ubuntu and Arch.
My bugzilla-foo is weak, I overlooked that one. Couple of things.
I'm not having connection problems at all.
Yes, most of the websearch results are Arch & Ubuntu In that bugzilla report the messages the messages end with "retries=1", as do most of the found reports. Mine do not.
Logging to /var/log/message is just my old school habit. systemD journal gets them too.
wpa_supplicant is totally stock. Never even tried to look at config before.
Does wifi work if wpa_supplicant service is disabled?
Well, what I would do in this case is to first do "lspci -v" and compare my hardware specs and driver in use with that reported in the BZ to see how they match up. It is not inconceivable that an error message may be the same while the underlying issue different than reported in a BZ.
Not a driver match. Bug report is Broadcom, mine is Intel (iwlwifi)
On 02/07/2021 09:45, Jon LaBadie wrote:
On Fri, Jul 02, 2021 at 05:36:30AM +0800, Ed Greshko wrote:
Well, what I would do in this case is to first do "lspci -v" and compare my hardware specs and driver in use with that reported in the BZ to see how they match up. It is not inconceivable that an error message may be the same while the underlying issue different than reported in a BZ.
Not a driver match. Bug report is Broadcom, mine is Intel (iwlwifi)
I see. So, in summary. Your wifi is working OK. The device wlo1 is connected to an access point. And the logs are getting flooded with messages.
Would you mind to post the output of "sudo lspci -vnn" for that device for completeness?
It may be that iwlwifi has been updated upstream but the changes have yet made it to fedora. Are you on F34? I don't think you mentioned it
On Fri, Jul 02, 2021 at 01:50:57PM +0800, Ed Greshko wrote:
On 02/07/2021 09:45, Jon LaBadie wrote:
On Fri, Jul 02, 2021 at 05:36:30AM +0800, Ed Greshko wrote:
Well, what I would do in this case is to first do "lspci -v" and compare my hardware specs and driver in use with that reported in the BZ to see how they match up. It is not inconceivable that an error message may be the same while the underlying issue different than reported in a BZ.
Not a driver match. Bug report is Broadcom, mine is Intel (iwlwifi)
I see. So, in summary. Your wifi is working OK. The device wlo1 is connected to an access point. And the logs are getting flooded with messages.
Would you mind to post the output of "sudo lspci -vnn" for that device for completeness?
It may be that iwlwifi has been updated upstream but the changes have yet made it to fedora. Are you on F34? I don't think you mentioned it
I did:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
$ sudo lspci -vnn 00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM Controller [8086:3e34] (rev 0b) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information: Len=10 <?> Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at a0000000 (64-bit, non-prefetchable) [size=16M] Memory at 90000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915
00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0b) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: fast devsel, IRQ 16 Memory at a1310000 (64-bit, non-prefetchable) [size=32K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Capabilities: [e0] Vendor Specific Information: Len=0c <?> Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: fast devsel, IRQ 11 Memory at a132e000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [dc] Power Management version 2 Capabilities: [f0] PCI Advanced Features
00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Point-LP Thermal Controller [8086:9df9] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: fast devsel, IRQ 16 Memory at a132d000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal
00:13.0 Serial controller [0700]: Intel Corporation Cannon Point-LP Integrated Sensor Hub [8086:9dfc] (rev 30) (prog-if 00 [8250]) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 20 Memory at a1324000 (64-bit, non-prefetchable) [size=8K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel_ish_ipc Kernel modules: intel_ish_ipc
00:14.0 USB controller [0c03]: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller [8086:9ded] (rev 30) (prog-if 30 [XHCI]) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, medium devsel, latency 0, IRQ 125 Memory at a1300000 (64-bit, non-prefetchable) [size=64K] Capabilities: [70] Power Management version 2 Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: xhci_hcd
00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: fast devsel Memory at a1322000 (64-bit, non-prefetchable) [disabled] [size=8K] Memory at a132c000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [80] Power Management version 3
00:14.3 Network controller [0280]: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30) DeviceName: Onboard - Ethernet Subsystem: Intel Corporation Device [8086:42a4] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at a131c000 (64-bit, non-prefetchable) [size=16K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [80] MSI-X: Enable+ Count=16 Masked- Capabilities: [100] Null Capabilities: [14c] Latency Tolerance Reporting Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?> Kernel driver in use: iwlwifi Kernel modules: iwlwifi
00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 [8086:9de8] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at 8e800000 (64-bit, non-prefetchable) [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss
00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 [8086:9de9] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 8e801000 (64-bit, non-prefetchable) [virtual] [size=4K] Capabilities: [80] Power Management version 3 Capabilities: [90] Vendor Specific Information: Len=14 <?> Kernel driver in use: intel-lpss
00:16.0 Communication controller [0780]: Intel Corporation Cannon Point-LP MEI Controller #1 [8086:9de0] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 153 Memory at a1329000 (64-bit, non-prefetchable) [size=4K] Capabilities: [50] Power Management version 3 Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [a4] Vendor Specific Information: Len=14 <?> Kernel driver in use: mei_me Kernel modules: mei_me
00:17.0 SATA controller [0106]: Intel Corporation Cannon Point-LP SATA Controller [AHCI Mode] [8086:9dd3] (rev 30) (prog-if 01 [AHCI 1.0]) DeviceName: Onboard - SATA Subsystem: Dell Device [1028:08a8] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 124 Memory at a1320000 (32-bit, non-prefetchable) [size=8K] Memory at a1328000 (32-bit, non-prefetchable) [size=256] I/O ports at 4090 [size=8] I/O ports at 4080 [size=4] I/O ports at 4060 [size=32] Memory at a1327000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci
00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Point-LP PCI Express Root Port #9 [8086:9db0] (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 00003000-00003fff [size=4K] Memory behind bridge: a1200000-a12fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device [1028:08a8] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [150] Precision Time Measurement Capabilities: [200] L1 PM Substates Capabilities: [220] Secondary PCI Express Capabilities: [250] Downstream Port Containment Kernel driver in use: pcieport
00:1d.4 PCI bridge [0604]: Intel Corporation Cannon Point-LP PCI Express Root Port #13 [8086:9db4] (rev f0) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 123 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: a1100000-a11fffff [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Dell Device [1028:08a8] Capabilities: [a0] Power Management version 3 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Access Control Services Capabilities: [150] Precision Time Measurement Capabilities: [200] L1 PM Substates Capabilities: [220] Secondary PCI Express Capabilities: [250] Downstream Port Containment Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation Cannon Point-LP LPC Controller [8086:9d84] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0
00:1f.3 Audio device [0403]: Intel Corporation Cannon Point-LP High Definition Audio Controller [8086:9dc8] (rev 30) (prog-if 80) DeviceName: Onboard - Sound Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 32, IRQ 160 Memory at a1318000 (64-bit, non-prefetchable) [size=16K] Memory at a1000000 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 <?> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl, snd_sof_pci_intel_cnl
00:1f.4 SMBus [0c05]: Intel Corporation Cannon Point-LP SMBus Controller [8086:9da3] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: medium devsel, IRQ 16 Memory at a1326000 (64-bit, non-prefetchable) [size=256] I/O ports at efa0 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller [8086:9da4] (rev 30) DeviceName: Onboard - Other Subsystem: Dell Device [1028:08a8] Flags: fast devsel Memory at fe010000 (32-bit, non-prefetchable) [size=4K]
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Dell Device [1028:08a8] Flags: bus master, fast devsel, latency 0, IRQ 16 I/O ports at 3000 [size=256] Memory at a1204000 (64-bit, non-prefetchable) [size=4K] Memory at a1200000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable+ Count=4 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00 Capabilities: [170] Latency Tolerance Reporting Capabilities: [178] L1 PM Substates Kernel driver in use: r8169 Kernel modules: r8169
02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] (prog-if 02 [NVM Express]) Subsystem: Samsung Electronics Co Ltd Device [144d:a801] Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0 Memory at a1100000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [b0] MSI-X: Enable+ Count=33 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [158] Power Budgeting <?> Capabilities: [168] Secondary PCI Express Capabilities: [188] Latency Tolerance Reporting Capabilities: [190] L1 PM Substates Kernel driver in use: nvme Kernel modules: nvme
On Thu, 1 Jul 2021 at 13:41, Jon LaBadie jonfu@jgcomp.com wrote:
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
My bugzilla-foo is weak, I overlooked that one. Couple of things.
I'm not having connection problems at all.
TCPIP is very robust. Users often report "network is fine" but some switch is getting hammered. This has gotten worse now that real cheap hardware can generate scads of packets.
Yes, most of the websearch results are Arch & Ubuntu In that bugzilla report the messages the messages end with "retries=1", as do most of the found reports. Mine do not.
Logging to /var/log/message is just my old school habit. systemD journal gets them too.
wpa_supplicant is totally stock. Never even tried to look at config before.
Does wifi work if wpa_supplicant service is disabled?
Short answer is no, see "man wpa_supplicant".
On Sun, Jul 04, 2021 at 10:15:22AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 13:41, Jon LaBadie jonfu@jgcomp.com wrote:
On Thu, Jul 01, 2021 at 07:35:12AM -0300, George N. White III wrote:
On Thu, 1 Jul 2021 at 02:02, Jon LaBadie jonfu@jgcomp.com wrote:
Laptop running F34 with an "Intel Cannon Point-LP CNVi [Wireless-AC]" controller.
Every 10 seconds I get this error message (/var/log/messages):
wpa_supplicant[78893]: wlo1: CTRL-EVENT-SCAN-FAILED ret=-22
More digging. Journalctl shows the problem started about a week after a dnf system-upgrade to F34. Around the problem start, I find nothing in dnf history that seems related (NM connection editor an unlikely cause). Kernel update yes, but I've booted from several older kernels with all showing the problem.
Considering a reinstall from scratch, I booted from a live F34 USB. Problem did not appear in the "live boot"!!
Live boot used same version of wpa_supplicant I have on the system, but NM was one version older. I had tried downgrading NM before and it didn't help. But I tried again.
Reboot to system, problem exists. Downgrade NM, reboot, problem gone!!!! Reboot again, still gone. Later I updated NM to current version, reboot, problem still gone! Several reboots and overnight, problem still gone.
Though there have been kernel updates in the interim, those are the same steps I took 2 weeks ago that did not help. To confirm it I checked that dnf history showed the previous downgrade and journalctl shows a reboot 1 minute later.
#@#%$# computer bugs!!
Happy Independence Day to my fellow Americans.
Jon
-
Ed Greshko -
George N. White III -
Jon LaBadie