On Tue, Mar 31, 2026 at 03:42:33PM -0300, Santiago Ruano Rincón wrote: > A quick follow up (that was unsuccessfully sent yesterday): > > After sending the report, my wifi network (Network A - "Starbucks") > stopped working. With "stopped working" I mean that my machine lost the > association with the AP. I made several tries to associate to the same > network again, without success. This I what I could see on dmesg: > > ... > [22444.808389] wlp2s0: authenticate with ee:55:b8:81:8b:af (local > address=04:7b:cb:b7:89:ca) > [22444.808402] wlp2s0: send auth to ee:55:b8:81:8b:af (try 1/3) > [22444.813991] wlp2s0: authenticated > [22444.816393] wlp2s0: associate with ee:55:b8:81:8b:af (try 1/3) > [22444.828044] wlp2s0: RX AssocResp from ee:55:b8:81:8b:af (capab=0x1501 > status=0 aid=69) > [22444.847942] wlp2s0: associated > [22444.847997] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by > ee:55:b8:81:8b:af > [22476.256989] wlp2s0: deauthenticating from ee:55:b8:81:8b:af by local > choice (Reason: 3=DEAUTH_LEAVING) > [22476.743627] wlp2s0: authenticate with ee:55:b8:81:8b:af (local > address=04:7b:cb:b7:89:ca) > [22476.743636] wlp2s0: send auth to ee:55:b8:81:8b:af (try 1/3) > [22476.748763] wlp2s0: authenticated > [22476.752418] wlp2s0: associate with ee:55:b8:81:8b:af (try 1/3) > [22476.764521] wlp2s0: RX AssocResp from ee:55:b8:81:8b:af (capab=0x1501 > status=0 aid=69) > [22476.781659] wlp2s0: associated > [22476.790502] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by > ee:55:b8:81:8b:af > [22522.001334] wlp2s0: deauthenticating from ee:55:b8:81:8b:af by local > choice (Reason: 3=DEAUTH_LEAVING) > [22808.678547] wlp2s0: authenticate with ee:55:b8:81:8b:af (local > address=04:7b:cb:b7:89:ca) > [22808.678556] wlp2s0: send auth to ee:55:b8:81:8b:af (try 1/3) > [22808.685713] wlp2s0: authenticated > [22808.688398] wlp2s0: associate with ee:55:b8:81:8b:af (try 1/3) > [22808.704101] wlp2s0: RX AssocResp from ee:55:b8:81:8b:af (capab=0x1501 > status=0 aid=77) > [22808.750002] wlp2s0: associated > [22808.750082] wlp2s0: Limiting TX power to 23 (23 - 0) dBm as advertised by > ee:55:b8:81:8b:af > > I switched to another wifi network (Network B) that my machine get > associated to, but the network wasn't actually usable (although, it was > usable from another device). My machine got an IPv4 address and route, > but it was not able to reach the outside network. > > 3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP > group default qlen 1000 > link/ether 04:7b:cb:b7:89:ca brd ff:ff:ff:ff:ff:ff > altname wlx047bcbb789ca > inet 192.168.33.84/24 brd 192.168.33.255 scope global dynamic > noprefixroute wlp2s0 > valid_lft 3464sec preferred_lft 3464sec > inet6 fe80::f74d:efc9:5cf4:6a7e/64 scope link noprefixroute > valid_lft forever preferred_lft forever > > ip r | grep wlp2s0 > default via 192.168.33.63 dev wlp2s0 proto dhcp src 192.168.33.84 metric 600 > 192.168.33.0/24 dev wlp2s0 proto kernel scope link src 192.168.33.84 metric > 600 > > ping -c 4 1.1.1.1: > PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. > >From 192.168.33.84 icmp_seq=1 Destination Host Unreachable > >From 192.168.33.84 icmp_seq=2 Destination Host Unreachable > >From 192.168.33.84 icmp_seq=3 Destination Host Unreachable > >From 192.168.33.84 icmp_seq=4 Destination Host Unreachable
Assuming this is reproducible: Does it help to reload the driver? E.g.
doing as root:
cd /sys/bus/pci/drivers/ath11k_pci
echo 0000:02:00.0 > unbind
echo 0000:02:00.0 > bind
Best regards
Uwe
signature.asc
Description: PGP signature
