On Wed, Dec 31, 2025 at 03:38:07PM +0000, Vitaliy Makkoveev wrote: > On Wed, Dec 31, 2025 at 12:19:15PM +0100, Stefan Sperling wrote: > > On Wed, Dec 31, 2025 at 12:09:06AM +0000, Vitaliy Makkoveev wrote: > > > Sorry, I mean I see no errors in debug output. According log, the card > > > performs association, but in fact it does not: > > > > Please send the full firmware error trace. > > Above "driver status" there should be lines which show firmware error > > details. These details include the hex code of the last command received > > by firmware, an important detail which is missing from this bug report. > > > > It has no errors, but I see "device timeout". The previous kernel from > November 30 works fine with this AP. > > iwx0: SCAN -> SCAN > iwx0: device timeout > iwx0: dumping device error log > iwx0: errlog not found, skipping > > > Are you able to re-configure the AP? If so, are there any settings related > > to management frame encryption (PMF/MFP) or WPA3 which you can change to > > see if this makes any difference? > > > > This is an old TP-Link N450. It has no such ability. > > iwx0: hw rev 0x420, fw 77.f92b5fed.0, pnvm ce1a5094, address aa:bb:cc:dd:ee:ff > iwx0: RUN -> ASSOC > iwx0: sending assoc_req to 01:01:01:01:01:01 on channel 2 mode 11n > iwx0: association timed out for 01:01:01:01:01:01 > iwx0: ASSOC -> SCAN > iwx0: end active scan > iwx0: best AP 01:01:01:01:01:01 "myap" score 53 > iwx0: switching to network "myap" > iwx0: - ---- AP list ---- > iwx0: - ---- AP list ---- > iwx0: firmware has detected regulatory domain 'RU' (0x5255) > iwx0: SCAN -> SCAN > iwx0: end active scan > iwx0: - ---- AP list ---- > iwx0: - ---- AP list ---- > iwx0: firmware has detected regulatory domain 'RU' (0x5255) > iwx0: SCAN -> SCAN > iwx0: device timeout > iwx0: dumping device error log > iwx0: errlog not found, skipping > driver status: > tx ring 0: qid=0 cur=52 cur_hw=52 queued=0 > tx ring 1: qid=1 cur=0 cur_hw=0 queued=0 > tx ring 2: qid=2 cur=0 cur_hw=0 queued=0 > tx ring 3: qid=3 cur=0 cur_hw=0 queued=0 > tx ring 4: qid=4 cur=0 cur_hw=0 queued=0 > tx ring 5: qid=5 cur=0 cur_hw=0 queued=0 > tx ring 6: qid=6 cur=0 cur_hw=0 queued=0 > tx ring 7: qid=7 cur=0 cur_hw=0 queued=0 > tx ring 8: qid=8 cur=0 cur_hw=0 queued=0 > tx ring 9: qid=9 cur=0 cur_hw=0 queued=0 > rx ring: cur=347 > 802.11 state SCAN > iwx0: SCAN -> INIT > iwx0: begin active scan > iwx0: INIT -> SCAN > iwx0: end active scan > iwx0: - ---- AP list ---- > iwx0: - ---- AP list ---- > iwx0: + 01:01:01:01:01:01 2 +38 54M ess privacy rsn "myap" > iwx0: firmware has detected regulatory domain 'RU' (0x5255) > iwx0: SCAN -> AUTH > iwx0: sending auth to 01:01:01:01:01:01 on channel 2 mode 11g > iwx0: AUTH -> ASSOC > iwx0: sending assoc_req to 01:01:01:01:01:01 on channel 2 mode 11g > iwx0: ASSOC -> RUN > iwx0: associated with 01:01:01:01:01:01 ssid "myap" channel 2 start MCS > 0 short preamble long slot time protection enabled HT enabled > iwx0: missed beacon threshold set to 30 beacons, beacon interval is 100 TU > > > $ ifconfig iwx0 > iwx0: flags=8947<UP,BROADCAST,DEBUG,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu > 1500 > lladdr aa:bb:cc:dd:ee:ff > index 1 priority 4 llprio 3 > trunk: trunkdev trunk0 > groups: wlan > media: IEEE802.11 autoselect (HT-MCS3 mode 11n) > status: no network > ieee80211: join myap chan 2 bssid 01:02:02:04:05:06 61% wpakey > wpaprotos wpa2 wpaakms psk,sha256-psk wpaciphers ccmp wpagroupcipher ccmp >
The AX211 on other machine also stopped to work with newest kernel. The previous kernel on this machine was from the December 1 snapshot. iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX211" rev 0x01, msix iwx0: hw rev 0x370, fw 77.f92b5fed.0, address aa:bb:cc:dd:ee:ff The only difference is that on this machine the association sequence happens only once. iwx0: hw rev 0x370, fw 77.f92b5fed.0, address aa:bb:cc:dd:ee:ff iwx0: RUN -> INIT iwx0: begin active scan iwx0: INIT -> SCAN iwx0: SCAN -> INIT iwx0: begin active scan iwx0: INIT -> SCAN iwx0: SCAN -> INIT iwx0: begin active scan iwx0: INIT -> SCAN iwx0: end active scan iwx0: - ---- AP list ---- iwx0: - ---- AP list ---- iwx0: + 01:01:01:01:01:01 2 +38 54M ess privacy rsn "myap" iwx0: SCAN -> AUTH iwx0: sending auth to 01:01:01:01:01:01 on channel 2 mode 11g iwx0: AUTH -> ASSOC iwx0: sending assoc_req to 01:01:01:01:01:01 on channel 2 mode 11g iwx0: ASSOC -> RUN iwx0: associated with 01:01:01:01:01:01 ssid "myap" channel 2 start MCS 0 short preamble short slot time HT enabled iwx0: missed beacon threshold set to 30 beacons, beacon interval is 100 TU That's all. It doesn't restart association sequence. I have no other AP at this location.
