Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Eason Lai (賴易聖)" <Eason.Lai@mediatek.com>
To: "lucid_duck@justthetip.ca" <lucid_duck@justthetip.ca>
Cc: "Litien Chang (張立典)" <Litien.Chang@mediatek.com>,
	"nbd@nbd.name" <nbd@nbd.name>,
	"lorenzo@kernel.org" <lorenzo@kernel.org>,
	"Quan Zhou (周全)" <Quan.Zhou@mediatek.com>,
	"Kun Wu (吳謹至)" <kun.wu@mediatek.com>,
	"Ryder Lee" <Ryder.Lee@mediatek.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Sean Wang" <Sean.Wang@mediatek.com>,
	"Leon Yen (顏良儒)" <Leon.Yen@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Deren Wu (武德仁)" <Deren.Wu@mediatek.com>,
	"JB Tsai (蔡志彬)" <Jb.Tsai@mediatek.com>
Subject: Re: [PATCH v1] wifi: mt76: mt7925: Fix MCU command timeouts during module unload
Date: Thu, 6 Aug 2026 05:24:44 +0000	[thread overview]
Message-ID: <20fad8c7654d543d7b1ca11e48a6486705ae559d.camel@mediatek.com> (raw)
In-Reply-To: <20260805174600.28064-1-lucid_duck@justthetip.ca>

On Wed, 2026-08-05 at 10:46 -0700, Devin Wittmayer wrote:
> 
> Tested this on an MT7927 here, against a reproduction I built on
> 2026-08-02 when I hit the same teardown. It fixes it.
> 
> mt7925e on 7.1.5, morrownr/mt76 at 217ee83d, which carries the
> unregister-deadlock change your Fixes tag names (openwrt
> 98c13eb564e5).
> Each cycle associates WPA2 at 2412 MHz, runs a 1400-byte ICMP flood,
> and
> rmmods with that traffic in flight, RX sampled off
> statistics/rx_packets
> immediately before the unload at 375 to 807 pps across both arms.
> Both
> arms built in the same directory, so only mt7925e and mt792x_lib
> differ
> between them.
> 
>   condition              stock                      patched
>   associated, 10 cycles  59-60 s, 19 timeouts each  0-1 s, none
>   idle, 3 cycles         9-10 s, 3 timeouts each    0 s, none
> 
> No warnings or call traces in any window on either arm.
> 
> The idle row is worth a line in the commit message: with nothing
> associated it still costs 9 to 10 seconds, so a bare rmmod does reach
> this, just small enough there to read as normal teardown.
> 
> Tested-by: Devin Wittmayer <lucid_duck@justthetip.ca>

I will update the commit message for v2 based on your suggestion.

Thanks,
Eason

      reply	other threads:[~2026-08-06  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  7:28 [PATCH v1] wifi: mt76: mt7925: Fix MCU command timeouts during module unload Eason Lai
2026-08-05 17:46 ` Devin Wittmayer
2026-08-06  5:24   ` Eason Lai (賴易聖) [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=20fad8c7654d543d7b1ca11e48a6486705ae559d.camel@mediatek.com \
    --to=eason.lai@mediatek.com \
    --cc=Deren.Wu@mediatek.com \
    --cc=Jb.Tsai@mediatek.com \
    --cc=Leon.Yen@mediatek.com \
    --cc=Litien.Chang@mediatek.com \
    --cc=Quan.Zhou@mediatek.com \
    --cc=Ryder.Lee@mediatek.com \
    --cc=Sean.Wang@mediatek.com \
    --cc=kun.wu@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox