[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
The only upstream bug that seems potentially related is https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024 . But that's more about ensuring that WPA auth has completed before starting the DHCP renewal, and it's not clear to me how blocking ICMP could avoid that problem. So it might not actually be related. The fix for that issue went into development version NM 1.39.9, so I may try building and trying an upstream version which includes it, to see if that fixes the problem (but I won't be able to try before next week at the earliest). ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1024 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1024 -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console:
[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
I have the same symptoms on Ubuntu 22.04.1 on a 12th-gen Framework laptop with Intel Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) device. Every time wpa-supplicant chooses to associate with a different BSSID (of the same SSID), the interface ends up being given a new IP address by the DHCP server (usually the sequentially next address). I don't have access to the DHCP server or its logs, but I tried the above suggested workaround of setting net.ipv4.icmp_echo_ignore_all=1 and this prevents the problem from occurring. So I expect the root cause is the same. (And as an aside, there is nothing in the client- side logs to indicate that ICMP pings could be in any way related; without this report it would have much more difficult to diagnose and work around the problem.) A different laptop running 18.04 on the same network is able to keep its IP address when roaming, so presumably this is due to a change in NetworkManager behaviour. The problem makes it difficult to work in an enterprise office environment (ie. moving around between desks and meeting rooms), because all TCP connections are lost when the IP address changes, which is especially impactful for ssh connections. -- 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface
[Kernel-packages] [Bug 1387221] Re: 14e4:4331 [MacBookPro10, 1] bcmwl-kernel-source >= 6.30.223.30+bdcom-0ubuntu1 fails to see 5GHz networks and is unstable on 2.5GHz
I recently had the need to compile this against Linux 4.13 (from current xenial hwe-edge). I was able to use patches 0023-add-support-for-Linux-4.11.patch and 0024 -add-support-for-Linux-4.12.patch from bcmwl_6.30.223.271+bdcom- 0ubuntu1~1.2 as the basis for creating 0014-add-support-for- linux-4.11.0.patch and 0015-add-support-for-linux-4.12.0.patch on top of Gerry's excellent bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu7 above. I'm now able to run bcmwl 6.20.155.1 in Linux 4.13 on this hardware to get reasonable wifi speed, without the random system lockups that 6.30.223.271 exhibited. The patches are attached, in case anyone has the same problem, or feels like packaging them properly (I sure don't; this is a temporary hack and I didn't even bother with DKMS: just compile, cp to new dir under /lib/modules/4.13.0-25-generic, depmod and modprobe). ** Attachment added: "0014-and-0015-patches-for-linux-4.11-and-4.12.tar" https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1387221/+attachment/5045948/+files/0014-and-0015-patches-for-linux-4.11-and-4.12.tar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1387221 Title: 14e4:4331 [MacBookPro10,1] bcmwl-kernel-source >= 6.30.223.30+bdcom- 0ubuntu1 fails to see 5GHz networks and is unstable on 2.5GHz Status in bcmwl package in Ubuntu: Triaged Bug description: 1) Utopic Unicorn 14.10 2) mzanetti@noneyet ~ $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.248+bdcom-0ubuntu1 Candidate: 6.30.223.248+bdcom-0ubuntu1 Version table: *** 6.30.223.248+bdcom-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ utopic/restricted amd64 Packages 100 /var/lib/dpkg/status lspci -vvnn | grep -A 9 Network 04:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331] (rev 02) Subsystem: Apple Inc. AirPort Extreme [106b:00ef] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: wl sudo dmidecode -s bios-version MBP101.88Z.00EE.B02.1208081132 sudo dmidecode -s bios-release-date 08/08/2012 sudo dmidecode -s system-version 1.0 sudo dmidecode -s baseboard-manufacturer Apple Inc. This is a MacBook Pro Retina 1st Generation 3) What is expected to happen is when one uses the bcmwl-kernel-source package in 14.10, it works on both 2.5Ghz and 5Ghz. 4) What happens instead is after upgrading to saucy or any newer release and installing bcmwl-kernel-source >=6.30.223.30+bdcom- 0ubuntu1 it fails to find any 5GHz networks and connections on 2.5GHz are unstable. Unfortunately, while b43 does detect the chip, it only uses 2.4GHz and it has very slow data rates and connection drops. WORKAROUND: This chip is working perfectly fine on 2.5GHz and 5GHz using version 6.20.155.1+bdcom-0ubuntu6 of the driver. Downgrading the machine to kernel 3.8.x and bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6 (both from raring) makes the chip work again. UPDATE: Up to kernel 3.13.0-23 a patched working package of bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6 here: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1387221/+attachment/4249077/+files/bcmwl-kernel-source_6.20.155.1%2Bbdcom-0ubuntu6_amd64.deb Currently there is no way to have utopic or vivid with an up to date kernel and properly working BCM4331 chip at the same time. Looking at the changelog its most likely caused by the update to the new upstream release in version 6.30.223.30+bdcom. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bcmwl-kernel-source 6.20.155.1+bdcom-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 29 15:26:09 2014 InstallationDate: Installed on 2012-11-10 (717 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64+mac (20120926) SourcePackage: bcmwl UpgradeStatus: Upgraded to utopic on 2013-10-22 (372 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1387221/+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
[Kernel-packages] [Bug 1637501] Re: Xenial update to v4.4.27 stable release
** Summary changed:
- Xenial update to v4.4.26 stable release
+ Xenial update to v4.4.27 stable release
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
- a minimally backported form of that patch. The v4.4.26 upstream stable
+ a minimally backported form of that patch. The v4.4.27 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
- The following patches from the v4.4.26 stable release shall be
+ The following patches from the v4.4.27 stable release shall be
applied:
serial: 8250_dw: Check the data->pclk when get apb_pclk
btrfs: assign error values to the correct bio structs
drivers: base: dma-mapping: page align the size when unmap_kernel_range
fuse: listxattr: verify xattr list
fuse: invalidate dir dentry after chmod
fuse: fix killing s[ug]id in setattr
i40e: avoid NULL pointer dereference and recursive errors on early PCI error
brcmfmac: fix memory leak in brcmf_fill_bss_param
ASoC: Intel: Atom: add a missing star in a memcpy call
reiserfs: Unlock superblock before calling reiserfs_quota_on_mount()
reiserfs: switch to generic_{get,set,remove}xattr()
async_pq_val: fix DMA memory leak
scsi: arcmsr: Simplify user_len checking
ext4: enforce online defrag restriction for encrypted files
ext4: reinforce check of i_dtime when clearing high fields of uid and gid
ext4: fix memory leak in ext4_insert_range()
ext4: allow DAX writeback for hole punch
ext4: release bh in make_indexed_dir
dlm: free workqueues after the connections
vfs: move permission checking into notify_change() for utimes(NULL)
cfq: fix starvation of asynchronous writes
Linux 4.4.27
--
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/1637501
Title:
Xenial update to v4.4.27 stable release
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Confirmed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The v4.4.27 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the v4.4.27 stable release shall be
applied:
serial: 8250_dw: Check the data->pclk when get apb_pclk
btrfs: assign error values to the correct bio structs
drivers: base: dma-mapping: page align the size when unmap_kernel_range
fuse: listxattr: verify xattr list
fuse: invalidate dir dentry after chmod
fuse: fix killing s[ug]id in setattr
i40e: avoid NULL pointer dereference and recursive errors on early PCI error
brcmfmac: fix memory leak in brcmf_fill_bss_param
ASoC: Intel: Atom: add a missing star in a memcpy call
reiserfs: Unlock superblock before calling reiserfs_quota_on_mount()
reiserfs: switch to generic_{get,set,remove}xattr()
async_pq_val: fix DMA memory leak
scsi: arcmsr: Simplify user_len checking
ext4: enforce online defrag restriction for encrypted files
ext4: reinforce check of i_dtime when clearing high fields of uid and gid
ext4: fix memory leak in ext4_insert_range()
ext4: allow DAX writeback for hole punch
ext4: release bh in make_indexed_dir
dlm: free workqueues after the connections
vfs: move permission checking into notify_change() for utimes(NULL)
cfq: fix starvation of asynchronous writes
Linux 4.4.27
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1637501/+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
