wl/b43 drivers conflict with tg3

jghodd · 2023-06-25 20:06:05

@seth - i did blacklist tg3 - probably a couple dozen times on and off over the 2 months i was trying to get this going before posting here. only wireless after reboot until i modprobed tg3. then the wireless was deactivated.

for whatever reason, tg3 somehow always gets top priority. the only way to fully disable it if all modules are loaded is to rmmod it. doesn't matter what order things are done, if tg3 is loaded and the cable is plugged in, tg3 appears to be forcing all other NICs to deactivate (but appearances can be deceptive). so far, i'm not seeing anything in the driver code that resembles that kind of logic, but then again, between the source and all the header files being pulled in, you'd have to be the actual developer to get your head around the entirety of the driver's functionality and interaction with the rest of the kernel.

Last edited by jghodd (2023-06-25 20:09:14)

seth · 2023-06-25 20:13:19

only wireless after reboot until i modprobed tg3.

That's what I'd suspect.

for whatever reason, tg3 somehow always gets top priority

That I severely doubt. tg3 doesn't depend on any of the *80211 modules, it's not gonna drive a wifi chip. Ever. Not even attempt.

My very best guess remains that the flaky eth0 connection sends NM into a frenzy and the wifi NIC or AP ends up "gfy"
=> https://bbs.archlinux.org/viewtopic.php … 4#p2106144
*How* was "neither interface [] actually working"?

Though, maybe interesting, is the eth0 connection also flickering when the wl module isn't loaded?

Edi, btw "@seth" does absolutely nothing in order to notify me - you can omit that.

Last edited by seth (2023-06-25 20:14:01)

jghodd · 2023-06-27 05:11:40

There is a known conflict between broadcom-wl and tg3 - https://wiki.archlinux.org/title/broadcom_wireless

4. Known issues
4.1 Ethernet card is not detected
Broadcom wireless module has a history of conflicting with Broadcom Ethernet module.
Due to conflicts between wl (wireless module) and tg3 (Ethernet module), tg3 is now blacklisted as of broadcom-wl-dkms 6.30.223.271-27[2]. See also FS#70476.
This also affects broadcom-wl as it is built based on broadcom-wl-dkms.

I think broadcom-wl has played itself out in this instance - it is known to conflict with the ethernet driver. Next up, I suppose, is to try again to get b43 working.

By "top priority", I didn't mean it'd take over the wireless adapter, I meant that it disables, or perhaps has a memory overlap/conflict with, or corrupts the broadcom-wl driver. That kind of priority.
if (broadcom-wl loaded)
disable broadcom-wl

In other words, plugging in the rj45 cable activates the tg3 driver and broadcom-wl is disabled. Doesn;t do that the other way around, so that gives a certain priority to tg3. The odd thing is that both drivers when active (wl without tg3, or just tg3) work as expected. I get no bad scan error messages for wls1 when tg3 isn;t connected, but I do when that cable is plugged in. Something here makes no sense...

Last edited by jghodd (2023-06-27 05:26:13)

seth · 2023-06-27 06:20:43

1. The subject of this thread says "wl/b43", not "wl"
2. not "in this instance", broadcom is the only wifi chip which gets afforded its own wiki, because it's a complete mess and the worst possible wifi chip one can have (at least on linux)
3. "Something here makes no sense":
If we take your theory and the unsourced conflict claims at face value what might happen is that the presence of the wl driver causes the eth0 to flicker. That flicker could then trigger the NM daemon to wet itself and lose the wifi in the frenzy to reconfigure the setup.

Instead of wasting time on trying to find confirmation for your hypothesis, test it:
1. does the ethernet connection flicker when wl isn't loaded?
2. get NM and its efforts to be smart™ out of the equation in an effort to eliminate variables

jghodd · 2023-06-27 20:53:08

so. a few journalctl greps.

without broadcom-wl or b43 (wl, b43* blacklisted):

