This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1922171 Title: Handle Intel Wifi firmware disconnection Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Won't Fix Bug description: [Impact] Intel Wifi firmware may crash when it's connected to B/G wireless. [Fix] There's a new "feature" that when firmware thinks there are too much noise in the current frequency, it will automatically disconnect wifi and expect software/OS to change channel/frequency and reconnect. Otherwise, firmware crashes. [Test] [ 2651.943142] wlp0s20f3: associate with 00:24:a5:b5:f8:93 (try 1/3) [ 2651.951043] wlp0s20f3: RX AssocResp from 00:24:a5:b5:f8:93 (capab=0x421 status=0 aid=1) [ 2651.962960] wlp0s20f3: associated [ 2651.966183] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready [ 2651.972582] wlp0s20f3: Driver requested disconnection from AP 00:24:a5:b5:f8:93 [ 2654.641627] wlp0s20f3: authenticate with 00:24:a5:b5:f8:93 Now it's "Driver requested disconnection" instead of firmware crash. [Where problems could occur] The first two patches on 80211 only provide new hook and don't bring any functional change. The third patch achieves the "feature" by removing cap IEEE80211_HE_PHY_CAP0_CHANNEL_WIDTH_SET_40MHZ_IN_2G. I am no expert on 80211, but if there's any AP that doesn't support 20MHZ for 2.4G, the reconnecting may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1922171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
