El 18/06/26 a las 07:49, Kyle Farnung escribió: > On Thu, Jun 18, 2026 at 7:31 AM Santiago Ruano Rincón [...] > > Kyle, have you observed any regression after your patch was included? > > And thanks for your work, BTW. > > > Thankfully I haven't seen the issue since my patch rolled out in Fedora. > Do you see the same log entries in journalctl when the issue occurs?
Yes, AFAICS. But the log is not very meaningful: [jun18 10:49] wlp2s0: deauthenticating from 20:08:89:51:ac:b9 by local choice (Reason: 3=DEAUTH_LEAVING) [ +0,630577] wlp2s0: authenticate with 20:08:89:51:ac:b9 (local address=04:7b:cb:b7:89:ca) [ +0,000014] wlp2s0: send auth to 20:08:89:51:ac:b9 (try 1/3) [ +0,002793] wlp2s0: authenticated [ +0,002480] wlp2s0: associate with 20:08:89:51:ac:b9 (try 1/3) [ +0,002276] wlp2s0: RX AssocResp from 20:08:89:51:ac:b9 (capab=0x1031 status=0 aid=16) [ +0,031584] wlp2s0: associated [ +0,007537] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 20:08:89:51:ac:b9 [jun18 10:51] wlp2s0: deauthenticating from 20:08:89:51:ac:b9 by local choice (Reason: 3=DEAUTH_LEAVING) [ +0,524257] wlp2s0: authenticate with 20:08:89:51:ac:b9 (local address=04:7b:cb:b7:89:ca) [ +0,000014] wlp2s0: send auth to 20:08:89:51:ac:b9 (try 1/3) [ +0,003748] wlp2s0: authenticated [ +0,007822] wlp2s0: associate with 20:08:89:51:ac:b9 (try 1/3) [ +0,002673] wlp2s0: RX AssocResp from 20:08:89:51:ac:b9 (capab=0x1031 status=0 aid=16) [ +0,021204] wlp2s0: associated [ +0,051593] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by 20:08:89:51:ac:b9 > What are the recovery steps you're using to get it working again? cd /sys/bus/pci/drivers/ath11k_pci/ ; sudo sh -c "echo 0000:02:00.0 > unbind" ; sudo sh -c "echo 0000:02:00.0 > bind" Which is seen in the logs as: [ +39,442465] wlp2s0: deauthenticating from 20:08:89:51:ac:b9 by local choice (Reason: 3=DEAUTH_LEAVING) [ +0,627384] ath11k_pci 0000:02:00.0: BAR 0 [mem 0x80000000-0x801fffff 64bit]: assigned [ +0,001582] ath11k_pci 0000:02:00.0: MSI vectors: 32 [ +0,000009] ath11k_pci 0000:02:00.0: wcn6855 hw2.1 [ +0,000024] ath11k_pci 0000:02:00.0: firmware: failed to load ath11k/WCN6855/hw2.1/firmware-2.bin (-2) [ +0,000011] ath11k_pci 0000:02:00.0: firmware: failed to load ath11k/WCN6855/hw2.1/firmware-2.bin (-2) [ +0,000011] ath11k_pci 0000:02:00.0: firmware: failed to load ath11k/WCN6855/hw2.1/firmware-2.bin (-2) [ +0,157972] mhi mhi0: Requested to power ON [ +0,000021] mhi mhi0: Power on setup success [ +0,091491] mhi mhi0: Wait for device to enter SBL or Mission mode [ +0,632959] ath11k_pci 0000:02:00.0: chip_id 0x12 chip_family 0xb board_id 0xff soc_id 0x400c1211 [ +0,000014] ath11k_pci 0000:02:00.0: fw_version 0x11088c35 fw_build_timestamp 2024-04-17 08:34 fw_build_id WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41 [ +0,353393] ath11k_pci 0000:02:00.0 wlp2s0: renamed from wlan0 [ +7,175918] wlp2s0: authenticate with 20:08:89:51:ac:b9 (local address=04:7b:cb:b7:89:ca) > $ uname -a > Linux kjfp14sg5amd 7.0.12-201.fc44.x86_64 #1 SMP PREEMPT_DYNAMIC Thu > Jun 11 01:30:16 UTC 2026 x86_64 GNU/Linux > $ uptime > 07:38:20 up 3 days, 9:37, 1 user, load average: 0.34, 0.57, 0.68 > > > > cheers, > > > > -- Santiago > > Thanks, > Kyle Cheers, -- Santiago
