From: "Luís Henriques" <lhenriques@suse.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Hans de Goede <hdegoede@redhat.com>,
Gregory Greenman <gregory.greenman@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: New 6.1 net/mac80211/rx.c warning with iwlwifi / Ultimate-N 6300 wifi
Date: Mon, 5 Sep 2022 18:16:00 +0100 [thread overview]
Message-ID: <YxYu0CawomVcTlRn@suse.de> (raw)
In-Reply-To: <644e506ab60a58b95bdbbb5d9c3e425622931f8f.camel@sipsolutions.net>
On Mon, Aug 22, 2022 at 12:21:49PM +0200, Johannes Berg wrote:
> On Mon, 2022-08-22 at 10:33 +0100, Luís Henriques wrote:
> > On Sat, Aug 20, 2022 at 03:12:33PM +0200, Hans de Goede wrote:
> > > Hi All,
> > >
> > > While testing 6.0-rc1 on a Dell Latitude E6430 with:
> > >
> > > 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 35)
> > >
> >
> > I've just seem a similar splat on -rc2, with a different card:
> >
> > 02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
> >
>
> Yeah this is an issue with the new multi-link work.
>
> We've seen it too, though the rx->link _should_ be set to deflink here
> in the cases of non-MLO connections.
>
> We're investigating.
FWIW I'm still seeing this with RC4.
Cheers,
--
Luís
next prev parent reply other threads:[~2022-09-05 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 13:12 New 6.1 net/mac80211/rx.c warning with iwlwifi / Ultimate-N 6300 wifi Hans de Goede
2022-08-22 9:33 ` Luís Henriques
2022-08-22 10:21 ` Johannes Berg
2022-09-05 17:16 ` Luís Henriques [this message]
2022-09-05 17:23 ` Johannes Berg
2022-09-05 17:37 ` Luís Henriques
2022-08-23 16:40 ` New 6.1 net/mac80211/rx.c warning with iwlwifi / Ultimate-N 6300 wifi #forregzbot Thorsten Leemhuis
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=YxYu0CawomVcTlRn@suse.de \
--to=lhenriques@suse.de \
--cc=gregory.greenman@intel.com \
--cc=hdegoede@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--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).