From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: emmanuel.grumbach@intel.com
Cc: johannes.berg@intel.com, 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
Date: Fri, 31 Jul 2026 18:04:54 +0100 [thread overview]
Message-ID: <amzVtgQb2p-_nShU@debian.local> (raw)
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?
Also comment #21 on bugzilla.kernel.org bug #220600 (which this commit
was supposed to fix) reports the same "Master Disable Timed Out" error
(although no IO_PAGE_FAULTS, probably the bad memory access is not
caught without iommu=strict).
#regzbot introduced: 0eaa1f245ac03ed0c6394159360532726f666811
reply other threads:[~2026-07-31 17:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=amzVtgQb2p-_nShU@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.