From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "lenb@kernel.org" <lenb@kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>
Subject: Re: iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000.
Date: Wed, 12 Jan 2022 15:42:33 +0000 [thread overview]
Message-ID: <f917dd2fca4f4f1227d5848681ec88cdd235d4ad.camel@intel.com> (raw)
In-Reply-To: <CAJvTdKmXuzwhV+ExqPAAUTgOFk1dnU+CjnErgUgdfXp=vug_EQ@mail.gmail.com>
On Wed, 2022-01-12 at 09:58 -0500, Len Brown wrote:
> On Wed, Jan 12, 2022 at 4:05 AM Coelho, Luciano
> <luciano.coelho@intel.com> wrote:
>
> > There was some refactoring in this area, to move the initialization to
> > the init phase, and that must be causing this. I suspect this patch:
> >
> > commit 78a19d5285d93e281b40c3b8d5a959fbbd2fe006
> > Author: Miri Korenblit <miriam.rachel.korenblit@intel.com>
> > AuthorDate: Thu Aug 5 14:21:56 2021 +0300
> > Commit: Luca Coelho <luciano.coelho@intel.com>
> > CommitDate: Thu Aug 26 23:36:10 2021 +0300
> >
> > iwlwifi: mvm: Read the PPAG and SAR tables at INIT stage
> >
> > ...which was introduced in v5.15.
>
> good guess!
> I have confirmed that upstream 5.14 works, and that 5.15 with the
> commit above reverted works.
Did you have a chance to test the patch I sent? I'm almost sure it
will, but it would be nice to get a confirmation. :)
--
Cheers,
Luca.
next prev parent reply other threads:[~2022-01-12 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 1:47 iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000 Len Brown
2022-01-12 8:34 ` Johannes Berg
2022-01-12 9:05 ` Coelho, Luciano
2022-01-12 9:27 ` Johannes Berg
2022-01-12 9:33 ` Coelho, Luciano
2022-01-12 9:35 ` Johannes Berg
2022-01-12 9:40 ` Coelho, Luciano
2022-01-12 14:58 ` Len Brown
2022-01-12 15:42 ` Coelho, Luciano [this message]
2022-01-12 18:14 ` Len Brown
2022-01-12 18:49 ` Len Brown
2022-01-13 8:51 ` Coelho, Luciano
2022-01-27 18:28 ` Coelho, Luciano
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=f917dd2fca4f4f1227d5848681ec88cdd235d4ad.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=johannes@sipsolutions.net \
--cc=lenb@kernel.org \
--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