From: Devin Wittmayer <lucid_duck@justthetip.ca>
To: moosager <moosager90@gmail.com>
Cc: linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>
Subject: Re: mt7921e: failure to reset causes network drop
Date: Wed, 9 Sep 2026 22:50:18 -0700 [thread overview]
Message-ID: <20260910055018.29328-1-lucid_duck@justthetip.ca> (raw)
In-Reply-To: <anG46qbvCqCHGF-f@fedora.fritz.box>
moosager,
Sorry this sat so long. You were right about the unchecked return. There
is a patch for it that the maintainer has taken, though it has not reached
a release yet:
14739102 mt7921: check drv_pmctrl return in the PCIe reset path
14739848 mt7925, same
It sits downstream of your bad read though, so it will not stop the
register going wrong in the first place.
On debugging further, I had the same ownership handshake fail on a mini
PC here. What that ruled out, so you can skip them: in-tree against
out-of-tree builds, a PCI bus reset, remove and rescan, and a cold boot.
The Bluetooth half of the same chip kept working throughout, so the
silicon was alive and only the WiFi side was stuck.
Devin
next prev parent reply other threads:[~2026-09-10 5:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 10:19 mt7921e: failure to reset causes network drop moosager
2026-09-10 5:50 ` Devin Wittmayer [this message]
2026-09-12 15:53 ` moosager
2026-09-14 21:27 ` Devin Wittmayer
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=20260910055018.29328-1-lucid_duck@justthetip.ca \
--to=lucid_duck@justthetip.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=moosager90@gmail.com \
--cc=nbd@nbd.name \
/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