Public bug reported:
SRU Justification
[Impact]
Systems using the Mediatek MT7925 Wi-Fi chip see frequent failures while
attempting to connect to an access point. Occasionally the first attempt
will succeed, but subsequent attempts fail consistently.
This issue is caused by the patch 816161051a03 ("wifi: mt76: mt7925:
Cleanup MLO settings post-disconnection"), which was included in 6.11
via stable updates.
The Noble 6.8 and older kernels do not include the breaking patch, and
Plucky 6.14 and newer kernels include the fix commit 0ebb60da8416
("wifi: mt76: mt7925: adjust rm BSS flow to prevent next connection
failure"). Thus, this only affects Oracular 6.11.
[Fix]
In the Oracular generic kernel, this was resolved by reverting 816161051a03
("wifi: mt76: mt7925: Cleanup MLO settings post-disconnection"):
https://bugs.launchpad.net/bugs/2111778.
However, the linux-nvidia-6.11 kernel has additional patches for this driver
that make the backport of 0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow
to prevent next connection failure") straightforward.
Thus, for linux-nvidia-6.11, we resolve the issue by backporting
0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow to prevent next
connection failure").
[Test]
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ ping -I wlP9s9 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.34 wlP9s9: 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=14.9 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=20.1 ms
^C
--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 14.884/17.470/20.057/2.586 ms
[Where problems could occur]
This change could result in issues with Wi-Fi connectivity on an MT7925
Wi-Fi chip, particularly after disconnecting from a network or when
utilizing MLO.
** Affects: linux-nvidia-6.11 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-nvidia-6.11 (Ubuntu Noble)
Importance: High
Assignee: Jacob Martin (jacobmartin)
Status: Fix Committed
** Also affects: linux-nvidia-6.11 (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-nvidia-6.11 (Ubuntu)
Status: New => Invalid
** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
Assignee: (unassigned) => Jacob Martin (jacobmartin)
** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux-nvidia-6.11 (Ubuntu Noble)
Status: New => In Progress
** Description changed:
SRU Justification
[Impact]
Systems using the Mediatek MT7925 Wi-Fi chip see frequent failures while
attempting to connect to an access point. Occasionally the first attempt
will succeed, but subsequent attempts fail consistently.
This issue is caused by the patch 816161051a03 ("wifi: mt76: mt7925:
Cleanup MLO settings post-disconnection"), which was included in 6.11
via stable updates.
The Noble 6.8 and older kernels do not include the breaking patch, and
Plucky 6.14 and newer kernels include the fix commit 0ebb60da8416
("wifi: mt76: mt7925: adjust rm BSS flow to prevent next connection
failure"). Thus, this only affects Oracular 6.11.
[Fix]
- In the Oracular generic kernel, this was resolved by reverting
- 816161051a03 ("wifi: mt76: mt7925: Cleanup MLO settings post-
- disconnection"), however the linux-nvidia-6.11 kernel has additional
- patches for this driver that make the backport of 0ebb60da8416 ("wifi:
- mt76: mt7925: adjust rm BSS flow to prevent next connection failure")
- straightforward.
+ In the Oracular generic kernel, this was resolved by reverting 816161051a03
("wifi: mt76: mt7925: Cleanup MLO settings post-disconnection"):
+ https://bugs.launchpad.net/bugs/2111778.
+ However, the linux-nvidia-6.11 kernel has additional patches for this driver
that make the backport of 0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow
to prevent next connection failure") straightforward.
Thus, for linux-nvidia-6.11, we resolve the issue by backporting
0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow to prevent next
connection failure").
[Test]
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ ping -I wlP9s9 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.34 wlP9s9: 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=14.9 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=20.1 ms
^C
--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 14.884/17.470/20.057/2.586 ms
[Where problems could occur]
This change could result in issues with Wi-Fi connectivity on an MT7925
Wi-Fi chip, particularly after disconnecting from a network or when
utilizing MLO.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2115812
Title:
mt7925 WiFi adapter often fails to connect to an access point
Status in linux-nvidia-6.11 package in Ubuntu:
Invalid
Status in linux-nvidia-6.11 source package in Noble:
Fix Committed
Bug description:
SRU Justification
[Impact]
Systems using the Mediatek MT7925 Wi-Fi chip see frequent failures
while attempting to connect to an access point. Occasionally the first
attempt will succeed, but subsequent attempts fail consistently.
This issue is caused by the patch 816161051a03 ("wifi: mt76: mt7925:
Cleanup MLO settings post-disconnection"), which was included in 6.11
via stable updates.
The Noble 6.8 and older kernels do not include the breaking patch, and
Plucky 6.14 and newer kernels include the fix commit 0ebb60da8416
("wifi: mt76: mt7925: adjust rm BSS flow to prevent next connection
failure"). Thus, this only affects Oracular 6.11.
[Fix]
In the Oracular generic kernel, this was resolved by reverting 816161051a03
("wifi: mt76: mt7925: Cleanup MLO settings post-disconnection"):
https://bugs.launchpad.net/bugs/2111778.
However, the linux-nvidia-6.11 kernel has additional patches for this driver
that make the backport of 0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow
to prevent next connection failure") straightforward.
Thus, for linux-nvidia-6.11, we resolve the issue by backporting
0ebb60da8416 ("wifi: mt76: mt7925: adjust rm BSS flow to prevent next
connection failure").
[Test]
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ sudo nmcli device wifi connect cert-be-open-tel-l10
Device 'wlP9s9' successfully activated with
'face54d7-aae0-4d75-b3e5-deda673ec4e5'.
$ sudo nmcli device wifi connect cert-ac-open-tel-l10
Device 'wlP9s9' successfully activated with
'dfcf7235-843f-4ac2-8be1-fd3d554e1857'.
$ ping -I wlP9s9 192.168.1.1
PING 192.168.1.1 (192.168.1.1) from 192.168.1.34 wlP9s9: 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=14.9 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=20.1 ms
^C
--- 192.168.1.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1003ms
rtt min/avg/max/mdev = 14.884/17.470/20.057/2.586 ms
[Where problems could occur]
This change could result in issues with Wi-Fi connectivity on an
MT7925 Wi-Fi chip, particularly after disconnecting from a network or
when utilizing MLO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2115812/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