[root@bslxhp64 log]# journalctl -b | grep tg3
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0: invalid VPD tag 0xff (size 65535) at offset 128
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0 eth0: Tigon3 [partno(BCM95751) rev b002] (PCI Express) MAC address 00:25:b3:7e:92:81
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0 eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Jun 27 14:38:59 bslxhp64 kernel: tg3 0000:85:00.0 ens5: renamed from eth0
Jun 27 14:39:23 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 14:39:23 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 27 14:39:23 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 27 14:39:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 14:39:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX

after reboot with wl (wl not blacklisted):

[root@bslxhp64 log]# journalctl -b | grep tg3
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0: invalid VPD tag 0xff (size 65535) at offset 128
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0 eth0: Tigon3 [partno(BCM95751) rev b002] (PCI Express) MAC address 00:25:b3:7e:92:81
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0 eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Jun 27 15:18:54 bslxhp64 kernel: tg3 0000:85:00.0 ens5: renamed from eth0
Jun 27 15:19:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:19:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 27 15:19:17 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 27 15:19:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:19:19 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX

after disconnecting rj45 (wl enabled):

[root@bslxhp64 jghodd]# journalctl -b | grep tg3
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0: invalid VPD tag 0xff (size 65535) at offset 128
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0 eth0: Tigon3 [partno(BCM95751) rev b002] (PCI Express) MAC address 00:25:b3:7e:92:81
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0 eth0: attached PHY is 5787 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0 eth0: dma_rwctrl[76180000] dma_mask[64-bit]
Jun 27 15:33:06 bslxhp64 kernel: tg3 0000:85:00.0 ens5: renamed from eth0
Jun 27 15:33:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:33:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 27 15:33:25 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 27 15:33:27 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:33:27 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 27 15:41:26 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down

[root@bslxhp64 jghodd]# journalctl -b | grep wls1
Jun 27 15:41:38 bslxhp64 wpa_supplicant[527]: wls1: Trying to associate with e8:6f:f2:ec:a6:32 (SSID='HODDNET' freq=2462 MHz)
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.2397] device (wls1): supplicant interface state: inactive -> associating
Jun 27 15:41:38 bslxhp64 wpa_supplicant[527]: wls1: Associated with e8:6f:f2:ec:a6:32
Jun 27 15:41:38 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.2994] device (wls1): supplicant interface state: associating -> 4way_handshake
Jun 27 15:41:38 bslxhp64 wpa_supplicant[527]: wls1: WPA: Key negotiation completed with e8:6f:f2:ec:a6:32 [PTK=CCMP GTK=CCMP]
Jun 27 15:41:38 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-CONNECTED - Connection to e8:6f:f2:ec:a6:32 completed [id=0 id_str=]
Jun 27 15:41:38 bslxhp64 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.3132] device (wls1): supplicant interface state: 4way_handshake -> completed
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.3135] device (wls1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "HODDNET"
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.3140] device (wls1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:41:38 bslxhp64 NetworkManager[526]: <info>  [1687894898.3150] dhcp4 (wls1): activation: beginning transaction (timeout in 45 seconds)
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.3297] dhcp4 (wls1): state changed new lease, address=192.168.1.108
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.3311] policy: set 'HODDNET' (wls1) as default for IPv4 routing and DNS
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.4754] device (wls1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.4897] device (wls1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.4911] device (wls1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.4934] device (wls1): Activation: successful, device activated.
Jun 27 15:41:40 bslxhp64 NetworkManager[526]: <info>  [1687894900.5809] audit: op="statistics" interface="wls1" ifindex=2 args="2000" pid=1578 uid=1001 result="success"

after plugging in rj45 cable:

[root@bslxhp64 jghodd]# journalctl -b | grep tg3
Jun 27 15:46:46 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:46:46 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX
Jun 27 15:46:46 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is down
Jun 27 15:46:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Link is up at 100 Mbps, full duplex
Jun 27 15:46:47 bslxhp64 kernel: tg3 0000:85:00.0 ens5: Flow control is on for TX and on for RX

