Comment # 4 on bug 1201845 from Kostas Peletidis

It is not easy to reproduce this issue because I wasn't running any test. I was
just using the machine (it is my work laptop). From what I see here it happened
once more before. I have attached the dmesg output for both cases (one not
tainted, the other tainted probably because of vbox and friends).

It looks like there is a correlation between chip reset attempts that timed out
and the kernel warning. For example:

Chip reset OK, no warning
-------------------------
Jul 04 13:06:33 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 04 13:06:35 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 04 13:06:35 savra kernel: mt7921e 0000:03:00.0: chip reset
Jul 04 13:06:35 savra kernel: mt7921e 0000:03:00.0: HW/SW Version: 0x8a108a10,
Build Time: 20220311230842a
Jul 04 13:06:35 savra kernel: mt7921e 0000:03:00.0: WM Firmware Version:
____010000, Build Time: 20220311230931
Jul 04 13:06:36 savra kernel: wlp3s0: Driver requested disconnection from AP
f8:5b:3b:0f:2b:9f


Chip reset timeout, warning
---------------------------
Jul 08 08:47:17 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 08 08:47:18 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 08 08:47:18 savra kernel: mt7921e 0000:03:00.0: chip reset
Jul 08 08:47:19 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 08 08:47:19 savra kernel: pcieport 0000:00:02.3: pciehp: Slot(0): Link Down
Jul 08 08:47:19 savra kernel: pcieport 0000:00:02.3: pciehp: Slot(0): Card not
present
Jul 08 08:47:19 savra kernel: wlp3s0: deauthenticating from e6:5b:3b:0f:2b:9e
by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 08 08:47:20 savra kernel: mt7921e 0000:03:00.0: Timeout for driver own
Jul 08 08:47:21 savra kernel: mt7921e 0000:03:00.0: driver own failed
Jul 08 08:47:21 savra kernel: ------------[ cut here ]------------
Jul 08 08:47:21 savra kernel: WARNING: CPU: 7 PID: 113 at kernel/kthread.c:659
kthread_park+0x7b/0x90