From nobody Sun Feb 18 21:12:03 2024 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 4TdJJh1NCbz5Bm44 for ; Sun, 18 Feb 2024 21:12:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TdJJg69MFz447y for ; Sun, 18 Feb 2024 21:12:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1708290723; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=R2ACasxslyaT7fWBCX9h5orlZ5mL4XqBbzsdhqjM+kU=; b=rSzKF8oU3iCBuHPQS56lPkcnN82Rn5KO1CYph9acs9gZVRVt59mzqahHI70PemqefEJJzz x79jp+zjLBbahchIpnxxTOdzv/RKnKhL6s6MB90b92wf0hfVwff8+FM8fH1zVLHeGb4iDk AY30P7QSgnWu2nv2RKGq5HsbM2tSqTvYkx9N6UQ67aRXyMIQEtDWy1Aq5Nb0d4FK6/RwCH 9UHdcKTJWU3bX9rB3a+fhnm/8x9rUy4zrDFXLK4gfoT//HIACHT5w0oMMQMO65MNvRfA3w ngnK8W9/HumVFXoYR82wR/SawCnHf6aJcXVKJ4DdS6gwUzcHlgwIP3MjC98CmA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1708290723; a=rsa-sha256; cv=none; b=XAb2hrdABNP77KcIY7mWRtpByIR2qZb1B39mq9UuROtMZ0W+BWu2f15ruU+xIjc9GBjRP1 1U8iuBu7O4lkrq9Pdsf25T5UVxRFLmOBxIoYZpjuiMxuhCYXTNE5gwWWD/0pOMLqG4VanH xz8d5KyA8vXgg8x5hPvTXuiEIW5vzakduHfO97E1c7ck5Wm8JYbku5Pijg0bDK3/OAH0Wf xgS024XqA9X6Gf1ZihEirtzcC041WK1ZpRgJWl/PNJMUyOCqnT6kQR2POBkw1LdJ2di8AL aR/39zlwZzPAibBi5VO35czFdoMtRln9dfaCryw79SJXsMYJRWL2atNWjzE/Fw== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4TdJJg50VNz15yC for ; Sun, 18 Feb 2024 21:12:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 41ILC3mA070163 for ; Sun, 18 Feb 2024 21:12:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 41ILC3v3070160 for wireless@FreeBSD.org; Sun, 18 Feb 2024 21:12:03 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 271979] bsdinstall(8): iwlwifi(4): system crash when authenticating for Wi-Fi: panic: lkpi_sta_auth_to_scan: lsta 0x... state not NONE: 0, nstate 1 arg 1 Date: Sun, 18 Feb 2024 21:12:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: crash, install, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bz@FreeBSD.org X-Bugzilla-Flags: mfc-stable14? mfc-stable13? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271979 --- Comment #40 from commit-hook@FreeBSD.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=3D8c450ea1083b03f30871506b59034f26b= c608972 commit 8c450ea1083b03f30871506b59034f26bc608972 Author: Bjoern A. Zeeb AuthorDate: 2024-02-03 16:33:56 +0000 Commit: Bjoern A. Zeeb CommitDate: 2024-02-18 18:31:17 +0000 LinuxKPI: 802.11: band-aid for invalid state changes after (*iv_update_= bss) With firmware based solutions we cannot just jump from an active session to a new iv_bss node without tearing down state for the old and bringing up the new node. This likely used to work on softmac based cards/drive= rs where one could essentially set the state and fire at will. We track (*iv_update_bss) calls from net80211 and set a local flag that we are out of synch and do not allow any further operations up the state machine until we hit INIT or SCAN. That means someone will take the st= ate down, clean up firmware state and then we can join again and build up state. Apparently this problem has been "known" for a while as native iwm(4) a= nd others have similar workarounds (though less strict) and can be equally pestered into bad states. For LinuxKPI all the KASSERTs just massively brought this problem out. The solution will be some rewrites in net802= 11. Until then, try to keep us more stable at least and not die on second join1() calls triggered by service netif start wlan0 and similar. PR: 271979, 271988, 275255, 263613, 274003 Sponsored by: The FreeBSD Foundation (2023, partial) Reviewed by: cc Differential Revision: https://reviews.freebsd.org/D43725 (cherry picked from commit 2ac8a2189ac6707f48f77ef2e36baf696a0d2f40) sys/compat/linuxkpi/common/src/linux_80211.c | 309 +++++++++++++++++++----= ---- sys/compat/linuxkpi/common/src/linux_80211.h | 2 + 2 files changed, 216 insertions(+), 95 deletions(-) --=20 You are receiving this mail because: You are on the CC list for the bug.=