From: Ben Greear <greearb@candelatech.com>
To: Ilya K <me@0upti.me>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [bug] Triple whammy of mt7996e bugs on 7.2+
Date: Mon, 7 Sep 2026 09:30:31 -0700 [thread overview]
Message-ID: <eb405366-6574-4e4c-a89d-363751ed848b@candelatech.com> (raw)
In-Reply-To: <2418461788691106@84aa39c5-f501-4e64-8418-6a8b6eb88e21>
On 9/6/26 3:38 AM, Ilya K wrote:
>> This abomination is now booted on my hardware and I'll get back to you if it explodes again, which I'd expect to happen at some point
> during the weekend at worst (and if it survives longer, that's already an improvement).
>
> OK so it's been over a day with no explosions which is already better than its previous best. The question now I guess is: which one of the patches actually fixes it? And do the teardown paths still need fixing?
>
I don't know why your kernel wasn't working to begin with, so not sure exactly what in our tree would
fix it. We do have some mt7996 tx-hang work arounds, but that bug was reproduced in STA mode in a fairly weird
test case with lots of virtual STA vdevs, so not sure it applies to your case.
Possibly too it is something we pulled in from Felix's tree that will likely be in 7.3
kernel.
As a note, we found a regression in our current 7.2 tree, MLMR has regressed with scan failure being the
symptom, hopefully we'll get that fixed this week.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2026-09-07 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 14:28 [bug] Triple whammy of mt7996e bugs on 7.2+ Ilya K
2026-09-04 16:07 ` Ben Greear
2026-09-04 16:11 ` Ilya K
2026-09-04 16:20 ` Ben Greear
2026-09-04 20:26 ` Ilya K
2026-09-06 10:38 ` Ilya K
2026-09-07 16:30 ` Ben Greear [this message]
2026-09-07 16:35 ` Ilya K
2026-09-12 10:08 ` Ilya K
2026-09-12 10:08 ` Ilya K
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=eb405366-6574-4e4c-a89d-363751ed848b@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@0upti.me \
--cc=netdev@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