Date: Mon, 22 Jan 2024 19:22:47 -0500 From: Cheng Cui <cc@freebsd.org> To: wireless@freebsd.org Subject: Weekly Development report(Jan 16 ~ Jan 19) on the iwlwifi WiFi project Message-ID: <CAGaXuiL1cZYahBEC8XMf2Gd6hrGPQRYsZAa%2BMN4%2BH=_oA%2BRrSw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
--0000000000004a2e4d060f91f43c Content-Type: text/plain; charset="UTF-8" I was still focusing on the problem in PR 276083 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=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 <https://cgit.freebsd.org/src/commit/?id=404b91dac415c5c9126fb4201145049c4d3dfbba>; . 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 <div dir=3D"ltr"><div dir=3D"ltr">I was still focusing on the problem in=C2= =A0<a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D276083" t= arget=3D"_blank">PR 276083</a>=C2=A0which caused a timeout in iwlwifi firmw= are during 802.11n (11ng, 11na) association,=C2=A0thus failing 11n associat= ion.<br></div><div><ol><li>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.</li><ul><li>But the HW cmd from=C2=A0diffe= rent FWs could be different that causes the same symptom.</li><li>So the pr= oblem could be in an earlier command or a missing command, or a flag, etc.<= /li></ul><li>Previously mentioned potential workaround in the PR is not wor= king as the data path fails with firmware not able to re-start.</li><li>Lea= rning=C2=A0Driver API tracing (<span style=3D"color:rgb(0,0,0)">trace-cmd</= span>).</li><li>Finished reviewing D43469.</li><li>Committed MFC stable/14 = in git:<span class=3D"gmail-Apple-converted-space">=C2=A0</span><a href=3D"= https://cgit.freebsd.org/src/commit/?id=3D404b91dac415c5c9126fb4201145049c4= d3dfbba">404b91dac415</a>.</li><li>Had the second project monthly meeting o= n Jan 19, and talked with Bjoern and Joseph about the recent progress.=C2= =A0</li></ol></div><span class=3D"gmail_signature_prefix">-- </span><br><di= v dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature">= <div dir=3D"ltr"><div></div>Best Regards,<div>Cheng Cui</div></div></div></= div> --0000000000004a2e4d060f91f43c--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGaXuiL1cZYahBEC8XMf2Gd6hrGPQRYsZAa%2BMN4%2BH=_oA%2BRrSw>