Re: mt7921e: repeated driver own failures cause hanging

Sean Wang
2026-01-03T07:10:21Z

Hi moosager90,

Could you please share more details on how this issue can be
reproduced? For example, does it occur after suspend/resume, under
heavy traffic, or during normal runtime? Also, please confirm which
firmware version you are using.

It would be helpful to test with the latest linux-firmware version:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek?id=5cf85776762a544ad27c4447b61eaabb0d4716e7

As a debugging step, could you also try disabling PCIe ASPM and check
whether the issue still occurs?

Sean

On Fri, Jan 2, 2026 at 4:35 AM moosager90 <moosager90@gmail.com> wrote:
>
> 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/
>
>
>
>