mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Woody Suwalski <terraluna977@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
	johannes.berg@intel.com
Subject: Re: Regression in 6.16-rc1 iwlwifi: IRQ issue
Date: Tue, 17 Jun 2025 07:29:17 -0400	[thread overview]
Message-ID: <31460147-3df4-cb16-4537-ab3a0b5b9eb5@gmail.com> (raw)
In-Reply-To: <e8c45d32-6129-8a5e-af80-ccc42aaf200b@gmail.com>

Woody Suwalski wrote:
> Hi Miri,
>
> Just had a chance to try 6.16-rc1 on an older Dell XPS and noticed a 
> constant stream of warning messages
> similar to
>
> "wrong command queue 0 (should be 9), sequence 0x0 readp=40 writep=40"
>
> However actual WiFi connection seems functional.
>
> Is it something you have taken care of in -next already or have I 
> found a new problem?
> And if the latter - can you make a quick patch to test, or will you 
> need a full bisection to analyze?
>
> Thanks, Woody
>
>
Fixed by a patch from Johannes:

diff --git a/drivers/net/wireless/intel/iwlwifi/dvm/main.c b/drivers/net/wireless/intel/iwlwifi/dvm/main.c
index dbfd45948e8b..66211426aa3a 100644
--- a/drivers/net/wireless/intel/iwlwifi/dvm/main.c
+++ b/drivers/net/wireless/intel/iwlwifi/dvm/main.c
@@ -1316,6 +1316,7 @@ static struct iwl_op_mode *iwl_op_mode_dvm_start(struct iwl_trans *trans,
  		     sizeof(trans->conf.no_reclaim_cmds));
  	memcpy(trans->conf.no_reclaim_cmds, no_reclaim_cmds,
  	       sizeof(no_reclaim_cmds));
+	trans->conf.n_no_reclaim_cmds = ARRAY_SIZE(no_reclaim_cmds);
  
  	switch (iwlwifi_mod_params.amsdu_size) {
  	case IWL_AMSDU_DEF:

Thanks, Woody


      reply	other threads:[~2025-06-17 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-15 19:32 Woody Suwalski
2025-06-17 11:29 ` Woody Suwalski [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=31460147-3df4-cb16-4537-ab3a0b5b9eb5@gmail.com \
    --to=terraluna977@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miriam.rachel.korenblit@intel.com \
    /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

all inboxes | Powered by JetHome®