[root@bslxhp64 jghodd]# journalctl -b | grep wls1
Jun 27 15:46:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DISCONNECTED bssid=e8:6f:f2:ec:a6:32 reason=0
Jun 27 15:46:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 27 15:46:47 bslxhp64 NetworkManager[526]: <info>  [1687895207.7745] device (wls1): supplicant interface state: completed -> disconnected
Jun 27 15:46:47 bslxhp64 NetworkManager[526]: <info>  [1687895207.8918] device (wls1): supplicant interface state: disconnected -> scanning
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: Trying to associate with e8:6f:f2:ec:a6:32 (SSID='HODDNET' freq=2462 MHz)
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.3855] device (wls1): supplicant interface state: scanning -> associating
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: Associated with e8:6f:f2:ec:a6:32
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4478] device (wls1): supplicant interface state: associating -> 4way_handshake
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: WPA: Key negotiation completed with e8:6f:f2:ec:a6:32 [PTK=CCMP GTK=CCMP]
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-CONNECTED - Connection to e8:6f:f2:ec:a6:32 completed [id=0 id_str=]
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4579] device (wls1): supplicant interface state: 4way_handshake -> completed
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4581] device (wls1): ip:dhcp4: restarting
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4772] dhcp4 (wls1): canceled DHCP transaction
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4772] dhcp4 (wls1): state changed no lease
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.4774] dhcp4 (wls1): activation: beginning transaction (timeout in 45 seconds)
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DISCONNECTED bssid=e8:6f:f2:ec:a6:32 reason=0
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 27 15:46:48 bslxhp64 NetworkManager[526]: <info>  [1687895208.7508] device (wls1): supplicant interface state: completed -> disconnected
Jun 27 15:46:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:49 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:50 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:51 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:52 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:53 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:54 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:56 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:57 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:58 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:46:59 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:00 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:01 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:47:01 bslxhp64 NetworkManager[526]: <info>  [1687895221.2080] audit: op="statistics" interface="wls1" ifindex=2 args="2000" pid=1578 uid=1001 result="success"
Jun 27 15:47:01 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:02 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.5653] dhcp4 (wls1): state changed no lease
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <warn>  [1687895223.5655] device (wls1): link timed out.
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.5655] device (wls1): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <warn>  [1687895223.5676] device (wls1): Activation: failed for connection 'HODDNET'
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.5693] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:03 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.5940] dhcp4 (wls1): canceled DHCP transaction
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.5940] dhcp4 (wls1): state changed no lease
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.7962] audit: op="statistics" interface="wls1" ifindex=2 args="0" pid=1578 uid=1001 result="success"
Jun 27 15:47:03 bslxhp64 NetworkManager[526]: <info>  [1687895223.8722] device (wls1): supplicant interface state: disconnected -> inactive
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1852] device (wls1): Activation: starting connection 'HODDNET' (596810c9-f44c-4af0-b14d-2e8a6b542c33)
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1856] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1870] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1888] device (wls1): Activation: (wifi) access point 'HODDNET' has security, but secrets are required.
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1888] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1891] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1945] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1950] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:04 bslxhp64 NetworkManager[526]: <info>  [1687895224.1954] device (wls1): Activation: (wifi) connection 'HODDNET' has security, and secrets exist.  No new secrets needed.
Jun 27 15:47:04 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:47:04 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:06 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:07 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:08 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:09 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:10 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:11 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:12 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:13 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:14 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:15 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:16 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:17 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:18 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:19 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:20 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:21 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:22 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:23 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:24 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:25 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:26 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:27 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:28 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:29 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:29 bslxhp64 NetworkManager[526]: <warn>  [1687895249.5645] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:47:29 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:47:29 bslxhp64 NetworkManager[526]: <info>  [1687895249.5646] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:47:29 bslxhp64 NetworkManager[526]: <warn>  [1687895249.5664] device (wls1): Activation: failed for connection 'HODDNET'
Jun 27 15:47:29 bslxhp64 NetworkManager[526]: <info>  [1687895249.5696] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:29 bslxhp64 NetworkManager[526]: <info>  [1687895249.5717] device (wls1): supplicant interface state: inactive -> disconnected
Jun 27 15:47:29 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0847] device (wls1): Activation: starting connection 'HODDNET' (596810c9-f44c-4af0-b14d-2e8a6b542c33)
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0849] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0857] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0861] device (wls1): Activation: (wifi) access point 'HODDNET' has security, but secrets are required.
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0861] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0863] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0892] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0899] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:30 bslxhp64 NetworkManager[526]: <info>  [1687895250.0909] device (wls1): Activation: (wifi) connection 'HODDNET' has security, and secrets exist.  No new secrets needed.
Jun 27 15:47:30 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:47:30 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:31 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:32 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:33 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:34 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:35 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:36 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:37 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:38 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:39 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:40 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:41 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:42 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:43 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:44 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:45 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:46 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:49 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:50 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:51 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:52 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:53 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:54 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:55 bslxhp64 NetworkManager[526]: <warn>  [1687895275.5656] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:47:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:47:55 bslxhp64 NetworkManager[526]: <info>  [1687895275.5658] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:47:55 bslxhp64 NetworkManager[526]: <warn>  [1687895275.5674] device (wls1): Activation: failed for connection 'HODDNET'
Jun 27 15:47:55 bslxhp64 NetworkManager[526]: <info>  [1687895275.5678] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0850] device (wls1): Activation: starting connection 'HODDNET' (596810c9-f44c-4af0-b14d-2e8a6b542c33)
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0852] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0860] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0864] device (wls1): Activation: (wifi) access point 'HODDNET' has security, but secrets are required.
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0865] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0867] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0882] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0915] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:47:56 bslxhp64 NetworkManager[526]: <info>  [1687895276.0929] device (wls1): Activation: (wifi) connection 'HODDNET' has security, and secrets exist.  No new secrets needed.
Jun 27 15:47:56 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:47:56 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:57 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:58 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:47:59 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:00 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:01 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:02 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:03 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:04 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:06 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:07 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:08 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:09 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:10 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:11 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:12 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:13 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:14 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:15 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:16 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:17 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:18 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:19 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:20 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:21 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:21 bslxhp64 NetworkManager[526]: <warn>  [1687895301.5655] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:48:21 bslxhp64 NetworkManager[526]: <info>  [1687895301.5656] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:48:21 bslxhp64 NetworkManager[526]: <warn>  [1687895301.5678] device (wls1): Activation: failed for connection 'HODDNET'
Jun 27 15:48:21 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:48:21 bslxhp64 NetworkManager[526]: <info>  [1687895301.5686] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:21 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0977] device (wls1): Activation: starting connection 'TDS2173' (77672178-54c2-4381-83df-1dd53f6c32d7)
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0978] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0983] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0986] device (wls1): Activation: (wifi) access point 'TDS2173' has security, but secrets are required.
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0986] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.0988] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:48:22 bslxhp64 wpa_supplicant[527]: wls1: WPS-PBC-ACTIVE
Jun 27 15:48:22 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.2211] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.2214] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:22 bslxhp64 NetworkManager[526]: <info>  [1687895302.2217] device (wls1): Activation: (wifi) connection 'TDS2173' has security, and secrets exist.  No new secrets needed.
Jun 27 15:48:22 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:48:22 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:23 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:24 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:25 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:26 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:27 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:28 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:29 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:30 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:31 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:32 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:33 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:34 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:35 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:36 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:37 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:38 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:39 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:40 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:41 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:42 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:43 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:44 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:45 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:46 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:47 bslxhp64 NetworkManager[526]: <warn>  [1687895327.5649] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:48:47 bslxhp64 NetworkManager[526]: <info>  [1687895327.5651] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:48:47 bslxhp64 NetworkManager[526]: <warn>  [1687895327.5668] device (wls1): Activation: failed for connection 'TDS2173'
Jun 27 15:48:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:48:47 bslxhp64 NetworkManager[526]: <info>  [1687895327.5754] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.0986] device (wls1): Activation: starting connection 'TDS2173' (77672178-54c2-4381-83df-1dd53f6c32d7)
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.0988] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1042] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1053] device (wls1): Activation: (wifi) access point 'TDS2173' has security, but secrets are required.
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1089] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1104] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:48:48 bslxhp64 wpa_supplicant[527]: wls1: WPS-PBC-ACTIVE
Jun 27 15:48:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1512] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1532] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:48:48 bslxhp64 NetworkManager[526]: <info>  [1687895328.1535] device (wls1): Activation: (wifi) connection 'TDS2173' has security, and secrets exist.  No new secrets needed.
Jun 27 15:48:48 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:48:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:49 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:50 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:51 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:52 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:53 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:54 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:56 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:57 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:58 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:48:59 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:00 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:01 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:02 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:03 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:04 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:06 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:07 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:08 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:09 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:10 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:11 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:12 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:13 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:13 bslxhp64 NetworkManager[526]: <warn>  [1687895353.5647] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:49:13 bslxhp64 NetworkManager[526]: <info>  [1687895353.5648] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:49:13 bslxhp64 NetworkManager[526]: <warn>  [1687895353.5665] device (wls1): Activation: failed for connection 'TDS2173'
Jun 27 15:49:13 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:49:13 bslxhp64 NetworkManager[526]: <info>  [1687895353.5751] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:13 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0920] device (wls1): Activation: starting connection 'TDS2173' (77672178-54c2-4381-83df-1dd53f6c32d7)
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0922] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0927] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0929] device (wls1): Activation: (wifi) access point 'TDS2173' has security, but secrets are required.
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0929] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.0931] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:49:14 bslxhp64 wpa_supplicant[527]: wls1: WPS-PBC-ACTIVE
Jun 27 15:49:14 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.1344] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.1362] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:14 bslxhp64 NetworkManager[526]: <info>  [1687895354.1373] device (wls1): Activation: (wifi) connection 'TDS2173' has security, and secrets exist.  No new secrets needed.
Jun 27 15:49:14 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:49:14 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:15 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:16 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:17 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:18 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:19 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:20 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:21 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:22 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:23 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:24 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:25 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:26 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:27 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:28 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:29 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:30 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:31 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:32 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:33 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:34 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:35 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:36 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:37 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:38 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:39 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:39 bslxhp64 NetworkManager[526]: <warn>  [1687895379.5649] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:49:39 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:49:39 bslxhp64 NetworkManager[526]: <info>  [1687895379.5650] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:49:39 bslxhp64 NetworkManager[526]: <warn>  [1687895379.5667] device (wls1): Activation: failed for connection 'TDS2173'
Jun 27 15:49:39 bslxhp64 NetworkManager[526]: <info>  [1687895379.5673] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:39 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0843] device (wls1): Activation: starting connection 'TDS2173' (77672178-54c2-4381-83df-1dd53f6c32d7)
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0844] device (wls1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0849] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0852] device (wls1): Activation: (wifi) access point 'TDS2173' has security, but secrets are required.
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0852] device (wls1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.0854] sup-iface[4af50bffa873d81d,0,wls1]: wps: type pbc start...
Jun 27 15:49:40 bslxhp64 wpa_supplicant[527]: wls1: WPS-PBC-ACTIVE
Jun 27 15:49:40 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.1295] device (wls1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.1299] device (wls1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 27 15:49:40 bslxhp64 NetworkManager[526]: <info>  [1687895380.1302] device (wls1): Activation: (wifi) connection 'TDS2173' has security, and secrets exist.  No new secrets needed.
Jun 27 15:49:40 bslxhp64 wpa_supplicant[527]: wls1: WPS-CANCEL
Jun 27 15:49:40 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:41 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:42 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:43 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:44 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:45 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:46 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:47 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:48 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:49 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:50 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:51 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:52 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:53 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:54 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:55 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:56 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:57 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:58 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:49:59 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:00 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:01 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:02 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:03 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:04 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
Jun 27 15:50:05 bslxhp64 NetworkManager[526]: <warn>  [1687895405.5650] device (wls1): Activation: (wifi) association took too long, failing activation
Jun 27 15:50:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-DSCP-POLICY clear_all
Jun 27 15:50:05 bslxhp64 NetworkManager[526]: <info>  [1687895405.5652] device (wls1): state change: config -> failed (reason 'ssid-not-found', sys-iface-state: 'managed')
Jun 27 15:50:05 bslxhp64 NetworkManager[526]: <warn>  [1687895405.5669] device (wls1): Activation: failed for connection 'TDS2173'
Jun 27 15:50:05 bslxhp64 NetworkManager[526]: <info>  [1687895405.5674] device (wls1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 27 15:50:05 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:50:06 bslxhp64 NetworkManager[526]: <info>  [1687895406.2023] device (wls1): supplicant interface state: disconnected -> inactive
Jun 27 15:50:06 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:50:09 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22
Jun 27 15:50:14 bslxhp64 wpa_supplicant[527]: wls1: CTRL-EVENT-SCAN-FAILED ret=-22

I'm not seeing any wobbly behavior from tg3. However, when tg3 becomes active, wls1 becomes unable to perform an SSID scan, so it fails. Disconnect the rj45 and voila, wls1 can suddenly do an SSID scan, connects and becomes available. Plug the rj45 back in and suddenly wls1 can no longer perform an SSID scan.

Unfortunately, b43 is no help. When the module is loaded, and broadcom-wl uninstalled, rfkill shows that the wifi isn't even there. Also tried b43-classic and b43legacy.

So, I'm back to broadcom-wl (the very latest version - 479) and back to where we started.

jghodd · 2023-06-27 20:56:19

broadcom is the only wifi chip which gets afforded its own wiki, because it's a complete mess and the worst possible wifi chip one can have (at least on linux)

...but broadcom wifi hardware is practically ubiquitous, used in many, many systems, so there has to be a solution somewhere.

seth · 2023-06-27 21:17:56

Please don't grep the journal - you're moving the events out of order and context.
Also see https://bbs.archlinux.org/viewtopic.php?pid=10#p10

seth wrote:

wls1 fails all by itself after ens5 went up/down/up again.

and cut out NM

----
Ftr, I've spent a happy life w/o ever using one single broadcom wifi chip - before ever seeing the arch wiki page, at which point I burst into a diabolic laughter.
We'll see whether there's a solution (cut. out. NM.) but that doesn't change the "worst possible wifi chip one can have (at least on linux)" part.

jghodd · 2023-06-28 02:32:20

i'll take a look around tomorrow for netmanager alternatives. there's also linux-6.4 on its way soon - and i did browse the commit logs for both drivers which showed some odd fixes (like undoing some code in tg3 that resets APs). i'm having a real problem pinning this on networkmanager which has worked and continues to work flawlessly on multiple systems over a 10 year period. but, nonetheless, i'm willing to look at alternatives. i find it most likely that something is broken in one of the drivers that either corrupts the other driver's memory heap (more likely than stack), or sets something it shouldn;t be setting that causes the wireless driver to fail its scanning for APs - a wireless driver that works perfectly when the other driver is inactive (rj45 unplugged) - or something entirely different. but, there's way too much source code feeding into and around the drivers to get my head around in just a minute or two, so i really can't be thorough in pinning this fault on any particular thing. i can only look at the patterns. if it turns out to be networkmanager, i'll eat my words... but i really think this is something else we haven't put our finger on yet.

jghodd · 2023-06-29 20:05:06

OK. After replacing NetworkManager with connman and then going back back and forth with iwd and wpa_supplicant, I think I can safely say that what I'm seeing is a driver conflict. When tg3 become active - vs loaded, but rj45 not plugged in, so not "active" - I start getting SCAN FAIL errors off of the wl driver (the only driver I've found thus far that actually works with the bcm4312, or whatever version/manufacturer of the 4312 I have installed).

So, something is happening when tg3 becomes active that's blocking wl's ability to scan for SSIDs.

That's the long and the short of it.

Hopefully tg3's fixes coming up in 6.4 will fix this.

seth · 2023-06-29 20:29:05

So, something is happening when tg3 becomes [active - vs loaded, but rj45 not plugged in, so not "active"] that's blocking wl's ability to scan for SSIDs.

You mean the wifi breaks down when you merely bring the tg3 NIC "up" (ip link set ens5 up)?

I start getting SCAN FAIL errors off of the wl driver

If you don't scan, can you still just connect/remain connected/talk to the AP?

going back back and forth with iwd and wpa_supplicant

nb. that https://wiki.archlinux.org/title/ConnMa … _supported

Edit:

Hopefully tg3's fixes coming up in 6.4 will fix this.

https://github.com/torvalds/linux/commi … dcom/tg3.c
https://github.com/torvalds/linux/commi … dcom/tg3.c
Which one?

Last edited by seth (2023-06-29 20:34:41)

jghodd · 2023-07-01 17:58:40

I don't know which one will or might fix it - maybe neither. Something's already going on though. my device names suddenly changed with the last linux-firmware-* updates. wls1 changed to wlan0 and ens5 changed to enp133s0 - same drivers loaded and same behavior. Part of the path towards finding what works is just shaping one's search phrasing around any nuances in the problematic behavior. I'm really leaning away from there being an issue with any network manager - this is an interaction between the drivers. And frankly, I'm not certain which driver is causing the problem. You're obviously more familiar with at least the networking portion of the kernel source - is there anywhere you can think to look for what happens when tg3 changes state/powers on? I can poke and prod a little myself, but there's a whole lot of source code behind kernel services that would take a very long time to try to absorb. More than half of my career as an SE was spent designing and developing drivers for proprietary embedded systems, so I know what kind of messes can be instigated at a low level, even if just by accident. An overwrite that happens to spill into memory space used by another driver for (mmapped) register access... Despite over 40 years working on *nix systems, I have never developed a linux driver - closest i got was a unix driver over 30 years ago and mm has changed a bit since then. The best I can do is to possibly identify spots of code that look suspicious, but I will take a look.

jghodd · 2023-07-01 18:37:14

I assume you were referring to the latest tg3.c fix, although it;s referenced twice. The thing is, @seth, it could be firmware, driver code/logic, kernel code/logic, etc. We don't know. What we do know is one particular behavior, which is that when you plug a live rj45 cable into the ethernet port, driven by a bcm5787m chipset, using the tg3 linux driver, the wireless driver, wl, reports an error on AP scanning, and so it deactivates the wireless device, which is a bcm4312. If the rj45 cable is removed, powering down the ethernet port and changing the tg3 driver's state to idle, the wireless driver/device pops up within 30 seconds, having successfully scanned for, and registered with, its access point (AP). I can do this all day. Always this same repeatable behavior - even if you change network managers or try managing them with cli tools. This sequence of events is completely repeatable. i am wondering though if this is a tg3 problem or a wl problem...

seth · 2023-07-01 18:45:05

I don't know which one will or might fix it - maybe neither.

The point was that there's no tg3 comit between 6.3 and 6.4, so I'm wondering what "tg3's fixes coming up in 6.4" you're talking about.

wls1 changed to wlan0 and ens5 changed to enp133s0

First is because you installed iwd, 2nd no idea, but this is done by systemd and has nothing to do w/ kernel or firmware - if at all the BIOS or HW config.
https://wiki.archlinux.org/title/Networ … face_names

is there anywhere you can think to look for what happens when tg3 changes state/powers on?

It, possibly, draws more power. This is wy I asked to skip the scanning.
The chips seem on different pci lanes, though. So I'm not even super optimistic about that.

when you plug a live rj45 cable into the ethernet port

There's gonna be some SW response (ifplugd or alike), I doubt that the physical act alone can cause any of this - unless the cable itself causes radio interference (can you change the HW geometry?)
Therefore:

seth wrote:

You mean the wifi breaks down when you merely bring the tg3 NIC "up" (ip link set ens5 up)?

loqs · 2023-07-01 19:35:10

linux 6.4.1.arch1-1 is now in core-testing. Is there any change in behavior with it?

jghodd · 2023-07-03 17:11:17

i have tested against linux-6.4.1, with both drivers (wl and b43) and tested both wpa_supplicant and iwd. no change in behavior. i'm going to try the intel NIC again, see if it comes up unblocked now (not holding my breath but worth a try).

@seth - how does one skip the scanning? i've already locked in the bssid, which i figured should have stopped the scanning, but it didn't. is there something else i can do or should be doing?

jghodd · 2023-07-03 17:41:50

You mean the wifi breaks down when you merely bring the tg3 NIC "up" (ip link set ens5 up)?

when it becomes active. it automatically becomes active as soon as the rj45 cable is plugged in. otherwise, it's idle, but is listed by ifconfig as UP, as you can see:

enp133s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:25:b3:7e:92:81  txqueuelen 1000  (Ethernet)
        RX packets 292235  bytes 263513730 (251.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 306962  bytes 324816352 (309.7 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

if i were to plug in the rj45 cable at this point, within 30 seconds my wireless deactivates itself, even though the wlan0 interface remains UP

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:21:00:1f:7e:60  txqueuelen 1000  (Ethernet)
        RX packets 13493  bytes 19354607 (18.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 7810
        TX packets 7238  bytes 672924 (657.1 KiB)
        TX errors 127  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 17

journalctl shows SCAN errors not just from wpa_supplicant, but from the kernel itself.

Jul 03 13:31:46 bslxhp64 NetworkManager[525]: <info>  [1688405506.4307] device (wlan0): supplicant interface state: disconnected -> inactive
Jul 03 13:31:46 bslxhp64 wpa_supplicant[526]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22
Jul 03 13:31:46 bslxhp64 kernel: ERROR @wl_cfg80211_scan : 
Jul 03 13:31:46 bslxhp64 kernel: WLC_SCAN error (-22)
Jul 03 13:31:49 bslxhp64 wpa_supplicant[526]: wlan0: CTRL-EVENT-SCAN-FAILED ret=-22
Jul 03 13:31:49 bslxhp64 kernel: ERROR @wl_cfg80211_scan : 
Jul 03 13:31:49 bslxhp64 kernel: WLC_SCAN error (-22)

i'd love it if i could just connect directly to the AP without scanning - i initially figured that was what was going to happen when i locked in the bssid. at this point i'm even considering plugging a wifi repeater into the ethernet switch just to get back to normal functionality.

seth · 2023-07-03 19:42:33

it automatically becomes active as soon as the rj45 cable is plugged in

No. It might get used (to stablish the carrier) but that's not what I asked for.

otherwise, it's idle, but is listed by ifconfig as UP, as you can see

The enp133s0 in that output seems to have a carrier (what means that a cable is plugged in) and what I previously inquired is whether bringing the NIC up and down (alone) kills the wifi.
You will *HAVE* to get rid of NM for those tests in order to manually control the states of the NICs.

i initially figured that was what was going to happen when i locked in the bssid.

No, that (supposingly) prevents NM from scanning while there's a connection.
Disable networkmanager, create a netctl profile for your SSID w/ wifi-menu, plug the rj45 cable and the "netctl start" the wifi profile.

Arch Linux

#26 2023-06-25 20:06:05

Re: wl/b43 drivers conflict with tg3

#27 2023-06-25 20:13:19

Re: wl/b43 drivers conflict with tg3

#28 2023-06-27 05:11:40

Re: wl/b43 drivers conflict with tg3

#29 2023-06-27 06:20:43

Re: wl/b43 drivers conflict with tg3

#30 2023-06-27 20:53:08

Re: wl/b43 drivers conflict with tg3

#31 2023-06-27 20:56:19

Re: wl/b43 drivers conflict with tg3

#32 2023-06-27 21:17:56

Re: wl/b43 drivers conflict with tg3

#33 2023-06-28 02:32:20

Re: wl/b43 drivers conflict with tg3

#34 2023-06-29 20:05:06

Re: wl/b43 drivers conflict with tg3

#35 2023-06-29 20:29:05

Re: wl/b43 drivers conflict with tg3

#36 2023-07-01 17:58:40

Re: wl/b43 drivers conflict with tg3

#37 2023-07-01 18:37:14

Re: wl/b43 drivers conflict with tg3

#38 2023-07-01 18:45:05

Re: wl/b43 drivers conflict with tg3

#39 2023-07-01 19:35:10

Re: wl/b43 drivers conflict with tg3

#40 2023-07-03 17:11:17

Re: wl/b43 drivers conflict with tg3

#41 2023-07-03 17:41:50

Re: wl/b43 drivers conflict with tg3

#42 2023-07-03 19:42:33

Re: wl/b43 drivers conflict with tg3

Board footer