From nobody Wed Feb 25 04:26:58 2026 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4fLM4Q1KGyz6Trtr for ; Wed, 25 Feb 2026 04:27:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4fLM4Q0Jx9z3wkx for ; Wed, 25 Feb 2026 04:27:02 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1771993622; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=OhQZ4ncqfMaFJwf+YjpdHwCNWPygnyk27qcFBQXm7vI=; b=xWKoNSGVemsTSTeaVz9bGxOBG9mYnkDIde6Ai4rhQ7FfTXLZo8YPvEhikWtqGq+3ITQvG2 9NYcmVPhBqw7M06H49wNfz7oKOH1CJFcroVGYNQE5NNZT0qC6qN5RchCROWkLsD29WiqaZ Sg4pU6/ZttFtSjiOsGODwZ5fmYUV7EeMNF3ofd+XysnEbqfQNbt9cTV7M0ACrDUa7unl9u gKR/TZmGAICj2gNKA1cVKouyLzrcI+PDx+q7QS3yo9ZcinITLd4nKAqh1/HgNMUHqGNKI8 dWQ+wzbuaPYMm/X31ekWY8QjD8aNQi6tlLCi9nEjb7J5vPMxSmeDncnDftHUnw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1771993622; a=rsa-sha256; cv=none; b=CtVkLnLL/p4Tbmi2MeIV3fvWgF2p4YG2Sw6iRcWYxA+qQz3BzTfCAcblpWPUqZIJLBPmrx uzBmDMKYRE7yQbJb1qiMeoSF09cCLvse4QZ0VCRZqnJsuijk3vF3l/Y4wMaFf/U0DLOaRf pf2zkQIhMiCeX/sr/GhPUoSX5bU6rFLcMupLvIgvIsc5Uii7vgEuWJdokJqEA247iLOb4E b0lEqUDiy+dFrKv66D4W75B4xMZMNmZQ8TPPwy5fFRzkI0jk0mBDWLkE526HyadH2aS6bf ve7Zto0gsAckN7UruHPSSFFOjrWD+Q9JkO24lhVZMvrftpW4yLncZzGVWNO0tg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1771993622; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=OhQZ4ncqfMaFJwf+YjpdHwCNWPygnyk27qcFBQXm7vI=; b=T7hV+FwfYxuqYWXMmYNbZBu5lYtu2hzkKswyb+aP438b1xuHLVUX2nYzmS0SwU/NsYrKZu DLN7c+PqjiMOPDBL1W7Y0VquzpNCeuUMykzAhu5L8jWEnhzfW0+LrDQb54nfErQgzzy2Am 3wqEt5jQtjiYhErYX2Hs4dby5+dyv1tGzffT/FwaOgtcghmthlm9SYnPn6yIww2xQMghc/ ZDKJY/LasODNM3neqNzQJew2kBCqTCY3M2/I7k/V82PgCxk2gYHaDZKwbzrbtxtO7t9Nqz o0jTK8V1wT/ijbuMQMApV6/7C+u/JL9DBT2J38msPm3mQETHY1UkhYCTbjl6zg== Received: from mx-01.divo.sbone.de (legacy1.sbone.de [80.151.10.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (prime256v1) client-digest SHA256) (Client CN "mx-01.divo.sbone.de", Issuer "E7" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4fLM4P4vhdz17X3 for ; Wed, 25 Feb 2026 04:27:01 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx-01.divo.sbone.de (Postfix) with ESMTPS id 3DA3EA64806 for ; Wed, 25 Feb 2026 04:26:41 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 01D182D029E7 for ; Wed, 25 Feb 2026 04:27:00 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id pQJH0mxs6mjz for ; Wed, 25 Feb 2026 04:26:59 +0000 (UTC) Received: from nv.t4-02.sbone.de (nv.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:22]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 11E792D029D8 for ; Wed, 25 Feb 2026 04:26:59 +0000 (UTC) Date: Wed, 25 Feb 2026 04:26:58 +0000 (UTC) From: "Bjoern A. Zeeb" To: FreeBSD wireless mailing list Subject: LinuxKPI (iwlwifi, rtw8x) Please test! Important! Message-ID: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Hi, about 3 years ago, some of you may remember, we were hunting down the constant (firmware) crashes with iwlwifi due to net80211 not playing nice and the LinuxKPI 802.11 sta state machine not able to deal with it to make the firmware happy. In that course I unfolded some state machine bits, which resultet in code duplication and some other complications. Fast forward, I just undone some of that in main. This is probably one of the more risky changes as of late. I tried to test it but as we also have learnt in the last years, the testing of many will reveal problems more likely than me trying to test in my limited capacity. So please all test main now! Prepare yourself in case of trouble (boot envorments, or otherwise, in case you need to roll back know how to). Let it run for a few hours or a day or two and then please report back if it is still working without extra troubles compared to before. In case you hit any hiccup please report right away! I will try to reply promptly (I do sleep occassionally) but real life currently also takes some share so it may be a day before I get to the emails. Please include driver and chipset/firmware you are using if possible along with any possible problem report. Why is this important (now)? There'll be follow-up changes needed to get the iwlwifi update into main as well so that all drivers are on the same level (v6.19) for a change again. The reason this is important now is that this will be our base for 15.1-RELEASE so we will have 6ish weeks still to sort out any problems. In addition (bonus points) if things go smoothly there is the next branch waiting for me to merge to bring further improvements still during March (at least to main and possibly stable/15). What if you are on stable/15? I believe you could just grab the last changes and merge them yourself. I will go and have a look and try to merge anything I can Thu or Fri (before the weekend) to keep the diff minimal in case that helps! Lots of health! Bjoern -- Bjoern A. Zeeb r15:7