Received: by 2002:a05:7412:8d09:b0:fa:4c10:6cad with SMTP id bj9csp390231rdb; Tue, 16 Jan 2024 03:44:13 -0800 (PST) X-Google-Smtp-Source: AGHT+IHkrcgNbMBK/M82pJqpQB7ZHo+aZWx7VAtCTMrWs9c9PX1wHunDHI2ArcG2xJg6OUNDQlNF X-Received: by 2002:a17:90b:1d90:b0:28b:ee54:1051 with SMTP id pf16-20020a17090b1d9000b0028bee541051mr3032811pjb.81.1705405453646; Tue, 16 Jan 2024 03:44:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1705405453; cv=none; d=google.com; s=arc-20160816; b=hEdedIMabzeqD/5JRDikEUFkCAa5jGqVRPrtCfZ8jKksipYZdWfJKzsg6N0zZCWMky nDvQRB0518KYNXyOHIWRpsxmPvPU3JoX/0GM4+6FhxeOMzVUAkzvmXlCJ65KEQWAjfcL JLIxMp6eqNd6aoMhxDmSPIwIzyODYujwUHdKrNbDAYlqwkoQvKoLVspzPofhzUenNemb N+5kLfFxsF9k6JVMf0eppWZfRHqVA2ZIYGUWRaKTwS/JkyDaMAu+nwGJWvLyST8RisGM 50xku+RFBEcmKBlcWf9ILENm3goJ8nwLPvse5wxggqBhny7YgeRenewNXh8HitNBOgff 3r4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=mime-version:list-unsubscribe:list-subscribe:list-id:precedence :user-agent:content-transfer-encoding:references:in-reply-to:date:cc :to:from:subject:message-id:dkim-signature; bh=0OCZPW6BtUdee4wcdmdcNhZkbu6nqvpWo+Hiv6o8ilQ=; fh=evMIRIYI2AW8kQRVdGWfRPHRDEfCP/XM3hFm6iCWY8w=; b=ItadOMdZrrW7ksMBLZGK8kRAdMpTTrnjlUaBMbElWe4IZHZRP6iGDnvHAIJ0l6K++e XdWIfJ3AfI0N3n9/MIe1vhzlv6ATQfkKVwvT9SawXQLd9j/3gkzKAoM69rIe98I/NIU9 QA5G8APNtQ/RzlH57jkQP1iSsf+uRjc+OKcbH36lhOISee+zcWwg6CsXf6RyGs/SOX4z Ul1xYborFSHr5C2PNHLVpX6OL4Uz2aP2PeUG7IvwJMD5oQL9k9Nu2c58Kf3dbW0nzvVO ykN3Kj2dXzGFpU5iO0W+O8mEeLrTO/KQWeSg+IrpjmNa8hslztvTiDrYRKb1v+OTVwAX iMuw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=Btb2fs00; spf=pass (google.com: domain of linux-wireless+bounces-1973-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-wireless+bounces-1973-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [139.178.88.99]) by mx.google.com with ESMTPS id s3-20020a17090ad48300b0028e006edae3si9366302pju.175.2024.01.16.03.44.13 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jan 2024 03:44:13 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless+bounces-1973-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=Btb2fs00; spf=pass (google.com: domain of linux-wireless+bounces-1973-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) smtp.mailfrom="linux-wireless+bounces-1973-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 4780A282F7C for ; Tue, 16 Jan 2024 11:44:13 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id C6D9F1BC25; Tue, 16 Jan 2024 11:44:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="Btb2fs00" X-Original-To: linux-wireless@vger.kernel.org Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 270791BC20; Tue, 16 Jan 2024 11:44:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=0OCZPW6BtUdee4wcdmdcNhZkbu6nqvpWo+Hiv6o8ilQ=; t=1705405447; x=1706615047; b=Btb2fs00mYKLl4zp+7z7mvXrfVVlJ+cegj5+sWweRYmJzOc JlldMwwUeMofcxeW9Awr2qt8/ylt9BXcuqNFtNp/tb+Q+ZsGzYHl4DIYiDB0DNTE0wUY2b9SLwxaI hqBHJNwf6dcTB5SWj/L0edWPAz0JIH3Krb5arY+pZ72YW2eFUKXcSCw47JoTzUu0bzDCVfXtWfSbd As/4qieHUV7jv6X8qwDqAqy1Wkc9RSDYWDAox1HeVTPqIRzdvNH5rzHmc0VgPoDlGyU80nVXezPn+ s+Fq+wEusJfmzH2OFEEuQb2Hv2h0DuODQUL/6Yo/jsLd7pOzzIMNWLe0oCGLUkVg==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.97) (envelope-from ) id 1rPhrJ-00000004vh7-46DK; Tue, 16 Jan 2024 12:43:58 +0100 Message-ID: Subject: Re: [REGRESSION] 6.7 broke wifi "AP is in CSA process, reject auth" From: Johannes Berg To: coldolt Cc: ayala.beker@intel.com, linux-wireless@vger.kernel.org, regressions@lists.linux.dev Date: Tue, 16 Jan 2024 12:43:56 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.50.3 (3.50.3-1.fc39) Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned On Tue, 2024-01-16 at 01:56 +0200, coldolt wrote: > I can try to keep connecting for over 5 minutes, it never connects, > keeps outputting the same dmesg message. The kernel before 6.7 > connects immediately. > DS Parameter set: channel 36 > Unknown IE (60): 01 16 24 09 >=20 So it is indeed - as expected of course - advertising that it's about to switch channel and even saying everyone else needs to be *quiet*. This is struct ieee80211_ext_chansw_ie { u8 mode; u8 new_operating_class; u8 new_ch_num; u8 count; } __packed; so mode=3D=3D1 indicates quiet, new_operating_class/new_ch_num are actually the channel it's currently on, and count is 9. Can you say if it actually changes the count? Maybe capture on channel 36 using the NIC as a sniffer what it does over time: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#air_sni= ffing Initially I'd say though that if this situation persists, then your AP is having some problems and we'd not have stayed connected without the patch in question either. If you want, maybe revert and see what the symptom is then? johannes