From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
lkml <linux-kernel@vger.kernel.org>,
Gregory Greenman <gregory.greenman@intel.com>,
Kalle Valo <kvalo@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Linux Wireless <linux-wireless@vger.kernel.org>,
Linux Networking <netdev@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: Linux-6.5 iwlwifi crash
Date: Sun, 9 Jul 2023 08:00:40 +0800 [thread overview]
Message-ID: <CAAJw_ZvBUpMMC886CDdsLFW6bUG69X78zVfre7gCfu=aTR1xGQ@mail.gmail.com> (raw)
In-Reply-To: <0068af47-e475-7e8d-e476-c374e90dff5f@lwfinger.net>
On Sat, Jul 8, 2023 at 2:07 AM Larry Finger <Larry.Finger@lwfinger.net> wrote:
> I am certainly no expert on iwlwifi, but this change looks suspicious:
>
> @@ -10,8 +10,7 @@
> #include "fw/api/txq.h"
>
> /* Highest firmware API version supported */
> -#define IWL_22000_UCODE_API_MAX 81
> -#define IWL_22500_UCODE_API_MAX 77
> +#define IWL_22000_UCODE_API_MAX 77
>
> /* Lowest firmware API version supported */
>
> The parameter that was originally set to 81 is now set to 77.
>
> Please try the attached patch.
>
> Larry
Larry, tried, but that didn't help.
Thanks,
Jeff.
prev parent reply other threads:[~2023-07-09 0:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230429020951.082353595@lindbergh.monkeyblade.net>
[not found] ` <CAAJw_ZueYAHQtM++4259TXcxQ_btcRQKiX93u85WEs2b2p19wA@mail.gmail.com>
2023-04-29 14:07 ` iwlwifi broken in post-linux-6.3.0 after April 26 Bagas Sanjaya
2023-04-29 18:17 ` Jeff Chua
2023-04-30 10:58 ` Jeff Chua
2023-04-30 17:06 ` Greenman, Gregory
2023-04-30 18:00 ` Greenman, Gregory
2023-04-30 23:57 ` Jeff Chua
2023-05-01 4:46 ` Bagas Sanjaya
2023-07-05 7:24 ` Linux-6.5 iwlwifi crash Jeff Chua
2023-07-05 8:37 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-05 11:56 ` Jeff Chua
2023-07-05 18:11 ` Larry Finger
2023-07-07 1:56 ` Jeff Chua
2023-07-07 8:43 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-07 9:48 ` Thorsten Leemhuis
2023-07-07 18:07 ` Larry Finger
2023-07-09 0:00 ` Jeff Chua [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='CAAJw_ZvBUpMMC886CDdsLFW6bUG69X78zVfre7gCfu=aTR1xGQ@mail.gmail.com' \
--to=jeff.chua.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregory.greenman@intel.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).