Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "Peer, Ilan" <ilan.peer@intel.com>, "angelsl@in04.sg" <angelsl@in04.sg>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi: 9260: Spurious "Unhandled alg: 0x707" and 0x71b
Date: Sat, 17 Aug 2019 20:01:51 +0000	[thread overview]
Message-ID: <0e1a890d2896791d7291f0174cc0e96832d7ed33.camel@intel.com> (raw)
In-Reply-To: <badc218b-ea1f-3697-b1f2-3ebb294d9849@in04.sg>

Hi,

On Fri, 2019-08-16 at 16:55 +0800, Tee Hao Wei wrote:
> Hi,
> 
> I've been getting "Unhandled alg: 0x707" or 0x71b randomly
> on my Intel 9260. It seems to happen most often when it
> associates to a new AP (or roams to a different one that
> has the same SSID/authentication). It also seems to happen
> only with particular APs. (I don't have access to the APs,
> so there's not much I know about them.)
> 
> I applied the two patches mentioned in Bugzilla #203593[1]
> i.e. "iwlwifi: mvm: Allow multicast data frames only when
> associated" and "iwlwifi: mvm: Allow multicast data frames
> only when authorized" on top of iwlwifi in 5.2.8, which
> improved the situation a lot, but it still happens pretty
> frequently.
> 
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=203593

This print is harmless really. After this bug has been reported, I have
been contact by the firmware team who wanted to deprecate the flag that
we change in the bug for that Bugzilla, so that the fix will be a no-op 
for newer firmware. Bottom line, we are removing this print, or we are
leaving it only for unicast packets. This has been merged in our
internal repository and it will be upstreamed following the regular
process.

You can find it here in our backport based driver:

https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/commit/?id=f9b9f92dd84c5c467cbcc620584864de8fbfb56c


> 
> I'll try to collect some debug data soon. Also, I'll try
> to see if my 8260 has the same issues.
> 
> Is there anything else I should try or any other patches I
> should backport?
> 
> Thanks.
> 

      reply	other threads:[~2019-08-17 20:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16  8:55 iwlwifi: 9260: Spurious "Unhandled alg: 0x707" and 0x71b Tee Hao Wei
2019-08-17 20:01 ` Grumbach, Emmanuel [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=0e1a890d2896791d7291f0174cc0e96832d7ed33.camel@intel.com \
    --to=emmanuel.grumbach@intel.com \
    --cc=angelsl@in04.sg \
    --cc=ilan.peer@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    /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