Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8340931ybn; Tue, 1 Oct 2019 06:51:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzgYA6UhQK66S4aUl3WGVnGyDPwdDo8o4kvQkqhAh/QXPQoEEDBAVe/SvzGzZMLWlgQcPjP X-Received: by 2002:a17:906:7d0:: with SMTP id m16mr24680635ejc.95.1569937869305; Tue, 01 Oct 2019 06:51:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569937869; cv=none; d=google.com; s=arc-20160816; b=OQ7Qjit7SSRqvZYAsm0uxLQgEQ5u+QP2C8j5tw7ZFZeyAWDYJ8vj81j5hMY277aTOK SlxB9eZIu4BV+QcQ9BhsRzKRwbg8A8KOyJElLfhrXkjYfpVxAsdAnGqHN7V4nh1KCQga UhefRuYXVB8YV/j1u39CC6WuzIX01WB/v7bQzmsiCkkgm36iMsvjZb8vT/yQOphr6aOs GR1+KCxqNR41nBnurim7h57wuGBBkF5cZyvYPMfYzFJZPE5mq7sriGqCs+akr4XjveEU Y9erdpb3XiPX+mVPRkR+Hn0uux6rNktSGY8lszKfvT7Q5m4DwX7LoVe7CJBc73QIL9Uy 8gmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=qAq4D9XubMPKEkr1wOqycnRaswMy9j7JVCSsXg5fjns=; b=natHlrC5SPdFS7SDFqN9REDNUtaD5ON2vhI60w4nU2epQHztVXj3zR4aCCaHP9o0KD HkoHxXEwRJSePhJjVYeqM4Y8WANIrYWQgLEERv2ayQIIYHkJQoYfJd9PlwQkkssDawhp D/txYzu9BG/UzT9xnq9WARDb4by/YpjvSln2LdxXkxDgYnMYDUSQQ+2yUTxAJzpxLmwe 9zokR8RtwxWXapr3HHp3DhUgxgtWLXj6tiJwWXjIWHd3oz4DlqW6ow3OlRNEls9LWERw XfdcWJ+T5HmgQhzCNrh+rmL4AvYECdHnrLCYXbnkwLQs/betJknN4hBewZ1lD+gJUhsa RLJQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c28si9416389ede.3.2019.10.01.06.50.33; Tue, 01 Oct 2019 06:51:09 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388760AbfJANti (ORCPT + 99 others); Tue, 1 Oct 2019 09:49:38 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:34406 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388742AbfJANti (ORCPT ); Tue, 1 Oct 2019 09:49:38 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.2) (envelope-from ) id 1iFIX1-0001dW-FZ; Tue, 01 Oct 2019 15:49:35 +0200 Message-ID: <616a319e4b8623508f6cd00fcfca8303f494a2de.camel@sipsolutions.net> Subject: Re: mac80211_hwsim (kernel 4.18+): wmediumd + 2.4Ghz From: Johannes Berg To: Ramon Fontes , Bob Copeland Cc: Krishna Chaitanya , linux-wireless Date: Tue, 01 Oct 2019 15:49:33 +0200 In-Reply-To: (sfid-20191001_152002_684460_EE3686CE) References: <80d9c12986ec0a13c34672ca1c16f37cae0cc096.camel@sipsolutions.net> <39d646206446159a2b0a67ee7d8667483ade0733.camel@sipsolutions.net> (sfid-20191001_152002_684460_EE3686CE) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, 2019-10-01 at 10:19 -0300, Ramon Fontes wrote: > > Do they also have the same version of wmediumd? > > Yes, they have the same version. As you can also see through the > video, I only change the kernel and all the packages have the same > version. I also tried to check the latest commits of mac80211_hwsim, > but haven't found a reason for the problem yet. I had been looking, but didn't consider that where you say "4.18" you probably meant "4.18.xyz" for some stable version of 4.18 ... Now that I look at that, I think most likely the reason is commit 119f94a6fefc ("cfg80211: Address some corner cases in scan result channel updating") which was backported to the 4.18 series. Before this commit, we'd have used the DS element all the time, after this commit we'd trust the RX channel on 5 GHz... Here's a test to reproduce this: https://p.sipsolutions.net/63b37d07fd52179c.txt However, I think the only reasonable way to fix this is in wmediumd: https://p.sipsolutions.net/6c52392b5e31d9d1.txt Bob, what do you think? johannes