From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] iwlwifi IO_PAGE_FAULT and Master Disable Timed Out
Date: Tue, 4 Aug 2026 22:03:19 +0100 [thread overview]
Message-ID: <anJTlyrKsASh9gZg@debian.local> (raw)
In-Reply-To: <DS0PR11MB78800B96A0FE637DC5390E4AA3D62@DS0PR11MB7880.namprd11.prod.outlook.com>
On Sun, Aug 02, 2026 at 07:24:04AM +0000, Korenblit, Miriam Rachel wrote:
>
>
> > -----Original Message-----
> > From: Chris Bainbridge <chris.bainbridge@gmail.com>
> > Sent: Friday, July 31, 2026 8:05 PM
> > To: Grumbach, Emmanuel <emmanuel.grumbach@intel.com>
> > Cc: Berg, Johannes <johannes.berg@intel.com>; Korenblit, Miriam Rachel
> > <miriam.rachel.korenblit@intel.com>; linux-wireless@vger.kernel.org;
> > regressions@lists.linux.dev
> > Subject: [REGRESSION] iwlwifi IO_PAGE_FAULT and Master Disable Timed Out
> >
> > Hi,
> >
> > 0eaa1f245ac0 ("wifi: iwlwifi: mvm: don't support the reset handshake for old
> > firmwares") introduced an intermittent boot regression on my laptop:
> >
> > [ 15.974991] iwlwifi 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
> > domain=0x000a address=0xbe9f5000 flags=0x0000]
> > [ 15.976184] iwlwifi 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT
> > domain=0x000a address=0xbe9f5400 flags=0x0000]
> > [ 15.978501] iwlwifi 0000:01:00.0: Master Disable Timed Out, 100 usec
> >
> > The commit only contains:
> >
> > + /* Those firmware versions claim to support the fw_reset_handshake
> > + * but they are buggy.
> > + */
> > + if (IWL_UCODE_MAJOR(mvm->fw->ucode_ver) <= 77)
> > + trans->conf.fw_reset_handshake = false;
> >
> > The if condition is evaluating true on my laptop despite using firmware ty-a0-gf-
> > a0-89.ucode. So I suspect this is not the correct way to check the firmware
> > version?
>
> Yes, seems like you are right.
> Thanks for the report!
>
> I am attaching a fix candidate, I'd appreciate if you could test it.
Thanks, the fix is working fine.
Reported-and-tested-by: Chris Bainbridge <chris.bainbridge@gmail.com>
prev parent reply other threads:[~2026-08-04 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:04 [REGRESSION] iwlwifi IO_PAGE_FAULT and Master Disable Timed Out Chris Bainbridge
2026-08-02 7:24 ` Korenblit, Miriam Rachel
2026-08-04 21:03 ` Chris Bainbridge [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=anJTlyrKsASh9gZg@debian.local \
--to=chris.bainbridge@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.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