Comment # 7 on bug 1201845 from Kostas Peletidis

(In reply to Takashi Iwai from comment #6)
> Does this happen after some operations, or does it appear at boot?
> 
> There has been issues with the power management, and a workaround was
> somehow to do cold boot from the complete power off (so that BIOS resets the
> chip state), and I wonder whether this is a similar case.

The bug happens during "normal use". As I mentioned earlier, I can see the chip
reset in older logs:

----
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
----

But in some cases, like today's, the chip reset doesn't seem to have the
desired effect (or maybe it is being probed too soon after the reset?) so we
end up with:

[11910.884024] mt7921e 0000:03:00.0: driver own failed
[11912.046411] mt7921e 0000:03:00.0: driver own failed
[11912.046429] mt7921e 0000:03:00.0: chip reset
[11913.218988] mt7921e 0000:03:00.0: driver own failed
[11913.327042] pcieport 0000:00:02.3: pciehp: Slot(0): Link Down
[11913.327054] pcieport 0000:00:02.3: pciehp: Slot(0): Card not present
[11913.362898] wlp3s0: deauthenticating from f8:5b:3b:0f:2b:9f by local choice
(Reason: 3=DEAUTH_LEAVING)
[11914.341792] mt7921e 0000:03:00.0: Timeout for driver own
[11915.546880] mt7921e 0000:03:00.0: driver own failed
[11915.546903] ------------[ cut here ]------------
[11915.546905] WARNING: CPU: 6 PID: 26340 at kernel/kthread.c:659
kthread_park+0x81/0x90