public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: silverducks <silverducks@altlinux.org>
To: Sean Wang <sean.wang@kernel.org>
Cc: linux-wireless@vger.kernel.org, nbd@nbd.name, lorenzo@kernel.org,
	ryder.lee@mediatek.com, shayne.chen@mediatek.com,
	sean.wang@mediatek.com, matthias.bgg@gmail.com,
	angelogioacchino.delregno@collabora.com,
	"moderated list:ARM/Mediatek SoC support"
	<linux-mediatek@lists.infradead.org>
Subject: Re: [BUG] mt7921e: Intermittent connection failure
Date: Tue, 14 Apr 2026 09:22:34 +0300	[thread overview]
Message-ID: <ddb70af0-b3b1-42c3-9459-ce41914c4d20@altlinux.org> (raw)
In-Reply-To: <651b9626-0c2c-4993-829a-3259141109dc@altlinux.org>

[-- Attachment #1: Type: text/plain, Size: 454 bytes --]

Greetings!

Update:
New version of the script is less consistent at reproducing the bug.
I've also noticed that on patched kernel it triggers timeout way
more often than older script. I've rolled back to the older one,
which relies on the NM autoconnect feature, though retained cleanup
changes.
I'm guessing direct nmcli command is often preventing NM from doing
whatever it is usually doing that triggers the error.
Script and reruns with it attached.

[-- Attachment #2: attachments.tar.gz --]
[-- Type: application/gzip, Size: 158890 bytes --]

  reply	other threads:[~2026-04-14  6:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 14:13 [BUG] mt7921e: Intermittent connection failure silverducks
2026-03-31  7:33 ` silverducks
2026-04-01 22:58   ` Sean Wang
2026-04-09 12:18     ` silverducks
2026-04-14  6:22       ` silverducks [this message]
2026-04-16 21:59         ` Sean Wang
2026-04-17 10:51           ` silverducks

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=ddb70af0-b3b1-42c3-9459-ce41914c4d20@altlinux.org \
    --to=silverducks@altlinux.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=nbd@nbd.name \
    --cc=ryder.lee@mediatek.com \
    --cc=sean.wang@kernel.org \
    --cc=sean.wang@mediatek.com \
    --cc=shayne.chen@mediatek.com \
    /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