From nobody Thu Jan 30 22:46:50 2025 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 4YkYzt5xCzz5m08y for ; Thu, 30 Jan 2025 22:46:50 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YkYzt5Q5Lz3YMf for ; Thu, 30 Jan 2025 22:46:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738277210; 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=6AqIJc3X5GDL7SvmsnTsFaxq23+CfKWKufLUq0DsPUo=; b=h9jOloRWL6F6nELVm+JPMk0A7ZWEqItaxRai1iTQl0R4jioX2W2vPK4XLyOQzpQVFm0bg/ oPt3/7dYj+AY4TMfAnCn21CtMJYFCrnOZnJYyOPEOhnWRcPyz2Fam1u/YXq01/yqNR0D0f +Xwlxv/Q3k6XERs0iCDPSPzniEB9TNqYVfLCnl6gQb1lnbSivGHXo8K56RgsUAyCHXniqp onEkBT6yUibs63x85WY1QnNi/CVaRJl8P8RWng70hOGr6jO3VuaqN0ayAOCxnrhxjWUolA CrtYsKBjHNUmS2Ax6Jfc3ekZG1zb7lt2Qw8z92P/nJvc3V4NoUQj84J5wtUKVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1738277210; 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=6AqIJc3X5GDL7SvmsnTsFaxq23+CfKWKufLUq0DsPUo=; b=NvG5g4ldYRg1uR1uBxWkALOF0zmOylpk+c8m9xY8g3vIsh3YV3Ko6iJvfCw2M87jzh9c7Y ODNoyfint7GpmvQM9lHHMPdBdthQ/+3d4je/V2N//aqEeSd+HvXxs2SKCW16IhVQM5iVoL Evc4ihpLFjGoZLjiTolDbVlyxo0xo9qBABw+eF8NeNd/5WX1JE0yhZFcO2kRU0JRG2fxiw immcU3J54EI6mJz756l1Qs72hZ4GDEHBzU35o0qPqokbBNJ40v1jMdvRVLH8JxzQ/kCApX kayN43hXJ5x/sDnBbaok7PX5SmM6YnkNzfGRhbMRKSjTvsaXrgtvASW11g8QaQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1738277210; a=rsa-sha256; cv=none; b=pLH+WMenNZs6Rmj6IFwPKa72M8rxtxhpbmgkDV+DzG8Ssb/t2L+JX53ySsDMJKsIlaV/Iz h9OB+F19ZvQ0bv8BijQ2V8sQ1SG1jrKewy1XERvS7saiBRwuDFyyzPwRJHO3353b74lgrQ ccyZQ2IFL+sRzyRzPsWAPty1EPZrUtO/QbF+Omke+uUkcnyDyvUkoOdjXqWM4doI8zwvfU hJZi/dz/vPEjrYff3KTjnVTt99s7hEz3qFog7PwzorNl/skQXj9YX4JWso0mJ/YzLzbUav Vkt8E8sOCTHZbU84zN6DWMnIvf8OxMUPggUJwQ5NobOPW9Jyl6Np4Xh18Xne0Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none 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 4YkYzt4lBWz16JS for ; Thu, 30 Jan 2025 22:46:50 +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 50UMkoIh050417 for ; Thu, 30 Jan 2025 22:46:50 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50UMkobu050416 for wireless@FreeBSD.org; Thu, 30 Jan 2025 22:46:50 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 284421] iwlwifi: kernel panic: lkpi_sta_scan_to_auth:1346: mo_sta_state(NONE) failed: -5 [Intel 8260] Date: Thu, 30 Jan 2025 22:46:50 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: mshirk@daemon-security.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bz@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D284421 --- Comment #7 from Shirkdog --- I believe reporting this bug has caused the issue not to happen as much...a= nd this is probably due to interacting with the laptop and not letting it sit = idle for a long time. I will report back on this bug when I can provide answers = to your questions. Specifically when it happens again I will tell you about th= is. >>>If instead of doing a netif restart wlan0, can you simply try: >>> ifconfig wlan0 down >>> ifconfig wlan0 up >>> ifconfig wlan0 scan >>>and see if that helps to get you associated again without the panic when= this happens? I will load up the latest FreeBSD 15-CURRENT build, setting debug on wpa_supplicant over the weekend when I am not using this laptop to see if I= can get the panic condition again.=20 Now some responses to your other comments: >>>Right, and why is that? What happened before? >>>I see beacon misses in the log below. >>>Crowded spectrum? Low signal? ..? Crowded spectrum is interesting, as this has happened with different wirele= ss routers (Netgear, TP_Link) at two different locations where there is defini= te overlap of wireless signals. For both locations, I had the laptop very clos= e to the router. The Intel driver works negotiates on the 2.4GHz band with 802.1= 1g. Of interest, the modulation does appear to change over time, from OFDM to D= S,=20 >>>But I didn't manage a follow-up panic. >>>You mentioned that you had that problem with iwm(4) already? >>>Did it just drop or did you get firmware crashes there as well? >>>I would really be interested on how this showed on iwm(8) given this see= ms to be related to older chipsets. The iwm driver acted the same way you have found, after a period of time, I would come back and find "no carrier" on "wlan0", but I would simply refresh the interface and get an IP address. I never got a panic with the iwm drive= r, this is something I have only seen with the iwlwifi driver. The laptop is getting old, but since intel wireless is pretty common, I wanted to raise t= his issue. --=20 You are receiving this mail because: You are on the CC list for the bug.=