Public bug reported:

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

** Affects: hwe-next
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: linux-oem-5.10 (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu Focal)
     Importance: Undecided
         Status: Won't Fix

** Affects: linux-oem-5.10 (Ubuntu Focal)
     Importance: Medium
         Status: Confirmed

** Affects: linux (Ubuntu Hirsute)
     Importance: Medium
         Status: Confirmed

** Affects: linux-oem-5.10 (Ubuntu Hirsute)
     Importance: Undecided
         Status: Won't Fix


** Tags: oem-priority originate-from-1921340 stella

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.10 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Also affects: linux-oem-5.10 (Ubuntu Hirsute)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Hirsute)
       Status: New => Confirmed

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
       Status: New => Won't Fix

** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
       Status: New => Won't Fix

** Changed in: linux-oem-5.10 (Ubuntu Focal)
       Status: New => Confirmed

** Changed in: linux-oem-5.10 (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
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:
  Confirmed
Status in linux-oem-5.10 package in Ubuntu:
  New
Status in linux source package in Focal:
  Won't Fix
Status in linux-oem-5.10 source package in Focal:
  Confirmed
Status in linux source package in Hirsute:
  Confirmed
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

Reply via email to