[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1049.52~18.04.46)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1049.52~18.04.46) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1980688] Re: [Lenovo ThinkPad T14] Mouse / trackpad buttons sometimes don't work after waking up from suspend
** Summary changed: - Mouse / trackpad buttons sometimes don't work after waking up from suspend + [Lenovo ThinkPad T14] Mouse / trackpad buttons sometimes don't work after waking up from suspend ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1980688 Title: [Lenovo ThinkPad T14] Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1973143] Re: [impish] Wayland session limited to 1024x768
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1973143 Title: [impish] Wayland session limited to 1024x768 Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Even though my monitor support maximum resolution, I can only set it to 1024x768. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 12 13:21:28 2022 DistUpgraded: 2022-05-02 12:21:49,539 DEBUG /openCache(), new cache size 70582 DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-40-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2022-03-02 (70 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2022-05-02 (10 days ago) dmi.bios.date: 10/20/2014 dmi.bios.release: 0.29 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973143/+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 1973143] Re: [impish] Wayland session limited to 1024x768
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1973143 Title: [impish] Wayland session limited to 1024x768 Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: Even though my monitor support maximum resolution, I can only set it to 1024x768. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 12 13:21:28 2022 DistUpgraded: 2022-05-02 12:21:49,539 DEBUG /openCache(), new cache size 70582 DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-40-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-41-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] Subsystem: Lenovo Sun LE [Radeon HD 8550M / R5 M230] [17aa:380c] InstallationDate: Installed on 2022-03-02 (70 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20351 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2022-05-02 (10 days ago) dmi.bios.date: 10/20/2014 dmi.bios.release: 0.29 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:br0.29:efr0.29:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:skuLENOVO_MT_20351_BU_idea_FM_LenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973143/+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 1786013] Autopkgtest regression report (linux-meta-gcp-5.4/5.4.0.1083.62)
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1083.62) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.045.08-2ubuntu1 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gcp-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
I can't see this SAUCE patch on kinetic tree. Invalidate the kinetic task. ** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Invalid ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1975691 Title: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] test_vxlan_under_vrf.sh should not be failing anymore with patches submitted to fix it in bug 1871015 (unless it's a kernel config related issue). With the regression-testing result hinting system available, we should remove the SAUCE patches that mark "underlay in a VRF" test failure as an expected failure to catch regressions in the future. This could reduce maintenance cost as well. [Fix] Revert the following patches: * UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non-default VRF an expected failure * UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail [Test] Patched test script tested with F/I/J/F-oem-5.14/J-oem-5.17. I have also modify the test case to fail it deliberately to verify this change, it works as expected. [Where problems could occur] Change limit to test cases, should not have any real impact to any kernel functions. We may see failures reported from this test in our SRU regression-testing report in the future, but it means we're doing the right thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1975691/+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 1981075] Re: ubuntu_kernel_selftests.net:fib_nexthops.sh times out on riscv
Timeout bumped to 45 mins: https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/commit/?id=b1724fef0a0a1341c75c92c3ce15283ed633cb3e ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1981075 Title: ubuntu_kernel_selftests.net:fib_nexthops.sh times out on riscv Status in ubuntu-kernel-tests: Fix Released Status in linux-riscv package in Ubuntu: Invalid Status in linux-riscv source package in Jammy: Invalid Bug description: net:fib_nexthops.sh times out on riscv kernels 12284 12:09:41 DEBUG| [stdout] # 12285 12:09:41 DEBUG| [stdout] # IPv6 runtime resilient nexthop group torture 12286 12:09:41 DEBUG| [stdout] # 12287 12:14:40 INFO | Timer expired (1800 sec.), nuking pid 43387 would be nice to possibly increase timer on riscv, as otherwise the test seems to be running ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1981075/+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 1981390] [NEW] Mass Storage Gadget driver truncates device >2TB
Public bug reported: I tried to use f_mass_storage to expose a 16TB hard drive attached to Raspberry Pi to another computer. On the remote computer the recognised drive has incorrect capacity and the data is truncated. After some debugging I noted the problem is caused by a bug in the read capacity function of f_mass_storage in kernel version prior to 5.15, which had already been fixed upstream in mainline kernel since v5.16 https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/ I tried the kernel from https://github.com/raspberrypi/linux version rpi-5.16.y and confirmed that the problem is fixed at v5.16. I wonder if the fix can be backported to the Ubuntu kernel. Thank you very much! Current kernel package version: linux-raspi (5.15.0-1011.13) jammy Hardware: Raspberry Pi 4B ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1981390 Title: Mass Storage Gadget driver truncates device >2TB Status in linux-raspi package in Ubuntu: New Bug description: I tried to use f_mass_storage to expose a 16TB hard drive attached to Raspberry Pi to another computer. On the remote computer the recognised drive has incorrect capacity and the data is truncated. After some debugging I noted the problem is caused by a bug in the read capacity function of f_mass_storage in kernel version prior to 5.15, which had already been fixed upstream in mainline kernel since v5.16 https://lore.kernel.org/all/20210914052728.23369-1-nikita.yo...@cogentembedded.com/ I tried the kernel from https://github.com/raspberrypi/linux version rpi-5.16.y and confirmed that the problem is fixed at v5.16. I wonder if the fix can be backported to the Ubuntu kernel. Thank you very much! Current kernel package version: linux-raspi (5.15.0-1011.13) jammy Hardware: Raspberry Pi 4B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1981390/+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 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1078.84~18.04.40)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1078.84~18.04.40) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kpatch/0.5.0-0ubuntu1.1 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) r8168/8.045.08-2ubuntu1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
I suggest your next step should be to reach out to the AMD graphics and Mesa developers by reporting the issue on one or both of: https://gitlab.freedesktop.org/drm/amd/-/issues https://gitlab.freedesktop.org/mesa/mesa/-/issues Assuming you can't find the problem in those lists already. -- 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/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 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.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A
[Kernel-packages] [Bug 1981383] [NEW] package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: Unable to use or turn on bluetooth ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 12 04:11:50 2022 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-06 (155 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_F543MA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=a1980608-1f3e-4705-9432-421aa3851fe6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540MA.314 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540MA.314:bd10/01/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_F543MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540MA_F543MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0: Type: Primary Bus: USB BD Address: C0:E4:34:24:68:A6 ACL MTU: 820:8 SCO MTU: 255:12 DOWN RX bytes:1154613008 acl:1610113 sco:0 events:493522 errors:0 TX bytes:35384460 acl:492878 sco:0 commands:420 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1981383 Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: Unable to use or turn on bluetooth ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 12 04:11:50 2022 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-02-06 (155 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) InterestingModules: rfcomm bnep btusb bluetooth MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_F543MA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=a1980608-1f3e-4705-9432-421aa3851fe6 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: bluez Title: package bluez 5.53-0ubuntu3.6 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540MA.314 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540MA.314:bd10/01/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_F543MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540MA_F543MA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: C0:E4:34:24:68:A6 ACL
[Kernel-packages] [Bug 1980893] Re: Linux, Ubuntu, 22.04, dell-bto-jammy-jellyfish-X10-20220519-17, SFP LAN can not work after system restart
Closed by invalid project, will open another one to track. ** 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/1980893 Title: Linux,Ubuntu,22.04,dell-bto-jammy-jellyfish-X10-20220519-17,SFP LAN can not work after system restart Status in linux package in Ubuntu: Invalid Bug description: [Reproduce Steps] 1. Disable Secure Boot in BIOS and USB install Ubuntu 22.04 X-Rev image "dell-bto-jammy-jellyfish-X10-20220519-17" 2. Run command "sudo apt update" and then "sudo apt install linux-oem-22.04" to get the latest oem kernel version 5.17.0-1012-oem test environment. 2. Connect SFP Fiber LAN or SFP RJ45 LAN cable to Troy JSL SFP connector 3. Check the SFP LAN establish correctly and Network is workable 4. Restart the system (pressing the top right-hand power button) and check the SFP LAN function re-connect successfully [Results] Expected Result: The SFP LAN can auto connect successfully after system restart Actual Result: The SFP LAN connection can not re-establish after restart and have to recover SFP LAN function after cold boot. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU: Troy JSL Thin Client SFP SKU BIOS Version: 1.0.13 Image/Manifest: Ubuntu 22.04 (dell-bto-jammy-jellyfish-X10-20220519-17.iso) CPU: Jasper Lake N6005 Pentium/N5105 Celeron GPU: Intel® UHD Graphics Realtek LAN:1Gb Failure rate: 100% --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 965 F pulseaudio CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish+X10 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-06 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp1s0no wireless extensions. enp2s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 04ca:00bd Lite-On Technology Corp. Dell Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Dell Inc. OptiPlex 3000 Thin Client Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1012-oem root=UUID=65da961f-f1e5-4c2d-a1da-789a662548a3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.17.0-1012.13-oem 5.17.9 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.17.0-1012-oem N/A linux-backports-modules-5.17.0-1012-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy Uname: Linux 5.17.0-1012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2022 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd06/30/2022:br1.0:svnDellInc.:pnOptiPlex3000ThinClient:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0AE8: dmi.product.family: Optiplex Thin Client 3000 Series dmi.product.name: OptiPlex 3000 Thin Client dmi.product.sku: 0AE8 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980893/+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 1981185] Status changed to Confirmed
This change was made by a bot. ** 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/1981185 Title: soft lockup -CPU#11 struck for 186s! Status in linux package in Ubuntu: Confirmed Bug description: bad: scheduling from the idle thread! firmware Bug:TPM interrupted not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: socwatch2_14 sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 11 11:52:54 2022 InstallationDate: Installed on 2021-03-01 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-07-11 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2022-07-01T11:19:47.062167 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981185/+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 1981185] Re: soft lockup -CPU#11 struck for 186s!
** Package changed: ubuntu-release-upgrader (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/1981185 Title: soft lockup -CPU#11 struck for 186s! Status in linux package in Ubuntu: New Bug description: bad: scheduling from the idle thread! firmware Bug:TPM interrupted not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: socwatch2_14 sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 11 11:52:54 2022 InstallationDate: Installed on 2021-03-01 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-07-11 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2022-07-01T11:19:47.062167 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981185/+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 1981185] [NEW] soft lockup -CPU#11 struck for 186s!
You have been subscribed to a public bug: bad: scheduling from the idle thread! firmware Bug:TPM interrupted not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.38 ProcVersionSignature: Ubuntu 5.15.0-33.34~20.04.1-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: socwatch2_14 sep5 socperf3 pax ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Jul 11 11:52:54 2022 InstallationDate: Installed on 2021-03-01 (496 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to focal on 2022-07-11 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2022-07-01T11:19:47.062167 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal third-party-packages wayland-session -- soft lockup -CPU#11 struck for 186s! https://bugs.launchpad.net/bugs/1981185 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 1786013] Autopkgtest regression report (linux-meta-gke-5.4/5.4.0.1077.83~18.04.39)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1077.83~18.04.39) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/8.045.08-2ubuntu1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) dpdk/17.11.10-0ubuntu0.1 (amd64) lxd/3.0.3-0ubuntu1~18.04.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1981380] Re: compile error in ima.h when CONFIG_IMA_LSM_RULES is not set
I think we can skip the apport-collect in this case? I was manually
building the kernel fwiw.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1981380
Title:
compile error in ima.h when CONFIG_IMA_LSM_RULES is not set
Status in linux package in Ubuntu:
Confirmed
Bug description:
Seems to be a typo strcut -> struct (upstream does not have a struct
argument).
```
diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
index 783a3b2fc826..c1d10bbd7c8a 100644
--- a/security/integrity/ima/ima.h
+++ b/security/integrity/ima/ima.h
@@ -437,7 +437,7 @@ static inline void ima_filter_rule_free(void *lsmrule)
{
}
-static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 field, u32
op,
+static inline int ima_filter_rule_match(struct lsmblob *blob, u32 field, u32
op,
void *lsmrule)
{
return -EINVAL;
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981380/+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 1981380] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1981380
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** 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/1981380
Title:
compile error in ima.h when CONFIG_IMA_LSM_RULES is not set
Status in linux package in Ubuntu:
Incomplete
Bug description:
Seems to be a typo strcut -> struct (upstream does not have a struct
argument).
```
diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
index 783a3b2fc826..c1d10bbd7c8a 100644
--- a/security/integrity/ima/ima.h
+++ b/security/integrity/ima/ima.h
@@ -437,7 +437,7 @@ static inline void ima_filter_rule_free(void *lsmrule)
{
}
-static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 field, u32
op,
+static inline int ima_filter_rule_match(struct lsmblob *blob, u32 field, u32
op,
void *lsmrule)
{
return -EINVAL;
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981380/+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 1981380] [NEW] compile error in ima.h when CONFIG_IMA_LSM_RULES is not set
Public bug reported:
Seems to be a typo strcut -> struct (upstream does not have a struct
argument).
```
diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
index 783a3b2fc826..c1d10bbd7c8a 100644
--- a/security/integrity/ima/ima.h
+++ b/security/integrity/ima/ima.h
@@ -437,7 +437,7 @@ static inline void ima_filter_rule_free(void *lsmrule)
{
}
-static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 field, u32
op,
+static inline int ima_filter_rule_match(struct lsmblob *blob, u32 field, u32
op,
void *lsmrule)
{
return -EINVAL;
```
** Affects: linux (Ubuntu)
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/1981380
Title:
compile error in ima.h when CONFIG_IMA_LSM_RULES is not set
Status in linux package in Ubuntu:
New
Bug description:
Seems to be a typo strcut -> struct (upstream does not have a struct
argument).
```
diff --git a/security/integrity/ima/ima.h b/security/integrity/ima/ima.h
index 783a3b2fc826..c1d10bbd7c8a 100644
--- a/security/integrity/ima/ima.h
+++ b/security/integrity/ima/ima.h
@@ -437,7 +437,7 @@ static inline void ima_filter_rule_free(void *lsmrule)
{
}
-static inline int ima_filter_rule_match(strcut lsmblob *blob, u32 field, u32
op,
+static inline int ima_filter_rule_match(struct lsmblob *blob, u32 field, u32
op,
void *lsmrule)
{
return -EINVAL;
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981380/+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 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
I edited /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf changing wifi.powersave = 3 to wifi.powersave = 2. This improved the stability of the WiFi and appears to have stopped the continuous 'roaming'. I will keep an eye on the dhcp logs at home and report back if the 'ping during roam' continues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975]
[Kernel-packages] [Bug 1981375] [NEW] Jammy update: v5.15.42 upstream stable release
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:
v5.15.42 upstream stable release
from git://git.kernel.org/
usb: gadget: fix race when gadget driver register via ioctl
io_uring: arm poll for non-nowait files
kernel/resource: Introduce request_mem_region_muxed()
i2c: piix4: Replace hardcoded memory map size with a #define
i2c: piix4: Move port I/O region request/release code into functions
i2c: piix4: Move SMBus controller base address detect into function
i2c: piix4: Move SMBus port selection into function
i2c: piix4: Add EFCH MMIO support to region request and release
i2c: piix4: Add EFCH MMIO support to SMBus base address detect
i2c: piix4: Add EFCH MMIO support for SMBus port select
i2c: piix4: Enable EFCH MMIO for Family 17h+
Watchdog: sp5100_tco: Move timer initialization into function
Watchdog: sp5100_tco: Refactor MMIO base address initialization
Watchdog: sp5100_tco: Add initialization using EFCH MMIO
Watchdog: sp5100_tco: Enable Family 17h+ CPUs
mm/kfence: reset PG_slab and memcg_data before freeing __kfence_pool
Revert "drm/i915/opregion: check port number bounds for SWSCI display power
state"
rtc: fix use-after-free on device removal
rtc: pcf2127: fix bug when reading alarm registers
um: Cleanup syscall_handler_t definition/cast, fix warning
Input: add bounds checking to input_set_capability()
Input: stmfts - fix reference leak in stmfts_input_open
nvme-pci: add quirks for Samsung X5 SSDs
gfs2: Disable page faults during lockless buffered reads
rtc: sun6i: Fix time overflow handling
crypto: stm32 - fix reference leak in stm32_crc_remove
crypto: x86/chacha20 - Avoid spurious jumps to other functions
s390/traps: improve panic message for translation-specification exception
s390/pci: improve zpci_dev reference counting
vhost_vdpa: don't setup irq offloading when irq_num < 0
tools/virtio: compile with -pthread
nvmet: use a private workqueue instead of the system workqueue
nvme-multipath: fix hang when disk goes live over reconnect
rtc: mc146818-lib: Fix the AltCentury for AMD platforms
fs: fix an infinite loop in iomap_fiemap
MIPS: lantiq: check the return value of kzalloc()
drbd: remove usage of list iterator variable after loop
platform/chrome: cros_ec_debugfs: detach log reader wq from devm
ARM: 9191/1: arm/stacktrace, kasan: Silence KASAN warnings in unwind_frame()
nilfs2: fix lockdep warnings in page operations for btree nodes
nilfs2: fix lockdep warnings during disk space reclamation
ALSA: usb-audio: Restore Rane SL-1 quirk
ALSA: wavefront: Proper check of get_user() error
ALSA: hda/realtek: Add quirk for TongFang devices with pop noise
perf: Fix sys_perf_event_open() race against self
selinux: fix bad cleanup on error in hashtab_duplicate()
Fix double fget() in vhost_net_set_backend()
PCI/PM: Avoid putting Elo i2 PCIe Ports in D3cold
Revert "can: m_can: pci: use custom bit timings for Elkhart Lake"
KVM: x86/mmu: Update number of zapped pages even if page list is stable
arm64: paravirt: Use RCU read locks to guard stolen_time
arm64: mte: Ensure the cleared tags are visible before setting the PTE
crypto: qcom-rng - fix infinite loop on requests not multiple of WORD_SZ
libceph: fix potential use-after-free on linger ping and resends
drm/i915/dmc: Add MMIO range restrictions
drm/dp/mst: fix a possible memory leak in fetch_monitor_name()
dma-buf: fix use of DMA_BUF_SET_NAME_{A,B} in userspace
dma-buf: ensure unique directory name for dmabuf stats
ARM: dts: aspeed-g6: remove FWQSPID group in pinctrl dtsi
pinctrl: pinctrl-aspeed-g6: remove FWQSPID group in pinctrl
ARM: dts: aspeed-g6: fix SPI1/SPI2 quad pin group
ARM: dts: aspeed: Add ADC for AST2600 and enable for Rainier and Everest
ARM: dts: aspeed: Add secure boot controller node
ARM: dts: aspeed: Add video engine to g6
pinctrl: mediatek: mt8365: fix IES control pins
ALSA: hda - fix unused Realtek function when PM is not enabled
net: ipa: record proper RX transaction count
net: macb: Increment rx bd head after allocating skb and buffer
xfrm: rework default policy structure
xfrm: fix "disable_policy" flag use when arriving from different devices
net/sched: act_pedit: sanitize shift argument before usage
netfilter: flowtable: fix excessive hw offload attempts after failure
netfilter: nft_flow_offload: skip dst neigh lookup for ppp devices
net: fix dev_fill_forward_path with pppoe + bridge
netfilter: nft_flow_offload: fix offload with pppoe + vlan
net: systemport: Fix an error handling path in bcm_sysport_probe()
net: vmxnet3: fix possible use-after-free bugs in vmxnet3_rq_alloc_rx_buf()
net: vmxnet3: fix possible NULL
[Kernel-packages] [Bug 1981364] Re: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
The bug was confirmed on the linked ticket. -- 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/1981364 Title: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop Status in linux package in Ubuntu: Confirmed Bug description: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981364/+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 1981364] Re: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1981364 Title: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop Status in linux package in Ubuntu: Confirmed Bug description: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981364/+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 1981366] [NEW] Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
Public bug reported: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Jul 11 20:11:17 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251 Jul 11 20:11:17 gateway-ycs dhcpd: Abandoning IP address 172.16.251.221: pinged before offer Jul 11 20:11:19 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c3:f9:42 via br_v251 Jul 11 20:11:20 gateway-ycs dhcpd: DHCPOFFER on 172.16.251.220 to 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251 Jul 11 20:11:20 gateway-ycs dhcpd: DHCPREQUEST for 172.16.251.220 (172.16.251.254) from 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251 Jul 11 20:11:20 gateway-ycs dhcpd: DHCPACK on 172.16.251.220 to 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251
[Kernel-packages] [Bug 1981366] Re: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam
** Also affects: network-manager (Ubuntu) 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Jul 11 20:11:17 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251 Jul 11 20:11:17
[Kernel-packages] [Bug 1981366] Status changed to Confirmed
This change was made by a bot. ** 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/1981366 Title: Intel AX201 / Thinkpad X1 Carbon Gen 9 returns ping during WiFi roam Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: My Thinkpad X1 Carbon Gen 9 has started to return pings in the middle of WiFi roam events which is causing the IP address to change every time it roams on the WiFi network. This is a huge problem for me because I install WiFi networks for a living but in general it causes every TCP connection over IPv4 to die every time the laptop roams to a new wifi cell. 00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20) I tried kernel 5.15.0-40-generic and mainline kernel 5.17 and 5.18. Jul 11 20:11:15 littlebrat kernel: [620752.349053] wlp0s20f3: authenticate with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat kernel: [620752.349074] wlp0s20f3: Invalid HE elem, Disable HE Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0110] device (wlp0s20f3): supplicant interface state: completed -> authenticating Jul 11 20:11:15 littlebrat kernel: [620752.354373] wlp0s20f3: send auth to 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> authenticating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0111] device (wlp0s20f3): ip:dhcp4: restarting Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): canceled DHCP transaction Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0112] dhcp4 (wlp0s20f3): state changed no lease Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0113] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Trying to associate with 86:2a:a8:8b:05:cb (SSID='YesComputerSolutions-Private' freq=5540 MHz) Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0463] device (wlp0s20f3): supplicant interface state: authenticating -> associating Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0464] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating Jul 11 20:11:15 littlebrat kernel: [620752.390520] wlp0s20f3: authenticated Jul 11 20:11:15 littlebrat kernel: [620752.393074] wlp0s20f3: associate with 86:2a:a8:8b:05:cb (try 1/3) Jul 11 20:11:15 littlebrat kernel: [620752.397915] wlp0s20f3: RX ReassocResp from 86:2a:a8:8b:05:cb (capab=0x1511 status=0 aid=4) Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: Associated with 86:2a:a8:8b:05:cb Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Jul 11 20:11:15 littlebrat kernel: [620752.406395] wlp0s20f3: associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (wlp0s20f3): supplicant interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0779] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> associated Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0799] device (wlp0s20f3): supplicant interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0800] device (p2p-dev-wlp0s20f3): supplicant management interface state: associated -> 4way_handshake Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: WPA: Key negotiation completed with 86:2a:a8:8b:05:cb [PTK=CCMP GTK=CCMP] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to 86:2a:a8:8b:05:cb completed [id=0 id_str=] Jul 11 20:11:15 littlebrat discord_discord.desktop[4119]: [2022-07-11 20:11:15.091] [4119] (discord.cpp:551): JS console: ["%c[GatewaySocket]","Performing an expedited heartbeat reason: network detected online."] Jul 11 20:11:15 littlebrat wpa_supplicant[1550]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-66 noise= txrate=26000 Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0970] device (wlp0s20f3): supplicant interface state: 4way_handshake -> completed Jul 11 20:11:15 littlebrat NetworkManager[1519]: [1657566675.0975] device (p2p-dev-wlp0s20f3): supplicant management interface state: 4way_handshake -> completed Jul 11 20:11:17 gateway-ycs dhcpd: DHCPDISCOVER from 5c:e4:2a:c3:f9:42 (littlebrat) via br_v251 Jul 11 20:11:17
[Kernel-packages] [Bug 1981364] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1981364 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1981364 Title: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop Status in linux package in Ubuntu: Incomplete Bug description: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981364/+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 1975593] Re: rename DKMS compat module for potential name collision
This bug was fixed in the package backport-iwlwifi-dkms - 9858-0ubuntu6 --- backport-iwlwifi-dkms (9858-0ubuntu6) kinetic; urgency=medium [ You-Sheng Yang ] * install iwlmei when compiled against kernel >= 5.17. (LP: #1975573) * compat: rename built module to iwlwifi-compat.ko (LP: #1975593) [ Dimitri John Ledkov ] * dkms: bump obsoleted by to 5.20.0 kernel * backport: patch backport headers to support CFI (LP: #1980484) -- Dimitri John Ledkov Mon, 11 Jul 2022 16:46:24 +0100 ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1975593 Title: rename DKMS compat module for potential name collision Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: While we're to build Intel DG2 DKMS in bug 1971712, the newly created binary package would carry a module named compat, which is also found in backport-iwlwifi-dkms because they're both generated by linux- backports project. To avoid name collision, they shall be renamed as iwlwifi-compat and i915-compat correspondingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1975593/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
This bug was fixed in the package backport-iwlwifi-dkms - 9858-0ubuntu6 --- backport-iwlwifi-dkms (9858-0ubuntu6) kinetic; urgency=medium [ You-Sheng Yang ] * install iwlmei when compiled against kernel >= 5.17. (LP: #1975573) * compat: rename built module to iwlwifi-compat.ko (LP: #1975593) [ Dimitri John Ledkov ] * dkms: bump obsoleted by to 5.20.0 kernel * backport: patch backport headers to support CFI (LP: #1980484) -- Dimitri John Ledkov Mon, 11 Jul 2022 16:46:24 +0100 ** Changed in: backport-iwlwifi-dkms (Ubuntu Kinetic) 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1981345] Re: jammy: override starfive and allwinner from universe to main
Override component to main linux-allwinner-5.17 5.17.0-1002.2 in jammy: universe/devel -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy amd64: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy arm64: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy armhf: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy i386: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy ppc64el: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy riscv64: universe/devel/optional/100% -> main linux-allwinner-5.17-headers-5.17.0-1002 5.17.0-1002.2 in jammy s390x: universe/devel/optional/100% -> main linux-allwinner-5.17-tools-5.17.0-1002 5.17.0-1002.2 in jammy riscv64: universe/devel/optional/100% -> main linux-buildinfo-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/kernel/optional/100% -> main linux-headers-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/devel/optional/100% -> main linux-image-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/kernel/optional/100% -> main linux-modules-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/kernel/optional/100% -> main linux-modules-extra-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/kernel/optional/100% -> main linux-tools-5.17.0-1002-allwinner 5.17.0-1002.2 in jammy riscv64: universe/devel/optional/100% -> main linux-meta-allwinner-5.17 5.17.0.1002.4 in jammy: universe/devel -> main linux-allwinner 5.17.0.1002.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-headers-allwinner 5.17.0.1002.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-image-allwinner 5.17.0.1002.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-tools-allwinner 5.17.0.1002.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-starfive-5.17 5.17.0-1003.4 in jammy: universe/devel -> main linux-buildinfo-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-headers-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/devel/optional/100% -> main linux-image-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-modules-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-modules-extra-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy amd64: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy arm64: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy armhf: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy i386: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy ppc64el: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy riscv64: universe/devel/optional/100% -> main linux-starfive-5.17-headers-5.17.0-1003 5.17.0-1003.4 in jammy s390x: universe/devel/optional/100% -> main linux-starfive-5.17-tools-5.17.0-1003 5.17.0-1003.4 in jammy riscv64: universe/devel/optional/100% -> main linux-tools-5.17.0-1003-starfive 5.17.0-1003.4 in jammy riscv64: universe/devel/optional/100% -> main linux-meta-starfive-5.17 5.17.0.1003.4 in jammy: universe/devel -> main linux-headers-starfive 5.17.0.1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-image-starfive 5.17.0.1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-starfive 5.17.0.1003.4 in jammy riscv64: universe/kernel/optional/100% -> main linux-tools-starfive 5.17.0.1003.4 in jammy riscv64: universe/kernel/optional/100% -> main 40 publications overridden. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: New Status in linux-meta-allwinner-5.17 package in Ubuntu: New Status in linux-meta-starfive-5.17 package in Ubuntu: New Status in linux-starfive-5.17 package in Ubuntu: New Status in linux-allwinner-5.17 source package in Jammy: New Status in linux-meta-allwinner-5.17 source package in Jammy: New Status in linux-meta-starfive-5.17 source package in Jammy: New Status in linux-starfive-5.17 source package in Jammy: New Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug
[Kernel-packages] [Bug 1910113] Re: zfsutils-linux does not match kernel version
*** This bug is a duplicate of bug 1939210 *** https://bugs.launchpad.net/bugs/1939210 ** This bug has been marked a duplicate of bug 1939210 When using HWE, zfs-kmod and zfs user tools versions must match -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1910113 Title: zfsutils-linux does not match kernel version Status in zfs-linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04.5 running a "linux-image-generic-hwe-18.04 5.4.0.53.59~18.04.47" kernel. This kernel comes with ZFS 0.8.3-1ubuntu12.4. Sadly, I'm unable to use features included in zfs 0.8 release (ex. TRIM support) because zfsutils-linux is stuck on version 0.7.5-1ubuntu16.10. Can we please package zfsutils-linux that will match ZFS versions provided with hwe and hwe-edge kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1910113/+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 1980957] Re: RM linux-nezha-5.17 and linux-meta-nezha-5.17 from jammy
Removing packages from jammy-proposed: linux-nezha-5.17 5.17.0-1001.1 in jammy linux-buildinfo-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-headers-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-image-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-modules-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-modules-extra-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy amd64 linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy arm64 linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy armhf linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy i386 linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy ppc64el linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy riscv64 linux-nezha-5.17-headers-5.17.0-1001 5.17.0-1001.1 in jammy s390x linux-nezha-5.17-tools-5.17.0-1001 5.17.0-1001.1 in jammy riscv64 linux-tools-5.17.0-1001-nezha 5.17.0-1001.1 in jammy riscv64 linux-meta-nezha-5.17 5.17.0.1001.2 in jammy linux-headers-nezha 5.17.0.1001.2 in jammy riscv64 linux-image-nezha 5.17.0.1001.2 in jammy riscv64 linux-nezha 5.17.0.1001.2 in jammy riscv64 linux-tools-nezha 5.17.0.1001.2 in jammy riscv64 Comment: Replaced by linux-allwinner LP: #1980957 2 packages successfully removed. ** Changed in: linux-meta-nezha-5.17 (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-nezha-5.17 (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-meta-nezha-5.17 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-nezha-5.17 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nezha-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1980957 Title: RM linux-nezha-5.17 and linux-meta-nezha-5.17 from jammy Status in linux-meta-nezha-5.17 package in Ubuntu: Fix Released Status in linux-nezha-5.17 package in Ubuntu: Fix Released Bug description: RM linux-nezha-5.17 and linux-meta-nezha-5.17 Instead we are using -allwinner- name now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nezha-5.17/+bug/1980957/+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 1981364] [NEW] ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
Public bug reported: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. ** Affects: linux (Ubuntu) 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/1981364 Title: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop Status in linux package in Ubuntu: New Bug description: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981364/+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 1970586] Re: No sound support on Linux AWS/Azure kernels (but supported on GCP)
This bug was fixed in the package linux-azure - 5.15.0-1014.17
---
linux-azure (5.15.0-1014.17) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1014.17 -proposed tracker (LP: #1979425)
* nbd: requests can become stuck when disconnecting from server with qemu-nbd
(LP: #1896350)
- nbd: don't handle response without a corresponding request message
- nbd: make sure request completion won't concurrent
- nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed
- nbd: fix io hung while disconnecting device
* SGX fixes for 5.15 Azure tuned kernel (LP: #1979541)
- x86/sgx: Disconnect backing page references from dirty status
- x86/sgx: Mark PCMD page as dirty when modifying contents
- x86/sgx: Obtain backing storage page with enclave mutex held
- x86/sgx: Fix race between reclaimer and page fault handler
- x86/sgx: Ensure no data in PCMD page after truncate
* No sound support on Linux AWS/Azure kernels (but supported on GCP)
(LP: #1970586)
- [Config] azure: CONFIG_SOUND=m
[ Ubuntu: 5.15.0-41.44 ]
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel
[Kernel-packages] [Bug 1979541] Re: SGX fixes for 5.15 Azure tuned kernel
This bug was fixed in the package linux-azure - 5.15.0-1014.17
---
linux-azure (5.15.0-1014.17) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1014.17 -proposed tracker (LP: #1979425)
* nbd: requests can become stuck when disconnecting from server with qemu-nbd
(LP: #1896350)
- nbd: don't handle response without a corresponding request message
- nbd: make sure request completion won't concurrent
- nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed
- nbd: fix io hung while disconnecting device
* SGX fixes for 5.15 Azure tuned kernel (LP: #1979541)
- x86/sgx: Disconnect backing page references from dirty status
- x86/sgx: Mark PCMD page as dirty when modifying contents
- x86/sgx: Obtain backing storage page with enclave mutex held
- x86/sgx: Fix race between reclaimer and page fault handler
- x86/sgx: Ensure no data in PCMD page after truncate
* No sound support on Linux AWS/Azure kernels (but supported on GCP)
(LP: #1970586)
- [Config] azure: CONFIG_SOUND=m
[ Ubuntu: 5.15.0-41.44 ]
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel
[Kernel-packages] [Bug 1971205] Re: CVE-2022-25258 and CVE-2022-25375
Fixed in linux-bluefield 5.4.0-1040.44. ** Changed in: linux-bluefield (Ubuntu) Status: Fix Committed => Fix Released -- 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/1971205 Title: CVE-2022-25258 and CVE-2022-25375 Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.13 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Fix Released Status in linux-azure-5.13 package in Ubuntu: Fix Released Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-dell300x package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: Fix Released Status in linux-gcp-5.13 package in Ubuntu: Fix Released Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Released Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.13 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.13 package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-riscv package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Bug description: These packages are vulnerable to CVE-2022-25258 and CVE-2022-25375 in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker. Please release fixed packages. Debian released an advisory on March 7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1971205/+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 1976399] Re: focal/azure: The console log of ARM64 Ubuntu 18.04 has duplicate output
This bug was fixed in the package linux-azure - 5.4.0-1086.91 --- linux-azure (5.4.0-1086.91) focal; urgency=medium * focal/linux-azure: 5.4.0-1086.91 -proposed tracker (LP: #1979462) * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - [Config] azure: updateconfigs for NVM, NVM_PBLK * focal/azure: The console log of ARM64 Ubuntu 18.04 has duplicate output (LP: #1976399) - printk: Move console matching logic into a separate function - printk: Fix preferred console selection with multiple matches * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - blk-mq: blk-mq: provide forced completion method - blk-mq: move failure injection out of blk_mq_complete_request - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Azure 5.4: vDSO broken with 5.4.0-1075-azure (LP: #1977753) - Revert "clocksource/drivers/hyper-v: Handle vDSO differences inline" [ Ubuntu: 5.4.0-122.138 ] * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04
[Kernel-packages] [Bug 1974096] Re: cls_flower: Fix inability to match GRE/IPIP packets
This bug was fixed in the package linux-bluefield - 5.4.0-1040.44 --- linux-bluefield (5.4.0-1040.44) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1040.44 -proposed tracker (LP: #1978639) * fix ref leak when switching zones (LP: #1979009) - net/sched: act_ct: fix ref leak when switching zones * Fix XFRM flags validity check (LP: #1978967) - SAUCE: net/xfrm: Fix XFRM flags validity check [ Ubuntu: 5.4.0-121.137 ] * focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.05.30) * CVE-2022-28388 - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error path * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) (LP: #1871015) - selftests: net: test_vxlan_under_vrf: fix HV connectivity test * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 (LP: #1974433) - s390/cpumf: add new extended counter set for IBM z16 * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup (LP: #1974017) - KVM: s390: vsie/gmap: reduce gmap_rmap overhead * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z (LP: #1968096) - NFS: Fix up nfs_ctx_key_to_expire() [ Ubuntu: 5.4.0-120.136 ] * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166 - cpu/speculation: Add prototype for cpu_show_srbds() - x86/cpu: Add Jasper Lake to Intel family - x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU family - x86/cpu: Add another Alder Lake CPU to the Intel family - Documentation: Add documentation for Processor MMIO Stale Data - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug - x86/speculation: Add a common function for MD_CLEAR mitigation update - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data - x86/speculation/srbds: Update SRBDS mitigation selection - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS - KVM: x86/speculation: Disable Fill buffer clear within guests - x86/speculation/mmio: Print SMT warning -- Zachary Tahenakos Tue, 21 Jun 2022 13:59:23 -0400 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21123 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21125 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21166 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28388 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974096 Title: cls_flower: Fix inability to match GRE/IPIP packets Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: * Explain the bug When a packet of a new flow arrives in openvswitch kernel module, it dissects the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw- offload configuration is enabled, the daemon creates a new TC flower entry to bypass openvswitch kernel module for the flow (TC flower can also offload flows to NICs but this time that does not matter). In this processing flow, I found the following issue in cases of GRE/IPIP packets. When ovs_flow_key_extract() in openvswitch module parses a packet of a new GRE (or IPIP) flow received on non-tunneling vports, it extracts information of the outer IP header for ip_proto/src_ip/dst_ip match keys. This means ovs-vswitchd creates a TC flower entry with IP protocol/addresses match keys whose values are those of the outer IP header. OTOH, TC flower, which uses flow_dissector (different parser from openvswitch module), extracts information of the inner IP header. * How to test The following flow is an example to describe the issue in more detail. <--- Outer IP -> <-- Inner IP --> +--+--+--+--+--+--+ | ip_proto | src_ip | dst_ip | ip_proto | src_ip | dst_ip | | 47 (GRE) | 192.168.10.1 | 192.168.10.2 | 6 (TCP) | 10.0.0.1 | 10.0.0.2 | +--+--+--+--+--+--+ In this case, TC flower entry and extracted information are shown as below:
[Kernel-packages] [Bug 1974241] Re: mlxbf_gige: revert "add interrupt counts" commit
This bug was fixed in the package linux-bluefield - 5.4.0-1040.44 --- linux-bluefield (5.4.0-1040.44) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1040.44 -proposed tracker (LP: #1978639) * fix ref leak when switching zones (LP: #1979009) - net/sched: act_ct: fix ref leak when switching zones * Fix XFRM flags validity check (LP: #1978967) - SAUCE: net/xfrm: Fix XFRM flags validity check [ Ubuntu: 5.4.0-121.137 ] * focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.05.30) * CVE-2022-28388 - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error path * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) (LP: #1871015) - selftests: net: test_vxlan_under_vrf: fix HV connectivity test * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 (LP: #1974433) - s390/cpumf: add new extended counter set for IBM z16 * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup (LP: #1974017) - KVM: s390: vsie/gmap: reduce gmap_rmap overhead * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z (LP: #1968096) - NFS: Fix up nfs_ctx_key_to_expire() [ Ubuntu: 5.4.0-120.136 ] * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166 - cpu/speculation: Add prototype for cpu_show_srbds() - x86/cpu: Add Jasper Lake to Intel family - x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU family - x86/cpu: Add another Alder Lake CPU to the Intel family - Documentation: Add documentation for Processor MMIO Stale Data - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug - x86/speculation: Add a common function for MD_CLEAR mitigation update - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data - x86/speculation/srbds: Update SRBDS mitigation selection - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS - KVM: x86/speculation: Disable Fill buffer clear within guests - x86/speculation/mmio: Print SMT warning -- Zachary Tahenakos Tue, 21 Jun 2022 13:59:23 -0400 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21123 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21125 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21166 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28388 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974241 Title: mlxbf_gige: revert "add interrupt counts" commit Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: SRU Justification: [Impact] There is a mlxbf_gige driver commit (ed0dd97e64a5) which pertains to "UBUNTU: SAUCE: mlxbf_gige: add interrupt counts to "ethtool -S". This logic is modified in upstream Linux, so this SAUCE commit will need to be reverted. [Fix] The fix is to revert this driver commit. [Test Case] With this commit reverted the driver should function as before (e.g. probe succeeds, oob_net0 link up, etc) EXCEPT that the output of "ethtool -S" will no longer show the interrupt counts. [Regression Potential] The amount of driver logic being reverted is quite small, so no potential for creating a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974241/+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 1977753] Re: Azure 5.4: vDSO broken with 5.4.0-1075-azure
This bug was fixed in the package linux-azure - 5.4.0-1086.91 --- linux-azure (5.4.0-1086.91) focal; urgency=medium * focal/linux-azure: 5.4.0-1086.91 -proposed tracker (LP: #1979462) * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - [Config] azure: updateconfigs for NVM, NVM_PBLK * focal/azure: The console log of ARM64 Ubuntu 18.04 has duplicate output (LP: #1976399) - printk: Move console matching logic into a separate function - printk: Fix preferred console selection with multiple matches * nbd: requests can become stuck when disconnecting from server with qemu-nbd (LP: #1896350) - blk-mq: blk-mq: provide forced completion method - blk-mq: move failure injection out of blk_mq_complete_request - nbd: don't handle response without a corresponding request message - nbd: make sure request completion won't concurrent - nbd: don't clear 'NBD_CMD_INFLIGHT' flag if request is not completed - nbd: fix io hung while disconnecting device * Azure 5.4: vDSO broken with 5.4.0-1075-azure (LP: #1977753) - Revert "clocksource/drivers/hyper-v: Handle vDSO differences inline" [ Ubuntu: 5.4.0-122.138 ] * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04
[Kernel-packages] [Bug 1974246] Re: mlxbf_gige: increase MDIO polling rate
This bug was fixed in the package linux-bluefield - 5.4.0-1040.44 --- linux-bluefield (5.4.0-1040.44) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1040.44 -proposed tracker (LP: #1978639) * fix ref leak when switching zones (LP: #1979009) - net/sched: act_ct: fix ref leak when switching zones * Fix XFRM flags validity check (LP: #1978967) - SAUCE: net/xfrm: Fix XFRM flags validity check [ Ubuntu: 5.4.0-121.137 ] * focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.05.30) * CVE-2022-28388 - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error path * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) (LP: #1871015) - selftests: net: test_vxlan_under_vrf: fix HV connectivity test * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 (LP: #1974433) - s390/cpumf: add new extended counter set for IBM z16 * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup (LP: #1974017) - KVM: s390: vsie/gmap: reduce gmap_rmap overhead * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z (LP: #1968096) - NFS: Fix up nfs_ctx_key_to_expire() [ Ubuntu: 5.4.0-120.136 ] * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166 - cpu/speculation: Add prototype for cpu_show_srbds() - x86/cpu: Add Jasper Lake to Intel family - x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU family - x86/cpu: Add another Alder Lake CPU to the Intel family - Documentation: Add documentation for Processor MMIO Stale Data - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug - x86/speculation: Add a common function for MD_CLEAR mitigation update - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data - x86/speculation/srbds: Update SRBDS mitigation selection - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS - KVM: x86/speculation: Disable Fill buffer clear within guests - x86/speculation/mmio: Print SMT warning -- Zachary Tahenakos Tue, 21 Jun 2022 13:59:23 -0400 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21123 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21125 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21166 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28388 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1974246 Title: mlxbf_gige: increase MDIO polling rate Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: SRU Justification: [Impact] There is MDIO logic within the mlxbf_gige driver that currently polls for completed transactions every 100us. This has been reviewed and tested in the lab and found to be inefficient. [Fix] The fix is to modify the driver logic to increase the MDIO polling rate to 5us. With this change the amount of time spent waiting for the MDIO BUSY signal to de-assert drops from ~100us to ~27us for each operation. [Test Case] The driver should function as before, specifically: * driver probes successfully * oob_net0 link comes up, as seen with "ifconfig -a" * reset and power cycle testing toggle PHY hardware, and oob_net0 link still comes up [Regression Potential] This change affects all MDIO transactions to the board-level PHY device, and as such, could cause a regression with PHY communications. However, this change has been heavily tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1974246/+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 1978967] Re: Fix XFRM flags validity check
This bug was fixed in the package linux-bluefield - 5.4.0-1040.44 --- linux-bluefield (5.4.0-1040.44) focal; urgency=medium * focal/linux-bluefield: 5.4.0-1040.44 -proposed tracker (LP: #1978639) * fix ref leak when switching zones (LP: #1979009) - net/sched: act_ct: fix ref leak when switching zones * Fix XFRM flags validity check (LP: #1978967) - SAUCE: net/xfrm: Fix XFRM flags validity check [ Ubuntu: 5.4.0-121.137 ] * focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2022.05.30) * CVE-2022-28388 - can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error path * test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM connectivity through VXLAN (underlay in the default VRF) [FAIL]) (LP: #1871015) - selftests: net: test_vxlan_under_vrf: fix HV connectivity test * [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16 (LP: #1974433) - s390/cpumf: add new extended counter set for IBM z16 * [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in stalls during cleanup (LP: #1974017) - KVM: s390: vsie/gmap: reduce gmap_rmap overhead * [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z (LP: #1968096) - NFS: Fix up nfs_ctx_key_to_expire() [ Ubuntu: 5.4.0-120.136 ] * CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166 - cpu/speculation: Add prototype for cpu_show_srbds() - x86/cpu: Add Jasper Lake to Intel family - x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel CPU family - x86/cpu: Add another Alder Lake CPU to the Intel family - Documentation: Add documentation for Processor MMIO Stale Data - x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug - x86/speculation: Add a common function for MD_CLEAR mitigation update - x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data - x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations - x86/speculation/mmio: Enable CPU Fill buffer clearing on idle - x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data - x86/speculation/srbds: Update SRBDS mitigation selection - x86/speculation/mmio: Reuse SRBDS mitigation for SBDS - KVM: x86/speculation: Disable Fill buffer clear within guests - x86/speculation/mmio: Print SMT warning -- Zachary Tahenakos Tue, 21 Jun 2022 13:59:23 -0400 ** Changed in: linux-bluefield (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21123 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21125 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21166 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28388 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1978967 Title: Fix XFRM flags validity check Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Released Bug description: * Explain the bug(s) commit a3ca11eec78 introduced a flags validity check for XFRM , the check excluded flag XFRM_OFFLOAD_FULL from the check hence the flag is being blocked from getting to the kernel space. The above is preventing IPsec states from being added with the full_offload option. * Brief explanation of fixes The commit restricted unknown flags from being configured from user space by adding a validity check, since the Bluefield feature added such a flag , the fix expands the validity check to include this flag which is added only in Bluefield kernel . * How to test Need to make sure that configuring IPsec with full_offload option using IProute2 can be done successfully with no issues. (Not getting the RTNETLINK answers: Invalid argument error anymore) * What it could break. NA, this patch allows a specific flag to get passed to the kernel space, the kernel was using this flag already however after validity check got introduced the flag just got blocked from getting to the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1978967/+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 1979009] Re: fix ref leak when switching zones
This bug was fixed in the package linux-bluefield - 5.4.0-1040.44
---
linux-bluefield (5.4.0-1040.44) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1040.44 -proposed tracker (LP:
#1978639)
* fix ref leak when switching zones (LP: #1979009)
- net/sched: act_ct: fix ref leak when switching zones
* Fix XFRM flags validity check (LP: #1978967)
- SAUCE: net/xfrm: Fix XFRM flags validity check
[ Ubuntu: 5.4.0-121.137 ]
* focal/linux: 5.4.0-121.137 -proposed tracker (LP: #1978666)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2022.05.30)
* CVE-2022-28388
- can: usb_8dev: usb_8dev_start_xmit(): fix double dev_kfree_skb() in error
path
* test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed (Check VM
connectivity through VXLAN (underlay in the default VRF) [FAIL])
(LP: #1871015)
- selftests: net: test_vxlan_under_vrf: fix HV connectivity test
* [UBUNTU 20.04] CPU-MF: add extended counter set definitions for new IBM z16
(LP: #1974433)
- s390/cpumf: add new extended counter set for IBM z16
* [UBUNTU 20.04] KVM nesting support leaks too much memory, might result in
stalls during cleanup (LP: #1974017)
- KVM: s390: vsie/gmap: reduce gmap_rmap overhead
* [UBUNTU 20.04] Null Pointer issue in nfs code running Ubuntu on IBM Z
(LP: #1968096)
- NFS: Fix up nfs_ctx_key_to_expire()
[ Ubuntu: 5.4.0-120.136 ]
* CVE-2022-21123 // CVE-2022-21125 // CVE-2022-21166
- cpu/speculation: Add prototype for cpu_show_srbds()
- x86/cpu: Add Jasper Lake to Intel family
- x86/cpu: Add Lakefield, Alder Lake and Rocket Lake models to the to Intel
CPU family
- x86/cpu: Add another Alder Lake CPU to the Intel family
- Documentation: Add documentation for Processor MMIO Stale Data
- x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug
- x86/speculation: Add a common function for MD_CLEAR mitigation update
- x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data
- x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations
- x86/speculation/mmio: Enable CPU Fill buffer clearing on idle
- x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data
- x86/speculation/srbds: Update SRBDS mitigation selection
- x86/speculation/mmio: Reuse SRBDS mitigation for SBDS
- KVM: x86/speculation: Disable Fill buffer clear within guests
- x86/speculation/mmio: Print SMT warning
-- Zachary Tahenakos Tue, 21 Jun
2022 13:59:23 -0400
** Changed in: linux-bluefield (Ubuntu Focal)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21123
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21125
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-21166
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-28388
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1979009
Title:
fix ref leak when switching zones
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
Fix Released
Bug description:
* Explain the bug(s)
When switching zones or network namespaces without doing a ct clear in
between, it is now leaking a reference to the old ct entry. That's
because tcf_ct_skb_nfct_cached() returns false and
tcf_ct_flow_table_lookup() may simply overwrite it.
The fix is to, as the ct entry is not reusable, free it already at
tcf_ct_skb_nfct_cached().
* brief explanation of fixes
The fix is to, as the ct entry is not reusable, free it already at
tcf_ct_skb_nfct_cached().
* How to test
Setup ovs with ovs offload enabled on veth or other software only devices
(so it will
only be offloaded to TC and not also to HW which will take longer), example:
function config_veth() {
local ns=$1
local ip=$2
local peer=${ns}_peer
local veth=${ns}_veth
echo "Create namespace $ns, veths: hv $veth <-> ns $peer ($ip)"
ip netns add $ns
ip link del $veth &>/dev/null
ip link add $veth type veth peer name $peer
ip link set $veth up
ip link set $peer netns $ns
ip netns exec $ns ifconfig $peer $ip/24 mtu 1400 up
}
IP1="7.7.7.1"
IP2="7.7.7.2"
config_veth ns0 $IP1
config_veth ns1 $IP2
ovs-vsctl add-br ovs-br
ovs-vsctl add-port ovs-br ns0_veth
ovs-vsctl add-port ovs-br ns1_veth
Add openflow rules configuring two or more chained zones, example:
function configure_rules() {
local orig_dev=$1
local reply_dev=$2
ovs-ofctl del-flows ovs-br
ovs-ofctl add-flow ovs-br "table=0, arp, actions=normal"
#ORIG
ovs-ofctl add-flow ovs-br
[Kernel-packages] [Bug 1910113] Re: zfsutils-linux does not match kernel version
Same on Ubuntu 22.04 root@Ubuntu22:~# zpool version zfs-2.1.4-0ubuntu0.1 zfs-kmod-2.1.2-1ubuntu3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1910113 Title: zfsutils-linux does not match kernel version Status in zfs-linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 18.04.5 running a "linux-image-generic-hwe-18.04 5.4.0.53.59~18.04.47" kernel. This kernel comes with ZFS 0.8.3-1ubuntu12.4. Sadly, I'm unable to use features included in zfs 0.8 release (ex. TRIM support) because zfsutils-linux is stuck on version 0.7.5-1ubuntu16.10. Can we please package zfsutils-linux that will match ZFS versions provided with hwe and hwe-edge kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1910113/+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 1912935] Re: battery drain while notebook off / shutdown
p.s. in the meantime i can still use the workaround as mentioned in #49: the power reset. that one still works perfectly, so i can rule out the bad battery in my case. hopefully the module that causes the drain can still be found. -- 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/1912935 Title: battery drain while notebook off / shutdown Status in linux package in Ubuntu: Confirmed Bug description: Hello, my battery drains around 15 to 20 percent a day when shutdown on linux ubuntu. It is an HP notebook HP 15s-eq0355ng , Ryzen 5 3500U , Vega8 . Tested: - with ubuntu 20.04 - Kernel 5.4, 5.8 (hwe) and the current mainline kernel 5.11 (rc4) - no usb devices are plugged in - no wake ob lan available - no USB power when off (checked with optical mouse) - no visible LEDs are on when shutdown I reinstalled window 10, when shutdown from windows there is no (visible) battery drain (or significantly lower). Linux is unusable on this device, if the battery drains in a short time to 0% percent. This cause battery damage ... --- Tested TLP with default settings and activated DEVICES_TO_DISABLE_ON_SHUTDOWN (bluetooth wifi wwan), same power consumption after shutdown. Same power consumption on 20.10 (Groovy Gorilla). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: test953 F pulseaudio /dev/snd/controlC0: test953 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP Laptop 15s-eq0xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=17ad50f6-ec98-46b2-8c2e-c169f9baace8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.8 Tags: focal Uname: Linux 5.4.0-64-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86FD dmi.board.vendor: HP dmi.board.version: 99.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.30:bd11/18/2020:svnHP:pnHPLaptop15s-eq0xxx:pvr:rvnHP:rn86FD:rvr99.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-eq0xxx dmi.product.sku: 20T63EA#ABD dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912935/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
This bug was fixed in the package v4l2loopback - 0.12.5-1ubuntu7 --- v4l2loopback (0.12.5-1ubuntu7) kinetic; urgency=medium * Drop obsolte REMAKE_INITRD option from dkms.conf. * Update module init & exit calls to use kernel provided macros, such that they gain correct IBT attributes. LP: #1980484 -- Dimitri John Ledkov Mon, 11 Jul 2022 16:14:38 +0100 ** Changed in: v4l2loopback (Ubuntu Kinetic) 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1980925] Re: [SRU] bcache deadlock during read IO in writeback mode
Logs have been pasted in the description of the bug. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => 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/1980925 Title: [SRU] bcache deadlock during read IO in writeback mode Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification: [Impact] This bug in bcache affects focal and jammy releases. When Random Read I/O is started with a test like - fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --randrepeat=0 or random read-writes with a test like, fio --filename=/home/ubuntu/bcache_mount/cachedfile --size=15GB --direct=1 --rw=randrw --bs=4k --ioengine=libaio --iodepth=128 --name=iops-test-job --randrepeat=0 traces are seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] The bug exists till kernel 5.15.50-051550-generic, and is fixed through upstream commit commit b57a534df246999bc09a510dc0e0125cacd1724c (HEAD) Author: Coly Li Date: Fri May 27 23:28:16 2022 +0800 bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init() The local variables check_state (in bch_btree_check()) and state (in bch_sectors_dirty_init()) should be fully filled by 0, because before allocating them on stack, they were dynamically allocated by kzalloc(). Signed-off-by: Coly Li Link: https://lore.kernel.org/r/20220527152818.27545-2-col...@suse.de Signed-off-by: Jens Axboe The reproducer is pasted below: # uname -a Linux bronzor 5.15.50-051550-generic #202206251445 SMP Sat Jun 25 14:51:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 0 279.4G 0 disk └─sdd18:49 060G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount nvme0n1 259:00 372.6G 0 disk └─nvme0n1p1 259:2015G 0 part └─bcache0 252:0060G 0 disk /home/ubuntu/bcache_mount fio --name=read_iops --directory=/home/ubuntu/bcache_mount --size=12G --ioengine=libaio --direct=1 --verify=0 --bs=4K --iodepth=128 --rw=randread --group_reporting=1 read_iops: (g=0): rw=randread, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=128 fio-3.28 Starting 1 process read_iops: Laying out IO file (1 file / 12288MiB) The test does not progress beyond a few minutes, and this trace is then seen in the kernel log, [ 4473.699902] INFO: task bcache_writebac:1835 blocked for more than 120 seconds. [ 4474.050921] Not tainted 5.15.50-051550-generic #202206251445 [ 4474.350883] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4474.731391] task:bcache_writebac state:D stack:0 pid: 1835 ppid: 2 flags:0x4000 [ 4474.731408] Call Trace: [ 4474.731411] [ 4474.731413] __schedule+0x23d/0x5a0 [ 4474.731433] schedule+0x4e/0xb0 [ 4474.731436] rwsem_down_write_slowpath+0x220/0x3d0 [ 4474.731441] down_write+0x43/0x50 [ 4474.731446] bch_writeback_thread+0x78/0x320 [bcache] [ 4474.731471] ? read_dirty_submit+0x70/0x70 [bcache] [ 4474.731487] kthread+0x12a/0x150 [ 4474.731491] ? set_kthread_struct+0x50/0x50 [ 4474.731494] ret_from_fork+0x22/0x30 [ 4474.731499] [ 4474.731735] INFO: task fio:16626 blocked for more than 121 seconds. [ 4475.035858] Not tainted 5.15.50-051550-generic #202206251445 [ 4475.335859] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 4475.716526] task:fio state:D stack:0 pid:16626 ppid: 1715 flags:0x4002 [ 4475.716531] Call Trace: [ 4475.716546] [ 4475.716549]
[Kernel-packages] [Bug 621185] Re: Network module atl1c 1.0.1.0-NAPI not available in Lucid
** Changed in: baltix 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/621185 Title: Network module atl1c 1.0.1.0-NAPI not available in Lucid Status in linux package in Ubuntu: Fix Released Status in linux-backports-modules-2.6.32 package in Ubuntu: Invalid Status in linux source package in Lucid: Won't Fix Status in linux-backports-modules-2.6.32 source package in Lucid: Fix Released Status in Baltix: Invalid Bug description: SRU Justification: Impact: Newer hardware not supported by driver released with Lucid. Fix: In order to add support without risking regression, the updated driver is provided as part of an additional linux-backports-modules- compat-wireless-2.6.35-lucid. Testcase: TBD --- Network module atl1c 1.0.1.0-NAPI is not available in Lucid. Acer Aspire D260 netbooks require the atl1c network module. The version of the module in Lucid 10.04.0 (1.0.0.1-NAPI) does not support the onboard card [1]. There is a newer version (1.0.0.2-NAPI) in linux-backports-modules-wireless-2.6.32-21-generic which does but results in unstable behaviour. I have tested extensively with version 1.0.1.0-NAPI, which is available in "linux-next" and I am happy with the behaviour. [1] 04:00.0 Ethernet controller [0200]: Atheros Communications AR8152 v1.1 Fast Ethernet [1969:2060] (rev c1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/621185/+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 1981345] [NEW] jammy: override starfive and allwinner from universe to main
Public bug reported: Kernels must be published in main, please override component to main. As otherwise image building fails. ** Affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-allwinner-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-meta-allwinner-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-meta-starfive-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-starfive-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-starfive-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-starfive-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-meta-allwinner-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-allwinner-5.17 (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-starfive-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1981345 Title: jammy: override starfive and allwinner from universe to main Status in linux-allwinner-5.17 package in Ubuntu: New Status in linux-meta-allwinner-5.17 package in Ubuntu: New Status in linux-meta-starfive-5.17 package in Ubuntu: New Status in linux-starfive-5.17 package in Ubuntu: New Status in linux-allwinner-5.17 source package in Jammy: New Status in linux-meta-allwinner-5.17 source package in Jammy: New Status in linux-meta-starfive-5.17 source package in Jammy: New Status in linux-starfive-5.17 source package in Jammy: New Bug description: Kernels must be published in main, please override component to main. As otherwise image building fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1981345/+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 1980688] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602407/+files/WifiSyslog.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602402/+files/ProcInterrupts.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602394/+files/Lspci-vt.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602408/+files/acpidump.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602405/+files/RfKill.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602403/+files/ProcModules.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602404/+files/PulseList.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602406/+files/UdevDb.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602399/+files/ProcCpuinfo.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602401/+files/ProcEnviron.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602400/+files/ProcCpuinfoMinimal.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602397/+files/Lsusb-v.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602398/+files/PaInfo.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602396/+files/Lsusb-t.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602395/+files/Lsusb.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602390/+files/AudioDevicesInUse.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602393/+files/Lspci.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602392/+files/IwConfig.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602391/+files/CurrentDmesg.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 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.40 dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UES17F00 dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980688/+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 1980688] Re: Mouse / trackpad buttons sometimes don't work after waking up from suspend
apport information ** Tags added: apport-collected jammy ** Description changed: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-07-02 (9 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + MachineType: LENOVO 20UES17F00 + NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-40-generic N/A + linux-backports-modules-5.15.0-40-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.2 + Tags: jammy + Uname: Linux 5.15.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/05/2022 + dmi.bios.release: 1.40 + dmi.bios.vendor: LENOVO + dmi.bios.version: R1BET71W(1.40 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20UES17F00 + 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.40 + dmi.modalias: dmi:bvnLENOVO:bvrR1BET71W(1.40):bd04/05/2022:br1.40:efr1.40:svnLENOVO:pn20UES17F00:pvrThinkPadT14Gen1:rvnLENOVO:rn20UES17F00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UE_BU_Think_FM_ThinkPadT14Gen1: + dmi.product.family: ThinkPad T14 Gen 1 + dmi.product.name: 20UES17F00 + dmi.product.sku: LENOVO_MT_20UE_BU_Think_FM_ThinkPad T14 Gen 1 + dmi.product.version: ThinkPad T14 Gen 1 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1980688/+attachment/5602389/+files/AlsaInfo.txt -- 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/1980688 Title: Mouse / trackpad buttons sometimes don't work after waking up from suspend Status in linux package in Ubuntu: Incomplete Bug description: After waking up from suspend, the trackpad (and, if connected mouse) buttons sometimes don't work anymore. Only a reboot fixes it. Note that I move the mouse pointer and use the keyboard, just the trackpad / mouse buttons stop working. I have observed this bug both with Wayland and with X11. 1. Release: Ubuntu 22.04 2. Version: gnome-shell 42.2-0ubuntu0.2 3. What I expect to happen: the trackpad and mouse buttons work always after waking up from suspend. 4. What happened instead: the trackpad and mouse buttons do not work about every third time after waking up from suspend. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-07-02 (9 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20UES17F00 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-40-generic N/A linux-backports-modules-5.15.0-40-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 Tags: jammy Uname: Linux 5.15.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/05/2022 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET71W(1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UES17F00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information
[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: v4l2loopback (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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Confirmed Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Confirmed Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: backport-iwlwifi-dkms (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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Confirmed Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Confirmed Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
** Also affects: backport-iwlwifi-dkms (Ubuntu) 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Confirmed Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Confirmed Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
Modules that do not use any of the init.h or module.h macros to generate init_module / cleanup_module symbols: # objdump -x /lib/modules/5.19.0-9-generic/updates/dkms/v4l2loopback.ko | grep -e init_module -e cleanup_module g F .exit.text 004d cleanup_module g F .init.text 0979 init_module 0138 R_X86_64_64 init_module 0338 R_X86_64_64 cleanup_module Modules that do use any of the init.h or module.h macros to generate init_module / cleanup_module symbols: # objdump -x /lib/modules/5.19.0-9-generic/updates/dkms/v4l2loopback.ko | grep -e init_module -e cleanup_module 0810 l F .text 0030 v4l2loopback_cleanup_module 0149 l F .text.unlikely 0035 v4l2loopback_cleanup_module.cold l F .init.text 0979 v4l2loopback_init_module 0810 g F .text 0030 cleanup_module g O .exit.data 0008 __cfi_jt_cleanup_module g F .init.text 0979 init_module g O .init.data 0008 __cfi_jt_init_module R_X86_64_64 cleanup_module R_X86_64_64 init_module 0138 R_X86_64_64 init_module 0338 R_X86_64_64 cleanup_module Specifically addition of __cfi_jt_init_module & __cfi_jt_cleanup_module is important for correctly functioning Control Flow Integrity, aka on intel IBT. The fix is to use macros from init.h / module.h to declare entry and exit functions of the module. ** Also affects: v4l2loopback (Ubuntu) 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Confirmed Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Confirmed Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
Same story with other modules, i.e.: # objdump -x ./ubuntu/iwlwifi/iwlwifi.ko | grep init_module g F .init.text 00dc init_module 0138 R_X86_64_64 init_module versus # objdump -x ./kernel/drivers/net/wireless/intel/iwlwifi/iwlwifi.ko | grep -e init_module g F .init.text 007c init_module g O .init.data 0008 __cfi_jt_init_module R_X86_64_64 init_module 0138 R_X86_64_64 init_module -- 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Confirmed Status in backport-iwlwifi-dkms source package in Kinetic: Confirmed Status in linux source package in Kinetic: Incomplete Status in v4l2loopback source package in Kinetic: Confirmed Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+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 1981339] Re: [UBUNTU 22.04] s390x system emulation of QEMU has random hangs
** Changed in: linux (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: linux (Ubuntu) => qemu (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) -- 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/1981339 Title: [UBUNTU 22.04] s390x system emulation of QEMU has random hangs Status in Ubuntu on IBM z Systems: New Status in qemu package in Ubuntu: New Bug description: ---Problem Description--- QEMU system emulation of s390x sometimes hangs when running Linux. Turns out that interrupts on an EX instructions can result in endless loops. Contact Information = cborn...@de.ibm.com These 4 patches are missing from TCG https://git.qemu.org/?p=qemu.git;a=commit;h=b67b6c7ce4d56bb76a523eb63feb4a1978b05351 https://git.qemu.org/?p=qemu.git;a=commit;h=8ec2edac5f32117b523620a216638704d80bbed9 https://git.qemu.org/?p=qemu.git;a=commit;h=872e13796f732cfd65c4dc62bd2e4bbdbb4fa848 https://git.qemu.org/?p=qemu.git;a=commit;h=3d8111fd3bf7298486bcf1a72013b44c9044104e Richard Henderson (4): target/s390x: Remove DISAS_GOTO_TB target/s390x: Remove DISAS_PC_STALE target/s390x: Remove DISAS_PC_STALE_NOCHAIN target/s390x: Exit tb after executing ex_value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1981339/+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 1981339] [NEW] [UBUNTU 22.04] s390x system emulation of QEMU has random hangs
Public bug reported: ---Problem Description--- QEMU system emulation of s390x sometimes hangs when running Linux. Turns out that interrupts on an EX instructions can result in endless loops. Contact Information = cborn...@de.ibm.com These 4 patches are missing from TCG https://git.qemu.org/?p=qemu.git;a=commit;h=b67b6c7ce4d56bb76a523eb63feb4a1978b05351 https://git.qemu.org/?p=qemu.git;a=commit;h=8ec2edac5f32117b523620a216638704d80bbed9 https://git.qemu.org/?p=qemu.git;a=commit;h=872e13796f732cfd65c4dc62bd2e4bbdbb4fa848 https://git.qemu.org/?p=qemu.git;a=commit;h=3d8111fd3bf7298486bcf1a72013b44c9044104e Richard Henderson (4): target/s390x: Remove DISAS_GOTO_TB target/s390x: Remove DISAS_PC_STALE target/s390x: Remove DISAS_PC_STALE_NOCHAIN target/s390x: Exit tb after executing ex_value ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-all bugnameltc-198914 severity-medium targetmilestone-inin--- ** Tags added: architecture-all bugnameltc-198914 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: 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/1981339 Title: [UBUNTU 22.04] s390x system emulation of QEMU has random hangs Status in linux package in Ubuntu: New Bug description: ---Problem Description--- QEMU system emulation of s390x sometimes hangs when running Linux. Turns out that interrupts on an EX instructions can result in endless loops. Contact Information = cborn...@de.ibm.com These 4 patches are missing from TCG https://git.qemu.org/?p=qemu.git;a=commit;h=b67b6c7ce4d56bb76a523eb63feb4a1978b05351 https://git.qemu.org/?p=qemu.git;a=commit;h=8ec2edac5f32117b523620a216638704d80bbed9 https://git.qemu.org/?p=qemu.git;a=commit;h=872e13796f732cfd65c4dc62bd2e4bbdbb4fa848 https://git.qemu.org/?p=qemu.git;a=commit;h=3d8111fd3bf7298486bcf1a72013b44c9044104e Richard Henderson (4): target/s390x: Remove DISAS_GOTO_TB target/s390x: Remove DISAS_PC_STALE target/s390x: Remove DISAS_PC_STALE_NOCHAIN target/s390x: Exit tb after executing ex_value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981339/+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 1981078] Re: [pi-kernel] Please set CONFIG_RTC_DRV_DS1307=y
** Package changed: linux (Ubuntu) => linux-raspi (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/1981078 Title: [pi-kernel] Please set CONFIG_RTC_DRV_DS1307=y Status in linux-raspi package in Ubuntu: Confirmed Bug description: We recently got a bugreport from a user who uses a PI with an external RTC. The chips is a ds3231. The driver for this is currently compiled as a module. Doing RTC as a module is unfortunately broken in the general case today (see https://github.com/systemd/systemd/issues/17737 and https://forum.snapcraft.io/t/adding-ubuntu-core-fails-on-first-boot- with-rtc-is-present/30391/15 for details). Until a more general fix is available I would like to ask to just compile CONFIG_RTC_DRV_DS1307=y into the kernel that should cover a lot of popular chips and we already build CONFIG_RTC_DRV_DS1307_CENTURY=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1981078/+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 1981339] [NEW] [UBUNTU 22.04] s390x system emulation of QEMU has random hangs
You have been subscribed to a public bug: ---Problem Description--- QEMU system emulation of s390x sometimes hangs when running Linux. Turns out that interrupts on an EX instructions can result in endless loops. Contact Information = cborn...@de.ibm.com These 4 patches are missing from TCG https://git.qemu.org/?p=qemu.git;a=commit;h=b67b6c7ce4d56bb76a523eb63feb4a1978b05351 https://git.qemu.org/?p=qemu.git;a=commit;h=8ec2edac5f32117b523620a216638704d80bbed9 https://git.qemu.org/?p=qemu.git;a=commit;h=872e13796f732cfd65c4dc62bd2e4bbdbb4fa848 https://git.qemu.org/?p=qemu.git;a=commit;h=3d8111fd3bf7298486bcf1a72013b44c9044104e Richard Henderson (4): target/s390x: Remove DISAS_GOTO_TB target/s390x: Remove DISAS_PC_STALE target/s390x: Remove DISAS_PC_STALE_NOCHAIN target/s390x: Exit tb after executing ex_value ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-all bugnameltc-198914 severity-medium targetmilestone-inin--- -- [UBUNTU 22.04] s390x system emulation of QEMU has random hangs https://bugs.launchpad.net/bugs/1981339 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 1975582] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2022-07-11 11:05 EDT--- With this fix being released to -updates, I am closing the bug. Thanks to everyone for your work on this. Changing Bugzilla status to: CLOSED -- 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/1975582 Title: [UBUNTU 20.04] rcu stalls with many storage key guests Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * Ubuntu on s390x KVM environments with lots of large guests with storage keys can be affected by rcu stalls. * These rcu stalls can cause the system to crash/dump. [Fix] * 3ae11dbcfac9 3ae11dbcfac906a8c3a480e98660a823130dc16a "s390/mm: use non-quiescing sske for KVM switch to keyed guest" * 6d5946274df1 6d5946274df1fff539a7eece458a43be733d1db8 "s390/gmap: voluntarily schedule during key setting" [Test Plan] * There is no trigger or direct test or re-creation of the problem situation possible, but... * and IBM z13 or LinuxONE (or never) LPAR is needed that runs Ubuntu Server 20.04 LTS or 18.04 LTS with HWE kernel and acts as KVM host with again several large guests running on top with storage groups. * Let such a system running for days under significant load and watch the logs for rcu issues. * Prior to the submission of this SRU patched test kernels for focal 5.4 and bionic hwe-5.4 were created and tested. They ran for days at a staging environemnt at IBM without further issues. * The modifications are all limited to s390x. * A test kernel was build (see below) that ran in a test environment at IBM under appropriate load for several days. [Where problems could occur] * Due to the change for the KVM switch to keyed guest from classic sske to non-quiescing sske the KVM behaviour might have changed and the storage keys harmed. * The now more generous scheduling while setting keys has an impact on the guest memory management and mapping which will lead to a different performance. * This, with the introduction of __s390_enable_skey_pmd and cond_resched, might increase the overhead in certain situations, but eventually improves the responsiveness over time, hence avoid rcu stalls. [Other Info] * Since the patches are upstream in 5.19-rc1, they will be included in the kernel that is planned for kinetic (5.19). * Hence this is an SRU to jammy, impish and focal. __ ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 Contact Information = cborn...@de.ibm.com ---uname output--- RELEASE: 5.4.0-90-generic VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 == Comment: #1 - Christian Borntraeger - 2022-05-24 03:59:37 == This is a test patch that might address the rcu stalls. == Comment: #2 - Christian Borntraeger - 2022-05-24 04:00:22 == This is a 2nd patch that reduces the cost of key setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975582/+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 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
Since Impish with reach it's EOL this week on July the 14th, I'll change Impish here also to Won't Fix that allows to close this bug entirely. ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Won't Fix ** Changed in: ubuntu-z-systems Status: Fix Committed => 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/1975582 Title: [UBUNTU 20.04] rcu stalls with many storage key guests Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * Ubuntu on s390x KVM environments with lots of large guests with storage keys can be affected by rcu stalls. * These rcu stalls can cause the system to crash/dump. [Fix] * 3ae11dbcfac9 3ae11dbcfac906a8c3a480e98660a823130dc16a "s390/mm: use non-quiescing sske for KVM switch to keyed guest" * 6d5946274df1 6d5946274df1fff539a7eece458a43be733d1db8 "s390/gmap: voluntarily schedule during key setting" [Test Plan] * There is no trigger or direct test or re-creation of the problem situation possible, but... * and IBM z13 or LinuxONE (or never) LPAR is needed that runs Ubuntu Server 20.04 LTS or 18.04 LTS with HWE kernel and acts as KVM host with again several large guests running on top with storage groups. * Let such a system running for days under significant load and watch the logs for rcu issues. * Prior to the submission of this SRU patched test kernels for focal 5.4 and bionic hwe-5.4 were created and tested. They ran for days at a staging environemnt at IBM without further issues. * The modifications are all limited to s390x. * A test kernel was build (see below) that ran in a test environment at IBM under appropriate load for several days. [Where problems could occur] * Due to the change for the KVM switch to keyed guest from classic sske to non-quiescing sske the KVM behaviour might have changed and the storage keys harmed. * The now more generous scheduling while setting keys has an impact on the guest memory management and mapping which will lead to a different performance. * This, with the introduction of __s390_enable_skey_pmd and cond_resched, might increase the overhead in certain situations, but eventually improves the responsiveness over time, hence avoid rcu stalls. [Other Info] * Since the patches are upstream in 5.19-rc1, they will be included in the kernel that is planned for kinetic (5.19). * Hence this is an SRU to jammy, impish and focal. __ ---Problem Description--- There can be rcu stalls when running lots of large guests with storage keys: [1377614.579833] rcu: INFO: rcu_sched self-detected stall on CPU [1377614.579845] rcu: 18-: (2099 ticks this GP) idle=54e/1/0x4002 softirq=35598716/35598716 fqs=998 [1377614.579895](t=2100 jiffies g=155867385 q=20879) [1377614.579898] Task dump for CPU 18: [1377614.579899] CPU 1/KVM R running task0 1030947 256019 0x0604 [1377614.579902] Call Trace: [1377614.579912] ([<001f1f4b4f52>] show_stack+0x7a/0xc0) [1377614.579918] [<001f1ec8e96c>] sched_show_task.part.0+0xdc/0x100 [1377614.579919] [<001f1f4b7248>] rcu_dump_cpu_stacks+0xc0/0x100 [1377614.579924] [<001f1ecdd10c>] rcu_sched_clock_irq+0x75c/0x980 [1377614.579926] [<001f1eceb26c>] update_process_times+0x3c/0x80 [1377614.579931] [<001f1ecfcfea>] tick_sched_handle.isra.0+0x4a/0x70 [1377614.579932] [<001f1ecfd28e>] tick_sched_timer+0x5e/0xc0 [1377614.579933] [<001f1ecec294>] __hrtimer_run_queues+0x114/0x2f0 [1377614.579935] [<001f1ececfdc>] hrtimer_interrupt+0x12c/0x2a0 [1377614.579938] [<001f1ebecb6a>] do_IRQ+0xaa/0xb0 [1377614.579942] [<001f1f4c6d08>] ext_int_handler+0x130/0x134 [1377614.579945] [<001f1ec0af10>] ptep_zap_key+0x40/0x60 Contact Information = cborn...@de.ibm.com ---uname output--- RELEASE: 5.4.0-90-generic VERSION: #101-Ubuntu SMP Fri Oct 15 19:59:45 UTC 2021 == Comment: #1 - Christian Borntraeger - 2022-05-24 03:59:37 == This is a test patch that might address the rcu stalls. == Comment: #2 - Christian Borntraeger - 2022-05-24 04:00:22 == This is a 2nd patch that reduces the cost of key setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1975582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1976533] Re: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices
** Changed in: linux (Ubuntu Jammy) Status: Fix Committed => 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/1976533 Title: [UBUNTU 20.04] s390/DASD: Fix data corruption for ESE devices Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Description: s390/dasd: Fix data corruption for ESE devices Symptom: Filesystem errors and data inconsistency. Problem: Wrong tracks are formatted or the same track is formatted twice. 1. For ESE devices we get an error when accessing an unformatted track. The handling of this error will return zero data for read requests and format the track on demand before writing to it. To do this the code needs to distinguish between read and write requests. This is done with data from the blocklayer request. A pointer to the blocklayer request is stored in the CQR. If there is an error on the device an ERP request is built to do error recovery. While the ERP request is mostly a copy of the original CQR the pointer to the blocklayer request is not copied to not accidentally pass it back to the blocklayer without cleanup. This leads to the error that during ESE handling after an ERP request was built it is not possible to determine the IO direction. This leads to the formatting of a track for read requests which might in turn lead to data corruption. 2. When using alias devices a track might be accessed by multiple requests simultaneously and there is a race window that a track gets formatted twice resulting in data loss. Solution: 1. Return the callback data of the original request in case there are ERP requests build on top of it and thus determine the correct IO direction. 2. Prevent the double format by remembering the amount of formatted tracks when starting a request and comparing this number before actually formatting a track on the fly. If the number has changed there is a chance that the current track was finally formatted in between. As a result do not format the track and restart the current IO to check. Reproduction: Prepare an ESE DASD device using dasdfmt and fdasd. Install any filesystem on the prepared partitions and issue regular I/O using dd or any other tool while Alias DASD devices are set online as well. Upstream-ID: 5b53a405e4658580e1faf7c217db3f55a21ba849 71f3871657370dbbaf942a1c758f64e49a36c70f Problem-ID:198418 Preventive:yes Date: 2022-06-01 Author:hoepp...@linux.ibm.com Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1976533/+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 1973167] Re: linux-image-4.15.0-177-generic freezes on the welcome screen
This bug was fixed in the package linux - 4.15.0-189.200 --- linux (4.15.0-189.200) bionic; urgency=medium * bionic/linux: 4.15.0-189.200 -proposed tracker (LP: #1979525) * linux-image-4.15.0-177-generic freezes on the welcome screen (LP: #1973167) - mfd: intel-lpss: Use MODULE_SOFTDEP() instead of implicit request * Bionic update: upstream stable patchset 2022-06-03 (LP: #1977622) - etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead - mm: page_alloc: fix building error on -Werror=array-compare - tracing: Dump stacktrace trigger to the corresponding instance - gfs2: assign rgrp glock before compute_bitstructs - ALSA: usb-audio: Clear MIDI port active flag after draining - tcp: fix race condition when creating child sockets from syncookies - tcp: Fix potential use-after-free due to double kfree() - dmaengine: imx-sdma: Fix error checking in sdma_event_remap - net/packet: fix packet_sock xmit return value checking - netlink: reset network and mac headers in netlink_dump() - ARM: vexpress/spc: Avoid negative array index when !SMP - platform/x86: samsung-laptop: Fix an unsigned comparison which can never be negative - ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant - vxlan: fix error return code in vxlan_fdb_append - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant - drm/msm/mdp5: check the return of kzalloc() - net: macb: Restart tx only if queue pointer is lagging - stat: fix inconsistency between struct stat and struct compat_stat - ata: pata_marvell: Check the 'bmdma_addr' beforing reading - dma: at_xdmac: fix a missing check on list iterator - powerpc/perf: Fix power9 event alternatives - openvswitch: fix OOB access in reserve_sfa_size() - ASoC: soc-dapm: fix two incorrect uses of list iterator - e1000e: Fix possible overflow in LTR decoding - ARC: entry: fix syscall_trace_exit argument - ext4: fix symlink file size not match to file content - ext4: fix overhead calculation to account for the reserved gdt blocks - ext4: force overhead calculation if the s_overhead_cluster makes no sense - staging: ion: Prevent incorrect reference counting behavour - block/compat_ioctl: fix range check in BLKGETSIZE - ax25: add refcount in ax25_dev to avoid UAF bugs - ax25: fix reference count leaks of ax25_dev - ax25: fix UAF bugs of net_device caused by rebinding operation - ax25: Fix refcount leaks caused by ax25_cb_del() - ax25: fix UAF bug in ax25_send_control() - ax25: fix NPD bug in ax25_disconnect - ax25: Fix NULL pointer dereferences in ax25 timers - ax25: Fix UAF bugs in ax25 timers - ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek - net/sched: cls_u32: fix possible leak in u32_init_knode() - drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised - drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare * Bionic update: upstream stable patchset 2022-05-17 (LP: #1973831) - USB: serial: pl2303: add IBM device IDs - USB: serial: simple: add Nokia phone driver - netdevice: add the case if dev is NULL - virtio_console: break out of buf poll on remove - ethernet: sun: Free the coherent when failing in probing - spi: Fix invalid sgs value - spi: Fix erroneous sgs value with min_t() - af_key: add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register - fuse: fix pipe buffer lifetime for direct_io - tpm: fix reference counting for struct tpm_chip - block: Add a helper to validate the block size - virtio-blk: Use blk_validate_block_size() to validate block size - USB: usb-storage: Fix use of bitfields for hardware data in ene_ub6250.c - coresight: Fix TRCCONFIGR.QE sysfs interface - iio: inkern: apply consumer scale on IIO_VAL_INT cases - iio: inkern: apply consumer scale when no channel scale is available - iio: inkern: make a best effort on offset calculation - clk: uniphier: Fix fixed-rate initialization - Documentation: add link to stable release candidate tree - Documentation: update stable tree link - SUNRPC: avoid race between mod_timer() and del_timer_sync() - NFSD: prevent underflow in nfssvc_decode_writeargs() - pinctrl: samsung: drop pin banks references on error paths - jffs2: fix use-after-free in jffs2_clear_xattr_subsystem - jffs2: fix memory leak in jffs2_do_mount_fs - jffs2: fix memory leak in jffs2_scan_medium - mm/pages_alloc.c: don't create ZONE_MOVABLE beyond the end of a node - mempolicy: mbind_range() set_policy() after vma_merge() - scsi: libsas: Fix sas_ata_qc_issue() handling of NCQ NON DATA commands - qed: display VF trust config - qed: validate and restrict
[Kernel-packages] [Bug 1981328] Re: Azure: Fix the Focal Azure CVM kernel for VBS VMs
Patch submitted: https://lists.ubuntu.com/archives/kernel- team/2022-July/131812.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1981328 Title: Azure: Fix the Focal Azure CVM kernel for VBS VMs Status in linux-azure-cvm package in Ubuntu: Invalid Status in linux-azure-cvm source package in Focal: In Progress Bug description: SRU Justification [Impact] The latest 5.4-based linux-azure-cvm kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- azure/+git/focal/tag/?h=Ubuntu-azure-cvm-5.4.0-1085.90%2bcvm2) works fine when it runs in an AMD SNP VM, but doesn't work when it runs in a VBS VM (for VBS, please refer to https://docs.microsoft.com/en- us/windows-hardware/design/device-experiences/oem-vbs) [Fix] https://github.com/dcui/linux-azure- cvm/commit/b262b15df05e06be0a43ecc4c72fb3b735a78fe7 [Test Case] Microsoft tested [Where things could go wrong] This could affect regular CVM instances [Other Info] SF: #00340455 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1981328/+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 1981328] [NEW] Azure: Fix the Focal Azure CVM kernel for VBS VMs
Public bug reported: SRU Justification [Impact] The latest 5.4-based linux-azure-cvm kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- azure/+git/focal/tag/?h=Ubuntu-azure-cvm-5.4.0-1085.90%2bcvm2) works fine when it runs in an AMD SNP VM, but doesn't work when it runs in a VBS VM (for VBS, please refer to https://docs.microsoft.com/en- us/windows-hardware/design/device-experiences/oem-vbs) [Fix] https://github.com/dcui/linux-azure- cvm/commit/b262b15df05e06be0a43ecc4c72fb3b735a78fe7 [Test Case] Microsoft tested [Where things could go wrong] This could affect regular CVM instances [Other Info] SF: #00340455 ** Affects: linux-azure-cvm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure-cvm (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux-azure-cvm (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure-cvm (Ubuntu) Status: New => Invalid ** Changed in: linux-azure-cvm (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure-cvm (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure-cvm (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-cvm in Ubuntu. https://bugs.launchpad.net/bugs/1981328 Title: Azure: Fix the Focal Azure CVM kernel for VBS VMs Status in linux-azure-cvm package in Ubuntu: Invalid Status in linux-azure-cvm source package in Focal: In Progress Bug description: SRU Justification [Impact] The latest 5.4-based linux-azure-cvm kernel (https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux- azure/+git/focal/tag/?h=Ubuntu-azure-cvm-5.4.0-1085.90%2bcvm2) works fine when it runs in an AMD SNP VM, but doesn't work when it runs in a VBS VM (for VBS, please refer to https://docs.microsoft.com/en- us/windows-hardware/design/device-experiences/oem-vbs) [Fix] https://github.com/dcui/linux-azure- cvm/commit/b262b15df05e06be0a43ecc4c72fb3b735a78fe7 [Test Case] Microsoft tested [Where things could go wrong] This could affect regular CVM instances [Other Info] SF: #00340455 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure-cvm/+bug/1981328/+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 1975580] Re: Enable StarFive VisionFive board
This bug was fixed in the package linux-starfive-5.17 - 5.17.0-1003.4 --- linux-starfive-5.17 (5.17.0-1003.4) jammy; urgency=medium * Enable StarFive VisionFive board (LP: #1975580) - SAUCE: hwrng: starfive - fix unused variable warning - SAUCE: watchdog: starfive-wdt: Use platform_get_irq - SAUCE: nvdla: Use specific platform api rather than platform_get_resource - SAUCE: drm/starfive: Fix invalid use of devm_clk_bulk_get - SAUCE: drm/starfive: Fix invalid use of devm_reset_control_get_exclusive - SAUCE: drm/starfive: Fix starfive_drm_bind error path - SAUCE: drm/starfive: Use dev_err_probe in error path - SAUCE: watchdog: starfive-wdt: Fix invalid use of devm_reset_control_get_exclusive - SAUCE: watchdog: starfive-wdt: Various cleanups - SAUCE: ASoC: starfive: pwmdac: Fix bulk API usage - SAUCE: ASoC: starfive: i2svad: Fix bulk API usage * Miscellaneous Ubuntu changes - [Packaging] fixup etc/getabis linux-starfive-5.17 (5.17.0-1002.3) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Config] Enable Designware serial port and DMA - [Config] Disable unused StarFive specific DMA code - [Config] Disable the non-working StarFive sound drivers - [Config] Make DRM_STARFIVE built-in - [Packaging] Update abi after config changes linux-starfive-5.17 (5.17.0-1001.2) jammy; urgency=medium * Miscellaneous Ubuntu changes - [Packaging] commit initial ABI files linux-starfive-5.17 (5.17.0-1001.1) jammy; urgency=medium * jammy/linux-starfive-5.17: 5.17.0-1001.1 -proposed tracker (LP: #1976388) * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/master) * Enable StarFive VisionFive board (LP: #1975580) - SAUCE: riscv: add ARCH_DMA_MINALIGN support - SAUCE: riscv: optimized memcpy - SAUCE: riscv: optimized memmove - SAUCE: riscv: optimized memset - SAUCE: riscv: Add -ffreestanding for string functions - SAUCE: riscv: dts: starfive: Group tuples in interrupt properties - SAUCE: dt-bindings: clock: Add JH7100 audio clock definitions - SAUCE: dt-bindings: clock: Add starfive,jh7100-audclk bindings - SAUCE: clk: starfive: jh7100: Make hw clock implementation reusable - SAUCE: clk: starfive: jh7100: Support more clock types - SAUCE: clk: starfive: Add JH7100 audio clock driver - SAUCE: RISC-V: Add StarFive JH7100 audio clock node - SAUCE: dt-bindings: reset: Add StarFive JH7100 audio reset definitions - SAUCE: dt-bindings: reset: Add starfive,jh7100-audrst bindings - SAUCE: reset: Create subdirectory for StarFive drivers - SAUCE: reset: starfive: Use 32bit I/O on 32bit registers - SAUCE: reset: starfive: Add JH7100 audio reset driver - SAUCE: RISC-V: Add StarFive JH7100 audio reset node - SAUCE: clk: starfive: jh7100: Keep more clocks alive - SAUCE: pinctrl: starfive: Reset pinmux settings - SAUCE: serial: 8250_dw: Use device tree match data - SAUCE: serial: 8250_dw: Add starfive,jh7100-hsuart compatible - SAUCE: dt-bindings: hwmon: add starfive,jh7100-temp bindings - SAUCE: hwmon: (sfctemp) Add StarFive JH7100 temperature sensor - SAUCE: watchdog: Add StarFive SI5 watchdog driver - SAUCE: drivers/hw_random: Add StarFive JH7100 Random Number Generator driver - SAUCE: sifive/sifive_l2_cache: Add sifive_l2_flush64_range function - SAUCE: sifive/sifive_l2_cache: Add Starfive support - SAUCE: sifive/sifive_l2_cache: Add disabling IRQ option (workaround) - SAUCE: sifive/sifive_l2_cache: Print a backtrace on out-of-range flushes - SAUCE: sifive/sifive_l2_cache: Align the address to cache line - SAUCE: drivers/tty/serial/8250: update driver for JH7100 - SAUCE: pwm: sifive-ptc: Add SiFive PWM PTC driver - SAUCE: dt-bindings: dma: dw-axi-dmac: Increase DMA channel limit to 16 - SAUCE: dmaengine: dw-axi-dmac: Fix RMW on channel suspend register - SAUCE: dmaengine: dw-axi-dmac: Handle xfer start while non-idle - SAUCE: dmaengine: dw-axi-dmac: Add StarFive JH7100 support - SAUCE: dmaengine: Add dw-axi-dmac-starfive driver for JH7100 - SAUCE: dmaengine: dw-axi-dmac-starfive: Remove calls specific to ARM64 ACPI - SAUCE: net: phy: motorcomm: Add YT8521 support - SAUCE: net: phy: motorcomm: Add WIP YT8521 wake-on-lan code - SAUCE: net: stmmac: Configure gtxclk based on speed - SAUCE: net: stmmac: use GFP_DMA32 - SAUCE: ASoC: starfive: Add StarFive JH7100 audio drivers - SAUCE: drm/starfive: Add StarFive drm driver - SAUCE: drm/i2c/tda998x: Hardcode register values for Starlight - SAUCE: drm/starfive: crtc: Use devm_platform_ioremap_resource_byname - SAUCE: drm/starfive: Use clock api - SAUCE: drm/starfive: Use reset api - SAUCE: drm/starfive: Use actual clock rate - SAUCE: drm/starfive: Support DRM_FORMAT_XRGB - SAUCE: drm/starfive: Propagate bridge error properly
[Kernel-packages] [Bug 1973831] Re: Bionic update: upstream stable patchset 2022-05-17
This bug was fixed in the package linux - 4.15.0-189.200 --- linux (4.15.0-189.200) bionic; urgency=medium * bionic/linux: 4.15.0-189.200 -proposed tracker (LP: #1979525) * linux-image-4.15.0-177-generic freezes on the welcome screen (LP: #1973167) - mfd: intel-lpss: Use MODULE_SOFTDEP() instead of implicit request * Bionic update: upstream stable patchset 2022-06-03 (LP: #1977622) - etherdevice: Adjust ether_addr* prototypes to silence -Wstringop-overead - mm: page_alloc: fix building error on -Werror=array-compare - tracing: Dump stacktrace trigger to the corresponding instance - gfs2: assign rgrp glock before compute_bitstructs - ALSA: usb-audio: Clear MIDI port active flag after draining - tcp: fix race condition when creating child sockets from syncookies - tcp: Fix potential use-after-free due to double kfree() - dmaengine: imx-sdma: Fix error checking in sdma_event_remap - net/packet: fix packet_sock xmit return value checking - netlink: reset network and mac headers in netlink_dump() - ARM: vexpress/spc: Avoid negative array index when !SMP - platform/x86: samsung-laptop: Fix an unsigned comparison which can never be negative - ALSA: usb-audio: Fix undefined behavior due to shift overflowing the constant - vxlan: fix error return code in vxlan_fdb_append - cifs: Check the IOCB_DIRECT flag, not O_DIRECT - brcmfmac: sdio: Fix undefined behavior due to shift overflowing the constant - drm/msm/mdp5: check the return of kzalloc() - net: macb: Restart tx only if queue pointer is lagging - stat: fix inconsistency between struct stat and struct compat_stat - ata: pata_marvell: Check the 'bmdma_addr' beforing reading - dma: at_xdmac: fix a missing check on list iterator - powerpc/perf: Fix power9 event alternatives - openvswitch: fix OOB access in reserve_sfa_size() - ASoC: soc-dapm: fix two incorrect uses of list iterator - e1000e: Fix possible overflow in LTR decoding - ARC: entry: fix syscall_trace_exit argument - ext4: fix symlink file size not match to file content - ext4: fix overhead calculation to account for the reserved gdt blocks - ext4: force overhead calculation if the s_overhead_cluster makes no sense - staging: ion: Prevent incorrect reference counting behavour - block/compat_ioctl: fix range check in BLKGETSIZE - ax25: add refcount in ax25_dev to avoid UAF bugs - ax25: fix reference count leaks of ax25_dev - ax25: fix UAF bugs of net_device caused by rebinding operation - ax25: Fix refcount leaks caused by ax25_cb_del() - ax25: fix UAF bug in ax25_send_control() - ax25: fix NPD bug in ax25_disconnect - ax25: Fix NULL pointer dereferences in ax25 timers - ax25: Fix UAF bugs in ax25 timers - ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek - net/sched: cls_u32: fix possible leak in u32_init_knode() - drm/panel/raspberrypi-touchscreen: Avoid NULL deref if not initialised - drm/panel/raspberrypi-touchscreen: Initialise the bridge in prepare * Bionic update: upstream stable patchset 2022-05-17 (LP: #1973831) - USB: serial: pl2303: add IBM device IDs - USB: serial: simple: add Nokia phone driver - netdevice: add the case if dev is NULL - virtio_console: break out of buf poll on remove - ethernet: sun: Free the coherent when failing in probing - spi: Fix invalid sgs value - spi: Fix erroneous sgs value with min_t() - af_key: add __GFP_ZERO flag for compose_sadb_supported in function pfkey_register - fuse: fix pipe buffer lifetime for direct_io - tpm: fix reference counting for struct tpm_chip - block: Add a helper to validate the block size - virtio-blk: Use blk_validate_block_size() to validate block size - USB: usb-storage: Fix use of bitfields for hardware data in ene_ub6250.c - coresight: Fix TRCCONFIGR.QE sysfs interface - iio: inkern: apply consumer scale on IIO_VAL_INT cases - iio: inkern: apply consumer scale when no channel scale is available - iio: inkern: make a best effort on offset calculation - clk: uniphier: Fix fixed-rate initialization - Documentation: add link to stable release candidate tree - Documentation: update stable tree link - SUNRPC: avoid race between mod_timer() and del_timer_sync() - NFSD: prevent underflow in nfssvc_decode_writeargs() - pinctrl: samsung: drop pin banks references on error paths - jffs2: fix use-after-free in jffs2_clear_xattr_subsystem - jffs2: fix memory leak in jffs2_do_mount_fs - jffs2: fix memory leak in jffs2_scan_medium - mm/pages_alloc.c: don't create ZONE_MOVABLE beyond the end of a node - mempolicy: mbind_range() set_policy() after vma_merge() - scsi: libsas: Fix sas_ata_qc_issue() handling of NCQ NON DATA commands - qed: display VF trust config - qed: validate and restrict
[Kernel-packages] [Bug 1972905] Re: Jammy update: v5.15.36 upstream stable release
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1967493] Re: pl2303 serial adapter not recognized
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1973085] Re: Focal update: v5.4.190 upstream stable release
This bug was fixed in the package linux - 5.4.0-122.138 --- linux (5.4.0-122.138) focal; urgency=medium * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: check asoc strreset_chunk in sctp_generate_reconf_event - ARM: dts: imx6ull-colibri: fix vqmmc regulator - arm64: dts: imx8mn-ddr4-evk: Describe the 32.768 kHz PMIC clock - pinctrl: pistachio: fix use of irq_of_parse_and_map() - cpufreq: fix memory leak in sun50i_cpufreq_nvmem_probe - net: hns3: add validity check for message data length - net/smc: sync err code when tcp connection was refused - ip_gre: Make o_seqno start from 0 in native mode - tcp: fix potential xmit stalls caused by TCP_NOTSENT_LOWAT - bus: sunxi-rsb: Fix the return value
[Kernel-packages] [Bug 1979628] Re: Improve config to boot to userspace
This bug was fixed in the package linux-allwinner-5.17 - 5.17.0-1002.2 --- linux-allwinner-5.17 (5.17.0-1002.2) jammy; urgency=medium * jammy/linux-allwinner-5.17: 5.17.0-1002.2 -proposed tracker (LP: #1979636) * Rename nezha to allwinner (LP: #1979635) - [Packaging] Rename nezha to allwinner * Improve config to boot to userspace (LP: #1979628) - [Config] Update configs to be closer to previously working build * Miscellaneous Ubuntu changes - [Packaging] update etc/getabis config file -- Dimitri John Ledkov Thu, 23 Jun 2022 15:04:56 +0100 ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nezha-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1979628 Title: Improve config to boot to userspace Status in linux-allwinner-5.17 package in Ubuntu: Fix Released Status in linux-nezha-5.17 package in Ubuntu: Won't Fix Bug description: improve config to boot to userspace Initial build of nezha kernel did not complete boot to userspace with ethernet. Improve config such that it is able to achieve that. It seems that many config options cannot be compiled as modules and have to be builtin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/1979628/+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 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
This bug was fixed in the package linux - 5.4.0-122.138 --- linux (5.4.0-122.138) focal; urgency=medium * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: check asoc strreset_chunk in sctp_generate_reconf_event - ARM: dts: imx6ull-colibri: fix vqmmc regulator - arm64: dts: imx8mn-ddr4-evk: Describe the 32.768 kHz PMIC clock - pinctrl: pistachio: fix use of irq_of_parse_and_map() - cpufreq: fix memory leak in sun50i_cpufreq_nvmem_probe - net: hns3: add validity check for message data length - net/smc: sync err code when tcp connection was refused - ip_gre: Make o_seqno start from 0 in native mode - tcp: fix potential xmit stalls caused by TCP_NOTSENT_LOWAT - bus: sunxi-rsb: Fix the return value
[Kernel-packages] [Bug 1975691] Re: Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
This bug was fixed in the package linux - 5.4.0-122.138 --- linux (5.4.0-122.138) focal; urgency=medium * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: check asoc strreset_chunk in sctp_generate_reconf_event - ARM: dts: imx6ull-colibri: fix vqmmc regulator - arm64: dts: imx8mn-ddr4-evk: Describe the 32.768 kHz PMIC clock - pinctrl: pistachio: fix use of irq_of_parse_and_map() - cpufreq: fix memory leak in sun50i_cpufreq_nvmem_probe - net: hns3: add validity check for message data length - net/smc: sync err code when tcp connection was refused - ip_gre: Make o_seqno start from 0 in native mode - tcp: fix potential xmit stalls caused by TCP_NOTSENT_LOWAT - bus: sunxi-rsb: Fix the return value
[Kernel-packages] [Bug 1975582] Re: [UBUNTU 20.04] rcu stalls with many storage key guests
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1976116] Re: Focal update: v5.4.191 upstream stable release
This bug was fixed in the package linux - 5.4.0-122.138 --- linux (5.4.0-122.138) focal; urgency=medium * focal/linux: 5.4.0-122.138 -proposed tracker (LP: #1979489) * Remove SAUCE patches from test_vxlan_under_vrf.sh in net of ubuntu_kernel_selftests (LP: #1975691) - Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on xfail" - Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in non- default VRF an expected failure" * Enable Asus USB-BT500 Bluetooth dongle(0b05:190e) (LP: #1976613) - Bluetooth: btusb: Add flag to define wideband speech capability - Bluetooth: btrtl: Add support for RTL8761B - Bluetooth: btusb: Add 0x0b05:0x190e Realtek 8761BU (ASUS BT500) device. * [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582) - s390/gmap: voluntarily schedule during key setting - s390/mm: use non-quiescing sske for KVM switch to keyed guest * Ubuntu 5.4.0-117.132-generic 5.4.189 has BUG: kernel NULL pointer dereference, address: 0034 (LP: #1978719) - mm: rmap: explicitly reset vma->anon_vma in unlink_anon_vmas() * Focal update: upstream stable patchset v5.4.192 (LP: #1979014) - floppy: disable FDRAWCMD by default - [Config] updateconfigs for BLK_DEV_FD_RAWCMD - hamradio: defer 6pack kfree after unregister_netdev - hamradio: remove needs_free_netdev to avoid UAF - lightnvm: disable the subsystem - [Config] updateconfigs for NVM, NVM_PBLK - usb: mtu3: fix USB 3.0 dual-role-switch from device to host - USB: quirks: add a Realtek card reader - USB: quirks: add STRING quirk for VCOM device - USB: serial: whiteheat: fix heap overflow in WHITEHEAT_GET_DTR_RTS - USB: serial: cp210x: add PIDs for Kamstrup USB Meter Reader - USB: serial: option: add support for Cinterion MV32-WA/MV32-WB - USB: serial: option: add Telit 0x1057, 0x1058, 0x1075 compositions - xhci: stop polling roothubs after shutdown - xhci: increase usb U3 -> U0 link resume timeout from 100ms to 500ms - iio: dac: ad5592r: Fix the missing return value. - iio: dac: ad5446: Fix read_raw not returning set value - iio: magnetometer: ak8975: Fix the error handling in ak8975_power_on() - usb: misc: fix improper handling of refcount in uss720_probe() - usb: typec: ucsi: Fix role swapping - usb: gadget: uvc: Fix crash when encoding data for usb request - usb: gadget: configfs: clear deactivation flag in configfs_composite_unbind() - usb: dwc3: core: Fix tx/rx threshold settings - usb: dwc3: gadget: Return proper request status - serial: imx: fix overrun interrupts in DMA mode - serial: 8250: Also set sticky MCR bits in console restoration - serial: 8250: Correct the clock for EndRun PTP/1588 PCIe device - arch_topology: Do not set llc_sibling if llc_id is invalid - hex2bin: make the function hex_to_bin constant-time - hex2bin: fix access beyond string end - video: fbdev: udlfb: properly check endpoint type - arm64: dts: meson: remove CPU opps below 1GHz for G12B boards - arm64: dts: meson: remove CPU opps below 1GHz for SM1 boards - mtd: rawnand: fix ecc parameters for mt7622 - USB: Fix xhci event ring dequeue pointer ERDP update issue - ARM: dts: imx6qdl-apalis: Fix sgtl5000 detection issue - phy: samsung: Fix missing of_node_put() in exynos_sata_phy_probe - phy: samsung: exynos5250-sata: fix missing device put in probe error paths - ARM: OMAP2+: Fix refcount leak in omap_gic_of_init - phy: ti: omap-usb2: Fix error handling in omap_usb2_enable_clocks - ARM: dts: at91: Map MCLK for wm8731 on at91sam9g20ek - phy: mapphone-mdm6600: Fix PM error handling in phy_mdm6600_probe - phy: ti: Add missing pm_runtime_disable() in serdes_am654_probe - ARM: dts: Fix mmc order for omap3-gta04 - ARM: dts: am3517-evm: Fix misc pinmuxing - ARM: dts: logicpd-som-lv: Fix wrong pinmuxing on OMAP35 - ipvs: correctly print the memory size of ip_vs_conn_tab - mtd: rawnand: Fix return value check of wait_for_completion_timeout - bpf, lwt: Fix crash when using bpf_skb_set_tunnel_key() from bpf_xmit lwt hook - tcp: md5: incorrect tcp_header_len for incoming connections - tcp: ensure to use the most recently sent skb when filling the rate sample - sctp: check asoc strreset_chunk in sctp_generate_reconf_event - ARM: dts: imx6ull-colibri: fix vqmmc regulator - arm64: dts: imx8mn-ddr4-evk: Describe the 32.768 kHz PMIC clock - pinctrl: pistachio: fix use of irq_of_parse_and_map() - cpufreq: fix memory leak in sun50i_cpufreq_nvmem_probe - net: hns3: add validity check for message data length - net/smc: sync err code when tcp connection was refused - ip_gre: Make o_seqno start from 0 in native mode - tcp: fix potential xmit stalls caused by TCP_NOTSENT_LOWAT - bus: sunxi-rsb: Fix the return value
[Kernel-packages] [Bug 1976214] Re: [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1976135] Re: Jammy update: v5.15.37 upstream stable release
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1976248] Re: Revert PPC get_user workaround
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
[Kernel-packages] [Bug 1976587] Re: Fix can't boot up after change to vmd
This bug was fixed in the package linux - 5.15.0-41.44
---
linux (5.15.0-41.44) jammy; urgency=medium
* jammy/linux: 5.15.0-41.44 -proposed tracker (LP: #1979448)
* Fix can't boot up after change to vmd (LP: #1976587)
- PCI: vmd: Assign VMD IRQ domain before enumeration
- PCI: vmd: Revert 2565e5b69c44 ("PCI: vmd: Do not disable MSI-X remapping
if
interrupt remapping is enabled by IOMMU.")
* [SRU][Jammy/OEM-5.17][PATCH 0/1] Fix calltrace in mac80211 (LP: #1978297)
- mac80211: fix struct ieee80211_tx_info size
* [SRU][Jammy][PATCH 0/1] Fix amd display corruption on s2idle resume
(LP: #1978244)
- drm/amd/display: Don't reinitialize DMCUB on s0ix resume
* pl2303 serial adapter not recognized (LP: #1967493)
- USB: serial: pl2303: fix type detection for odd device
* Remove SAUCE patches from test_vxlan_under_vrf.sh in net of
ubuntu_kernel_selftests (LP: #1975691)
- Revert "UBUNTU: SAUCE: selftests: net: Don't fail test_vxlan_under_vrf on
xfail"
- Revert "UBUNTU: SAUCE: selftests: net: Make test for VXLAN underlay in
non-
default VRF an expected failure"
* Fix hp_wmi_read_int() reporting error (0x05) (LP: #1979051)
- platform/x86: hp-wmi: Fix hp_wmi_read_int() reporting error (0x05)
* Request to back port vmci patches to Ubuntu kernel (LP: #1978145)
- VMCI: dma dg: whitespace formatting change for vmci register defines
- VMCI: dma dg: add MMIO access to registers
- VMCI: dma dg: detect DMA datagram capability
- VMCI: dma dg: set OS page size
- VMCI: dma dg: register dummy IRQ handlers for DMA datagrams
- VMCI: dma dg: allocate send and receive buffers for DMA datagrams
- VMCI: dma dg: add support for DMA datagrams sends
- VMCI: dma dg: add support for DMA datagrams receive
- VMCI: Fix some error handling paths in vmci_guest_probe_device()
- VMCI: Release notification_bitmap in error path
- VMCI: Check exclusive_vectors when freeing interrupt 1
- VMCI: Add support for ARM64
- [Config] Update policies for VMWARE_VMCI and VMWARE_VMCI_VSOCKETS
* [UBUNTU 20.04] rcu stalls with many storage key guests (LP: #1975582)
- s390/gmap: voluntarily schedule during key setting
- s390/mm: use non-quiescing sske for KVM switch to keyed guest
* [SRU][OEM-5.14/OEM-5.17/Jammy][PATCH 0/1] Fix i915 calltrace on new ADL BIOS
(LP: #1976214)
- drm/i915: update new TMDS clock setting defined by VBT
* Revert PPC get_user workaround (LP: #1976248)
- powerpc: Export mmu_feature_keys[] as non-GPL
* Jammy update: v5.15.39 upstream stable release (LP: #1978240)
- MIPS: Fix CP0 counter erratum detection for R4k CPUs
- parisc: Merge model and model name into one line in /proc/cpuinfo
- ALSA: hda/realtek: Add quirk for Yoga Duet 7 13ITL6 speakers
- ALSA: fireworks: fix wrong return count shorter than expected by 4 bytes
- mmc: sdhci-msm: Reset GCC_SDCC_BCR register for SDHC
- mmc: sunxi-mmc: Fix DMA descriptors allocated above 32 bits
- mmc: core: Set HS clock speed before sending HS CMD13
- gpiolib: of: fix bounds check for 'gpio-reserved-ranges'
- x86/fpu: Prevent FPU state corruption
- KVM: x86/svm: Account for family 17h event renumberings in
amd_pmc_perf_hw_id
- iommu/vt-d: Calculate mask for non-aligned flushes
- iommu/arm-smmu-v3: Fix size calculation in arm_smmu_mm_invalidate_range()
- drm/amd/display: Avoid reading audio pattern past AUDIO_CHANNELS_COUNT
- drm/amdgpu: do not use passthrough mode in Xen dom0
- RISC-V: relocate DTB if it's outside memory region
- Revert "SUNRPC: attempt AF_LOCAL connect on setup"
- timekeeping: Mark NMI safe time accessors as notrace
- firewire: fix potential uaf in outbound_phy_packet_callback()
- firewire: remove check of list iterator against head past the loop body
- firewire: core: extend card->lock in fw_core_handle_bus_reset
- net: stmmac: disable Split Header (SPH) for Intel platforms
- genirq: Synchronize interrupt thread startup
- ASoC: da7219: Fix change notifications for tone generator frequency
- ASoC: wm8958: Fix change notifications for DSP controls
- ASoC: meson: Fix event generation for AUI ACODEC mux
- ASoC: meson: Fix event generation for G12A tohdmi mux
- ASoC: meson: Fix event generation for AUI CODEC mux
- s390/dasd: fix data corruption for ESE devices
- s390/dasd: prevent double format of tracks for ESE devices
- s390/dasd: Fix read for ESE with blksize < 4k
- s390/dasd: Fix read inconsistency for ESE DASD devices
- can: grcan: grcan_close(): fix deadlock
- can: isotp: remove re-binding of bound socket
- can: grcan: use ofdev->dev when allocating DMA memory
- can: grcan: grcan_probe(): fix broken system id check for errata
workaround
needs
- can: grcan: only use the NAPI poll budget for RX
- nfc: replace improper check device_is_registered() in
