From nobody Tue Jan 23 00:22:47 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 4TJnqz53ZNz58WHp for ; Tue, 23 Jan 2024 00:23:27 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lf1-f49.google.com (mail-lf1-f49.google.com [209.85.167.49]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TJnqy4JkTz4rBx for ; Tue, 23 Jan 2024 00:23:26 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of ccfreebsd@gmail.com designates 209.85.167.49 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lf1-f49.google.com with SMTP id 2adb3069b0e04-50e6ee8e911so5027378e87.1 for ; Mon, 22 Jan 2024 16:23:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705969404; x=1706574204; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=cEoUZjhgunSSBDpBqF2YJbnWdcma6yrMdeLbmXtCkWY=; b=HbfthEQ71dm7lK8mYG8ZsdR3Szd87zGWj2lIDe9eyv3UBMejDNa9HeHzKJA9ZOB4v2 AOzyOgijGGfn/QR5ZfwuHfZNoIN+bIDKp8xm8G8nPiaga3ewqMv/HzdhP+j0iqpnHEQv RD9m+p7GnbYdjVKd2TY1q219GCpaD8OgUyK8Vh/4hDTzpErwTq6Fx21XavSv+u7YTeYE SsceCKxpSkcKDj1SZACeynafuN/O+CTDESM3RSGl2s8Tz2G6FcF81i00dTs17+BqHNIW tDd+eksvXaD3XzooWuI2wE+310442eGg2kLooDQzRhi8yOh9esb2szJYuO6RBdeAqvO0 veaQ== X-Gm-Message-State: AOJu0YzDLDl6IVDU5T+6ejxXLVRMdu+D0xU7P1kKTfrpxUrfat1zFAKs GrJlqGWFruJscNjIou1etdGU29S0sjQF8MylS+fbEsdpiqlfXAbvRlXcY7bngBQ= X-Google-Smtp-Source: AGHT+IGocdgf2woMTWHmB6Q7hyF+sB0JNdQt0DVv48c4bIW0UIQYljta0irE0dzJk5J3eKFn5NvVrQ== X-Received: by 2002:a05:6512:3117:b0:510:56f:293 with SMTP id n23-20020a056512311700b00510056f0293mr125880lfb.46.1705969403893; Mon, 22 Jan 2024 16:23:23 -0800 (PST) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com. [209.85.167.54]) by smtp.gmail.com with ESMTPSA id fc8-20020a056512138800b0050e75afd92csm2148907lfb.212.2024.01.22.16.23.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 22 Jan 2024 16:23:23 -0800 (PST) Received: by mail-lf1-f54.google.com with SMTP id 2adb3069b0e04-50e6ee8e911so5027348e87.1 for ; Mon, 22 Jan 2024 16:23:23 -0800 (PST) X-Received: by 2002:a05:6512:238e:b0:50e:afc5:b251 with SMTP id c14-20020a056512238e00b0050eafc5b251mr2656939lfv.93.1705969403439; Mon, 22 Jan 2024 16:23:23 -0800 (PST) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 From: Cheng Cui Date: Mon, 22 Jan 2024 19:22:47 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Jan 16 ~ Jan 19) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="0000000000004a2e4d060f91f43c" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.90 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FORGED_SENDER(0.30)[cc@freebsd.org,ccfreebsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[cc@freebsd.org,ccfreebsd@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.49:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.49:from,209.85.167.54:received] X-Rspamd-Queue-Id: 4TJnqy4JkTz4rBx --0000000000004a2e4d060f91f43c Content-Type: text/plain; charset="UTF-8" I was still focusing on the problem in PR 276083 which caused a timeout in iwlwifi firmware during 802.11n (11ng, 11na) association, thus failing 11n association. 1. The latest discovery shows that newer firmwares or older firmwares have the same symptom during 11ng association: the firmware crashes and HW cmd timeouts. - But the HW cmd from different FWs could be different that causes the same symptom. - So the problem could be in an earlier command or a missing command, or a flag, etc. 2. Previously mentioned potential workaround in the PR is not working as the data path fails with firmware not able to re-start. 3. Learning Driver API tracing (trace-cmd). 4. Finished reviewing D43469. 5. Committed MFC stable/14 in git: 404b91dac415 . 6. Had the second project monthly meeting on Jan 19, and talked with Bjoern and Joseph about the recent progress. -- Best Regards, Cheng Cui --0000000000004a2e4d060f91f43c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was still focusing on the problem in=C2= =A0PR 276083=C2=A0which caused a timeout in iwlwifi firmw= are during 802.11n (11ng, 11na) association,=C2=A0thus failing 11n associat= ion.
  1. The latest discovery shows that newer firmwares = or older firmwares have the same symptom during 11ng association: the firmw= are crashes and HW cmd timeouts.
    • But the HW cmd from=C2=A0diffe= rent FWs could be different that causes the same symptom.
    • So the pr= oblem could be in an earlier command or a missing command, or a flag, etc.<= /li>
  2. Previously mentioned potential workaround in the PR is not wor= king as the data path fails with firmware not able to re-start.
  3. Lea= rning=C2=A0Driver API tracing (trace-cmd).
  4. Finished reviewing D43469.
  5. Committed MFC stable/14 = in git:=C2=A0404b91dac415.
  6. Had the second project monthly meeting o= n Jan 19, and talked with Bjoern and Joseph about the recent progress.=C2= =A0
--
=
Best Regards,
Cheng Cui
--0000000000004a2e4d060f91f43c--