From: Rudi Heitbaum <rudi@heitbaum.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
"Johannes Berg" <johannes.berg@intel.com>,
"Xi Ruoyao" <xry111@xry111.site>,
"Niklāvs Koļesņikovs" <pinkflames.linux@gmail.com>,
"Jeff Chua" <jeff.chua.linux@gmail.com>,
"Zhang Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH net] wifi: iwlwifi: remove 'use_tfh' config to fix crash
Date: Wed, 12 Jul 2023 15:33:43 +0000 [thread overview]
Message-ID: <ZK7H1zISQ1yzkg4X@823b66c6476b> (raw)
In-Reply-To: <20230710145038.84186-2-johannes@sipsolutions.net>
On Mon, Jul 10, 2023 at 04:50:39PM +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> This is equivalent to 'gen2', and it was always confusing to have
> two identical config entries. The split config patch actually had
> been originally developed after removing 'use_tfh" and didn't add
> the use_tfh in the new configs as they'd later been copied to the
> new files. Thus the easiest way to fix the init crash here now is
> to just remove use_tfh (which is erroneously unset in most of the
> configs now) and use 'gen2' in the code instead.
>
> There's possibly still an unwind error in iwl_txq_gen2_init() as
> it crashes if TXQ 0 fails to initialize, but we can deal with it
> later since the original failure is due to the use_tfh confusion.
>
> Tested-by: Xi Ruoyao <xry111@xry111.site>
> Reported-and-tested-by: Niklāvs Koļesņikovs <pinkflames.linux@gmail.com>
> Reported-and-tested-by: Jeff Chua <jeff.chua.linux@gmail.com>
> Reported-and-tested-by: Zhang Rui <rui.zhang@intel.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217622
> Link: https://lore.kernel.org/all/9274d9bd3d080a457649ff5addcc1726f08ef5b2.camel@xry111.site/
> Link: https://lore.kernel.org/all/CAAJw_Zug6VCS5ZqTWaFSr9sd85k%3DtyPm9DEE%2BmV%3DAKoECZM%2BsQ@mail.gmail.com/
> Fixes: 19898ce9cf8a ("wifi: iwlwifi: split 22000.c into multiple files")
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Hi Johannes,
I can confirm that this is now working with 83.e8f84e98.0 so-a0-gf-a0-83.ucode.
it wasnt with 6.5-rc1 and both 78 and 83 firmwares.
Tested-by: Rudi Heitbaum <rudi@heitbaum.com>
prev parent reply other threads:[~2023-07-12 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 14:50 [PATCH net] wifi: iwlwifi: remove 'use_tfh' config to fix crash Johannes Berg
2023-07-12 3:30 ` patchwork-bot+netdevbpf
2023-07-12 15:33 ` Rudi Heitbaum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZK7H1zISQ1yzkg4X@823b66c6476b \
--to=rudi@heitbaum.com \
--cc=jeff.chua.linux@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pinkflames.linux@gmail.com \
--cc=rui.zhang@intel.com \
--cc=xry111@xry111.site \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox