From nobody Tue Feb 06 14:24:11 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 4TTlrM3Ggwz59M87 for ; Tue, 6 Feb 2024 14:24:51 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lf1-f51.google.com (mail-lf1-f51.google.com [209.85.167.51]) (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 4TTlrL5NmPz4ZvR for ; Tue, 6 Feb 2024 14:24:50 +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.51 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lf1-f51.google.com with SMTP id 2adb3069b0e04-51124d86022so8793264e87.0 for ; Tue, 06 Feb 2024 06:24:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707229489; x=1707834289; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MpWeXevr8KlHda6i6yRyYROiwquRdjPPFRDZT+kKl9c=; b=R6Me+VBIZmrNYTfz2ReCekDnsTkzR3T49Q1Bi9QonRJrmlk862X2dHYgASU/gEDA5l DSFtqsBMWF/mOg/RqThgMyZ2YR8FowLYZE0b+wUgq39EIbp5QIQkGNRcQjbTgTV8AfaM 4v+g6pHWDRj7oBJEFHudiiZeX7QDs4JOa8i0nqoHXWxe4AuJtDz++RT5oBHyqRrBhFdx CcY6M6wF54dCz2RHyBoZvmYgylYMvjT/5UHv4hFJtDlNDaaoqug4tXjZceWUCyd5o3HL 3Q0vo5XocIYtxLjooFi63F8PYO93fAowLeWiyKhkKgy9Nd+ZQIqcu91tv+tmhLkvky9m n4HQ== X-Gm-Message-State: AOJu0Yz0iZ4iWTmd2t78U90f1neA6E37NznP9/0i5Ly8yhV1drES9gU1 Sd/kLB1LT5sTUDFn17b2KM4eaIhWy/2sU5Yn+sofL9iTGDZjD6q9IVy+m7okkQE= X-Google-Smtp-Source: AGHT+IFkForxpqXeRC7YZ5DkyfBwhNH7iAoOM5WBS/VGhUPKIldug/Ky89sT/+mJA6ZnonBRbon/Ig== X-Received: by 2002:a19:8c46:0:b0:511:4eb3:8ef9 with SMTP id i6-20020a198c46000000b005114eb38ef9mr1663326lfj.5.1707229488281; Tue, 06 Feb 2024 06:24:48 -0800 (PST) Received: from mail-lj1-f182.google.com (mail-lj1-f182.google.com. [209.85.208.182]) by smtp.gmail.com with ESMTPSA id l26-20020ac2555a000000b005101bcba21asm252214lfk.6.2024.02.06.06.24.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 06 Feb 2024 06:24:48 -0800 (PST) Received: by mail-lj1-f182.google.com with SMTP id 38308e7fff4ca-2d073b54359so71896581fa.0 for ; Tue, 06 Feb 2024 06:24:48 -0800 (PST) X-Received: by 2002:a05:651c:1504:b0:2d0:a19f:e44a with SMTP id e4-20020a05651c150400b002d0a19fe44amr2004183ljf.44.1707229487972; Tue, 06 Feb 2024 06:24:47 -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: Tue, 6 Feb 2024 09:24:11 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Jan 29 ~ Feb 02) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="0000000000002e4daf0610b75798" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.90 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; 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.51:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.51:from,209.85.208.182:received] X-Rspamd-Queue-Id: 4TTlrL5NmPz4ZvR --0000000000002e4daf0610b75798 Content-Type: text/plain; charset="UTF-8" I was still focusing on the problem in PR 276083 last week, which caused a timeout in iwlwifi firmware during 802.11n (11ng, 11na) association, thus failing 11n association. But this problem may need a second help after I have to move it to a lower priority. 1. Given the problem could be in an earlier command or a missing command, or a flag, (a needle in a haystack), etc, I am narrowing down the problem/learning scope. - In discussion, Bjoern reached out in his contact and found some feedback about the problem which may be caused by a short hcmd size. - With the help of trace-cmd and some hex raw data dump in Linux/FreeBSD, in comparison we found the raw data in the specific hcmd (grp=5, cmd=22) was intact. So the hcmd size problem is highly likely ruled-out. - Further investigation from Bjoern showed the hcmd had reached the firmware and at least processed to some extent, but the answer didn't come back. - We decided to reach out to the contact again and hope there is some help/feedback. 2. Meanwhile, I am lowering down the priority of PR 276083 , and focusing on remaining tasks. After discussion, I will work on some other TX/data path after disabling the ampdu_rx* case. 3. Finished reviewing D43646, D43635, D43512. -- Best Regards, Cheng Cui --0000000000002e4daf0610b75798 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was still focusing on the problem in=C2= =A0PR 276083=C2=A0last week, which caused a timeout in iw= lwifi firmware during 802.11n (11ng, 11na) association,=C2=A0thus failing 1= 1n association. But this problem may need a second help after I have to mov= e it to a lower priority.
  1. Given the problem could be = in an earlier command or a missing command, or a flag,=C2=A0(a needle in a = haystack), etc, I am narrowing down the problem/learning scope.
  2. In discussion, Bjoern reached out in his contact and found some feedba= ck about the problem which may be caused by a short hcmd size.
  3. With= the help of trace-cmd and some hex raw data dump in Linux/FreeBSD, in comp= arison we found the raw data in the specific hcmd (grp=3D5, cmd=3D22) was i= ntact. So the hcmd size problem is highly likely ruled-out.
  4. Further= investigation from Bjoern showed the hcmd had reached the firmware and at = least processed to some extent, but the answer didn't come back.
    5. We decided to reach out to the contact again and hope there is some help/= feedback.
  5. Meanwhile, I am lowering down the priority of=C2=A0<= a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276083" targe= t=3D"_blank">PR 276083, and focusing on remaining tasks. After discussi= on, I will work on some other TX/data path after disabling the ampdu_rx* ca= se.
  6. Finished reviewing=C2=A0D43646, D43635, D43512.

--
=
Best Regards,
Cheng Cui
--0000000000002e4daf0610b75798--