[Kernel-packages] [Bug 1929833] Re: bluez: meshctl missing
** Changed in: bluez (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Fix Released Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1929575] Re: [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all.
Hi, Can you give the latest mainline kernel a try to see if this issue exists in the upstream? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc7/ Please download and install amd64/build generic deb files (files marked A, see section "How do I install an upstream kernel?" in https://wiki.ubuntu.com/Kernel/MainlineBuilds) and reboot, let us know if it works and paste your "uname -a" command output in a terminal (ctrl+alt+t) here. Thanks -- 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/1929575 Title: [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all. Status in linux package in Ubuntu: New Bug description: I have Fujitsu Lifebook A514, I dual booted it with Windows 10 and Ubuntu. The trackpad works well in Windows 10 but it is not even moving in Ubuntu. I installed Pop! OS before Ubuntu and the trackpad was also not working on it. https://wiki.ubuntu.com/DebuggingTouchpadDetection I went to this link and trying to fix it now. Hope it works! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 20:27:44 2021 InstallationDate: Installed on 2021-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929575/+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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
I just tested this, but after hibernation, the same network errors occur as before. -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Hi, Can you give the latest mainline kernel a try to see if this issue exists in the upstream? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc7/ Please download and install amd64/build generic deb files (files marked A, see section "How do I install an upstream kernel?" in https://wiki.ubuntu.com/Kernel/MainlineBuilds) and reboot, let us know if it works and paste your "uname -a" command output in a terminal (ctrl+alt+t) here. Thanks ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Incomplete Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1931819] Re: [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices
Hi, Can you give the latest mainline kernel a try to see if this issue exists in the upstream? https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc7/ Please download and install amd64/build generic deb files (files marked A, see section "How do I install an upstream kernel?" in https://wiki.ubuntu.com/Kernel/MainlineBuilds) and reboot, let us know if it works and paste your "uname -a" command output in a terminal (ctrl+alt+t) here. Thanks -- 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/1931819 Title: [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices Status in linux package in Ubuntu: New Bug description: The touchpad is usually not recognized in ubuntu 20.04. A mouse works every time, but the touchpad works about 1 time out of every 4 reboots. r has never gotten it to work Laptop: IdeaPad-5-14ARE05 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 17:28:52 2021 InstallationDate: Installed on 2021-06-08 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931819/+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 1929575] Re: [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all.
** Summary changed: - The trackpad of the laptop is not working at all. + [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all. ** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux (Ubuntu) -- 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/1929575 Title: [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all. Status in linux package in Ubuntu: New Bug description: I have Fujitsu Lifebook A514, I dual booted it with Windows 10 and Ubuntu. The trackpad works well in Windows 10 but it is not even moving in Ubuntu. I installed Pop! OS before Ubuntu and the trackpad was also not working on it. https://wiki.ubuntu.com/DebuggingTouchpadDetection I went to this link and trying to fix it now. Hope it works! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 20:27:44 2021 InstallationDate: Installed on 2021-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929575/+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 1931546] Re: No ethernet with alx driver upon wake up in 5.11
The fix is already included since 5.11.0-14.15. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1931546 Title: No ethernet with alx driver upon wake up in 5.11 Status in linux package in Ubuntu: Fix Released Bug description: alx driver does not correctly restart the ethernet upon waking up. The bug (new behavior) has been introduced somewhere in the 5.10 kernel series (indirectly?) and got fixed for 5.12 and 5.13. However, no backport for 5.11 (Ubuntu 21.04) exists. The fix: https://github.com/gregkh/linux/commit/a4dcfbc4ee2218abd567d81d795082d8d4afcdf6#diff-641218b365d6949b9f2bbc730a547b421c127283cd0a5b5fd85c07cc6729bb81 Using 5.12 solves the issue due to an implemented fix: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.9/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931546/+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 1929575] [NEW] [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all.
You have been subscribed to a public bug: I have Fujitsu Lifebook A514, I dual booted it with Windows 10 and Ubuntu. The trackpad works well in Windows 10 but it is not even moving in Ubuntu. I installed Pop! OS before Ubuntu and the trackpad was also not working on it. https://wiki.ubuntu.com/DebuggingTouchpadDetection I went to this link and trying to fix it now. Hope it works! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 20:27:44 2021 InstallationDate: Installed on 2021-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Fujitsu Lifebook A514] The trackpad of the laptop is not working at all. https://bugs.launchpad.net/bugs/1929575 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1907886] Re: avinfo is missing
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1907886 Title: avinfo is missing Status in bluez package in Ubuntu: Fix Committed Bug description: The "avinfo" command line tools available in bluez/tools (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not available in the package. The package bluez-tools (https://packages.ubuntu.com/groovy/bluez- tools) seems to map another project external to bluez (https://github.com/khvzak/bluez-tools) and not the "tools" folder of bluez. "avinfo" is used for example in order to check which codecs are supported by a headphone set (see https://github.com/EHfive /pulseaudio-modules-bt/issues/31#issuecomment-462717049). Maybe have "bluez-tools" map the "tools" folder of bluez, and move the other project to another package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1907886/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
** Summary changed: - Notebook touchpad not working - does not appear on "cat /proc/bus/input/devices" + [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" ** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux (Ubuntu) -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: New Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1931819] Re: [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices
** Summary changed: - The touchpad isn't detected in cat /proc/bus/input/devices on my lenovo laptop + [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices ** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux (Ubuntu) -- 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/1931819 Title: [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices Status in linux package in Ubuntu: New Bug description: The touchpad is usually not recognized in ubuntu 20.04. A mouse works every time, but the touchpad works about 1 time out of every 4 reboots. r has never gotten it to work Laptop: IdeaPad-5-14ARE05 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 17:28:52 2021 InstallationDate: Installed on 2021-06-08 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931819/+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 1931715] [NEW] [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
You have been subscribed to a public bug: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1931715 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1931819] [NEW] [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices
You have been subscribed to a public bug: The touchpad is usually not recognized in ubuntu 20.04. A mouse works every time, but the touchpad works about 1 time out of every 4 reboots. r has never gotten it to work Laptop: IdeaPad-5-14ARE05 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 17:28:52 2021 InstallationDate: Installed on 2021-06-08 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Lenovo IdeaPad-5-14ARE05] The touchpad isn't detected in cat /proc/bus/input/devices https://bugs.launchpad.net/bugs/1931819 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: bluez (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1932022 Title: Can you add the btvirt executable to bluez-tests? Status in bluez package in Ubuntu: Fix Committed Bug description: See the Debian package: https://packages.debian.org/buster/i386/bluez- test-tools/filelist The Ubuntu package contains the same tools, except for btvirt. Would it be possible to add this? The buildlog shows that the btvirt executable is already built, but just not put into the *.deb package. Additions to be done to debian/bluez-tests.install: emulator/b1ee usr/bin emulator/btvirt usr/bin emulator/hfp usr/bin Having the btvirt tool available will make testing on CI systems a lot easier. References: https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82 https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1929833] Re: bluez: meshctl missing
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed ** Bug watch added: Debian Bug tracker #973579 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 ** Also affects: bluez (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1929833 Title: bluez: meshctl missing Status in bluez package in Ubuntu: Fix Committed Status in bluez package in Debian: Unknown Bug description: bluez has added a new tool for BT mesh handling. Debian has a new binary package: https://packages.debian.org/bullseye /bluez-meshd Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1933078] Re: BlueZ 5.59 release
** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: Fix Committed Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1901406] Re: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8
Can you please give OEM kernel a try? https://wiki.ubuntu.com/Kernel/OEMKernel#How_to_install_it.3F -- 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/1901406 Title: Lenovo T490 extremely show with Ubuntu 20.20 running kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from 20.04 to 20.20 on my laptop, the machine became extremely slow. After a days work I noticed that it never got any faster, and the machine was a lot colder than usual. Running cat /proc/cpuinfo and sudo cpupower frequency-info I noticed that the CPU was locked to 400Mhz. After some googling I found reports of people having trouble with CPU frequency governors on kernel 5.8. I tried to add intel_pstate=active to grub, but that didn't help. My short term workaround is to choose the old 5.4 kernel from 20.04. With this kernel everything is snappy again! Currently it's running at 3.2 Ghz with little load. CPU info from /proc/cpuinfo (with kernel 5.4): processor : 0 vendor_id : GenuineIntel cpu family: 6 model : 142 model name: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz stepping : 12 microcode : 0xd6 cpu MHz : 4551.153 cache size: 8192 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 4 apicid: 0 initial apicid: 0 fpu : yes fpu_exception : yes cpuid level : 22 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities bugs : spectre_v1 spectre_v2 spec_store_bypass swapgs taa itlb_multihit srbds bogomips : 4199.88 clflush size : 64 cache_alignment : 64 address sizes : 39 bits physical, 48 bits virtual power management: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hennikul 2402 F pulseaudio /dev/snd/pcmC0D0p: hennikul 2402 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-09-02 (418 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20N2CTO1WW Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=a36f1344-fd6c-40ef-a397-57f5a57594df ro intel_pstate=active quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190 Tags: groovy wayland-session Uname: Linux 5.8.0-25-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (2 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/19/2020 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET83W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N2CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN2IET83W(1.61):bd01/19/2020:br1.61:efr1.16:svnLENOVO:pn20N2CTO1WW:pvrThinkPadT490:rvnLENOVO:rn20N2CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490 dmi.product.name: 20N2CTO1WW dmi.product.sku: LENOVO_MT_20N2_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901406/+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 1910836] Re: Left Handed Mouse configuration switching to "Right" on reconnect V20.04
** Package changed: linux (Ubuntu) => gnome-settings-daemon (Ubuntu) -- 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/1910836 Title: Left Handed Mouse configuration switching to "Right" on reconnect V20.04 Status in gnome-settings-daemon package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Probably the Kernel What I expected: I expected the right mouse button to be the primary What happened instead: The primary button was the left button even though the mouse configuration showed it to be the right button. Re- selecting the right button is only a temporary work-a-round. This problem is constant and quite annoying and only started happening on a regular basis after I plugged in a USB game controller pad. It happened a few times before that but only after a software update and restart. Fixing it after a software update appeared to be permanent until the next update. After having my Logitech game pad controller F310 plugged in it happens constantly - even after just leaving the computer unattended for a while. If I unplug the game pad the problem persists. Perhaps that will give some developers a clue as to where the problem occurs. It may be a multilevel software thing. If not, reading my RANT below might elicit a clue as to what the software is doing wrong. I have seen other situations where when accessing a desktop from a left handed remote desktop, the buttons switch to right handed and after remoting to a third desktop it switches back to left handed etc like it is a toggle instead of a state. That is even more annoying if you need to cut and paste over 3 levels of button switch. We need an RFC to fix this in a standard way. I believe this bug is in many levels of Ubuntu from at least 19.x to the current 20.04.1 LTS based on what I have seen in the forums. If I could actually use my right hand - without poking my eyes out - I would definitely give up being left handed to avoid this issue. I do however prefer the pad to stay right handed and changing the mouse changes the pad in Ubuntu - they should be separately changeable. Perhaps the gamepad toggles the left right button thing - since it is set up as left handed as well. This problem also happens in many game consoles where you can change some things to left handed but not everything - in the software. In the 80s, mice had a switch on the bottom - left/right. Now the software determines right and left based on which user logs into the system. You have to use the mouse to login. That means it starts off right, then you login and then it switches to left. Incredibly stupid but only left-handers get this. I do however have a recommendation - to other left handers out there - since it is what I am going to do from now on - make the solution hardware. "Skip the software left handed thing and buy a true left handed mouse and controller or mod yours to switch". Don't rely on software for something so basic and critical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1910836/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Thanks Andy. I've added the fix to the 5.59 release (bug 1933078) and it works great. ** No longer affects: linux (Ubuntu) ** Also affects: gnome-settings-daemon (Ubuntu Impish) Importance: Undecided Status: Fix Released ** Also affects: bluez (Ubuntu Impish) Importance: High Assignee: Andy Chi (andch) Status: In Progress ** Also affects: gnome-settings-daemon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bluez (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: gnome-settings-daemon (Ubuntu Focal) ** No longer affects: gnome-settings-daemon (Ubuntu Hirsute) ** Changed in: bluez (Ubuntu Focal) Status: New => In Progress ** Changed in: bluez (Ubuntu Hirsute) Status: New => In Progress ** Changed in: bluez (Ubuntu Focal) Importance: Undecided => High ** Changed in: bluez (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: bluez (Ubuntu Focal) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Hirsute) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu Impish) Assignee: Andy Chi (andch) => Daniel van Vugt (vanvugt) ** Description changed: [Impact] - * On/off of Bluetooth in gnome-control-center will not work properly. - - * Devices are not refreshed in the list anymore. - - * The passed struct will depend on the length of the submitted read() and the -kernel version. - + On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. + [Test Plan] - * Open gnome-control-center and select Bluetooth + 1. Open gnome-control-center and select Bluetooth + 2. Turn off Bluetooth via UI + 3. Turn on Bluetooth via UI - * turn off Bluetooth via UI - - * turn on Bluetooth via UI + Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] - * If user install newer kernel such as 5.13, they may have this issue. + Since the fix involves the 'rfkill' logic it has the potential to affect + any Bluetooth or Wifi on/off setting. - * Tested on Intel AX201 and Intel 6235 with kernel version - 5.13.0-1003-oem. + [Other info] - * Upstream bug in gnome-bluetooth -https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + Upstream bug in gnome-bluetooth: + https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 - * Discussion in linux-bluetooth -https://marc.info/?t=16200475893=1=2 + Discussion in linux-bluetooth: + https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16
[Kernel-packages] [Bug 1933078] Re: BlueZ 5.59 release
** Attachment added: "bluez_5.59-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+attachment/5506368/+files/bluez_5.59-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Got it, thanks for sharing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933198] Re: [nvidia] Display mode after wake-up
Thanks. This is a recurring issue in mutter/gnome-shell so I don't think it's driver specific. To confirm if it is a mutter bug only, are you able to test some other desktop environment(s) that use Xorg? ** Package changed: nvidia-graphics-drivers-460 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1933198 Title: [nvidia] Display mode after wake-up Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 09:26:34 2021 DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. A] [1458:37d9] NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] InstallationDate: Installed on 2021-04-16 (66 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau:
[Kernel-packages] [Bug 1932528] Re: Touchpad stopped working after using as a tablet
** Description changed: Hi Everyone. So my touchpad has stopped working now out of the blue. I have a Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday. It was working perfectly, but it has stopped working as soon as I got into tablet mode. This laptop has the ability to fold its keyboard, so I did that and turn the laptop in 90 degrees (which the screen also turned due to the gyroscope). When we do this, its normal that the cursor disapears so we can you use only the touchscreen as a tablet, however when I turned back to a laptop the touchpad hasn't worked ag=0ain. I have rebooted the system, but still not signs of it. I have executed "cat /proc/bus/input/devices", but didn't find anything related to the touchpad, as the result shows below, so I think it's a kernel issue, right? Any thought how I could fix this? Thank you! I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=5986 Product=0535 Version=3653 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core
[Kernel-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 In a case like this it might have been easier to find just by searching for bluez bugs and ordering them newest-to-oldest. When you do that, bug 1926062 is near the top. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hi @Daniel, Yes, it has not been upstreamed yet. Linux-bluetooth does not reply the thread, maybe I'll have a try to send mail to them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Hi @Daniel, Sorry for that, I tried to search for existing bug, I guess I'm not using the right words to search. Will be careful next time or ask in mattermost channel first. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Description changed: + [Impact] + + * On/off of Bluetooth in gnome-control-center will not work properly. + + * Devices are not refreshed in the list anymore. + + * The passed struct will depend on the length of the submitted read() and the +kernel version. + + [Test Plan] + + * Open gnome-control-center and select Bluetooth + + * turn off Bluetooth via UI + + * turn on Bluetooth via UI + + [Where problems could occur] + + * If user install newer kernel such as 5.13, they may have this issue. + + * Tested on Intel AX201 and Intel 6235 with kernel version + 5.13.0-1003-oem. + + * Upstream bug in gnome-bluetooth +https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 + + * Discussion in linux-bluetooth +https://marc.info/?t=16200475893=1=2 + + [Original bug report] + When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS - Bluetooth: hci0: HCI reset during shutdown failed + Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@Georgi, would you please try the last drm-tip(amd64)? https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) [ 250.778336] xhci_hcd :0b:00.0: Controller not ready at resume -19 [ 250.778340] xhci_hcd :0b:00.0: PCI
[Kernel-packages] [Bug 1933078] Re: BlueZ 5.59 release
On hold again since there's also a fix for bug 1926062 coming. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933078 Title: BlueZ 5.59 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.59 to impish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933259] Re: Bluetooth not working/can't turn it on
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 ** This bug has been marked a duplicate of bug 1926062 [hirsute/impish] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
The bluez fix has not been upstreamed yet. Is that pending? ** Package changed: gnome-control-center (Ubuntu) => gnome-settings- daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Invalid => Fix Released ** Tags added: fixed-in-gsd-3.38.2 fixed-in-gsd-40.0.1 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues #38 https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 ** Also affects: gnome-bluetooth via https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Importance: Unknown Status: Unknown ** Changed in: bluez (Ubuntu) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: bluez (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in bluez package in Ubuntu: In Progress Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
*** This bug is a duplicate of bug 1926062 *** https://bugs.launchpad.net/bugs/1926062 Since the fix isn't in impish yet and that has to come first, we have time to clean up the duplicate bugs. Please use bug 1926062 instead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center
Thanks for the fix, but please be more careful to check for existing bugs (bug 1926062) in future rather than opening new ones. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933221 Title: Blutooth on/off does not work properly from gnome-control-center Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Bug description: [Impact] * On/off of Bluetooth in gnome-control-center will not work properly. * Devices are not refreshed in the list anymore. * The passed struct will depend on the length of the submitted read() and the kernel version. [Test Plan] * Open gnome-control-center and select Bluetooth * turn off Bluetooth via UI * turn on Bluetooth via UI [Where problems could occur] * If user install newer kernel such as 5.13, they may have this issue. * Tested on Intel AX201 and Intel 6235 with kernel version 5.13.0-1003-oem. * Upstream bug in gnome-bluetooth https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 * Discussion in linux-bluetooth https://marc.info/?t=16200475893=1=2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933274] Re: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"
** Tags added: patch -- 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/1933274 Title: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)" Status in linux package in Ubuntu: New Bug description: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
Hi Evan, The SRU cycle has completed, and all kernels containing the Raid10 block discard performance patches have now been released to -updates. Note that the versions are different than the kernels in -proposed, due to the kernel team needing to do a last minute respin to fix two sets of CVEs, one for broadcom wifi chipsets and the other for bpf, hence the kernels being released a day later than usual. The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic The HWE equivalents have also been released to -updates. You may now install these kernels to your systems and enjoy fast block discard for your Raid10 arrays. Thanks, Matthew -- 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/1896578 Title: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1896578 [Impact] Block discard is very slow on Raid10, which causes common use cases which invoke block discard, such as mkfs and fstrim operations, to take a very long time. For example, on a i3.8xlarge instance on AWS, which has 4x 1.9TB NVMe devices which support block discard, a mkfs.xfs operation on Raid 10 takes between 8 to 11 minutes, where the same mkfs.xfs operation on Raid 0, takes 4 seconds. The bigger the devices, the longer it takes. The cause is that Raid10 currently uses a 512k chunk size, and uses this for the discard_max_bytes value. If we need to discard 1.9TB, the kernel splits the request into millions of 512k bio requests, even if the underlying device supports larger requests. For example, the NVMe devices on i3.8xlarge support 2.2TB of discard at once: $ cat /sys/block/nvme0n1/queue/discard_max_bytes 2199023255040 $ cat /sys/block/nvme0n1/queue/discard_max_hw_bytes 2199023255040 Where the Raid10 md device only supports 512k: $ cat /sys/block/md0/queue/discard_max_bytes 524288 $ cat /sys/block/md0/queue/discard_max_hw_bytes 524288 If we perform a mkfs.xfs operation on the /dev/md array, it takes over 11 minutes and if we examine the stack, it is stuck in blkdev_issue_discard() $ sudo cat /proc/1626/stack [<0>] wait_barrier+0x14c/0x230 [raid10] [<0>] regular_request_wait+0x39/0x150 [raid10] [<0>] raid10_write_request+0x11e/0x850 [raid10] [<0>] raid10_make_request+0xd7/0x150 [raid10] [<0>] md_handle_request+0x123/0x1a0 [<0>] md_submit_bio+0xda/0x120 [<0>] __submit_bio_noacct+0xde/0x320 [<0>] submit_bio_noacct+0x4d/0x90 [<0>] submit_bio+0x4f/0x1b0 [<0>] __blkdev_issue_discard+0x154/0x290 [<0>] blkdev_issue_discard+0x5d/0xc0 [<0>] blk_ioctl_discard+0xc4/0x110 [<0>] blkdev_common_ioctl+0x56c/0x840 [<0>] blkdev_ioctl+0xeb/0x270 [<0>] block_ioctl+0x3d/0x50 [<0>] __x64_sys_ioctl+0x91/0xc0 [<0>] do_syscall_64+0x38/0x90 [<0>] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] Xiao Ni has developed a patchset which resolves the block discard performance problems. These commits have now landed in 5.13-rc1. commit cf78408f937a67f59f5e90ee8e6cadeed7c128a8 Author: Xiao Ni Date: Thu Feb 4 15:50:43 2021 +0800 Subject: md: add md_submit_discard_bio() for submitting discard bio Link: https://github.com/torvalds/linux/commit/cf78408f937a67f59f5e90ee8e6cadeed7c128a8 commit c2968285925adb97b9aa4ede94c1f1ab61ce0925 Author: Xiao Ni Date: Thu Feb 4 15:50:44 2021 +0800 Subject: md/raid10: extend r10bio devs to raid disks Link: https://github.com/torvalds/linux/commit/c2968285925adb97b9aa4ede94c1f1ab61ce0925 commit f2e7e269a7525317752d472bb48a549780e87d22 Author: Xiao Ni Date: Thu Feb 4 15:50:45 2021 +0800 Subject: md/raid10: pull the code that wait for blocked dev into one function Link: https://github.com/torvalds/linux/commit/f2e7e269a7525317752d472bb48a549780e87d22 commit d30588b2731fb01e1616cf16c3fe79a1443e29aa Author: Xiao Ni Date: Thu Feb 4 15:50:46 2021 +0800 Subject: md/raid10: improve raid10 discard request Link: https://github.com/torvalds/linux/commit/d30588b2731fb01e1616cf16c3fe79a1443e29aa commit 254c271da0712ea8914f187588e0f81f7678ee2f Author: Xiao Ni Date: Thu Feb 4 15:50:47 2021 +0800 Subject: md/raid10: improve discard request for far layout Link: https://github.com/torvalds/linux/commit/254c271da0712ea8914f187588e0f81f7678ee2f There is also an additional commit which is required, and was merged after "md/raid10: improve raid10 discard request" was merged. The following commit enables Radid10 to use
[Kernel-packages] [Bug 1907262] Re: raid10: discard leads to corrupted file system
Hi Thimo, The SRU cycle has completed, and all kernels containing the Raid10 block discard performance patches have now been released to -updates. Note that the versions are different than the kernels in -proposed, due to the kernel team needing to do a last minute respin to fix two sets of CVEs, one for broadcom wifi chipsets and the other for bpf, hence the kernels being released a day later than usual. The released kernels are: Hirsute: 5.11.0-22-generic Groovy: 5.8.0-59-generic Focal: 5.4.0-77-generic Bionic: 4.15.0-147-generic The HWE equivalents have also been released to -updates. You may now install these kernels to your systems and enjoy fast block discard for your Raid10 arrays. All of our testing has concluded that these patches are stable, but if you run into any issues whatsoever as you roll this out to more systems, please let us know, and we will investigate accordingly. I wish you a trouble free rollout of these kernels to your systems. Thanks, Matthew -- 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/1907262 Title: raid10: discard leads to corrupted file system Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: Seems to be closely related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578 After updating the Ubuntu 18.04 kernel from 4.15.0-124 to 4.15.0-126 the fstrim command triggered by fstrim.timer causes a severe number of mismatches between two RAID10 component devices. This bug affects several machines in our company with different HW configurations (All using ECC RAM). Both, NVMe and SATA SSDs are affected. How to reproduce: - Create a RAID10 LVM and filesystem on two SSDs mdadm -C -v -l10 -n2 -N "lv-raid" -R /dev/md0 /dev/nvme0n1p2 /dev/nvme1n1p2 pvcreate -ff -y /dev/md0 vgcreate -f -y VolGroup /dev/md0 lvcreate -n root-L 100G -ay -y VolGroup mkfs.ext4 /dev/VolGroup/root mount /dev/VolGroup/root /mnt - Write some data, sync and delete it dd if=/dev/zero of=/mnt/data.raw bs=4K count=1M sync rm /mnt/data.raw - Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (should be 0): cat /sys/block/md0/md/mismatch_cnt - Trigger the bug fstrim /mnt - Re-Check the RAID device echo check >/sys/block/md0/md/sync_action - After finishing (see /proc/mdstat), check the mismatch_cnt (probably in the range of N*1): cat /sys/block/md0/md/mismatch_cnt After investigating this issue on several machines it *seems* that the first drive does the trim correctly while the second one goes wild. At least the number and severity of errors found by a USB stick live session fsck.ext4 suggests this. To perform the single drive evaluation the RAID10 was started using a single drive at once: mdadm --assemble /dev/md127 /dev/nvme0n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root vgchange -a n /dev/VolGroup mdadm --stop /dev/md127 mdadm --assemble /dev/md127 /dev/nvme1n1p2 mdadm --run /dev/md127 fsck.ext4 -n -f /dev/VolGroup/root When starting these fscks without -n, on the first device it seems the directory structure is OK while on the second device there is only the lost+found folder left. Side-note: Another machine using HWE kernel 5.4.0-56 (after using -53 before) seems to have a quite similar issue. Unfortunately the risk/regression assessment in the aforementioned bug is not complete: the workaround only mitigates the issues during FS creation. This bug on the other hand is triggered by a weekly service (fstrim) causing severe file system corruption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262/+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
Re: [Kernel-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em quinta-feira, 17 de junho de 2021, às 00:45:30 -03, Thiago Jung Bauermann escreveu: > > > I think it may be related to a change in mesa. Specifically mesa > > > commit > > > 820dec3f7c7. For more info see > > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 > > > > I’ll run with Mario’s build of Mesa with that patch backported. > > Thanks, Mario! > > I’m running with the Mesa build from Mario’s PPA now. If I don’t see any > issue within two weeks, I think it will be possible to say that the bug > is gone, or at least much harder to hit. > > I can’t use my reproducer in this case, because I can’t change the Mesa > version inside the flatpak image. I just had this bug happen again spontaneously, while running with Mesa from Mario’s PPA. So this bug isn’t fixed by the patch mentioned by Alex. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" Status in amd: New Status in linux-firmware package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Confirmed Bug description: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1933274] [NEW] TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)"
Public bug reported: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Patch added: "i915-load-dram-from-pcode.patch" https://bugs.launchpad.net/bugs/1933274/+attachment/5506308/+files/i915-load-dram-from-pcode.patch -- 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/1933274 Title: TGL-H skl_dram_get_dimm_info crashes with "Missing case (val == 65535)" Status in linux package in Ubuntu: New Bug description: Tracing this back, I found the current Ubuntu 5.11 kernel has incorrect offsets for some platforms (TGL-H and ADL). I created an upstream bug at https://gitlab.freedesktop.org/drm/intel/-/issues/3662 and was directed to a commit, 5d0c938ec9cc, that ought to fix this issue. See the attached patch file for this commit applied to the current Ubuntu 5.11 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933274/+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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Can you please try to Hibernate your laptop to disk, then start it again and test the LAN connection? On my Fujitsu S7311 with I219-LM with Ubuntu kernel 5.10.0-18-generic hibernating running OS to disk and then turning it on makes LAN working as expected without any error (no special kernel parameters). Very strange behaviour. -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware
Hello koba, or anyone else affected, Accepted linux-firmware into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.197.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+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 1933268] [NEW] net kselftest failures in the tls bidir test case
Public bug reported: [Impact] The tls bidir test from the network kselftests fails with the ChaCha cipher: # RUN tls.12_chacha.bidir ... # tls.c:845:bidir:Expected ret (-1) == 0 (0) # bidir: Test terminated by assertion # FAIL tls.12_chacha.bidir This is a problem with the test. The test fixture setup configures tls in one direction on the test socket pair according to the cipher being tested. The test case configures tls in the other direction, however it always configures for GCM regardless of the cipher being tested. When the test cipher is ChaCha the setsockopt() calls fail as the cipher is required to be the same in both directions. [Test Plan] Run the tls test from the net kselftests and confirm that the bidir test now passes when the test cipher is ChaCha. [Where problems could occur] This is a fix for a test case and should have no user impact. A serious problem in the test case might cause passing test cases to fail or prevent subsequent test cases from running. Any such issues should be caught during testing in -proposed before releasing kernels to users. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Fix Committed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1933268 Title: net kselftest failures in the tls bidir test case Status in linux package in Ubuntu: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] The tls bidir test from the network kselftests fails with the ChaCha cipher: # RUN tls.12_chacha.bidir ... # tls.c:845:bidir:Expected ret (-1) == 0 (0) # bidir: Test terminated by assertion # FAIL tls.12_chacha.bidir This is a problem with the test. The test fixture setup configures tls in one direction on the test socket pair according to the cipher being tested. The test case configures tls in the other direction, however it always configures for GCM regardless of the cipher being tested. When the test cipher is ChaCha the setsockopt() calls fail as the cipher is required to be the same in both directions. [Test Plan] Run the tls test from the net kselftests and confirm that the bidir test now passes when the test cipher is ChaCha. [Where problems could occur] This is a fix for a test case and should have no user impact. A serious problem in the test case might cause passing test cases to fail or prevent subsequent test cases from running. Any such issues should be caught during testing in -proposed before releasing kernels to users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933268/+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 1931546] Re: No ethernet with alx driver upon wake up in 5.11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1931546 Title: No ethernet with alx driver upon wake up in 5.11 Status in linux package in Ubuntu: Confirmed Bug description: alx driver does not correctly restart the ethernet upon waking up. The bug (new behavior) has been introduced somewhere in the 5.10 kernel series (indirectly?) and got fixed for 5.12 and 5.13. However, no backport for 5.11 (Ubuntu 21.04) exists. The fix: https://github.com/gregkh/linux/commit/a4dcfbc4ee2218abd567d81d795082d8d4afcdf6#diff-641218b365d6949b9f2bbc730a547b421c127283cd0a5b5fd85c07cc6729bb81 Using 5.12 solves the issue due to an implemented fix: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.9/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931546/+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 1933262] Re: Groovy update: upstream stable patchset 2021-06-22
** 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 following upstream -stable patches should be included in the Ubuntu kernel: - -upstream stable patchset 2021-06-22 -from git://git.kernel.org/ + 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 following upstream + stable patches should be included in the Ubuntu kernel: + + upstream stable patchset 2021-06-22 + + Ported from the following upstream stable releases: + v5.4.124, v5.10.42 + + from git://git.kernel.org/ + + ALSA: hda/realtek: Headphone volume is controlled by Front mixer + ALSA: usb-audio: scarlett2: Fix device hang with ehci-pci + ALSA: usb-audio: scarlett2: Improve driver startup messages + cifs: set server->cipher_type to AES-128-CCM for SMB3.0 + NFSv4: Fix a NULL pointer dereference in pnfs_mark_matching_lsegs_return() + iommu/vt-d: Fix sysfs leak in alloc_iommu() + perf intel-pt: Fix sample instruction bytes + perf intel-pt: Fix transaction abort handling + perf scripts python: exported-sql-viewer.py: Fix copy to clipboard from Top Calls by elapsed Time report + perf scripts python: exported-sql-viewer.py: Fix Array TypeError + perf scripts python: exported-sql-viewer.py: Fix warning display + proc: Check /proc/$pid/attr/ writes against file opener + net: hso: fix control-request directions + ath10k: Validate first subframe of A-MSDU before processing the list + dm snapshot: properly fix a crash when an origin has no snapshots + drm/amdgpu/vcn1: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.0: add cancel_delayed_work_sync before power gate + drm/amdgpu/vcn2.5: add cancel_delayed_work_sync before power gate + selftests/gpio: Use TEST_GEN_PROGS_EXTENDED + selftests/gpio: Move include of lib.mk up + selftests/gpio: Fix build when source tree is read only + kgdb: fix gcc-11 warnings harder + Documentation: seccomp: Fix user notification documentation + serial: core: fix suspicious security_locked_down() call + misc/uss720: fix memory leak in uss720_probe + thunderbolt: dma_port: Fix NVM read buffer bounds and offset issue + mei: request autosuspend after sending rx flow control + staging: iio: cdc: ad7746: avoid overwrite of num_channels + iio: gyro: fxas21002c: balance runtime power in error path + iio: adc: ad7768-1: Fix too small buffer passed to iio_push_to_buffers_with_timestamp() + iio: adc: ad7124: Fix missbalanced regulator enable / disable on error. + iio: adc: ad7124: Fix potential overflow due to non sequential channel numbers + iio: adc: ad7793: Add missing error code in ad7793_setup() + serial: 8250_pci: Add support for new HPE serial device + serial: 8250_pci: handle FL_NOIRQ board flag + USB: trancevibrator: fix control-request direction + USB: usbfs: Don't WARN about excessively large memory allocations + serial: tegra: Fix a mask operation that is always true + serial: sh-sci: Fix off-by-one error in FIFO threshold register setting + serial: rp2: use 'request_firmware' instead of 'request_firmware_nowait' + USB: serial: ti_usb_3410_5052: add startech.com device id + USB: serial: option: add Telit LE910-S1 compositions 0x7010, 0x7011 + USB: serial: ftdi_sio: add IDs for IDS GmbH Products + USB: serial: pl2303: add device id for ADLINK ND-6530 GC + thermal/drivers/intel: Initialize RW trip to THERMAL_TEMP_INVALID + usb: dwc3: gadget: Properly track pending and queued SG + usb: gadget: udc: renesas_usb3: Fix a race in usb3_start_pipen() + net: usb: fix memory leak in smsc75xx_bind + Bluetooth: cmtp: fix file refcount when cmtp_attach_device fails + fs/nfs: Use fatal_signal_pending instead of signal_pending + NFS: fix an incorrect limit in filelayout_decode_layout() + NFS: Fix an Oopsable condition in __nfs_pageio_add_request() + NFS: Don't corrupt the value of pg_bytes_written in nfs_do_recoalesce() + NFSv4: Fix v4.0/v4.1 SEEK_DATA return -ENOTSUPP when set NFS_V4_2 config + drm/meson: fix shutdown crash when component not probed + net/mlx5e: Fix multipath lag activation + net/mlx5e: Fix nullptr in add_vlan_push_action() + net/mlx4: Fix EEPROM dump support + Revert "net:tipc: Fix a double free in tipc_sk_mcast_rcv" + tipc: wait and exit until all work queues are done + tipc: skb_linearize the head skb when reassembling msgs + spi:
[Kernel-packages] [Bug 1929870] Re: AMD desktop often fails to resume from deep suspend
Unclear what changed but I haven't been able to reproduce this issue in a week or so. My computer is now running: 5.11.0-18-generic When I reported the bug it was using: 5.11.0-17-generic -- 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/1929870 Title: AMD desktop often fails to resume from deep suspend Status in linux package in Ubuntu: Confirmed Bug description: Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU Approximately one in every 4 attempts to resume from a deep suspend fails. When the issue occurs the fans spin up but the monitor displays no output and input devices do not function, the system appears frozen and must be restarted using power or reset buttons. I have tried using different dNVIDIA isplay drivers (proprietary as well as open source) as well as trying an AMD Radeon HD 6450 GPU instead of the NVIDIA GPU. I have tried the following kernel parameters: processor.max_cstate=1 rcu_nocbs=0-23 I have updated the BIOS several times. I had similar problems with Ubuntu 20.10. I have enabled some additional kernel logging with initcall_debug. Fairly consistently the last message printed in the kernel log is from the ethernet driver: May 27 09:19:43 jacob-tm kernel: [ 230.878348] OOM killer enabled. May 27 09:19:43 jacob-tm kernel: [ 230.878349] Restarting tasks ... May 27 09:19:43 jacob-tm kernel: [ 230.879023] usb 5-2.3: USB disconnect, device number 4 May 27 09:19:43 jacob-tm kernel: [ 230.879026] usb 5-2.3.1: USB disconnect, device number 5 May 27 09:19:43 jacob-tm kernel: [ 230.879285] done. May 27 09:19:43 jacob-tm kernel: [ 230.879318] PM: suspend exit May 27 09:19:43 jacob-tm kernel: [ 230.880916] rfkill: input handler enabled May 27 09:19:43 jacob-tm kernel: [ 230.955727] kauditd_printk_skb: 1 callbacks suppressed May 27 09:19:43 jacob-tm kernel: [ 230.955731] audit: type=1400 audit(1622132383.424:64): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cupsd" pid=4418 comm="cupsd" capability=12 capname="net_admin" May 27 09:19:43 jacob-tm kernel: [ 230.966192] audit: type=1400 audit(1622132383.432:65): apparmor="DENIED" operation="capab le" profile="/usr/sbin/cups-browsed" pid=4429 comm="cups-browsed" capability=23 capname="sys_nice" May 27 09:19:43 jacob-tm kernel: [ 231.120385] rfkill: input handler disabled May 27 09:19:43 jacob-tm kernel: [ 231.225924] usb 5-2.3.2: USB disconnect, device number 6 May 27 09:19:43 jacob-tm kernel: [ 231.481893] usb 5-2.3.5: USB disconnect, device number 7 May 27 09:19:47 jacob-tm kernel: [ 235.009576] igb :05:00.0 enp5s0: igb: enp5s0 NIC Link is Up 1000 Mbps Full Duplex, Fl ow Control: RX/TX May 27 09:19:47 jacob-tm kernel: [ 235.009913] IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-17-generic 5.11.0-17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2024 F pulseaudio /dev/snd/controlC0: jacob 2024 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu May 27 14:12:33 2021 InstallationDate: Installed on 2020-10-28 (211 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash initcall_debug processor.max_cstate=1 rcu_nocbs=0-23 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-14 (13 days ago) dmi.bios.date: 05/08/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3604 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1933198] Re: [nvidia] Display mode after wake-up
You seem to be right : the hdmi monitor seems to be reset... This didn't happen a few weeks ago (maybe 21.04 update). Here is the output of xrandr : ### Initial xrandr result, when no problem is present (except that the hdmi monitor refresh rate should be 144Hz but is detected at 120, maybe this is related) ### Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 HDMI-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00 + 120.00* 119.88 100.0059.9450.0023.98 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 59.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 544mm x 303mm 1920x1080 60.00 + 143.98* 119.9899.9359.9450.00 1680x1050 59.95 1600x1200 60.00 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 59.9450.00 1152x720 59.97 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) ### After incorrect waking-up : HDMI monitor is back to 60hz and mirror mode ### Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 120.00 119.88 100.0059.9450.0023.98 1680x1050 59.95 1600x1200 60.00 1600x900 60.00 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 59.9450.00 1152x864 75.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 544mm x 303mm 1920x1080 60.00 + 143.98* 119.9899.9359.9450.00 1680x1050 59.95 1600x1200 60.00 1440x900 74.9859.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 59.9450.00 1152x720 59.97 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1933198 Title: [nvidia] Display mode after wake-up Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
I just want to say that after 2 years I remembered I had an SSD with different brand tham Samsung, a Kingston one. I installed it on my razer and it worked perfectly for days, I did several SSD stress tests and no errors. The error is defintely with Samsung AND linux. And it's not a faulty SSD because it happens on both of my samsung SSDs. It does not happen on Windows, neither Qubes, with any SSD. I tested the latest Ubuntu 21.04 and the problem still happens on Samsung SSDs right on the installation screen. Anyways I'm not even using this computer anymore, I bought a Dell XPS 13, but the error persists and it's either Samsung's or Linux fault. Probably Samsung since other brands work ok with Samsung. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk-
[Kernel-packages] [Bug 1845418] Re: Wifi is Slow
** Changed in: ubuntu-certification Status: New => Invalid -- 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/1845418 Title: Wifi is Slow Status in Ubuntu-Certification: Invalid Status in linux package in Ubuntu: Incomplete Bug description: We are facing Issues with the Wifi Connectivity,Lan is working fine and the wifi is too slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-certification/+bug/1845418/+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 1931896] Re: Hirsute update: upstream stable patchset 2021-06-14
Followup: the patch "linux/bits.h: fix compilation error with GENMASK" has been
omitted
(reference https://bugs.launchpad.net/bugs/1932585)
--
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/1931896
Title:
Hirsute update: upstream stable patchset 2021-06-14
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Hirsute:
In Progress
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 following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2021-06-14
Ported from the following upstream stable releases:
v5.10.39, v5.12.6
v5.10.40, v5.12.7
v5.10.41, v5.12.8
v5.10.42, v5.12.9
from git://git.kernel.org/
x86/msr: Fix wr/rdmsr_safe_regs_on_cpu() prototypes
drm/i915/display: fix compiler warning about array overrun
airo: work around stack usage warning
kgdb: fix gcc-11 warning on indentation
usb: sl811-hcd: improve misleading indentation
isdn: capi: fix mismatched prototypes
virtio_net: Do not pull payload in skb->head
PCI: thunder: Fix compile testing
dmaengine: dw-edma: Fix crash on loading/unloading driver
ARM: 9066/1: ftrace: pause/unpause function graph tracer in cpu_suspend()
ACPI / hotplug / PCI: Fix reference count leak in enable_slot()
PCI: tegra: Fix runtime PM imbalance in pex_ep_event_pex_rst_deassert()
Input: elants_i2c - do not bind to i2c-hid compatible ACPI instantiated
devices
Input: silead - add workaround for x86 BIOS-es which bring the chip up in a
stuck state
NFS: NFS_INO_REVAL_PAGECACHE should mark the change attribute invalid
um: Mark all kernel symbols as local
um: Disable CONFIG_GCOV with MODULES
ARM: 9075/1: kernel: Fix interrupted SMC calls
platform/chrome: cros_ec_typec: Add DP mode check
riscv: Use $(LD) instead of $(CC) to link vDSO
scripts/recordmcount.pl: Fix RISC-V regex for clang
riscv: Workaround mcount name prior to clang-13
scsi: lpfc: Fix illegal memory access on Abort IOCBs
ceph: fix fscache invalidation
ceph: don't clobber i_snap_caps on non-I_NEW inode
ceph: don't allow access to MDS-private inodes
scsi: target: tcmu: Return from tcmu_handle_completions() if cmd_id not found
amdgpu/pm: Prevent force of DCEFCLK on NAVI10 and SIENNA_CICHLID
bridge: Fix possible races between assigning rx_handler_data and setting
IFF_BRIDGE_PORT bit
net: hsr: check skb can contain struct hsr_ethhdr in fill_frame_info
nvmet: remove unsupported command noise
drm/amd/display: Fix two cursor duplication when using overlay
gpiolib: acpi: Add quirk to ignore EC wakeups on Dell Venue 10 Pro 5055
net:CXGB4: fix leak if sk_buff is not used
ALSA: hda: generic: change the DAC ctl name for LO+SPK or LO+HP
block: reexpand iov_iter after read/write
lib: stackdepot: turn depot_lock spinlock to raw_spinlock
net: stmmac: Do not enable RX FIFO overflow interrupts
ip6_gre: proper dev_{hold|put} in ndo_[un]init methods
sit: proper dev_{hold|put} in ndo_[un]init methods
ip6_tunnel: sit: proper dev_{hold|put} in ndo_[un]init methods
ipv6: remove extra dev_hold() for fallback tunnels
NFS: Fix fscache invalidation in nfs_set_cache_invalid()
f2fs: fix to avoid NULL pointer dereference
svcrdma: Don't leak send_ctxt on Send errors
UBUNTU: upstream stable to v5.10.39, v5.12.6
firmware: arm_scpi: Prevent the ternary sign expansion bug
openrisc: Fix a memory leak
tee: amdtee: unload TA only when its refcount becomes 0
RDMA/siw: Properly check send and receive CQ pointers
RDMA/siw: Release xarray entry
RDMA/core: Prevent divide-by-zero error triggered by the user
RDMA/rxe: Clear all QP fields if creation failed
scsi: ufs: core: Increase the usable queue depth
scsi: qedf: Add pointer checks in qedf_update_link_speed()
scsi: qla2xxx: Fix error return code in qla82xx_write_flash_dword()
RDMA/mlx5: Recover from fatal event in dual port mode
RDMA/core: Don't access cm_id after its destruction
nvmet: fix memory leak in nvmet_alloc_ctrl()
nvme-loop: fix memory leak in nvme_loop_create_ctrl()
nvme-tcp: rerun io_work if req_list is not empty
nvme-fc: clear q_live at beginning of association teardown
platform/mellanox: mlxbf-tmfifo: Fix a memory barrier issue
platform/x86: intel_int0002_vgpio: Only call enable_irq_wake() when using
s2idle
platform/x86: dell-smbios-wmi: Fix oops on rmmod dell_smbios
RDMA/mlx5: Fix query DCT via DEVX
[Kernel-packages] [Bug 1933262] Re: Groovy update: upstream stable patchset 2021-06-22
** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1933262 Title: Groovy update: upstream stable patchset 2021-06-22 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933262/+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 1933262] [NEW] Groovy update: upstream stable patchset 2021-06-22
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-22 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Groovy) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New -- 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/1933262 Title: Groovy update: upstream stable patchset 2021-06-22 Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-22 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933262/+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 1932209] Re: UAF on CAN J1939 j1939_can_recv
** Summary changed: - placeholder bug + UAF on CAN J1939 j1939_can_recv ** Description changed: - Another bug. + [Impact] + j1939_can_recv may run concurrently to can_rx_unregister on j1939_netdev_stop, which will, then, free the priv struct that is used by j1939_can_recv, leading to a system crash. + + [Potential regression] + CAN J1939 sockets may stop working as expected. + + [Test case] + A program that created multiple threads, binding to J1939 sockets and closing them, while sending RAW CAN sockets were run. ** Information type changed from Private to Public Security -- 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/1932209 Title: UAF on CAN J1939 j1939_can_recv Status in linux package in Ubuntu: Fix Released Bug description: [Impact] j1939_can_recv may run concurrently to can_rx_unregister on j1939_netdev_stop, which will, then, free the priv struct that is used by j1939_can_recv, leading to a system crash. [Potential regression] CAN J1939 sockets may stop working as expected. [Test case] A program that created multiple threads, binding to J1939 sockets and closing them, while sending RAW CAN sockets were run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932209/+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 1931855] Re: UAF on CAN BCM bcm_rx_handler
** Summary changed: - placeholder bug + UAF on CAN BCM bcm_rx_handler ** Description changed: - This reports a bug. + [Impact] + bcm_rx_handler may run concurrently to can_rx_unregister on bcm_release, which will, then, free the bcm_op that is used by bcm_rx_handler, leading to a system crash. + + [Potential regression] + CAN BCM sockets may stop working as expected. + + [Test case] + Programs from can-utils were run, some of them concurrently. ** Information type changed from Private to Public Security -- 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/1931855 Title: UAF on CAN BCM bcm_rx_handler Status in linux package in Ubuntu: Fix Released Bug description: [Impact] bcm_rx_handler may run concurrently to can_rx_unregister on bcm_release, which will, then, free the bcm_op that is used by bcm_rx_handler, leading to a system crash. [Potential regression] CAN BCM sockets may stop working as expected. [Test case] Programs from can-utils were run, some of them concurrently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931855/+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 1933259] [NEW] Bluetooth not working/can't turn it on
Public bug reported: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth bluetoothctl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1933259] Re: Bluetooth not working/can't turn it on
I should mention that bluetooth was working on 20.04 and 20.10 but after upgrade to 21.04 it doesn't work anymore. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1933259 Title: Bluetooth not working/can't turn it on Status in bluez package in Ubuntu: New Bug description: Can't turn on the bluetooth on 21.04. Using bluetoothctl these are the returns: ``` bluetoothctl Agent registered [CHG] Controller 60:14:B3:AC:14:C8 Pairable: yes [bluetooth]# connect 60:14:B3:AC:14:C8 Device 60:14:B3:AC:14:C8 not available [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady [bluetooth]# ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933259/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.04.1 --- crash (7.2.8-1ubuntu1.20.04.1) focal; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Thu, 15 Apr 2021 12:33:46 +0300 ** Changed in: crash (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu0.18.04.2 --- crash (7.2.8-1ubuntu0.18.04.2) bionic; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Wed, 14 Apr 2021 18:41:40 +0300 ** Changed in: crash (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: crash (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1931435] Update Released
The verification of the Stable Release Update for crash has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Fix Released Status in crash source package in Groovy: Fix Released Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+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 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2 --- crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium * Fix FTBFS (LP: #1931435): - d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Thu, 10 Jun 2021 16:07:41 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64
This bug was fixed in the package crash - 7.2.8-1ubuntu1.20.10.2 --- crash (7.2.8-1ubuntu1.20.10.2) groovy; urgency=medium * Fix FTBFS (LP: #1931435): - d/p/0004-Fix-for-an-ARM64-gcc-10-compilation-error.-Without-t.patch crash (7.2.8-1ubuntu1.20.10.1) groovy; urgency=medium * Fix cannot determine VA_BITS_ACTUAL (LP: #1919275): - d/p/0003-arm64-Change-tcr_el1_t1sz-variable-name-to-TCR_EL1_T.patch -- Ioanna Alifieraki Thu, 10 Jun 2021 16:07:41 + ** Changed in: crash (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Fix Released Status in crash source package in Groovy: Fix Released Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+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 1929255] Re: update-initrd-links creates incorrect symlinks
@fmalfoy it was fixed with the 06-04 round of sru updates. Does the new linux-base from proposed not resolve the reported regressions for you? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed
The x1e.xlarge and m3.large AWS instances report 0-14 as possible CPUs
(/sys/devices/system/cpu/possible) even though they have 4 or 2 CPUs
respectively. This should be fixed with LTP commit 14797491f1cc
("cpuset_hotplug_test.sh: Fix bug for obtaining task_cpus value in
root/generic_cpu_hotplut test").
** Changed in: ubuntu-kernel-tests
Status: Triaged => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
** No longer affects: linux (Ubuntu)
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-azure (Ubuntu Bionic)
** No longer affects: linux-aws (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Bionic)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux-aws (Ubuntu Focal)
** No longer affects: linux-azure (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1834006
Title:
cpuset_hotplug from controllers in ubuntu_ltp failed
Status in ubuntu-kernel-tests:
Fix Released
Bug description:
Issue found on node amaura:
<<>>
tag=cpuset_hotplug stime=1561372131
cmdline="cpuset_hotplug_test.sh"
contacts=""
analysis=exit
<<>>
incrementing stop
cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-15,
Expect: 0-7)
cpuset_hotplug 3 TFAIL: task's allowed list isn't expected.(Result: 0-15,
Expect: 0-7)
cpuset_hotplug 5 TPASS: Cpuset vs CPU hotplug test succeeded.
cpuset_hotplug 7 TFAIL: task's cpu allowed list isn't expected(Result: 0-15,
Expect: 0-7).
cpuset_hotplug 9 TPASS: Cpuset vs CPU hotplug test succeeded.
cpuset_hotplug 11 TPASS: Cpuset vs CPU hotplug test succeeded.
<<>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=19 cstime=81
<<>>
Test script:
https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/controllers/cpuset/cpuset_hotplug_test/cpuset_hotplug_test.sh
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-22-generic 4.18.0-22.23
ProcVersionSignature: User Name 4.18.0-22.23-generic 4.18.20
Uname: Linux 4.18.0-22-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Jun 24 10:25 seq
crw-rw 1 root audio 116, 33 Jun 24 10:25 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Mon Jun 24 10:30:59 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Intel Corporation S1200RP
PciMultimedia:
ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic
root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro
RelatedPackageVersions:
linux-restricted-modules-4.18.0-22-generic N/A
linux-backports-modules-4.18.0-22-generic N/A
linux-firmware 1.175.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/01/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: S1200RP.86B.03.02.0003.070120151022
dmi.board.asset.tag:
dmi.board.name: S1200RP
dmi.board.vendor: Intel Corporation
dmi.board.version: G62254-407
dmi.chassis.asset.tag:
dmi.chassis.type: 17
dmi.chassis.vendor: ..
dmi.chassis.version: ..
dmi.modalias:
dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: S1200RP
dmi.product.sku: To be filled by O.E.M.
dmi.product.version:
dmi.sys.vendor: Intel Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+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 1919275] Update Released
The verification of the Stable Release Update for crash has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+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 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux - 5.4.0-77.86 --- linux (5.4.0-77.86) focal; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.4.0-76.85) focal; urgency=medium * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux (5.4.0-75.84) focal; urgency=medium * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply - usb: typec: tcpm: update power supply once partner accepts - usb: xhci-mtk: remove or operator for setting schedule parameters - usb: xhci-mtk: improve bandwidth scheduling with TT - ASoC: samsung: tm2_wm5110: check
[Kernel-packages] [Bug 1836166] Re: cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Invalid -- 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/1836166 Title: cpuhotplug02 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: Invalid Bug description: Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug02 cpuhotplug02.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs <<>> incrementing stop Name: cpuhotplug02 Date: Thu Jul 11 08:21:54 UTC 2019 Desc: What happens to a process when its CPU is offlined? CPU is 1 sh: echo: I/O error cpuhotplug02 1 TFAIL: process did not change from CPU 1 <<>> Test passed on ThunderX ARM64, probably a test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:22:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836166/+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 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: fix subprog verifier bypass by div/mod by 0 exception
- SAUCE: bpf: Fix 32-bit register truncation on div/mod instruction
linux (4.15.0-146.150) bionic; urgency=medium
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
linux (4.15.0-145.149) bionic; urgency=medium
* bionic/linux: 4.15.0-145.149 -proposed tracker (LP: #1929967)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
* CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr
* Bionic update: upstream stable patchset 2021-05-25 (LP: #1929603)
- Input: nspire-keypad - enable interrupts only when opened
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- arc: kernel: Return -EFAULT if copy_to_user() fails
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- ARM: footbridge: fix PCI interrupt mapping
- ARM: 9071/1: uprobes: Don't hook on thumb instructions
- pinctrl: lewisburg: Update number of pins in community
- HID: wacom: Assign boolean values to a bool variable
- ARM: dts: Fix swapped mmc order for omap3
- net: geneve: check skb is large enough for IPv4/IPv6 header
- s390/entry: save the caller of psw_idle
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- drm/msm: Fix a5xx/a6xx timestamps
- Input: s6sy761 - fix coordinate read bit shift
- net: ip6_tunnel: Unregister catch-all devices
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
- net: usb: ax88179_178a: initialize local variables before use
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
- mips: Do not include hi and lo in clobber list for R6
- bpf: Fix masking negation logic upon negative dst register
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
- ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
- USB: Add reset-resume quirk for WD19's Realtek Hub
- platform/x86: thinkpad_acpi: Correct thermal sensor allocation
* r8152 tx
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux-aws - 5.4.0-1051.53 --- linux-aws (5.4.0-1051.53) focal; urgency=medium [ Ubuntu: 5.4.0-77.86 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.4.0-76.85 ] * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" -- Stefan Bader Thu, 17 Jun 2021 19:23:21 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1920944 Title: kvm: properly tear down PV features on hibernate Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-aws source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-aws source package in Hirsute: Fix Released Bug description: [Impact] In LP: #1918694 we applied a fix and a workaround to solve the hibernation issues on c5.18xlarge. The workaround was in the form of a SAUCE patch: "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot" It looks like we can replace this workaround with a proper fix, by applying this patch: http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/ This is required because various PV features (Async PF, PV EOI, steal time) work through memory shared with hypervisor and when we restore from hibernation we must properly tear down all these features to make sure hypervisor doesn't write to stale locations after we jump to the previously hibernated kernel. For this reason it is safe to apply this patch set also to all the generic kernels and not just AWS. [Test plan] This can be easily tested on AWS (but it should be reproduced by hibernating any kvm instance with multiple CPUs). Create a c5.18xlarge instance, run the memory stress test script (the same test script that we are using to stress test hibernation), trigger the hibernate event, trigger the resume event. Repeat a couple of times and the problem is very likely to happen. [Fix] On the AWS kernel replace "UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot" with: http://next.patchew.org/Linux/20210414123544.1060604-1-vkuzn...@redhat.com/ For the other kernels, simply apply this patch set. The fix has been tested extensively in the AWS infrastructure with positive results. [Regression potential] This new code introduced by the fix can be executed also when a CPU is put offline, so we may see potential regressions in the KVM CPU hot- plugging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920944/+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 1928522] Re: seccomp_bpf:syscall_faked from kselftests fail on s390x
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: fix subprog verifier bypass by div/mod by 0 exception
- SAUCE: bpf: Fix 32-bit register truncation on div/mod instruction
linux (4.15.0-146.150) bionic; urgency=medium
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
linux (4.15.0-145.149) bionic; urgency=medium
* bionic/linux: 4.15.0-145.149 -proposed tracker (LP: #1929967)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
* CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr
* Bionic update: upstream stable patchset 2021-05-25 (LP: #1929603)
- Input: nspire-keypad - enable interrupts only when opened
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- arc: kernel: Return -EFAULT if copy_to_user() fails
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- ARM: footbridge: fix PCI interrupt mapping
- ARM: 9071/1: uprobes: Don't hook on thumb instructions
- pinctrl: lewisburg: Update number of pins in community
- HID: wacom: Assign boolean values to a bool variable
- ARM: dts: Fix swapped mmc order for omap3
- net: geneve: check skb is large enough for IPv4/IPv6 header
- s390/entry: save the caller of psw_idle
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- drm/msm: Fix a5xx/a6xx timestamps
- Input: s6sy761 - fix coordinate read bit shift
- net: ip6_tunnel: Unregister catch-all devices
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
- net: usb: ax88179_178a: initialize local variables before use
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
- mips: Do not include hi and lo in clobber list for R6
- bpf: Fix masking negation logic upon negative dst register
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
- ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
- USB: Add reset-resume quirk for WD19's Realtek Hub
- platform/x86: thinkpad_acpi: Correct thermal sensor allocation
* r8152 tx
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This bug was fixed in the package linux - 5.8.0-59.66 --- linux (5.8.0-59.66) groovy; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.8.0-57.64) groovy; urgency=medium * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux (5.8.0-56.63) groovy; urgency=medium * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132) - Input: nspire-keypad - enable
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux-aws - 5.11.0-1011.11 --- linux-aws (5.11.0-1011.11) hirsute; urgency=medium [ Ubuntu: 5.11.0-22.23 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux-aws (5.11.0-1009.9) hirsute; urgency=medium * hirsute/linux-aws: 5.11.0-1009.9 -proposed tracker (LP: #1930058) * Hirsute update: v5.11.21 upstream stable release (LP: #1929455) - [Config] aws: updateconfigs for AD9467 [ Ubuntu: 5.11.0-20.21 ] * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function [ Ubuntu: 5.11.0-19.20 ] * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] enable soundwire audio mach driver * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux - 5.8.0-59.66 --- linux (5.8.0-59.66) groovy; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.8.0-57.64) groovy; urgency=medium * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux (5.8.0-56.63) groovy; urgency=medium * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132) - Input: nspire-keypad - enable
[Kernel-packages] [Bug 1928774] Re: RTL8188EE Wireless Network Adapter not supported
This bug was fixed in the package linux-raspi - 5.4.0-1038.41 --- linux-raspi (5.4.0-1038.41) focal; urgency=medium [ Ubuntu: 5.4.0-77.86 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.4.0-76.85 ] * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux-raspi (5.4.0-1037.40) focal; urgency=medium * focal/linux-raspi: 5.4.0-1037.40 -proposed tracker (LP: #1930027) * ath9k driver: miniPCIe Atheros AR93xx not recognized (LP: #1927037) - [Config] raspi: Disable ATH9K_AHB, set ATH9K_PCI=y - overlays: Add pcie-32bit-dma overlay * RTL8188EE Wireless Network Adapter not supported (LP: #1928774) - [Config] raspi: Set RTL8188EE=m [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL
[Kernel-packages] [Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
This bug was fixed in the package linux - 5.4.0-77.86 --- linux (5.4.0-77.86) focal; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.4.0-76.85) focal; urgency=medium * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux (5.4.0-75.84) focal; urgency=medium * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply - usb: typec: tcpm: update power supply once partner accepts - usb: xhci-mtk: remove or operator for setting schedule parameters - usb: xhci-mtk: improve bandwidth scheduling with TT - ASoC: samsung: tm2_wm5110: check
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux-aws - 5.8.0-1038.40 --- linux-aws (5.8.0-1038.40) groovy; urgency=medium [ Ubuntu: 5.8.0-59.66 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.8.0-57.64 ] * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux-aws (5.8.0-1036.38) groovy; urgency=medium * groovy/linux-aws: 5.8.0-1036.38 -proposed tracker (LP: #1930039) [ Ubuntu: 5.8.0-56.63 ] * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy
[Kernel-packages] [Bug 1928788] Re: linux-azure: Add Mana network driver
This bug was fixed in the package linux-azure-5.8 - 5.8.0-1036.38~20.04.1 --- linux-azure-5.8 (5.8.0-1036.38~20.04.1) focal; urgency=medium [ Ubuntu: 5.8.0-1036.38 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb -- Stefan Bader Thu, 17 Jun 2021 15:45:58 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1928788 Title: linux-azure: Add Mana network driver Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-5.8 source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-5.8 source package in Groovy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of the "mana" driver from Linux v5.11 https://canonical.my.salesforce.com/5004K05pZQCQA2 [Fix] This patch set consists of 5 patches that are now in mainline. The patches add the VF driver for Microsoft Azure Network Adapter (MANA), and also changes the hv_netvsc driver's netvsc/VF binding logic to check both the MAC address and the serial number (this is required by the MANA VF driver). Microsoft would like to request the following 5 patches in all supported releases: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64ff412ad41fe3a5bf759ff4844dc1382176485c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=55cdc26a91ac270887583945aef2bd460a2805f7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=45b102dd81491e30ac7596b5515856141f99319f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=d90a94680bc0a8069d93282bc5f2966d00b9c4a4 [Test Plan] 2021-05-17 15:25 UTC- -We tested the two versions of mana.ko: root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.4.0-1048-azure #50~sf00310147.1-Ubuntu SMP Tue May 11 02:06:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.4.0-1048-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.8.0-1032-azure #34~SF00310147.1-Ubuntu SMP Tue May 11 02:01:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.8.0-1032-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko Everything worked as expected in our testing: 1. The MANA driver loads and unloads multiple times without any issue. 2. iperf TX/RX tests run without any issue, and the performance numbers are on par with what we get with the latest mainline kernel: the TX number is pretty good; the RX number is sometimes not great but this is a known issue with the latest mainline kernel as well. 3. "ethtool -S" and "ethtool -L" work as expected. 4. When iperf TX/RX tests are running, changing the number of the MANA NIC TX/RX queues and unloading/reloading the MANA driver work without any issue. [Where problems could occur] The driver may have bug(s) that cause a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928788/+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 1922651] Re: r8152 tx status -71
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: fix subprog verifier bypass by div/mod by 0 exception
- SAUCE: bpf: Fix 32-bit register truncation on div/mod instruction
linux (4.15.0-146.150) bionic; urgency=medium
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
linux (4.15.0-145.149) bionic; urgency=medium
* bionic/linux: 4.15.0-145.149 -proposed tracker (LP: #1929967)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
* CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr
* Bionic update: upstream stable patchset 2021-05-25 (LP: #1929603)
- Input: nspire-keypad - enable interrupts only when opened
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- arc: kernel: Return -EFAULT if copy_to_user() fails
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- ARM: footbridge: fix PCI interrupt mapping
- ARM: 9071/1: uprobes: Don't hook on thumb instructions
- pinctrl: lewisburg: Update number of pins in community
- HID: wacom: Assign boolean values to a bool variable
- ARM: dts: Fix swapped mmc order for omap3
- net: geneve: check skb is large enough for IPv4/IPv6 header
- s390/entry: save the caller of psw_idle
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- drm/msm: Fix a5xx/a6xx timestamps
- Input: s6sy761 - fix coordinate read bit shift
- net: ip6_tunnel: Unregister catch-all devices
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
- net: usb: ax88179_178a: initialize local variables before use
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
- mips: Do not include hi and lo in clobber list for R6
- bpf: Fix masking negation logic upon negative dst register
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
- ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
- USB: Add reset-resume quirk for WD19's Realtek Hub
- platform/x86: thinkpad_acpi: Correct thermal sensor allocation
* r8152 tx
[Kernel-packages] [Bug 1920180] Re: Can't detect intel wifi 6235
This bug was fixed in the package linux - 5.8.0-59.66 --- linux (5.8.0-59.66) groovy; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.8.0-57.64) groovy; urgency=medium * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux (5.8.0-56.63) groovy; urgency=medium * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132) - Input: nspire-keypad - enable
[Kernel-packages] [Bug 1920944] Re: kvm: properly tear down PV features on hibernate
This bug was fixed in the package linux - 5.11.0-22.23 --- linux (5.11.0-22.23) hirsute; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.11.0-20.21) hirsute; urgency=medium * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function linux (5.11.0-19.20) hirsute; urgency=medium * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] enable soundwire audio mach driver * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * Fix screen flickering when two 4K 60Hz monitors are connected to AMD Oland
[Kernel-packages] [Bug 1925685] Re: [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer
This bug was fixed in the package linux-hwe-5.8 - 5.8.0-59.66~20.04.1 --- linux-hwe-5.8 (5.8.0-59.66~20.04.1) focal; urgency=medium [ Ubuntu: 5.8.0-59.66 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux-hwe-5.8 (5.8.0-57.64~20.04.1) focal; urgency=medium * focal/linux-hwe-5.8: 5.8.0-57.64~20.04.1 -proposed tracker (LP: #1932046) [ Ubuntu: 5.8.0-57.64 ] * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux-hwe-5.8 (5.8.0-56.63~20.04.1) focal; urgency=medium * focal/linux-hwe-5.8: 5.8.0-56.63~20.04.1 -proposed tracker (LP: #1930051) [ Ubuntu: 5.8.0-56.63 ] * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) -
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
This bug was fixed in the package linux - 5.4.0-77.86 --- linux (5.4.0-77.86) focal; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.4.0-76.85) focal; urgency=medium * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux (5.4.0-75.84) focal; urgency=medium * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply - usb: typec: tcpm: update power supply once partner accepts - usb: xhci-mtk: remove or operator for setting schedule parameters - usb: xhci-mtk: improve bandwidth scheduling with TT - ASoC: samsung: tm2_wm5110: check
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This bug was fixed in the package linux-azure - 5.11.0-1009.9 --- linux-azure (5.11.0-1009.9) hirsute; urgency=medium [ Ubuntu: 5.11.0-22.23 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux-azure (5.11.0-1007.7) hirsute; urgency=medium * hirsute/linux-azure: 5.11.0-1007.7 -proposed tracker (LP: #1930060) * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] azure: disable soundwire audio mach driver * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues [ Ubuntu: 5.11.0-20.21 ] * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function [ Ubuntu: 5.11.0-19.20 ] * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config]
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
This bug was fixed in the package linux - 5.11.0-22.23 --- linux (5.11.0-22.23) hirsute; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.11.0-20.21) hirsute; urgency=medium * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function linux (5.11.0-19.20) hirsute; urgency=medium * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] enable soundwire audio mach driver * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * Fix screen flickering when two 4K 60Hz monitors are connected to AMD Oland
[Kernel-packages] [Bug 1928788] Re: linux-azure: Add Mana network driver
This bug was fixed in the package linux-azure - 5.4.0-1051.53 --- linux-azure (5.4.0-1051.53) focal; urgency=medium [ Ubuntu: 5.4.0-77.86 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.4.0-76.85 ] * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" -- Stefan Bader Thu, 17 Jun 2021 19:43:15 +0200 ** Changed in: linux-azure-5.8 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1928788 Title: linux-azure: Add Mana network driver Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.8 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Fix Released Status in linux-azure-5.8 source package in Focal: Fix Released Status in linux source package in Groovy: Invalid Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-5.8 source package in Groovy: Invalid Bug description: SRU Justification [Impact] Microsoft has requested the addition of the "mana" driver from Linux v5.11 https://canonical.my.salesforce.com/5004K05pZQCQA2 [Fix] This patch set consists of 5 patches that are now in mainline. The patches add the VF driver for Microsoft Azure Network Adapter (MANA), and also changes the hv_netvsc driver's netvsc/VF binding logic to check both the MAC address and the serial number (this is required by the MANA VF driver). Microsoft would like to request the following 5 patches in all supported releases: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=64ff412ad41fe3a5bf759ff4844dc1382176485c https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=55cdc26a91ac270887583945aef2bd460a2805f7 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=45b102dd81491e30ac7596b5515856141f99319f https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=d90a94680bc0a8069d93282bc5f2966d00b9c4a4 [Test Plan] 2021-05-17 15:25 UTC- -We tested the two versions of mana.ko: root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.4.0-1048-azure #50~sf00310147.1-Ubuntu SMP Tue May 11 02:06:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.4.0-1048-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko root@decui-u2004-vf:~# uname -a Linux decui-u2004-vf 5.8.0-1032-azure #34~SF00310147.1-Ubuntu SMP Tue May 11 02:01:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux root@decui-u2004-vf:~# modinfo mana | grep filename filename: /lib/modules/5.8.0-1032-azure/kernel/drivers/net/ethernet/microsoft/mana/mana.ko Everything worked as expected in our testing: 1. The MANA driver loads and unloads multiple times without any issue. 2. iperf TX/RX tests run without any issue, and the performance numbers are on par with what we get with the latest mainline kernel: the TX number is pretty good; the RX number is sometimes not great but this is a known issue with the latest mainline kernel as well. 3. "ethtool -S" and "ethtool -L" work as expected. 4. When iperf TX/RX tests are running, changing the number of the MANA NIC TX/RX queues and unloading/reloading the MANA driver work without any issue. [Where problems could occur] The driver may have bug(s) that cause a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928788/+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 1928788] Re: linux-azure: Add Mana network driver
This bug was fixed in the package linux-azure - 5.8.0-1036.38 --- linux-azure (5.8.0-1036.38) groovy; urgency=medium [ Ubuntu: 5.8.0-59.66 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.8.0-57.64 ] * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux-azure (5.8.0-1034.36) groovy; urgency=medium * groovy/linux-azure: 5.8.0-1034.36 -proposed tracker (LP: #1930041) * linux-azure: Add Mana network driver (LP: #1928788) - hv_netvsc: Make netvsc/VF binding check both MAC and serial number - [Config] azure: CONFIG_MICROSOFT_MANA=m - net: mana: Add a driver for Microsoft Azure Network Adapter (MANA) - net: mana: remove redundant initialization of variable err - net: mana: fix PCI_HYPERV dependency - net: mana: Use int to check the return value of mana_gd_poll_cq() [ Ubuntu: 5.8.0-56.63 ] * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for
[Kernel-packages] [Bug 1927037] Re: ath9k driver: miniPCIe Atheros AR93xx not recognized
This bug was fixed in the package linux-raspi - 5.4.0-1038.41 --- linux-raspi (5.4.0-1038.41) focal; urgency=medium [ Ubuntu: 5.4.0-77.86 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.4.0-76.85 ] * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux-raspi (5.4.0-1037.40) focal; urgency=medium * focal/linux-raspi: 5.4.0-1037.40 -proposed tracker (LP: #1930027) * ath9k driver: miniPCIe Atheros AR93xx not recognized (LP: #1927037) - [Config] raspi: Disable ATH9K_AHB, set ATH9K_PCI=y - overlays: Add pcie-32bit-dma overlay * RTL8188EE Wireless Network Adapter not supported (LP: #1928774) - [Config] raspi: Set RTL8188EE=m [ Ubuntu: 5.4.0-75.84 ] * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL
[Kernel-packages] [Bug 1927518] Re: Fix kdump failures
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: fix subprog verifier bypass by div/mod by 0 exception
- SAUCE: bpf: Fix 32-bit register truncation on div/mod instruction
linux (4.15.0-146.150) bionic; urgency=medium
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
linux (4.15.0-145.149) bionic; urgency=medium
* bionic/linux: 4.15.0-145.149 -proposed tracker (LP: #1929967)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
* CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr
* Bionic update: upstream stable patchset 2021-05-25 (LP: #1929603)
- Input: nspire-keypad - enable interrupts only when opened
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- arc: kernel: Return -EFAULT if copy_to_user() fails
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- ARM: footbridge: fix PCI interrupt mapping
- ARM: 9071/1: uprobes: Don't hook on thumb instructions
- pinctrl: lewisburg: Update number of pins in community
- HID: wacom: Assign boolean values to a bool variable
- ARM: dts: Fix swapped mmc order for omap3
- net: geneve: check skb is large enough for IPv4/IPv6 header
- s390/entry: save the caller of psw_idle
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- drm/msm: Fix a5xx/a6xx timestamps
- Input: s6sy761 - fix coordinate read bit shift
- net: ip6_tunnel: Unregister catch-all devices
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
- net: usb: ax88179_178a: initialize local variables before use
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
- mips: Do not include hi and lo in clobber list for R6
- bpf: Fix masking negation logic upon negative dst register
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
- ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
- USB: Add reset-resume quirk for WD19's Realtek Hub
- platform/x86: thinkpad_acpi: Correct thermal sensor allocation
* r8152 tx
[Kernel-packages] [Bug 1929603] Re: Bionic update: upstream stable patchset 2021-05-25
This bug was fixed in the package linux - 4.15.0-147.151
---
linux (4.15.0-147.151) bionic; urgency=medium
* CVE-2021-3444
- bpf: Fix truncation handling for mod32 dst reg wrt zero
* CVE-2021-3600
- SAUCE: bpf: Do not use ax register in interpreter on div/mod
- bpf: fix subprog verifier bypass by div/mod by 0 exception
- SAUCE: bpf: Fix 32-bit register truncation on div/mod instruction
linux (4.15.0-146.150) bionic; urgency=medium
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
linux (4.15.0-145.149) bionic; urgency=medium
* bionic/linux: 4.15.0-145.149 -proposed tracker (LP: #1929967)
* Packaging resync (LP: #1786013)
- update dkms package versions
* raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations (LP: #1896578)
- md: add md_submit_discard_bio() for submitting discard bio
- md/raid10: extend r10bio devs to raid disks
- md/raid10: pull the code that wait for blocked dev into one function
- md/raid10: improve raid10 discard request
- md/raid10: improve discard request for far layout
* CVE-2021-23133
- sctp: delay auto_asconf init until binding the first addr
* Bionic update: upstream stable patchset 2021-05-25 (LP: #1929603)
- Input: nspire-keypad - enable interrupts only when opened
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- arc: kernel: Return -EFAULT if copy_to_user() fails
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- netfilter: nft_limit: avoid possible divide error in nft_limit_init
- net: davicom: Fix regulator not turned off on failed probe
- net: sit: Unregister catch-all devices
- i40e: fix the panic when running bpf in xdpdrv mode
- ibmvnic: avoid calling napi_disable() twice
- ibmvnic: remove duplicate napi_schedule call in do_reset function
- ibmvnic: remove duplicate napi_schedule call in open function
- ARM: footbridge: fix PCI interrupt mapping
- ARM: 9071/1: uprobes: Don't hook on thumb instructions
- pinctrl: lewisburg: Update number of pins in community
- HID: wacom: Assign boolean values to a bool variable
- ARM: dts: Fix swapped mmc order for omap3
- net: geneve: check skb is large enough for IPv4/IPv6 header
- s390/entry: save the caller of psw_idle
- xen-netback: Check for hotplug-status existence before watching
- cavium/liquidio: Fix duplicate argument
- ia64: fix discontig.c section mismatches
- ia64: tools: remove duplicate definition of ia64_mf() on ia64
- x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access
- net: hso: fix NULL-deref on disconnect regression
- USB: CDC-ACM: fix poison/unpoison imbalance
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- drm/msm: Fix a5xx/a6xx timestamps
- Input: s6sy761 - fix coordinate read bit shift
- net: ip6_tunnel: Unregister catch-all devices
- ACPI: tables: x86: Reserve memory occupied by ACPI tables
- ACPI: x86: Call acpi_boot_table_init() after acpi_table_upgrade()
- net: usb: ax88179_178a: initialize local variables before use
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_enqueue_hcmd()
- mips: Do not include hi and lo in clobber list for R6
- bpf: Fix masking negation logic upon negative dst register
- iwlwifi: Fix softirq/hardirq disabling in iwl_pcie_gen2_enqueue_hcmd()
- ALSA: usb-audio: Add MIDI quirk for Vox ToneLab EX
- USB: Add reset-resume quirk for WD19's Realtek Hub
- platform/x86: thinkpad_acpi: Correct thermal sensor allocation
* r8152 tx
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This bug was fixed in the package linux-azure - 5.4.0-1051.53
---
linux-azure (5.4.0-1051.53) focal; urgency=medium
[ Ubuntu: 5.4.0-77.86 ]
* UAF on CAN J1939 j1939_can_recv (LP: #1932209)
- SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu
* UAF on CAN BCM bcm_rx_handler (LP: #1931855)
- SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu
[ Ubuntu: 5.4.0-76.85 ]
* focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123)
* Upstream v5.9 introduced 'module' patches that removed exported symbols
(LP: #1932065)
- SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE"
- SAUCE: Revert "modules: return licensing information from find_symbol"
- SAUCE: Revert "modules: rename the licence field in struct symsearch to
license"
- SAUCE: Revert "modules: unexport __module_address"
- SAUCE: Revert "modules: unexport __module_text_address"
- SAUCE: Revert "modules: mark each_symbol_section static"
- SAUCE: Revert "modules: mark find_symbol static"
- SAUCE: Revert "modules: mark ref_module static"
-- Stefan Bader Thu, 17 Jun 2021 19:43:15
+0200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1930626
Title:
scsi: storvsc: Parameterize number hardware queues
Status in linux package in Ubuntu:
Fix Committed
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Status in linux-azure source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux-azure source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-azure source package in Impish:
Fix Committed
Bug description:
Microsoft would like to request inclusion of the following patch in
the 5.4 and later kernels:
a81a38cc6dda ("scsi: storvsc: Parameterize number hardware queues")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?id=a81a38cc6ddaf128c7ca9e3f21c243f33c97
This patch adds the ability to set the number of hardware queues with
new module parameter, storvsc_max_hw_queues.
This functionality is useful in Microsoft Azure) where decreasing the
number of hardware queues has been shown to improve performance.
https://canonical.lightning.force.com/lightning/r/Case/5004K05qB6EQAU/view
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930626/+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 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
This bug was fixed in the package linux-oracle - 5.11.0-1010.10 --- linux-oracle (5.11.0-1010.10) hirsute; urgency=medium [ Ubuntu: 5.11.0-22.23 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux-oracle (5.11.0-1008.8) hirsute; urgency=medium * hirsute/linux-oracle: 5.11.0-1008.8 -proposed tracker (LP: #1930066) * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] oracle: disable soundwire audio mach driver * Hirsute update: v5.11.21 upstream stable release (LP: #1929455) - [Config] oracle: updateconfigs for AD9467 [ Ubuntu: 5.11.0-20.21 ] * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function [ Ubuntu: 5.11.0-19.20 ] * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config]
[Kernel-packages] [Bug 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
This bug was fixed in the package linux-meta-azure - 5.4.0.1051.49 --- linux-meta-azure (5.4.0.1051.49) focal; urgency=medium * Bump ABI 5.4.0-1051 -- Stefan Bader Thu, 17 Jun 2021 19:43:45 +0200 ** Changed in: linux-meta-azure-5.8 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: Fix Released Status in linux-meta-aws-5.8 source package in Focal: Fix Committed Status in linux-meta-azure source package in Focal: Fix Released Status in linux-meta-azure-5.8 source package in Focal: Fix Released Status in linux-meta-gcp source package in Focal: Fix Released Status in linux-meta-gcp-5.8 source package in Focal: Fix Released Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
This bug was fixed in the package linux - 5.8.0-59.66 --- linux (5.8.0-59.66) groovy; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.8.0-57.64) groovy; urgency=medium * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux (5.8.0-56.63) groovy; urgency=medium * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132) - Input: nspire-keypad - enable
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
This bug was fixed in the package linux - 5.4.0-77.86 --- linux (5.4.0-77.86) focal; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.4.0-76.85) focal; urgency=medium * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux (5.4.0-75.84) focal; urgency=medium * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply - usb: typec: tcpm: update power supply once partner accepts - usb: xhci-mtk: remove or operator for setting schedule parameters - usb: xhci-mtk: improve bandwidth scheduling with TT - ASoC: samsung: tm2_wm5110: check
[Kernel-packages] [Bug 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
This bug was fixed in the package linux - 5.11.0-22.23 --- linux (5.11.0-22.23) hirsute; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.11.0-20.21) hirsute; urgency=medium * hirsute/linux: 5.11.0-20.21 -proposed tracker (LP: #1930854) * ath11k WIFI not working in proposed kernel 5.11.0-19-generic (LP: #1930637) - bus: mhi: core: Download AMSS image from appropriate function linux (5.11.0-19.20) hirsute; urgency=medium * hirsute/linux: 5.11.0-19.20 -proposed tracker (LP: #1930075) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * AX201 BT will cause system could not enter S0i3 (LP: #1928047) - SAUCE: drm/i915: Tweaked Wa_14010685332 for all PCHs * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Select correct boot VGA when BIOS doesn't do it properly (LP: #1929217) - vgaarb: Use ACPI HID name to find integrated GPU * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU][OEM-5.10/H] Fix typec output on AMD Cezanne GPU (LP: #1929646) - drm/amd/display: use max lb for latency hiding * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Add support for AMD wireless button (LP: #1928820) - platform/x86: hp-wireless: add AMD's hardware id to the supported list * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * Speed up resume time on HP laptops (LP: #1929048) - platform/x86: hp_accel: Avoid invoking _INI to speed up resume * Fix kernel panic on Intel Bluetooth (LP: #1928838) - Bluetooth: Shutdown controller after workqueues are flushed or cancelled * build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later (LP: #1921632) - [Config] enable soundwire audio mach driver * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * Fix screen flickering when two 4K 60Hz monitors are connected to AMD Oland
[Kernel-packages] [Bug 1930626] Re: scsi: storvsc: Parameterize number hardware queues
This bug was fixed in the package linux-azure - 5.8.0-1036.38 --- linux-azure (5.8.0-1036.38) groovy; urgency=medium [ Ubuntu: 5.8.0-59.66 ] * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu [ Ubuntu: 5.8.0-57.64 ] * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux-azure (5.8.0-1034.36) groovy; urgency=medium * groovy/linux-azure: 5.8.0-1034.36 -proposed tracker (LP: #1930041) * linux-azure: Add Mana network driver (LP: #1928788) - hv_netvsc: Make netvsc/VF binding check both MAC and serial number - [Config] azure: CONFIG_MICROSOFT_MANA=m - net: mana: Add a driver for Microsoft Azure Network Adapter (MANA) - net: mana: remove redundant initialization of variable err - net: mana: fix PCI_HYPERV dependency - net: mana: Use int to check the return value of mana_gd_poll_cq() [ Ubuntu: 5.8.0-56.63 ] * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for
[Kernel-packages] [Bug 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
This bug was fixed in the package linux-meta-azure-5.8 - 5.8.0.1036.38~20.04.8 --- linux-meta-azure-5.8 (5.8.0.1036.38~20.04.8) focal; urgency=medium * Bump ABI 5.8.0-1036.38~20.04 * Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred (LP: #1931576) - [Packaging] Fix provides for *--modules-extra--preferred -- Stefan Bader Thu, 17 Jun 2021 15:46:52 +0200 ** Changed in: linux-meta-gcp (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: Fix Released Status in linux-meta-aws-5.8 source package in Focal: Fix Committed Status in linux-meta-azure source package in Focal: Fix Released Status in linux-meta-azure-5.8 source package in Focal: Fix Released Status in linux-meta-gcp source package in Focal: Fix Released Status in linux-meta-gcp-5.8 source package in Focal: Fix Released Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+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 1931576] Re: Cloud kernels meta don't provide kernel-testing--*--modules-extra--preferred
This bug was fixed in the package linux-meta-aws - 5.4.0.1051.53 --- linux-meta-aws (5.4.0.1051.53) focal; urgency=medium * Bump ABI 5.4.0-1051 -- Stefan Bader Thu, 17 Jun 2021 19:24:12 +0200 ** Changed in: linux-meta-aws (Ubuntu Focal) Status: Fix Committed => Fix Released ** Changed in: linux-meta-azure (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: Fix Released Status in linux-meta-aws-5.8 source package in Focal: Fix Committed Status in linux-meta-azure source package in Focal: Fix Released Status in linux-meta-azure-5.8 source package in Focal: Fix Released Status in linux-meta-gcp source package in Focal: Fix Released Status in linux-meta-gcp-5.8 source package in Focal: Fix Released Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+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 1896578] Re: raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations
This bug was fixed in the package linux - 5.4.0-77.86 --- linux (5.4.0-77.86) focal; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.4.0-76.85) focal; urgency=medium * focal/linux: 5.4.0-76.85 -proposed tracker (LP: #1932123) * Upstream v5.9 introduced 'module' patches that removed exported symbols (LP: #1932065) - SAUCE: Revert "modules: inherit TAINT_PROPRIETARY_MODULE" - SAUCE: Revert "modules: return licensing information from find_symbol" - SAUCE: Revert "modules: rename the licence field in struct symsearch to license" - SAUCE: Revert "modules: unexport __module_address" - SAUCE: Revert "modules: unexport __module_text_address" - SAUCE: Revert "modules: mark each_symbol_section static" - SAUCE: Revert "modules: mark find_symbol static" - SAUCE: Revert "modules: mark ref_module static" linux (5.4.0-75.84) focal; urgency=medium * focal/linux: 5.4.0-75.84 -proposed tracker (LP: #1930032) * Packaging resync (LP: #1786013) - update dkms package versions * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * Focal update: v5.4.119 upstream stable release (LP: #1929615) - Bluetooth: verify AMP hci_chan before amp_destroy - hsr: use netdev_err() instead of WARN_ONCE() - bluetooth: eliminate the potential race condition when removing the HCI controller - net/nfc: fix use-after-free llcp_sock_bind/connect - Revert "USB: cdc-acm: fix rounding error in TIOCSSERIAL" - tty: moxa: fix TIOCSSERIAL jiffies conversions - tty: amiserial: fix TIOCSSERIAL permission check - USB: serial: usb_wwan: fix TIOCSSERIAL jiffies conversions - staging: greybus: uart: fix TIOCSSERIAL jiffies conversions - USB: serial: ti_usb_3410_5052: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL jiffies conversions - tty: moxa: fix TIOCSSERIAL permission check - staging: fwserial: fix TIOCSSERIAL permission check - usb: typec: tcpm: Address incorrect values of tcpm psy for fixed supply - usb: typec: tcpm: Address incorrect values of tcpm psy for pps supply - usb: typec: tcpm: update power supply once partner accepts - usb: xhci-mtk: remove or operator for setting schedule parameters - usb: xhci-mtk: improve bandwidth scheduling with TT - ASoC: samsung: tm2_wm5110: check
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
This bug was fixed in the package linux - 5.8.0-59.66 --- linux (5.8.0-59.66) groovy; urgency=medium * UAF on CAN J1939 j1939_can_recv (LP: #1932209) - SAUCE: can: j1939: delay release of j1939_priv after synchronize_rcu * UAF on CAN BCM bcm_rx_handler (LP: #1931855) - SAUCE: can: bcm: delay release of struct bcm_op after synchronize_rcu linux (5.8.0-57.64) groovy; urgency=medium * groovy/linux: 5.8.0-57.64 -proposed tracker (LP: #1932047) * pmtu.sh from selftests.net in linux ADT test failure with linux/5.8.0-56.63 (LP: #1931731) - net: geneve: modify IP header check in geneve6_xmit_skb and geneve_xmit_skb linux (5.8.0-56.63) groovy; urgency=medium * groovy/linux: 5.8.0-56.63 -proposed tracker (LP: #1930052) * Packaging resync (LP: #1786013) - update dkms package versions * scsi: storvsc: Parameterize number hardware queues (LP: #1930626) - scsi: storvsc: Parameterize number hardware queues * CVE-2021-33200 - bpf: Wrap aux data inside bpf_sanitize_info container - bpf: Fix mask direction swap upon off reg sign change - bpf: No need to simulate speculative domain for immediates * CVE-2021-3490 - SAUCE: Revert "UBUNTU: SAUCE: bpf: verifier: fix ALU32 bounds tracking with bitwise ops" - gpf: Fix alu32 const subreg bound tracking on bitwise operations * CVE-2021-3489 - SAUCE: Revert "UBUNTU: SAUCE: bpf: prevent writable memory-mapping of read- only ringbuf pages" - bpf: Prevent writable memory-mapping of read-only ringbuf pages * Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle (LP: #1928242) - USB: Verify the port status when timeout happens during port suspend * CVE-2020-26145 - ath10k: drop fragments with multicast DA for SDIO - ath10k: add CCMP PN replay protection for fragmented frames for PCIe - ath10k: drop fragments with multicast DA for PCIe * CVE-2020-26141 - ath10k: Fix TKIP Michael MIC verification for PCIe * CVE-2020-24587 - ath11k: Clear the fragment cache during key install * CVE-2020-24588 - mac80211: properly handle A-MSDUs that start with an RFC 1042 header - cfg80211: mitigate A-MSDU aggregation attacks - mac80211: drop A-MSDUs on old ciphers - ath10k: drop MPDU which has discard flag set by firmware for SDIO * CVE-2020-26139 - mac80211: do not accept/forward invalid EAPOL frames * CVE-2020-24586 // CVE-2020-24587 // CVE-2020-24587 for such cases. - mac80211: extend protection against mixed key and fragment cache attacks * CVE-2020-24586 // CVE-2020-24587 - mac80211: prevent mixed key and fragment cache attacks - mac80211: add fragment cache to sta_info - mac80211: check defrag PN against current frame - mac80211: prevent attacks on TKIP/WEP as well * CVE-2020-26147 - mac80211: assure all fragments are encrypted * raid10: Block discard is very slow, causing severe delays for mkfs and fstrim operations (LP: #1896578) - md: add md_submit_discard_bio() for submitting discard bio - md/raid10: extend r10bio devs to raid disks - md/raid10: pull the code that wait for blocked dev into one function - md/raid10: improve raid10 discard request - md/raid10: improve discard request for far layout - dm raid: remove unnecessary discard limits for raid0 and raid10 * [SRU] mpt3sas: only one vSES is handy even IOC has multi vSES (LP: #1926517) - scsi: mpt3sas: Only one vSES is present even when IOC has multi vSES * CVE-2021-23133 - sctp: delay auto_asconf init until binding the first addr * kvm: properly tear down PV features on hibernate (LP: #1920944) - x86/kvm: Fix pr_info() for async PF setup/teardown - x86/kvm: Teardown PV features on boot CPU as well - x86/kvm: Disable kvmclock on all CPUs on shutdown - x86/kvm: Disable all PV features on crash - x86/kvm: Unify kvm_pv_guest_cpu_reboot() with kvm_guest_cpu_offline() * CVE-2021-31440 - bpf: Fix propagation of 32 bit unsigned bounds from 64 bit bounds * Can't detect intel wifi 6235 (LP: #1920180) - SAUCE: iwlwifi: add new pci id for 6235 * [SRU] Patch for flicker and glitching on common LCD display panels, intel framebuffer (LP: #1925685) - drm/i915: Try to use fast+narrow link on eDP again and fall back to the old max strategy on failure - drm/i915/dp: Use slow and wide link training for everything * pmtu.sh from net in ubuntu_kernel_selftests failed with no error message (LP: #1887661) - selftests: pmtu.sh: use $ksft_skip for skipped return code * IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 (LP: #1926030) - SAUCE: Revert "media: rc: ite-cir: fix min_timeout calculation" - SAUCE: Revert "media: rc: fix timeout handling after switch to microsecond durations" * Groovy update: upstream stable patchset 2021-05-20 (LP: #1929132) - Input: nspire-keypad - enable
