From nobody Tue May 28 10:06:30 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 4VpSpf56hnz5Lw9x for ; Tue, 28 May 2024 10:06:34 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VpSpf4fl7z4Dwd; Tue, 28 May 2024 10:06:34 +0000 (UTC) (envelope-from bz@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1716890794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=J7Qcs9k5SJd8cPRwoCz5ITcDJrBm4gH0KtdrX7mXkYI=; b=eiZoOyvcyh73pbeTLSvHk97b5GXaB0PdTQRDfKZQa8tQwabn7SNuO4n911f7GAxKLxz9bQ Xw+AEUEHrOfTwiGiHHgHxRwwBPEs6hLY8rcPx0FK/NCbwIaOdT1KRb0PnuKrZr1x8zOv4K oP+pnYwN+5dgMrVC8xPC5X7XgccRMBmZlYQmerywMku40Qr0LiX5IVMGOVOLWreaELpUPw BS32B4YCJeVcEaUMVeqYq2Mbge0yc1TWsbHheoP1aXmeCv8TfaDe8vlKcCF5FCw9IXtsXF uMrlfY1Z/A35eoKggyJZlRrp5XSQbM6JcaaLjRQthd4PhDbrGrInu7pM9p/CjA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1716890794; a=rsa-sha256; cv=none; b=yXdB3psAIrkIW/eya6KL96ocm7Btg/rP9rLuQUwPoi4aZKNigLIE0GeCKw1yedDQCx1mvB ZjAipzpDpbDeh1FKgkGhzv7s2w9RT1KREq1fhSmBEWo6aghcPh3cMQ8NJKDNN+U5rrBLUF ZyxXshXCxNcr5jf+5y3XO6ynbyIPGJYbuzkb+p30Ck/UFGBMOO8Z4l3Pl5Q65MQhReLVAH yf1GPBiN+BDxCSfVJrYTljIz8wVOSoTFl0idnlNAy6tKSk5+u09+w2cQhqCUxaYnBPsA5M iiMnLSRkfOOJxEq8ihBBmYC/apzwviBxGoWZkHGuMYz9HGxQAHOQL2TCRx6xvQ== 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=1716890794; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=J7Qcs9k5SJd8cPRwoCz5ITcDJrBm4gH0KtdrX7mXkYI=; b=hWXxYnEZgf5RWxnAHb4sifKhAuxSF+9yJl2IkmZAOP1fCnEcDVEgSBXb6GHkQkVm+PV44G zB140BeOrlEJSoCqt9hLl8eM4nXqphKy+papqa6ygo4vRoB5nSDdBkJAqNQgEWPBPXjDUo +ukKPiQraAIKT759z240+QhJu2TS9vIw2d11H8B8VpMb+3VrV7nnwgkb3qAEWnyb4kgI8z Vfyj9AXOSwgMf0LciFG4OLPzWOnWgPhhHBZT7cvXX941whHe7hWBTRYtjqCcvkYDARrGbg 9YXmnVchVSoj6rS0dJmXtTCB4ZXSxg5/5FTy5mgmCZpUsybvghWo8C5nrmQG6A== Received: from mx1.sbone.de (cross.sbone.de [195.201.62.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4VpSpf3WPWzd45; Tue, 28 May 2024 10:06:34 +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.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 705778D4A126; Tue, 28 May 2024 10:06:32 +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 B80F82D029D8; Tue, 28 May 2024 10:06:31 +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 5-rnZMsaiZYu; Tue, 28 May 2024 10:06:30 +0000 (UTC) Received: from strong-iwl0.sbone.de (strong-iwl0.sbone.de [IPv6:fde9:577b:c1a9:4902:b66b:fcff:fef3:e3d2]) (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 861AD2D029D2; Tue, 28 May 2024 10:06:30 +0000 (UTC) Date: Tue, 28 May 2024 10:06:30 +0000 (UTC) From: "Bjoern A. Zeeb" To: Adrian Chadd cc: FreeBSD wireless mailing list Subject: Re: wireless porject status report In-Reply-To: Message-ID: <040s62p3-93o1-9nq2-60q3-qp6p02norro4@serrofq.bet> References: <4rq46736-pnp2-nrp2-r3q9-3r3s3256os84@SerrOFQ.bet> 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; charset=US-ASCII; format=flowed On Mon, 27 May 2024, Adrian Chadd wrote: > On Mon, 27 May 2024 at 15:59, Bjoern A. Zeeb wrote: > > Last I got fed up by SCAN problems this afternoon and started >> investigating. Have other people (with iwn/iwm/iwlwifi or others) noticed >> the fact that once you are associated with a channel in a band (say Channel >> 6) you will not get scan results for 11a/5Ghz anymore? Or that >> sometimes scanning will "just stop" (way beyond scanvalid interval) and >> triggering a manual scan (or from wpa_cli) you either just get the old >> cache >> or EINPROGRESS? (checking ddb on-off I noticed that the scan got stuck >> in ACTIVE or BGSCAN was on suddenly despite IEEE80211_FEXT_SCAN_OFFLOAD >> is set given iwlwifi does hw_scan and we never enable background >> scanning). >> I know this has bugged me in the past a lot on iwm(4) on 8xxx chipsets >> and ifconfig down/ifconifg mode auto/ifconfig up fixed it again. >> In case more people have observed similar things, please let me know >> so we can properly track this. >> > > Oh, wow, this is still a problem? Aiee. I remember fixing a WHOLE lot of > races > in the non scan offload and the then-new scan full offload paths. > > I'll see if I can reproduce it on iwn(4) (which supports full scan offload) You should know better given you introduced this .. Reproducing on iwn(4) will be hard unless you change the driver... supports (in theory) and "supports" (is implemented and working) .... just saying ... % grep -r IEEE80211_FEXT_SCAN_OFFLOAD sys/dev/ sys/dev/iwm/if_iwm.c: ic->ic_flags_ext = IEEE80211_FEXT_SCAN_OFFLOAD; sys/dev/usb/wlan/if_rsu.c: ic->ic_flags_ext |= IEEE80211_FEXT_SCAN_OFFLOAD; It's a hacked up solution and scrolling through I found at least two places where the logic seems wrong (and it's only what--8 checks in total?). I think atomics are the least of my concerns here... -- Bjoern A. Zeeb r15:7