public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: moosager90 <moosager90@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: mt7921e: repeated driver own failures cause hanging
Date: Fri, 02 Jan 2026 11:34:47 +0100	[thread overview]
Message-ID: <4870974.vXUDI8C0e8@fedora.fritz.box> (raw)

Hello,

There is an issue with mt7921e which causes repeated failures in chip resets,
bringing the network down and causing hanging on every command or action on the
system; the only workaround is to reboot. This is what the kernel output looks
like at those times:

mt7921e 0000:62:00.0: driver own failed
kernel: mt7921e 0000:62:00.0: Timeout for driver own
kernel: mt7921e 0000:62:00.0: driver own failed
kernel: mt7921e 0000:62:00.0: Timeout for driver own
kernel: mt7921e 0000:62:00.0: driver own failed
kernel: mt7921e 0000:62:00.0: Timeout for driver own
kernel: mt7921e 0000:62:00.0: driver own failed
kernel: mt7921e 0000:62:00.0: chip reset failed
kernel: mt7921e 0000:62:00.0: Timeout for driver own
kernel: Console: switching to colour frame buffer device 360x112
kernel: fbcon: Taking over console
kernel: mt7921e 0000:62:00.0: Message 00020001 (seq 1) timeout

I have observed the issue on many untainted kernels, and I have had it happen on
vanilla kernels not provided by my distro as well.

Mine and some other people's reports are available at [1]. More logs of the
issue on my system are in the attachments of my original report on the Red Hat
Bugzilla [2].

In the past, the issue was reported at [3], which resulted in a patch [4] that
only keeps the system running instead of panicking. This means the driver still
causes system hangs.

I still don't know the root cause of the issue and I would like to get to the
bottom of this; any help or guidance is appreciated. Crucially, I have not found
a way to reproduce the issue at will.

Best regards.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=220353
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2411854
[3] https://lore.kernel.org/linux-wireless/VE1PR04MB64945C660A81D38F290E4A4BE59F9@VE1PR04MB6494.eurprd04.prod.outlook.com/T/#u
[4] https://patchwork.kernel.org/project/linux-wireless/patch/727eb5ffd3c7c805245e512da150ecf0a7154020.1659452909.git.deren.wu@mediatek.com/




             reply	other threads:[~2026-01-02 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 10:34 moosager90 [this message]
2026-01-03  7:10 ` mt7921e: repeated driver own failures cause hanging Sean Wang
2026-01-04  8:19   ` moosager90
2026-04-09  1:41   ` Vinicius

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=4870974.vXUDI8C0e8@fedora.fritz.box \
    --to=moosager90@gmail.com \
    --cc=linux-wireless@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