From nobody Sun Oct 24 07:43:24 2021
X-Original-To: freebsd-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 8198F18088B9
	for <freebsd-wireless@mlmmj.nyi.freebsd.org>; Sun, 24 Oct 2021 07:43:35 +0000 (UTC)
	(envelope-from kevans@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 4HcVSl3KY1z3l64;
	Sun, 24 Oct 2021 07:43:35 +0000 (UTC)
	(envelope-from kevans@freebsd.org)
Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK))
	(Authenticated sender: kevans)
	by smtp.freebsd.org (Postfix) with ESMTPSA id 53E1725F7C;
	Sun, 24 Oct 2021 07:43:35 +0000 (UTC)
	(envelope-from kevans@freebsd.org)
Received: by mail-qk1-f175.google.com with SMTP id bp7so8797254qkb.12;
        Sun, 24 Oct 2021 00:43:35 -0700 (PDT)
X-Gm-Message-State: AOAM531Z+Yrjao/Nfi0hcp9v76tGk7CpQGDoYbWt7VtZxURbLbavHexj
	37nlUVkzmYjPbuoTn+RAtt5p/cKv7We2rjXRJCo=
X-Google-Smtp-Source: ABdhPJyri1oan8SctKVWI/BZ3QwvEbhiyUeW8KqEv1djcGavncCdOmuvRjcDrq46pyPX4eX8DdwK9DT3Yx3QiQViQhY=
X-Received: by 2002:a37:a956:: with SMTP id s83mr8261615qke.244.1635061414842;
 Sun, 24 Oct 2021 00:43:34 -0700 (PDT)
List-Id: Discussions <freebsd-wireless.freebsd.org>
List-Archive: https://lists.freebsd.org/archives/freebsd-wireless
List-Help: <mailto:wireless+help@freebsd.org>
List-Post: <mailto:wireless@freebsd.org>
List-Subscribe: <mailto:wireless+subscribe@freebsd.org>
List-Unsubscribe: <mailto:wireless+unsubscribe@freebsd.org>
Sender: owner-freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
MIME-Version: 1.0
From: Kyle Evans <kevans@freebsd.org>
Date: Sun, 24 Oct 2021 02:43:24 -0500
X-Gmail-Original-Message-ID: <CACNAnaGet4caY63bFwb8WXyi+cW0MbA2Z0ijtvGGhN7widVeaQ@mail.gmail.com>
Message-ID: <CACNAnaGet4caY63bFwb8WXyi+cW0MbA2Z0ijtvGGhN7widVeaQ@mail.gmail.com>
Subject: iwlwifi (AX210)
To: freebsd-wireless <freebsd-wireless@freebsd.org>
Cc: "Bjoern A. Zeeb" <bz@freebsd.org>
Content-Type: text/plain; charset="UTF-8"
X-ThisMailContainsUnwantedMimeParts: N

Hi,

I've got an AX210 chip in a Framework laptop that I've (hackily)
gotten working with iwlwifi tonight... as with some other reports, the
firmware dies in a terrible fire with the stock wpa configuration.
Investigation lead to the following chain of observations:

1. Without WPA at play, I can trigger a scan and it works

2. Starting WPA, the firmware dies.

3. I can avoid it by setting ap_scan=0 in wpa_supplicant.conf and just
triggering a scan manually, e.g., in /etc/rc.d/wpa_supplicant's
wpa_poststart

 4. I can hack around it altogether without modifying the service by
just never passing ssids into the scan request in wpa_supplicant's bsd
driver: https://people.freebsd.org/~kevans/iwlhack.diff -- of course,
then it doesn't consult the cache... but at least my wifi works. :-)

I'm sticking with #4 for now because that' the most maintainable of
the local hacks that I've put together, but it'd be nice to understand
what's going on... a cursory review of the path from net80211 through
to iwlwifi didn't seem to turn up anything too hinky. I haven't tested
whether there's some difference in specific ssid vs. wildcard ssid.

Thoughts?

Thanks,

Kyle Evans