From: moosager <moosager90@gmail.com>
To: Devin Wittmayer <lucid_duck@justthetip.ca>
Cc: linux-wireless@vger.kernel.org, Felix Fietkau <nbd@nbd.name>
Subject: Re: mt7921e: failure to reset causes network drop
Date: Sat, 12 Sep 2026 17:53:30 +0200 [thread overview]
Message-ID: <aqVwl7fe5zHVYXT9@fedora.fritz.box> (raw)
In-Reply-To: <20260910055018.29328-1-lucid_duck@justthetip.ca>
Hi Devin,
> 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.
I can confirm these are the things I've had to rule out with my testing as well.
I can also attest to the fact that the Bluetooth half of the chip works
regardless of the Wi-Fi's state (I should've mentioned that earlier): I've used
my laptop for a while with mt7921e unloaded, all the while Bluetooth was working
the whole time.
> There is a patch for it that the maintainer has taken
Good, though I don't see which tree it has been merged in, I'm sure I'll see it
soon in a future release.
> It sits downstream of your bad read though, so it will not stop the
> register going wrong in the first place.
True, I will stress that the root cause has not been found yet and this chip is
still unusable for me (and others).
Sorry for the late reply, I'll test the output of lspci as well when I get the
chance to debug this further.
next prev parent reply other threads:[~2026-09-12 15:53 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
2026-09-12 15:53 ` moosager [this message]
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=aqVwl7fe5zHVYXT9@fedora.fritz.box \
--to=moosager90@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lucid_duck@justthetip.ca \
--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 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.