Bug 216829

Summary:	mt7921e doens't complete connection since net-next merge
Product:	Drivers	Reporter:	Mike Lothian (mike)
Component:	network-wireless	Assignee:	drivers_network-wireless (drivers_network-wireless)
Status:	NEW ---
Severity:	normal	CC:	regressions
Priority:	P1
Hardware:	All
OS:	Linux
Kernel Version:	6.2-rc0	Subsystem:
Regression:	No	Bisected commit-id:

Description Mike Lothian 2022-12-21 12:47:12 UTC

I biesected it to the merge commit:

commit 7e68dd7d07a28faa2e6574dd6b9dbd90cdeaae91
Merge: 1ca06f1c1ace 7c4a6309e27f
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Tue Dec 13 15:47:48 2022 -0800

    Merge tag 'net-next-6.2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next


I mentioned this on #linux-wireless and they recommended I bisect the net-next tree

Unfortunately I can't find the net-next-6.2 tag on that tree

When there are network issues, the device is still enumerated and I can see Networks, it just doesn't complete the connection

Dec 21 12:12:53 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: enabling device (0000 -> 0002)
Dec 21 12:12:53 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: ASIC revision: 79610010
Dec 21 12:12:53 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20221109110918a
Dec 21 12:12:53 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20221109111005
Dec 21 12:13:02 axion.fireburn.co.uk NetworkManager[451]: <info>  [1671624782.7747] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:05:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)
Dec 21 12:13:14 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: Message 00020002 (seq 15) timeout
Dec 21 12:13:14 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20221109110918a
Dec 21 12:13:14 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20221109111005
Dec 21 12:13:23 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: Message 00020003 (seq 10) timeout
Dec 21 12:13:26 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: Message 00020002 (seq 11) timeout
Dec 21 12:13:26 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20221109110918a
Dec 21 12:13:26 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20221109111005

Which is probably related to those timeout messages

Is there anything else I can do to assist? I'll happily bisect further if you point me to a tree/tag I can bisect

Comment 1 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-12-22 07:12:19 UTC

[Just a wild guess from someone that is not a developer of the involved code]

Not sure, but maybe you are facing the same problem that is discussed here:
https://lore.kernel.org/all/CABXGCsMEnQd%3DgYKTd1knRsWuxCb%3DEtv5nAre%2BXJS_s5FgVteYA@mail.gmail.com/

Comment 2 Mike Lothian 2022-12-22 09:37:14 UTC

Unfortunately I can't get any of the patches to apply from that thread, should I be emailing in, or is bugzilla the way to go?

Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-12-22 09:57:28 UTC

(In reply to Mike Lothian from comment #2)
> Unfortunately I can't get any of the patches to apply from that thread,
> should I be emailing in, or is bugzilla the way to go?

Email is best (side note: as explained by https://docs.kernel.org/admin-guide/reporting-issues.html )