Archlinux freeze, mt7921e driver own failed Timeout for driver own

Firestar · 2025-06-04 06:02:06

Archlinux freeze when I was updating the system with paru -Syu, keyboard and mouse cannot do anything (such as switch TTY, my 87 key keyboard do not have the sysrq key)

Even the screen clock stuck at 11:59:07

I can only press the power button to reboot, and journalctl says:

[root@Archlinux firestar]# journalctl --since "11:58:00"
Jun 04 11:58:00 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:01 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:03 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:04 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:05 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:06 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:07 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:08 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:08 Archlinux kernel: mt7921e 0000:0b:00.0: chip reset failed
Jun 04 11:58:10 Archlinux wpa_supplicant[826]: wlp11s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jun 04 11:58:11 Archlinux kernel: mt7921e 0000:0b:00.0: Message 00020001 (seq 2) timeout
Jun 04 11:58:12 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:13 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:15 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:16 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:17 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:18 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:19 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:20 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:21 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:22 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:24 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:25 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:26 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:27 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:28 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:29 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:31 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:32 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:33 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:34 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:35 Archlinux wireplumber[1292]: wp-event-dispatcher: <WpAsyncEventHook:0x563cac3fdff0> failed: <WpSiSt>
Jun 04 11:58:35 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:35 Archlinux kernel: mt7921e 0000:0b:00.0: chip reset failed
Jun 04 11:58:38 Archlinux sudo[89414]: firestar : TTY=pts/4 ; PWD=/home/firestar ; USER=root ; COMMAND=/usr/bin/pac>
Jun 04 11:58:38 Archlinux sudo[89414]: pam_unix(sudo:session): session opened for user root(uid=0) by firestar(uid=>
Jun 04 11:58:38 Archlinux kernel: mt7921e 0000:0b:00.0: Message 00020001 (seq 4) timeout
Jun 04 11:58:39 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:40 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:41 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:42 Archlinux sudo[89414]: pam_unix(sudo:session): session closed for user root
Jun 04 11:58:42 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:44 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
Jun 04 11:58:45 Archlinux kernel: mt7921e 0000:0b:00.0: driver own failed
Jun 04 11:58:46 Archlinux kernel: mt7921e 0000:0b:00.0: Timeout for driver own
-- Boot 623df7b00eee4b67b4df157b4b31eb45 --

But I think this maybe has nothing to do with the crash, because I found that "the mt7921e 0000:0b:00.0: driver own failed" begins at least from yesterday (when I was still using the computer well and I did not know this)

Does anyone know how to fix this? This happens several times I think, about one per month

Operating System: Arch Linux 
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.14.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 9900X 12-Core Processor
Memory: 60.5 GiB of RAM
Graphics Processor 1: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
Graphics Processor 2: NVIDIA GeForce RTX 4060 Ti/PCIe/SSE2
Manufacturer: ASUS

Last edited by Firestar (2025-06-04 06:02:58)

Xephon · 2025-06-04 07:32:46

Do you dual boot with Windows?

If not, then it might be the same as
https://www.reddit.com/r/archlinux/comm … t/ml5tsee/

which was resolved like this
https://wiki.archlinux.org/title/Networ … ess#mt7921

seth · 2025-06-04 12:12:16

I can only press the power button to reboot, and journalctl says:

Nothing. The journal cannot be synced to disk if you reboot w/ the power button.
Avoid that at all costs, try to switch the TTY, ssh into the system, frenetically press ctrl+alt+del, *touch* the power button (do not hold it until the system powers off) or https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
You might also have trashed some packages since this happened during an update:

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

Processors: 24 × AMD Ryzen 9 9900X 12-Core Processor

https://wiki.archlinux.org/title/Ryzen#Troubleshooting

Firestar · 2025-06-04 14:34:32

Xephon wrote:

Do you dual boot with Windows?
If not, then it might be the same as
https://www.reddit.com/r/archlinux/comm … t/ml5tsee/
which was resolved like this
https://wiki.archlinux.org/title/Networ … ess#mt7921

NO, I dual boot with Windows

Last edited by Firestar (2025-06-05 06:21:36)

Xephon · 2025-06-04 15:07:27

Is fast startup disabled?

Firestar · 2025-06-05 06:22:33

Yes I disabled (and I must disable) fast startup

Also I seldom boot my windows, my recent boot is all archlinux

seth · 2025-06-05 06:40:47

Has the freeze re-occurred/is this a frequent problem or was that a one-off so far?

Firestar · 2025-06-05 06:45:55

> https://wiki.archlinux.org/title/Ryzen#Troubleshooting

What is the difference between system halt and Soft lock freezing? For system halt, this article also says that "unplugging is the only way out of this state"

I will first update the BIOS to see if this work

Firestar · 2025-06-05 17:20:51

seth wrote:

Has the freeze re-occurred/is this a frequent problem or was that a one-off so far?

I have bought this computer for about half a year and I come to this freeze about 3-5 times I think.

seth · 2025-06-05 18:53:45

On a softlock the kernel runs but gets stuck in a task, on a halt the kernel stops operating.
Since the discussed cause is a bad CPU, that's however academic, though likely to be addressed w/ d - but you might get to see soft lockups in the journal via watchdog errors. Halts can only be logged via the MCE.

Arch Linux

#1 2025-06-04 06:02:06

Archlinux freeze, mt7921e driver own failed Timeout for driver own

#2 2025-06-04 07:32:46

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#3 2025-06-04 12:12:16

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#4 2025-06-04 14:34:32

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#5 2025-06-04 15:07:27

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#6 2025-06-05 06:22:33

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#7 2025-06-05 06:40:47

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#8 2025-06-05 06:45:55

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#9 2025-06-05 17:20:51

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

#10 2025-06-05 18:53:45

Re: Archlinux freeze, mt7921e driver own failed Timeout for driver own

Board footer