[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1052.50)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1052.50) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) systemd/245.4-4ubuntu3.7 (amd64) lxc/1:4.0.6-0ubuntu1~20.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/focal/update_excuses.html#linux-meta-azure [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1933707] [NEW] Many ACPI errors
Public bug reported: Many ACPI errors in dmesg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-23-generic 5.11.0-23.24 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi1338 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 04:03:56 2021 InstallationDate: Installed on 2021-04-25 (61 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Acer Aspire A515-56 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-23-generic root=UUID=0c5f066e-35cd-4f76-a271-a1c97ba74ee3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-23-generic N/A linux-backports-modules-5.11.0-23-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1933707/+attachment/5507154/+files/dmesg.log -- 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/1933707 Title: Many ACPI errors Status in linux package in Ubuntu: New Bug description: Many ACPI errors in dmesg ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-23-generic 5.11.0-23.24 ProcVersionSignature: Ubuntu 5.11.0-23.24-generic 5.11.22 Uname: Linux 5.11.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi1338 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 04:03:56 2021 InstallationDate: Installed on 2021-04-25 (61 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Acer Aspire A515-56 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-23-generic root=UUID=0c5f066e-35cd-4f76-a271-a1c97ba74ee3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-23-generic N/A linux-backports-modules-5.11.0-23-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Chassis Location dmi.board.name: Iris_TL dmi.board.vendor: TGL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.12 dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd05/26/2021:br1.12:efr1.12:svnAcer:pnAspireA515-56:pvrV1.12:rvnTGL:rnIris_TL:rvrV1.12:cvnAcer:ct10:cvrV1.12: dmi.product.family: Aspire 5 dmi.product.name: Aspire A515-56 dmi.product.sku: dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933707/+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-dell300x/4.15.0.1023.25)
All autopkgtests for the newly accepted linux-meta-dell300x (4.15.0.1023.25) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) lxd/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-dell300x [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-azure-4.15/4.15.0.1119.92)
All autopkgtests for the newly accepted linux-meta-azure-4.15 (4.15.0.1119.92) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) lxd/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-azure-4.15 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-raspi-5.4/5.4.0.1039.41)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1039.41) for bionic have finished running. The following regressions have been reported in tests triggered by the package: ktap/unknown (arm64) lxc/unknown (arm64) zfs-linux/unknown (arm64) systemd/237-3ubuntu10.48 (armhf) rtl8812au/unknown (arm64) lxd/3.0.3-0ubuntu1~18.04.1 (arm64) glibc/unknown (arm64) xtables-addons/unknown (arm64) r8168/unknown (arm64) systemd/unknown (arm64) spl-linux/unknown (arm64) acpi-call/1.1.0-4 (arm64) ddcci-driver-linux/unknown (arm64) lime-forensics/unknown (arm64) wireguard-linux-compat/1.0.20201112-1~18.04.1 (arm64) rtl8821ce/unknown (arm64) fwts/unknown (arm64) dpdk/unknown (arm64) dm-writeboost/unknown (arm64) nat-rtsp/unknown (arm64) bbswitch/unknown (arm64) asic0x/unknown (arm64) 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-raspi-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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-oem-5.10/5.10.0.1035.36)
All autopkgtests for the newly accepted linux-meta-oem-5.10 (5.10.0.1035.36) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) broadcom-sta/6.30.223.271-12 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64) lime-forensics/1.9-1ubuntu0.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) dm-writeboost/2.2.9-1ubuntu1.2 (amd64) systemd/245.4-4ubuntu3.7 (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/focal/update_excuses.html#linux-meta-oem-5.10 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1039.74)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1039.74) for focal have finished running. The following regressions have been reported in tests triggered by the package: nat-rtsp/unknown (arm64) dpdk/unknown (arm64) rtl8812au/unknown (arm64) lime-forensics/unknown (arm64) langford/unknown (arm64) r8168/unknown (arm64) xtables-addons/unknown (arm64) snapd/unknown (arm64) evdi/unknown (arm64) iptables-netflow/unknown (arm64) rtl8821ce/unknown (arm64) mali-midgard/unknown (arm64) wireguard/unknown (arm64) openafs/unknown (arm64) wireguard-linux-compat/unknown (arm64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64, armhf) dm-writeboost/unknown (arm64) gost-crypto/unknown (arm64) systemd/245.4-4ubuntu3.7 (armhf) systemd/unknown (arm64) v4l2loopback/unknown (arm64) west-chamber/unknown (arm64) 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/focal/update_excuses.html#linux-meta-raspi [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1933703] [NEW] kernel BUG at mm/usercopy.c:99!
Public bug reported: I get randomly a bug with an error description for kernel BUG at mm/usercopy.c:99! I attached the error text. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 00:01:44 2021 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "error.txt" https://bugs.launchpad.net/bugs/1933703/+attachment/5507149/+files/error.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933703 Title: kernel BUG at mm/usercopy.c:99! Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: I get randomly a bug with an error description for kernel BUG at mm/usercopy.c:99! I attached the error text. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 00:01:44 2021 SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933703/+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 1932360] Re: IR receiver broken by 5.8.0-55, worked in -48
*** This bug is a duplicate of bug 1901089 *** https://bugs.launchpad.net/bugs/1901089 ** This bug has been marked a duplicate of bug 1901089 Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading -- 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/1932360 Title: IR receiver broken by 5.8.0-55, worked in -48 Status in linux package in Ubuntu: New Bug description: On intel nuc used as media server running ubuntu 20.04, the IR remote broke in kernel 5.8.0-55. Running ir-keytable -t shows that a single IR button press spews key down codes forever, and never does a key up. Going back to kernel 5.8.0-48 makes the remote work properly again. Here's a sample of the working output: Testing events. Please, press CTRL-C to abort. 381.380140: lirc protocol(rc6_mce): scancode = 0x800f0423 toggle=1 381.380213: event type EV_MSC(0x04): scancode = 0x800f0423 381.380213: event type EV_KEY(0x01) key_down: KEY_ESC(0x0001) 381.380213: event type EV_SYN(0x00). ^[381.485706: lirc protocol(rc6_mce): scancode = 0x800f0423 toggle=1 381.485722: event type EV_MSC(0x04): scancode = 0x800f0423 381.485722: event type EV_SYN(0x00). 381.592718: lirc protocol(rc6_mce): scancode = 0x800f0423 toggle=1 381.592736: event type EV_MSC(0x04): scancode = 0x800f0423 381.592736: event type EV_SYN(0x00). 381.725662: event type EV_KEY(0x01) key_up: KEY_ESC(0x0001) 381.725662: event type EV_SYN(0x00). The key down part just repeats over and over in the busted kernel. root@nuc:~# lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932360/+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-raspi2/4.15.0.1090.87)
All autopkgtests for the newly accepted linux-meta-raspi2 (4.15.0.1090.87) for bionic have finished running. The following regressions have been reported in tests triggered by the package: r8168/unknown (arm64) nat-rtsp/unknown (arm64) xtables-addons/unknown (arm64) dm-writeboost/unknown (arm64) r8168/8.045.08-2ubuntu1 (armhf) asic0x/unknown (arm64) spl-linux/unknown (arm64) systemd/237-3ubuntu10.48 (armhf) adv-17v35x/unknown (arm64) bbswitch/unknown (arm64) rtl8821ce/unknown (arm64) snapd/unknown (arm64) rtl8812au/unknown (arm64) ktap/unknown (arm64) fwts/unknown (arm64) systemd/unknown (arm64) langford/0.0.20130228-5ubuntu1 (armhf) lime-forensics/unknown (arm64) acpi-call/unknown (arm64) wireguard-linux-compat/unknown (arm64) glibc/unknown (arm64) zfs-linux/unknown (arm64) lttng-modules/unknown (arm64) dpdk/unknown (arm64) rtl8821ce/5.5.2.1-0ubuntu3~18.04.1 (armhf) v4l2loopback/unknown (arm64) ddcci-driver-linux/unknown (arm64) langford/unknown (arm64) west-chamber/unknown (arm64) 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-raspi2 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1047.56)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1047.56) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.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/focal/update_excuses.html#linux-meta-gcp [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1786013] Autopkgtest regression report (linux-meta-gke/5.4.0.1047.56)
All autopkgtests for the newly accepted linux-meta-gke (5.4.0.1047.56) for focal have finished running. The following regressions have been reported in tests triggered by the package: lxc/1:4.0.6-0ubuntu1~20.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/focal/update_excuses.html#linux-meta-gke [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1930637] Re: ath11k WIFI not working in proposed kernel 5.11.0-19-generic
Ok, although I am normally using Hirsute, today I installed Focal, so I could
do the requested testing here for Focal as well.
I tested:
- 5.11.0-20-generic
- 5.11.0-20-lowlatency
- 5.11.0-22-generic
- 5.11.0-22-lowlatency
- 5.11.0-23-generic
- 5.11.0-23-lowlatency
Because these where the kernels that I got available today with Proposed
enabled.
All of these kernels give me a working Soundwire and a working ath11k!
--
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/1930637
Title:
ath11k WIFI not working in proposed kernel 5.11.0-19-generic
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Bug 1928857 pulls stable patches from v5.11.20, which contains commit
dc764382762e {"bus: mhi: core: Process execution environment changes
serially") that cause a regression on ath11k cards and fails device
init:
mhi mhi0: MHI did not enter SBL
[Fix]
Upsteram commit 4884362f6977 ("bus: mhi: core: Download AMSS image
from appropriate function"), also landed to v5.12.6 but not v5.11
stable tree, has fixed this.
[Test Case]
Tested on Dell XPS 13 9310. No longer has this regression and both
WiFi/Bluetooth works fine as before.
[Where problems could occur]
The actual firmware downloading process is moved into a state machine
callback that has identical semantics with before. Additions or removals
to this in the future may change the timing of fw being dowloaded.
[Other Info]
While the commit causing this regress is backported to 5.11 onward and
fixed in v5.12 and 5.13, leaving Hirsute is the only victim.
== original bug report ==
See these references for more information:
- https://bugzilla.kernel.org/show_bug.cgi?id=213055
- https://bugs.archlinux.org/task/70849
Can you please prevent this already fixed bug from being introduced any
further into Ubuntu.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930637/+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 1933697] [NEW] touchpad not working
Public bug reported: my touchpad and mouses are not recongnized by ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-59-generic 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spiders17 4049 F pulseaudio /dev/snd/controlC0: spiders17 4049 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 21:00:22 2021 InstallationDate: Installed on 2020-10-09 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-43 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d1574370-d401-4eaa-86d0-ceeec8393f1b ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/18/2019:svnAcer:pnNitroAN515-43:pvrV1.06:rvnPK:rnOctavia_PKS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933697 Title: touchpad not working Status in linux package in Ubuntu: New Bug description: my touchpad and mouses are not recongnized by ubuntu 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-59-generic 5.4.0-59.65 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: spiders17 4049 F pulseaudio /dev/snd/controlC0: spiders17 4049 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 21:00:22 2021 InstallationDate: Installed on 2020-10-09 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Nitro AN515-43 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=d1574370-d401-4eaa-86d0-ceeec8393f1b ro recovery nomodeset dis_ucode_ldr RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd09/18/2019:svnAcer:pnNitroAN515-43:pvrV1.06:rvnPK:rnOctavia_PKS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933697/+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 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud
** Changed in: linux (Ubuntu) Status: New => Triaged -- 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/1931728 Title: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud Status in linux package in Ubuntu: Triaged Status in qemu package in Ubuntu: Invalid Bug description: This is something to do with the configuration or software versions running here, since we have identical hardware running in an adjacent cloud region but with different versions of the cloud/virt stack. When we boot bionic arm64 Ubuntu cloud images in "bos01" and they land on the eMAG systems, they always fail like this: ... [1.585611] Key type dns_resolver registered [1.587408] registered taskstats version 1 [1.588913] Loading compiled-in X.509 certificates [1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4' [1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [1.610861] Couldn't get size: 0x800e [1.613413] MODSIGN: Couldn't get UEFI db list [1.615920] Couldn't get size: 0x800e [1.618256] MODSIGN: Couldn't get UEFI MokListRT [1.620315] Couldn't get size: 0x800e [1.622317] MODSIGN: Couldn't get UEFI dbx list [1.624446] zswap: loaded using pool lzo/zbud [1.628185] Key type big_key registered [1.629937] Key type trusted registered [1.632012] Key type encrypted registered [1.633668] AppArmor: AppArmor sha1 policy hashing enabled [1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19) [1.638009] ima: Allocated hash algorithm: sha1 [1.639272] evm: HMAC attrs: 0x1 [1.640875] rtc-efi rtc-efi: setting system clock to 2021-05-11 09:28:43 UTC (1620725323) [1.646247] Freeing unused kernel memory: 5824K [1.657870] Checked W+X mappings: passed, no W+X pages found [1.660250] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.660250] [1.663294] CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-142-generic #146-Ubuntu [1.665939] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 [1.668204] Call trace: [1.668981] dump_backtrace+0x0/0x198 [1.670212] show_stack+0x24/0x30 [1.671282] dump_stack+0x98/0xc8 [1.672433] panic+0x128/0x2b0 [1.673502] do_exit+0x75c/0xa80 [1.674749] do_group_exit+0x40/0xb0 [1.676191] get_signal+0x114/0x6e8 [1.677867] do_signal+0x18c/0x240 [1.679498] do_notify_resume+0xd0/0x328 [1.681302] work_pending+0x8/0x10 [1.682771] SMP: stopping secondary CPUs [1.684624] Kernel Offset: disabled [1.686119] CPU features: 0x04802008 [1.687353] Memory Limit: none [1.688453] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0005 [1.688453] Full example log: https://autopkgtest.ubuntu.com/results/autopkgtest- bionic/bionic/arm64/c/chromium-browser/20210511_093739_ea3f2@/log.gz We tried to get IS to roll things back to match the working bos02, but they said it's too different and not possible. The working cloud is running Mitaka from the cloud archive on Xenial (qemu 2.5) The broken cloud is running Queens from the cloud archive on Xenial (qemu 2.11) The other thing someone suggested we try is that MDS mitigation is enabled in the broken cloud, so we could disable it. No idea if that makes sense tbh. That's about all we have right now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931728/+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 1933691] [NEW] Hirsute update: upstream stable patchset 2021-06-25
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-06-25 Ported from the following upstream stable releases: v5.10.43, v5.12.10 from git://git.kernel.org/ hwmon: (dell-smm-hwmon) Fix index values hwmon: (pmbus/isl68137) remove READ_TEMPERATURE_3 for RAA228228 netfilter: conntrack: unregister ipv4 sockopts on error unwind efi/fdt: fix panic when no valid fdt found efi: Allow EFI_MEMORY_XP and EFI_MEMORY_RO both to be cleared efi/libstub: prevent read overflow in find_file_option() efi: cper: fix snprintf() use in cper_dimm_err_location() vfio/pci: Fix error return code in vfio_ecap_init() vfio/pci: zap_vma_ptes() needs MMU samples: vfio-mdev: fix error handing in mdpy_fb_probe() vfio/platform: fix module_put call in error flow ipvs: ignore IP_VS_SVC_F_HASHED flag when adding service HID: logitech-hidpp: initialize level variable HID: pidff: fix error return code in hid_pidff_init() HID: i2c-hid: fix format string mismatch devlink: Correct VIRTUAL port to not have phys_port attributes net/sched: act_ct: Offload connections with commit action net/sched: act_ct: Fix ct template allocation for zone 0 mptcp: always parse mptcp options for MPC reqsk nvme-rdma: fix in-casule data send for chained sgls ACPICA: Clean up context mutex during object deletion perf probe: Fix NULL pointer dereference in convert_variable_location() net: dsa: tag_8021q: fix the VLAN IDs used for encoding sub-VLANs net: sock: fix in-kernel mark setting net/tls: Replace TLS_RX_SYNC_RUNNING with RCU net/tls: Fix use-after-free after the TLS device goes down and up net/mlx5e: Fix incompatible casting net/mlx5: Check firmware sync reset requested is set before trying to abort it net/mlx5e: Check for needed capability for cvlan matching net/mlx5: DR, Create multi-destination flow table with level less than 64 nvmet: fix freeing unallocated p2pmem netfilter: nft_ct: skip expectations for confirmed conntrack netfilter: nfnetlink_cthelper: hit EBUSY on updates if size mismatches drm/i915/selftests: Fix return value check in live_breadcrumbs_smoketest() bpf: Simplify cases in bpf_base_func_proto bpf, lockdown, audit: Fix buggy SELinux lockdown permission checks ieee802154: fix error return code in ieee802154_add_iface() ieee802154: fix error return code in ieee802154_llsec_getparams() igb: add correct exception tracing for XDP ixgbevf: add correct exception tracing for XDP cxgb4: fix regression with HASH tc prio value update ipv6: Fix KASAN: slab-out-of-bounds Read in fib6_nh_flush_exceptions ice: Fix allowing VF to request more/less queues via virtchnl ice: Fix VFR issues for AVF drivers that expect ATQLEN cleared ice: handle the VF VSI rebuild failure ice: report supported and advertised autoneg using PHY capabilities ice: Allow all LLDP packets from PF to Tx i2c: qcom-geni: Add shutdown callback for i2c cxgb4: avoid link re-train during TC-MQPRIO configuration i40e: optimize for XDP_REDIRECT in xsk path i40e: add correct exception tracing for XDP ice: simplify ice_run_xdp ice: optimize for XDP_REDIRECT in xsk path ice: add correct exception tracing for XDP ixgbe: optimize for XDP_REDIRECT in xsk path ixgbe: add correct exception tracing for XDP arm64: dts: ti: j7200-main: Mark Main NAVSS as dma-coherent optee: use export_uuid() to copy client UUID bus: ti-sysc: Fix am335x resume hang for usb otg module arm64: dts: ls1028a: fix memory node arm64: dts: zii-ultra: fix 12V_MAIN voltage arm64: dts: freescale: sl28: var4: fix RGMII clock and voltage ARM: dts: imx7d-meerkat96: Fix the 'tuning-step' property ARM: dts: imx7d-pico: Fix the 'tuning-step' property ARM: dts: imx: emcon-avari: Fix nxp,pca8574 #gpio-cells bus: ti-sysc: Fix flakey idling of uarts and stop using swsup_sidle_act tipc: add extack messages for bearer/media failure tipc: fix unique bearer names sanity check serial: stm32: fix threaded interrupt handling riscv: vdso: fix and clean-up Makefile io_uring: fix link timeout refs io_uring: use better types for cflags drm/amdgpu/vcn3: add cancel_delayed_work_sync before power gate drm/amdgpu/jpeg2.5: add cancel_delayed_work_sync before power gate drm/amdgpu/jpeg3: add cancel_delayed_work_sync before power gate Bluetooth: fix the erroneous flush_work() order Bluetooth: use correct lock to prevent UAF of hdev object wireguard: do not use -O3 wireguard: peer: allocate in kmem_cache wireguard: use synchronize_net rather than synchronize_rcu wireguard: selftests: remove old conntrack kconfig value wireguard: selftests: make sure rp_filter is
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.11/5.11.0.23.24~20.04.7)
All autopkgtests for the newly accepted linux-meta-hwe-5.11 (5.11.0.23.24~20.04.7) for focal have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) systemd/245.4-4ubuntu3.7 (ppc64el, s390x, amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.2 (amd64) broadcom-sta/6.30.223.271-12 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (s390x, armhf, arm64, amd64) evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (ppc64el, s390x, arm64, amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) dm-writeboost/2.2.9-1ubuntu1.2 (ppc64el, s390x, arm64, amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (ppc64el, arm64, amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (ppc64el, s390x, arm64, amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (arm64, amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (ppc64el, s390x, armhf, arm64, amd64) lime-forensics/1.9-1ubuntu0.2 (ppc64el, s390x, arm64, amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) west-chamber/20100405+svn2007.r124-12ubuntu0.3~20.04.1 (ppc64el, s390x, armhf, arm64, 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/focal/update_excuses.html#linux-meta-hwe-5.11 [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell
[Kernel-packages] [Bug 1930645] Re: Fix Ethernet not working by hotplug - RTL8106E
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1930645 Title: Fix Ethernet not working by hotplug - RTL8106E Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: New Bug description: [Impact] After hot-plug the Ethernet cable, the status of Ethernet is always down. [Fix] Because ASPM is enabled on RTL8106E, the link change interrupt can't be fired immediately. Must wait a long time to get the link change interrupt. After discuss with maintainer, he give some suggestions 1. use PHY_POLL. 2. he send a workaround(Ref. [1]) to disable ASPM on RTL8106E. For 2, because don't know the details about operated registers in rtl_hw_aspm_clkreq_enable, it have higher risk on power usage during suspend. For 1, Use PHY_POLL have a lower risk because don't change any register operations and use polling method to query link change status. SRU the patches for 1 first. Currently keep discussing with Realtek but don't figure out yet. Will re-SRU the official solution once Realtek resolve the issue. Ref [1], https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/?id=1ee8856de82faec9bc8bd0f2308a7f27e30ba207 [Test] Verified on machines with Realtek Ethernet device, the Ethernet works well after hotplug 30 times. [Regression Potential] Medium, use polling methond may have higher cpu usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930645/+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-hwe-5.4/5.4.0.78.87~18.04.70)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.78.87~18.04.70) for bionic have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) acpi-call/1.1.0-4 (ppc64el, s390x) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) zfs-linux/0.7.5-1ubuntu16.11 (arm64, ppc64el, amd64, s390x) lxd/3.0.3-0ubuntu1~18.04.1 (arm64, ppc64el, i386, amd64, s390x) lxc/3.0.3-0ubuntu1~18.04.1 (arm64, ppc64el, i386, amd64, s390x) kpatch/0.5.0-0ubuntu1.1 (amd64) asic0x/1.0.1-1 (s390x) systemd/237-3ubuntu10.48 (armhf) 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-hwe-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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1928482] Re: [Castle Peak]: pull in CPPC fixes
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928482 Title: [Castle Peak]: pull in CPPC fixes Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Bug description: Recently a CPPC fix was accepted for fixing CPPC on many AMD platforms. https://github.com/torvalds/linux/commit/3743d55b289c203d8f77b7cd47c24926b9d186ae It's CC'ed to stable, so it will eventually flow in, but to give best performance on customer systems, can you please pull this into all sustaining OEM trees? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928482/+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 1931147] Re: Fix non-working GPU on Some HP desktops
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931147 Title: Fix non-working GPU on Some HP desktops Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] Integrated GPU on AMD based HP desktop doesn't work. [Fix] Coalesce host bridge contiguous apertures so the resources requested by child devices can be met. [Test] Boot affected systems. No picture from the iGPU. With the patch applied, iGPU can work normally. [Where problems could occur] Assume there are device A and device B and they request overlapped resource region, the original logic may not be able to allocate enough resource for A so device B claimed the resource in the end. Once the fix is applied, the region may be big enough for device A, hence device B won't be able to get the resource it needs. Hopefully we don't have such broken systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931147/+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 1930188] Re: Acer Aspire 5 sound driver issues
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in linux package in Ubuntu: New Bug description: Hello, There seems to be lots of issues in sound driver for Acer Aspire A515-56-57XR with ALC255. I will list all of them below and what I have tried so far. 1. Headphones appears always plugged in even if they are physically not 2. When actually plugging in headset/earphones it does not auto switch from speakers/internal mic to headphones/headset microphone automatically and vice versa, have to manually switch everytime. 3. External headset/earphones microphone won't work at all After, logs of trial and error I have found a temporary fix. This seems to use legacy intel drivers which solves all 3 issues mentioned above but the internal/dmic mic is completely gone (which seems intentional when using this). Both depreciated dmic_detect and dsp_driver works, I have been using dsp_driver for now as I need external microphone at any cost. End of /etc/modprobe.d/alsa-base.conf # Headset mic fix options snd-hda-intel dmic_detect=0 / options snd-intel-dspcfg dsp_driver=1 options snd-hda-intel model=alc255-acer In another thread similar to this I got some support and at least fixed the external microphone without using the alsa-base.conf change in custom modified kernel. I will attach it here. Now, hoping to fix other issues as well slowly like making headphones unplugged when physically removing as well as auto switching like the legacy driver one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930188/+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 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+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 1932577] Re: [Cezanne/Renoir] Adjust uPEP for different _HID behavior
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932577 Title: [Cezanne/Renoir] Adjust uPEP for different _HID behavior Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: Feature: Correct uPEP support for all current ACPI _HID for AMD s2idle Code: Currently oem-5.10 carries hack ""platform/x86: force LPS0 functions for AMD"" which helps some RN platforms, but is not the correct solution. The code that is the correct solution has been submitted to linux-acpi: https://lore.kernel.org/linux-acpi/f50c6baf-a780-7a58-4083-88d539342...@gmail.com/T/#t This will fix RN properly and will also add support for the different variations used for CZN for uPEP. Please replace hack in oem-5.10, and also apply this series for oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1932577/+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 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1933566
Title:
XPS 9510 (TGL) Screen Brightness could not be changed
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933566/+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-snapdragon/4.15.0.1107.110)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1107.110) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) lxc/3.0.3-0ubuntu1~18.04.1 (arm64) 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-snapdragon [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1933685] Re: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.l
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933685 Title: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.8.0-59-generic.list-new': Operation not permitted Status in linux-hwe-5.8 package in Ubuntu: New Bug description: This error occurs after I boot up the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 23 06:50:52 2021 Dependencies: DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb ... Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-59-generic:5.8.0-59.66~20.04.1 Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-10-16 (251 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: linux-hwe-5.8 Title: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1933685/+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 1933685] [NEW] package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic
Public bug reported: This error occurs after I boot up the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 23 06:50:52 2021 Dependencies: DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb ... Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-59-generic:5.8.0-59.66~20.04.1 Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-10-16 (251 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: linux-hwe-5.8 Title: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.8 (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 linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933685 Title: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- modules-5.8.0-59-generic.list-new': Operation not permitted Status in linux-hwe-5.8 package in Ubuntu: New Bug description: This error occurs after I boot up the system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Jun 23 06:50:52 2021 Dependencies: DpkgTerminalLog: Preparing to unpack .../0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb ... Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted DuplicateSignature: package:linux-modules-5.8.0-59-generic:5.8.0-59.66~20.04.1 Unpacking linux-modules-5.8.0-59-generic (5.8.0-59.66~20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-kIeVCR/0-linux-modules-5.8.0-59-generic_5.8.0-59.66~20.04.1_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted ErrorMessage: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted InstallationDate: Installed on 2020-10-16 (251 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: linux-hwe-5.8 Title: package linux-modules-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-modules-5.8.0-59-generic.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1933685/+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 1927866] Re: Root filesystem becomes readonly frequenty freezing system
Thanks for the update @kaihengfeng I think I spoke too soon. The system just crashed again :( There was a set of system updates yesterday from Ubuntu for 20.04 that I ran. Not sure if that contributed. Can we add some debug capability to capture a little more info on what is happening? -- 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/1927866 Title: Root filesystem becomes readonly frequenty freezing system Status in linux package in Ubuntu: Confirmed Bug description: I have a brand new Lenovo Ideapad Flex 5.14 which came with Windows 10 and I have installed Ubuntu 21.04 with dual boot. I am running into this problem where the root filesystem becomes readonly and the system freezes with a screen full of errors shown about unable to write to filesystem. I booted into a live boot usb and did fsck and e2fsck but did not see any errors there. I read online that this could be because of io errors but smartctl and fsck does not show any errors So I was wondering if this could be a bug vs a hardward issue. Please let me know if you need any further information from the system. = = fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors Disk model: WDC PC SN530 SDBPMPZ-512G-1101 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: E8803E28-C4F7-4FA5-9B6D-0F3CAB7027A5 Device StartEnd Sectors Size Type /dev/nvme0n1p1 2048 534527532480 260M EFI System /dev/nvme0n1p2534528 567295 3276816M Microsoft reserved /dev/nvme0n1p3567296 199446527 198879232 94.8G Microsoft basic data /dev/nvme0n1p4 998166528 1000214527 2048000 1000M Windows recovery environmen /dev/nvme0n1p5 199446528 203352063 3905536 1.9G Linux filesystem /dev/nvme0n1p6 203352064 219353087 16001024 7.6G Linux swap /dev/nvme0n1p7 219353088 414664703 195311616 93.1G Linux filesystem /dev/nvme0n1p8 414664704 998166527 583501824 278.2G Microsoft basic data = = smartctl -a /dev/nvme0 smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.11.0-16-generic] (local build) Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC PC SN530 SDBPMPZ-512G-1101 Serial Number: 205135806243 Firmware Version: 21160001 PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 NVMe Version: 1.4 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:001b44 8b484daff7 Local Time is: Sun May 9 12:45:05 2021 EDT Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.10W -0 0 0 00 0 1 + 2.40W1.60W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0250W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:35 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:624,535 [319 GB] Data Units Written: 526,042 [269 GB] Host Read Commands:
[Kernel-packages] [Bug 1928686] Re: Oracle kernel has Android related config options disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Bionic: New Status in linux-oracle source package in Focal: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Committed Bug description: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+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 1931959] Re: iscsi-related backports requested for Oracle-cloud
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- groovy' to 'verification-done-groovy'. If the problem still exists, change the tag 'verification-needed-groovy' to 'verification-failed- groovy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1931959 Title: iscsi-related backports requested for Oracle-cloud Status in linux-oracle package in Ubuntu: New Status in linux-oracle source package in Focal: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Bug description: As part of some work to enable high performance iscsi storage leveraging multipath, Oracle submitted and landed patches upstream, which were released as part of 5.10. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2a242d59d6b908341c0d426bc6e7f8e28871cbd0 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0610959fbbca62b534f1f276873fd297f76b164b commit 2a242d59d6b908341c0d426bc6e7f8e28871cbd0 Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:53 2020 -0500 scsi: core: Add limitless cmd retry support commit 0610959fbbca62b534f1f276873fd297f76b164b Author: Mike Christie michael.chris...@oracle.com Date: Thu Oct 1 10:35:54 2020 -0500 scsi: sd: Allow user to configure command retries See https://canonical.lightning.force.com/lightning/r/Case/5004K05pykQQAQ/view for more info. [Impact] Optimizations/improvements in iscsi-code [Fix] 2 patches - see above [Test] Build, boot, initiate an iscsi connection to a target. [Regression Potential] Possible impact on iscsi functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1931959/+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 1925263] Re: TL-WN821N V5 does not work
** Also affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1925263 Title: TL-WN821N V5 does not work Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: I bought a TP-Link TL-WN821N V5 wireless adapter and it is not working on Xubuntu 20.04. On dmesg, it is detected correctly. However, the authentication times out very quickly. The module from https://github.com/clnhub/rtl8192eu-linux.git works, but this is not ideal, because it requires rebuilding the module for every kernel version and, either disable Secure Boot or sign every module for every kernel update. The attached file has the full dmesg log, including trying rtl8xxxu with debug=0x log. I noticed the log shows this device is untested. lshw output for this device: *-network:1 description: Wireless interface physical id: 4 bus info: usb@1:1 logical name: wlxd03745cb0794 serial: d0:37:45:cb:07:94 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8xxxu driverversion=5.8.0-50-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11 lsusb: Bus 001 Device 005: ID 2357:0107 TP-Link TL-WN821N Version 5 RTL8192EU ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-50-generic 5.8.0-50.56~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 20 19:42:11 2021 InstallationDate: Installed on 2017-06-13 (1406 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: Upgraded to focal on 2019-12-22 (485 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1925263/+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 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
For the sake of testing, I checked on the latest Impish daily image, with kernel 5.11.0-18-generic. Same problem. dmesg attached. Alsa and PulseAudio don't detect any sound card, even though in dmesg we can see: $ sudo dmesg | grep -i snd [ 26.169850] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 26.169858] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SST driver $ aplay -l aplay: device_list:276: no soundcards found... ubuntu@ubuntu:~$ pactl list cards ubuntu@ubuntu:~$ pactl list sources Source #0 State: SUSPENDED Name: auto_null.monitor Description: Monitor of Dummy Output Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 13 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: auto_null Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Dummy Output" device.class = "monitor" device.icon_name = "audio-input-microphone" Formats: pcm ubuntu@ubuntu:~$ pactl list sinks Sink #0 State: SUSPENDED Name: auto_null Description: Dummy Output Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 13 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: auto_null.monitor Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY SET_FORMATS Properties: device.description = "Dummy Output" device.class = "abstract" device.icon_name = "audio-card" Formats: pcm ** Attachment added: "dmesg_kernel_5.11.0-18-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507056/+files/dmesg_kernel_5.11.0-18-generic.log -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10
[Kernel-packages] [Bug 1932368] Re: boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic
*** This bug is a duplicate of bug 1931088 *** https://bugs.launchpad.net/bugs/1931088 ** This bug has been marked a duplicate of bug 1931088 boot-and-services tests fails in impish on armhf (248.3) -- 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/1932368 Title: boot-smoke systemd/237-3ubuntu10.48 ADT test failure with bionic Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/4.15.0-145.149 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Possibly similar to Bug 1931088 (boot-and-services tests fails in impish on armhf (248.3) Testing failed on: armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/armhf/s/systemd/20210617_212156_99b77@/log.gz Processing triggers for systemd (237-3ubuntu10.48) ... (Reading database ... 83520 files and directories currently installed.) Removing autopkgtest-satdep (0) ... autopkgtest [21:20:14]: test boot-smoke: [--- reboot #0 bash: line 1: 41305 Killed /tmp/autopkgtest.gB2khM/build.j7s/src/debian/tests/boot-smoke 2> >(tee -a /tmp/autopkgtest.gB2khM/boot-smoke-stderr >&2) > >(tee -a /tmp/autopkgtest.gB2khM/boot-smoke-stdout) autopkgtest [21:20:18]: test process requested reboot with marker 1 Unexpected error: Traceback (most recent call last): File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 740, in mainloop command() File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 669, in command r = f(c, ce) File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 364, in cmd_reboot caller.hook_wait_reboot(**wait_reboot_args) File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-lxd", line 238, in hook_wait_reboot wait_booted() File "/home/ubuntu/autopkgtest/virt/autopkgtest-virt-lxd", line 104, in wait_booted VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', r'if [ -d /run/systemd/system ]; then systemctl start network-online.target; else while ps -ef | grep -q "/etc/init\.d/rc"; do sleep 1; done; fi'], timeout=60) File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec (status, out, err) = execute_timeout(None, timeout, real_argv, File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 144, in execute_timeout (out, err) = sp.communicate(instr) File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate stderr = self.stderr.read() File "/home/ubuntu/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler raise Timeout() VirtSubproc.Timeout autopkgtest [21:21:55]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932368/+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 1928694] Re: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream
** Tags added: cezanne renoire -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928694 Title: [Cezanne/Renoire]: Replace some fixes from linux-oem-5.10 with those landing upstream Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Bug description: The following patches are accepted into upstream for 5.14 and should displace the existing patches carried in OEM tree. * "ACPI: processor idle: Fix up C-state latency if not ordered" replaces the hack to hardcode latency values for HP's RN systems. * "ACPI: PM: s2idle: Add missing LPS0 functions for AMD" has been accepted To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928694/+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 1932303] Re: Dell XPS 17 9700 wifi
Unfortunately 5.11.0-20-generic does NOT fix the wifi. As you can see in the dmesg output above, the ath11k driver is present but doesn't seem to enable any interfaces. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932303 Title: Dell XPS 17 9700 wifi Status in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Incomplete Bug description: Release: devops@devops-XPS-17-9700:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 devops@devops-XPS-17-9700:~$ Problem: Cannot get both wifi and sound working on a Dell XPS 17 9700 (i9 processor) at the same time. With the 5.10.0-1029-oem kernel wifi works, but sound (microphone) does not. With the 5.11.0-20-generic kernel, the microphone and sound works (thank you for fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632) but the wifi does not. With the 5.11.0-20-generic kernel and the linux-firmware (1.187.14) pkg installed (sound works but no wifi): Information with 5.11.0-20-generic kernel: devops@devops-XPS-17-9700:~$ sudo lspci -knn | grep Net -A3; rfkill list [sudo] password for devops: 04:00.0 Network controller [0280]: Qualcomm Device [17cb:1101] (rev 01) Subsystem: Bigfoot Networks, Inc. Device [1a56:a501] Kernel driver in use: ath11k_pci Kernel modules: ath11k_pci 05:00.0 PCI bridge [0604]: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] [8086:15ea] (rev 06) 0: hci0: Bluetooth Soft blocked: no Hard blocked: no devops@devops-XPS-17-9700:~$ sudo lshw -C network *-network description: Network controller product: Qualcomm vendor: Qualcomm physical id: 0 bus info: pci@:04:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:195 memory:d210-d21f devops@devops-XPS-17-9700:~$ uname -sr Linux 5.11.0-20-generic devops@devops-XPS-17-9700:~$ sudo dmesg | grep ath11k [2.671864] ath11k_pci :04:00.0: WARNING: ath11k PCI support is experimental! [2.679263] ath11k_pci :04:00.0: BAR 0: assigned [mem 0xd210-0xd21f 64bit] [2.679309] ath11k_pci :04:00.0: enabling device ( -> 0002) devops@devops-XPS-17-9700:~$ sudo dpkg -l | grep firmware ii amd64-microcode 3.20191218.1ubuntu1 amd64Processor microcode firmware for AMD CPUs ii intel-microcode 3.20201110.0ubuntu0.20.04.2 amd64Processor microcode firmware for Intel CPUs ii linux-firmware 1.187.14 all Firmware for Linux kernel drivers devops@devops-XPS-17-9700:~$ sudo ip addr 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever devops@devops-XPS-17-9700:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1932303/+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 1928820] Re: Add support for AMD wireless button
** Changed in: amd Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1928820 Title: Add support for AMD wireless button Status in amd: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: Some OEM platforms will be using a new ACPI interface for controlling wireless button. It behaves identically to existing hp-wireless driver, just has new ACPI interface. Here is the patch for it submitted into maintainer's tree for 5.13. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=fixes=89ec1e5e0ca9dfe745cb48f4d33979e3b6cc847d Can Canonical team please pull into oem-5.10 kernel? To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928820/+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 1933547] Re: tpm driver causes non-fatal kernel crash on boot
I have installed the following: linux-headers-5.11.0-23 5.11.0-23.24 linux-headers-5.11.0-23-generic 5.11.0-23.24 linux-image-5.11.0-23-generic 5.11.0-23.24 linux-libc-dev:amd64 5.11.0-23.24 linux-modules-5.11.0-23-generic 5.11.0-23.24 linux-modules-extra-5.11.0-23-generic 5.11.0-23.24 and rebooted dmesg now shows: [1.093058] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1B, rev-id 22) [1.109182] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead full dmesg file form boot attached No stack trace present in dmesg or kern.log Kind regards ** Attachment added: "dmesg-20210625.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933547/+attachment/5507035/+files/dmesg-20210625.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/1933547 Title: tpm driver causes non-fatal kernel crash on boot Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kerne
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
** Description changed: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space + + The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE - [Testing] TBD [Regression Risk] Low. Patch set only adds tested bug fixes and support for additional controllers that are shipping with current refreshes for various OEMs -- 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/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver
[Kernel-packages] [Bug 1903612] Re: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Hello Youhei, we have found the `modinfo` command (from the kmod package[1]) will need to be at least with version 27 (which is available in Focal) to support reading information from built-in modules. To be more precise, with these commits: https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=60084cf1cb24dc3a257976c0d539a4c3ffda5db5 https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=73eed2aba3cbe18bbda40f18f7bc32e8de1ec81f https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=b866b2165ae6cf18fb26b635f4a7ee57c0334731 https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git/commit/?h=v27=e7e2cb61fa9f1db3429d91ef6accff549500d268 I have these changes backported here: https://code.launchpad.net/~cypressyew/ubuntu/+source/kmod/+git/kmod/+ref/builtin-test If you want to give this a try, you can clone this repo and do the following: git clone -b builtin-test https://git.launchpad.net/~cypressyew/ubuntu/+source/kmod sudo apt install gtk-doc-tools autoconf automake libtool cd kmod ./autogen.sh ./configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib --with-rootprefix= --with-rootlibdir=/lib make cd tools ./modinfo vfio-pci This will fix this modinfo issue, it can print the built-in module info correctly. Hopefully we can push this to Ubuntu archive later. Regarding DPDK, I have no experience with it, not sure if it will use the modinfo command here (a quick check with their repository[2] I didn't see it calling modinfo directly.) I found this article with keyword "unused vfio-pci dpdk" on the Internet, it looks like you will have to bind the driver to the device with something like: # dpdk-devbind -b vfio-pci :01:00.0 :01:00.1 Hope this helps: https://www.miraclelinux.com/tech-blog/gofc5x [1] https://launchpad.net/ubuntu/+source/kmod [2] https://github.com/DPDK/dpdk -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1903612 Title: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel Status in kmod package in Ubuntu: New Status in linux-hwe package in Ubuntu: Confirmed Status in kmod source package in Bionic: New Status in linux-hwe source package in Bionic: Confirmed Bug description: Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel ``` ubuntu@ubuntu-2:~$ modinfo vfio-pci modinfo: ERROR: Module vfio-pci not found. ubuntu@ubuntu-2:~$ uname -a Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ``` But Generic kernel is Working. ``` ubuntu@ubuntu-4:~$ modinfo vfio-pci filename: /lib/modules/4.15.0-122-generic/kernel/drivers/vfio/pci/vfio-pci.ko description:VFIO PCI - User Level meta-driver author: Alex Williamson license:GPL v2 version:0.2 srcversion: 1E92A800B94EAE7B392AD50 depends:vfio,irqbypass,vfio_virqfd retpoline: Y intree: Y name: vfio_pci vermagic: 4.15.0-122-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:device[:subvendor[:subdevice[:class[:class_mask" and multiple comma separated entries can be specified (string) parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to linux-...@vger.kernel.org so the device can be fixed automatically via the broken_intx_masking flag. (bool) parm: disable_vga:Disable VGA resource access through vfio-pci (bool) parm: disable_idle_d3:Disable using the PCI D3 low power state for idle, unused devices (bool) ``` How to use vfio-pci module in HWE kernel? --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/midiC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-11-09 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType:
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
With v7 it seems that Fn+F4 and Fn+F10 still do nothing, however other media keys got Mute Mic mapping as well as their primary function. For example if I press Vol+ I hear that volume increased but also GNOME shows that microphone become muted. This happens for mute, vol+, vol- and playback control keys. This seems also bugs window manager since after pressing media key input from keyboard become unavailable until I switch to another window. As for mouse it works as expected now. ** Attachment added: "dmesg with v7" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5507012/+files/dmesg -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1933648] [NEW] Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04 Lenovo Ideapad-5-15ITL05
Public bug reported: But I can change brightness from brightness slider. I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. I updated the bios recently but the issue still persists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 18:11:50 2021 InstallationDate: Installed on 2021-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Confirmed ** Summary changed: - Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04 + Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04 Lenovo Ideapad-5-15ITL05 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933648 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04 Lenovo Ideapad-5-15ITL05 Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: But I can change brightness from brightness slider. I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. I updated the bios recently but the issue still persists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 18:11:50 2021 InstallationDate: Installed on 2021-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933648/+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 1897972] Re: "snapd" is not installed
Did you find a solution? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1897972 Title: "snapd" is not installed Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Connection to Snap Store failed Your system does not have a connection to the Snap Store. For the best upgrade experience make sure that your system can connect to api.snapcraft.io. Do you still want to continue with the upgrade? I got the error snap snapd is not installed and tried to apt get snapd, which said it was already installed. So I ignored, typed systemctl restart snapd and tried again but upgrade still failed. $ snap refresh snapd snap "snapd" is not installed $ sudo apt install snapd Reading package lists... Done Building dependency tree Reading state information... Done snapd is already the newest version (2.46.1+18.04). The following packages were automatically installed and are no longer required: linux-hwe-5.4-headers-5.4.0-42 linux-hwe-5.4-headers-5.4.0-45 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 14:47:56 2020 InstallationDate: Installed on 2019-12-29 (276 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2020-09-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1897972/+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 1897972] Re: "snapd" is not installed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1897972 Title: "snapd" is not installed Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: Connection to Snap Store failed Your system does not have a connection to the Snap Store. For the best upgrade experience make sure that your system can connect to api.snapcraft.io. Do you still want to continue with the upgrade? I got the error snap snapd is not installed and tried to apt get snapd, which said it was already installed. So I ignored, typed systemctl restart snapd and tried again but upgrade still failed. $ snap refresh snapd snap "snapd" is not installed $ sudo apt install snapd Reading package lists... Done Building dependency tree Reading state information... Done snapd is already the newest version (2.46.1+18.04). The following packages were automatically installed and are no longer required: linux-hwe-5.4-headers-5.4.0-42 linux-hwe-5.4-headers-5.4.0-45 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-48-generic 5.4.0-48.52~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 14:47:56 2020 InstallationDate: Installed on 2019-12-29 (276 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2020-09-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1897972/+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-aws/5.4.0.1052.54)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1052.54) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/245.4-4ubuntu3.7 (amd64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64, amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64) 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/focal/update_excuses.html#linux-meta-aws [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1933373] Re: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05. It didn't work on Ubuntu 21.04 eit
** 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/1933373 Title: Brightness hotkeys(Fn+F5 for decrease and Fn+F6 for Increase) are not working on Ubuntu 20.04. Hardware Lenovo Ideapad-5-15ITL05. It didn't work on Ubuntu 21.04 either . But I can change brightness from brightness slider. Status in linux package in Ubuntu: Confirmed Bug description: I used the command "watch -n1 cat /proc/interrupts". But when i pressed the brightness hot keys id didn't increased the interruptions. I also used the "acpi_listen" at that time it didn't feedback any output when i pressed the brightness hotkeys. Again I used "sudo showkey -s" it also didn't feedback any output. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-22-generic 5.11.0-22.23 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: akash 1329 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 23:41:15 2021 InstallationDate: Installed on 2021-06-21 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82FG ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=4d6dc3f0-ff06-49a5-b093-ae70cd670931 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-22-generic N/A linux-backports-modules-5.11.0-22-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: FHCN24WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ITL05 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrFHCN24WW:bd01/14/2021:br1.24:efr1.24:svnLENOVO:pn82FG:pvrIdeaPad515ITL05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrIdeaPad515ITL05: dmi.product.family: IdeaPad 5 15ITL05 dmi.product.name: 82FG dmi.product.sku: LENOVO_MT_82FG_BU_idea_FM_IdeaPad 5 15ITL05 dmi.product.version: IdeaPad 5 15ITL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933373/+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-bluefield/5.4.0.1014.15)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1014.15) for focal have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/unknown (arm64) lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64) dpdk/19.11.7-0ubuntu0.20.04.1 (arm64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64) 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/focal/update_excuses.html#linux-meta-bluefield [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: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid 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: Invalid 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: Confirmed 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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Before following Lukas' suggestions could you quickly do a: stat /etc/systemd/network/10-enP53p0s0.link (before deleting this file) since this would give us the creation / modification time and potentially (with some log correlation) this may provide a hint when and why it was created. -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047: Generating output files.. ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition ence0f is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdb0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition encdc0 is not for us (backend 1) ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
[Kernel-packages] [Bug 1933642] [NEW] mlx-bootctl: Fix exclusion issues around arm_smccc_smc
Public bug reported: SRU Justification: [Impact] Exclusion is being handled around arm_smccc_smc() only in the store functions. It should be implemented in the show functions also as this call might not be thread-safe. [Fix] Add mutex_lock/unlock around arm_smccc_smc calls in the show functions. [Test Case] Multiple simultaneous accesses to a sysfs entry exposed by the driver are successful. [Regression Potential] Can be considered minimum ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/1933642 Title: mlx-bootctl: Fix exclusion issues around arm_smccc_smc Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Exclusion is being handled around arm_smccc_smc() only in the store functions. It should be implemented in the show functions also as this call might not be thread-safe. [Fix] Add mutex_lock/unlock around arm_smccc_smc calls in the show functions. [Test Case] Multiple simultaneous accesses to a sysfs entry exposed by the driver are successful. [Regression Potential] Can be considered minimum To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1933642/+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 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)
Thank you! The core problem still is that systemd-networkd does not find any .link and .network file for the enP53p0s0.171 interface, that's why it cannot apply any configuration (IP address): > ? 9: enP53p0s0.171 > Link File: n/a > Network File: n/a This might very well be related to the additional /etc/systemd/network/10-enP53p0s0.link, which is now gone and apparently not needed (good!) – leave that away. Still the configuration/match of that file might still be loaded into the running udev, so we must somehow reset udev to a clean state. I'd like to ask you for another test run (and potential reboot of that machine – if that is possible?): # try to reload udev at runtime udevadm control --reload; udevadm trigger; udevadm settle # wait a bit sleep 30 # apply netplan configuration netplan --debug apply # wait a bit sleep 30 # check results networkctl status enP53p0s0.171 --no-pager ip a If the IP is still not set, could you please try to reboot the machine and check "networkctl" afterwards? -- 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/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: ---Problem Description--- Doing vLAN configuration one of the vLANs is not getting static IP assigned when the rest are workin without problems Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com ---uname output--- Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 17:29:32 UTC 2021 s390x s390x s390x GNU/Linux Machine Type = z15 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1)Configure the netplan file as follow: root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml # This is the network config written by 'subiquity' network: ethernets: encdb0: addresses: - 11.111.114.213/22 macaddress: 02:76:54:00:00:03 encdc0: addresses: - 11.111.112.213/22 macaddress: 02:76:54:00:00:04 enP50s3832 : addresses: - 11.111.112.214/22 enP53p0s0: addresses: - 11.111.112.215/22 vlans: encdb0.160: id: 160 link: encdb0 mtu: 9000 addresses: - 192.168.160.53/24 encdc0.150: id: 150 link: encdc0 mtu: 9000 addresses: - 192.168.150.53/24 enP50s3832.170: id: 170 link: enP50s3832 mtu: 9000 addresses: - 192.168.170.53/24 enP53p0s0.171: id: 171 link: enP53p0s0 mtu: 9000 addresses: - 192.168.171.53/24 version: 2 2)run net plan apply: root@ilabg13:~# netplan --debug apply ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/00-installer-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: Processing input file /etc/netplan/01-iscsi-config.yaml.. ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass them through a final round of validation ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default backend to 1 ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid ** (generate:59965): DEBUG: 14:55:15.047:
[Kernel-packages] [Bug 1931497] Re: Patch To Fix Bug in the Linux Block Layer Responsible For Merging BIOs
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
groovy' to 'verification-done-groovy'. If the problem still exists,
change the tag 'verification-needed-groovy' to 'verification-failed-
groovy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-groovy
--
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/1931497
Title:
Patch To Fix Bug in the Linux Block Layer Responsible For Merging
BIOs
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure source package in Groovy:
Fix Committed
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux-azure source package in Impish:
New
Bug description:
There is a bug in the Linux block layer responsible for merging BIOs
that go across the page boundary. This bug was introduced in Linux 5.1
when the block layer BIO page tracking is enhanced to support multiple
pages.
Without this patch, data corruption can occur. The change to the
kernel block layer in Linux 5.1 changes the way multiple pages are
merged to a single block I/O descriptor, and how contiguous block I/O
descriptors are merged with previous descriptors.
If contiguous block I/O requests cross a page boundary of 4k, defined
by the hv_storvsc driver, the new block merge process can create two
pages of block I/O requests (the latter page with an offset) that
refer to the same physical sector on disk. This page list is then
assembled for the SCSI generic driver.
In the above scenario, when the block I/O request sizes are 512 bytes,
the Azure LIS driver (hv_storvsc module) is not able to correctly
parse the page array from the SCSI generic driver due to this bug in
Linux block layer and creates a potential overflow of offset I/O
requests and corruption of data on disk.
Mitigation of data loss is proven with filesystems with block size 4k.
When block I/O requests are of sizes 4k or multiples of 4k, they are
the page aligned in the memory and are not affected by the block I/O
merging algorithm introduced in Linux 5.1. Most modern file systems
use 4k I/O block size by default, thus mitigating this problem.
We have submitted a patch to Linux mainline kernel to fix this:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-
next=c9c9762d4d44dcb1b2ba90cfb4122dc11ceebf31
c9c9762d4d44 ("block: return the correct bvec when checking for gaps")
Please include this patch in any supported kernels that are 5.1 or
later.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1931497/+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 1932029] Re: Support builtin revoked certificates
https://lists.ubuntu.com/archives/kernel-team/2021-June/121362.html -- 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/1932029 Title: Support builtin revoked certificates Status in linux package in Ubuntu: New Bug description: [Impact] Upstream linux kernel now supports configuring built-in revoked certificates for the .blacklist keyring. Add support in our kernel configuration to have built-in revoked certificates. Revoke UEFI amd64 & arm64 2012 signing certificate. Under UEFI Secureboot with lockdown, shim may attempt to communicate revoked certificates to the kernel and depending on how good EFI firmware is, this may or may not succeed. By having these built-in, it will be prohibited to kexec file_load older kernels that were signed with now revoked certificates, however one boots. [Test Plan] * Boot kernel directly, or just with grub, and without shim * Check that $ sudo keyctl list %:.blacklist Contains assymetric 2012 key. [Where problems could occur] * Derivative and per-arch kernels may need to revoke different keys, thus this should be evaluated on per arch & flavour basis as to which keys to revoke. [Other Info] * In theory, this only needs to be revoked on amd64 and arm64, but empty revocation list is not allowed by the kernel configury, thus at the moment revoking 2012 UEFI cert for all architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+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 1933547] Re: tpm driver causes non-fatal kernel crash on boot
The kernel seems try to set up the interrupt and send data, but failed. After got error returned, the kernel will disable interrupt and using polling instead. I beleve it will have the following messages in dmesg log kernel: tpm tpm0: tpm_try_transmit: send(): error -62 kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead The call trace seems from the patch which add the checking for the invalid status, https://patchwork.kernel.org/project/linux-integrity/patch/9bad3da0c31ae2620aaae0d75748c3387afa3d47.ca...@hansenpartnership.com/#23649371 -- 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/1933547 Title: tpm driver causes non-fatal kernel crash on boot Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kernel: [1.138781] bus_for_each_dev+0x7e/0xc0 Jun 24 07:22:45 munin kernel: [1.138785] driver_attach+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138789] bus_add_driver+0x135/0x1f0 Jun 24 07:22:45 munin kernel: [1.138793] driver_register+0x95/0xf0 Jun 24 07:22:45 munin kernel: [1.138798] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138805] __platform_driver_register+0x1e/0x20 Jun 24 07:22:45 munin kernel: [
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Triaged ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Triaged Status in linux-firmware source package in Hirsute: Won't Fix Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes
[Kernel-packages] [Bug 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
No it does not, tried to go from 1500 to 9000 and then to 1300 and 1000. No change at all. Only if i start TX from the LAN interface, then RX is working as expected. As soon as TX stops, RX comes to crawl. I have attached iper3 log to show this. The times when speed is in MBits is when i started iperf3 on another port in TX direction from laptop. Thank you. ** Attachment added: "iperf3_RX_start_stop_TX" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506981/+files/iperf3_RX_start_stop_TX -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1933029] Re: [Lenovo V14-IIL] Touchpad not working
It seems the touchpad are not even detected. Could you run apport- collect 1933029 to collect logs for your bug report? We will have more information about the touchpad. -- 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/1933029 Title: [Lenovo V14-IIL] Touchpad not working Status in linux package in Ubuntu: New Bug description: Have not seen Touchpad after executing the command "cat /proc/bus/input/devices",log file attached. OS: Ubutbu 20.04, Laptop: Lenovo V14-IIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933029/+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 1933627] Re: HUGETLBFS is disabled
** No longer affects: linux-raspi (Ubuntu Impish) -- 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/1933627 Title: HUGETLBFS is disabled Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Hirsute: New Bug description: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+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 1932528] Re: [Lenovo Yoga 3 Pro 1370] Touchpad stopped working after using as a tablet
The touchpad seems to be I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 Could you run apport-collect 1932528 to collect logs for your bug report? I'll have more information about the interrupts and how it connect. It would be better to give me the content of the `rdesc` file under /sys/kernel/debug/hid/0018:03EB:8A10.0001/ and the output of `cat /sys/kernel/debug/hid/0018:03EB:8A10.0001/events` for any actions on your touchpad. -- 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/1932528 Title: [Lenovo Yoga 3 Pro 1370] Touchpad stopped working after using as a tablet Status in linux package in Ubuntu: New Bug description: Hi Everyone. So my touchpad has stopped working now out of the blue. I have a Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday. It was working perfectly, but it has stopped working as soon as I got into tablet mode. This laptop has the ability to fold its keyboard, so I did that and turn the laptop in 90 degrees (which the screen also turned due to the gyroscope). When we do this, its normal that the cursor disapears so we can you use only the touchscreen as a tablet, however when I turned back to a laptop the touchpad hasn't worked ag=0ain. I have rebooted the system, but still not signs of it. I have executed "cat /proc/bus/input/devices", but didn't find anything related to the touchpad, as the result shows below, so I think it's a kernel issue, right? Any thought how I could fix this? Thank you! I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=5986 Product=0535 Version=3653 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S:
[Kernel-packages] [Bug 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Does changing MTU help? -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Yes. It's v7 and it should be silent to avoid the endless debug messages you mentioned. Could you give me the full dmesg because it should have the input mapping for the hid usage 0x0c? So the mic mute function still not working? And how about the mouse wheel? Is it affected? -- 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/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+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 1931240] Re: Intel ADL-S graphics feature enabling
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1931240
Title:
Intel ADL-S graphics feature enabling
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justfication]
[Impact]
While all other ADL-S i915 commits have been included in v5.13-rc1, the
last one missed the train is to add two more PCI IDs.
[Fix]
Commit 3f50033dd88a ("drm/i915/adl_s: ADL-S platform Update PCI ids for
Mobile BGA") that is currently in drm-intel, branch for-linux-next.
[Test Case]
With this patch, i915 kernel module should be automatically probed.
[Where problems could occur]
While this is part of the initial support for i915 on ADL-S platforms,
the hardware to be enabled could still be unstable and feature laking.
But since this patch only addes two additional PCI IDs to the new
family, it should not introduce any regression to the exsiting ones.
[Other Info]
ADL-S support targets kernel version 5.13, so only unstable and oem-5.13
will be nominated for this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931240/+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 1933547] Re: tpm driver causes non-fatal kernel crash on boot
Hello TomaszCiolek, There is a Hirsute 21.04 kernel update in -proposed with some tpm fixes applied. Could you please try kernel version 5.11.0-23.24 to check whether the issue is resolved with this kernel? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Also affects: linux (Ubuntu Hirsute) 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/1933547 Title: tpm driver causes non-fatal kernel crash on boot Status in linux package in Ubuntu: New Status in linux source package in Hirsute: New Bug description: tpm driver appears to be causng a non-fatal crash on boot. Trace below Jun 24 07:22:45 munin kernel: [1.138595] [ cut here ] Jun 24 07:22:45 munin kernel: [1.138596] TPM returned invalid status Jun 24 07:22:45 munin kernel: [1.138611] WARNING: CPU: 8 PID: 1 at drivers/char/tpm/tpm_tis_core.c:205 tpm_tis_st atus+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138627] Modules linked in: Jun 24 07:22:45 munin kernel: [1.138631] CPU: 8 PID: 1 Comm: swapper/0 Not tainted 5.11.0-22-generic #23-Ubuntu Jun 24 07:22:45 munin kernel: [1.138635] Hardware name: IT Channel Pty Ltd NH50_70RA /NH50_70 RA , BIOS 1.07.13TMB1 06/06/2020 Jun 24 07:22:45 munin kernel: [1.138638] RIP: 0010:tpm_tis_status+0x82/0x90 Jun 24 07:22:45 munin kernel: [1.138644] Code: 25 28 00 00 00 75 2b c9 c3 31 c0 80 3d 8d df 76 01 00 75 e4 48 c7 c7 24 44 04 a2 88 45 ef c6 05 7a df 76 01 01 e8 fb a3 43 00 <0f> 0b 0f b6 45 ef eb c6 e8 71 77 49 00 90 0f 1f 44 00 0 0 55 48 89 Jun 24 07:22:45 munin kernel: [1.138649] RSP: :bfc80007b860 EFLAGS: 00010286 Jun 24 07:22:45 munin kernel: [1.138653] RAX: RBX: 9a2617bf8000 RCX: a2723528 Jun 24 07:22:45 munin kernel: [1.138656] RDX: c000dfff RSI: RDI: 0247 Jun 24 07:22:45 munin kernel: [1.138659] RBP: bfc80007b878 R08: R09: bfc80007b640 Jun 24 07:22:45 munin kernel: [1.138661] R10: bfc80007b638 R11: a2753568 R12: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138663] R13: 9a26032fa558 R14: 9a260330 R15: 9a2617bf8000 Jun 24 07:22:45 munin kernel: [1.138666] FS: () GS:9a2d5060() knlGS: Jun 24 07:22:45 munin kernel: [1.138670] CS: 0010 DS: ES: CR0: 80050033 Jun 24 07:22:45 munin kernel: [1.138673] CR2: CR3: 000288e10001 CR4: 003706e0 Jun 24 07:22:45 munin kernel: [1.138676] Call Trace: Jun 24 07:22:45 munin kernel: [1.138680] tpm_tis_send_data+0x42/0x250 Jun 24 07:22:45 munin kernel: [1.138688] tpm_tis_send_main+0x32/0xf0 Jun 24 07:22:45 munin kernel: [1.138693] ? kernel_init_free_pages+0x4a/0x60 Jun 24 07:22:45 munin kernel: [1.138699] tpm_tis_send+0x30/0xa0 Jun 24 07:22:45 munin kernel: [1.138704] tpm_try_transmit+0x64/0x1d0 Jun 24 07:22:45 munin kernel: [1.138709] tpm_transmit+0x92/0x250 Jun 24 07:22:45 munin kernel: [1.138713] tpm_transmit_cmd+0x2a/0x90 Jun 24 07:22:45 munin kernel: [1.138717] tpm2_get_tpm_pt+0xe9/0x150 Jun 24 07:22:45 munin kernel: [1.138722] tpm_tis_probe_irq_single+0x17f/0x223 Jun 24 07:22:45 munin kernel: [1.138728] ? tpm_tcg_write32+0x1a/0x20 Jun 24 07:22:45 munin kernel: [1.138734] tpm_tis_core_init.cold+0x179/0x2e7 Jun 24 07:22:45 munin kernel: [1.138739] tpm_tis_init.part.0+0xa0/0x120 Jun 24 07:22:45 munin kernel: [1.138744] tpm_tis_plat_probe+0xd4/0x100 Jun 24 07:22:45 munin kernel: [1.138751] platform_probe+0x45/0xa0 Jun 24 07:22:45 munin kernel: [1.138757] really_probe+0xff/0x460 Jun 24 07:22:45 munin kernel: [1.138762] driver_probe_device+0xe9/0x160 Jun 24 07:22:45 munin kernel: [1.138767] device_driver_attach+0xab/0xb0 Jun 24 07:22:45 munin kernel: [1.138772] __driver_attach+0x8f/0x150 Jun 24 07:22:45 munin kernel: [1.138776] ? device_driver_attach+0xb0/0xb0 Jun 24 07:22:45 munin kernel: [1.138781] bus_for_each_dev+0x7e/0xc0 Jun 24 07:22:45 munin kernel: [1.138785] driver_attach+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138789] bus_add_driver+0x135/0x1f0 Jun 24 07:22:45 munin kernel: [1.138793] driver_register+0x95/0xf0 Jun 24 07:22:45 munin kernel: [1.138798] ? tpm_init+0xf6/0xf6 Jun 24 07:22:45 munin kernel: [1.138805] __platform_driver_register+0x1e/0x20 Jun 24 07:22:45 munin kernel: [1.138811] init_tis+0x87/0xdd Jun 24 07:22:45 munin kernel: [1.138817] ? kobject_uevent+0xb/0x10 Jun 24 07:22:45 munin kernel: [1.138823] ?
[Kernel-packages] [Bug 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Hi, it is the same as with the previous kernel 5.13.0-1004. Also since 5.13.x touchpad stopped working (using i2c_hid module). Iperf and dmesg attached. Thank you. ** Attachment added: "5.13.0_2004_iperf_dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+attachment/5506964/+files/5.13.0_2004_iperf_dmesg -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1933627] [NEW] HUGETLBFS is disabled
Public bug reported: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] TBD. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) 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/1933627 Title: HUGETLBFS is disabled Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Hirsute: New Status in linux-raspi source package in Impish: New Bug description: [Impact] Huge pages can't be managed via hugeadm which requires hugetlbfs. [Test Case] $ hugeadm --pool-list hugeadm:ERROR: kernel does not support huge pages [Fix] Enable CONFIG_HUGETLBFS [Regression Potential] TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933627/+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 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
This is what I have now, with: kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-1025-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 uname -a Linux 5.10.0-1025-oem #26 SMP Thu May 6 16:43:31 CST 2021 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "dmesg_20210625_kernel_5.10.0-1025-oem.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506963/+files/dmesg_20210625_kernel_5.10.0-1025-oem.log -- 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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+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 1933532] Re: Large Page support disabled on Raspberry Pi kernels
** Also affects: linux-raspi-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Package changed: linux-raspi-5.4 (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1933532 Title: Large Page support disabled on Raspberry Pi kernels Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: It appears that large page support and transparent hugepages are disabled in config on the Raspberry Pi. It would be nice if they were enabled in the kernel configuration, even if they are disabled by default. Then they could be set in user-editable config via the "transparent_hugepage" boot option. With 4GB hardware in this family, there might be valid uses for large pages. root@ubuntu:/home/ubuntu# hugeadm --explain hugeadm:ERROR: kernel does not support huge pages root@ubuntu:/home/ubuntu# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal root@ubuntu:/home/ubuntu# uname -a Linux ubuntu 5.4.0-1038-raspi #41-Ubuntu SMP PREEMPT Thu Jun 17 14:14:11 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux root@ubuntu:/home/ubuntu# grep -i huge /boot/config-5.4.0-1038-raspi CONFIG_SYS_SUPPORTS_HUGETLBFS=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_HAVE_ARCH_TRANSPARENT_HUGEPAGE=y CONFIG_HAVE_ARCH_HUGE_VMAP=y # CONFIG_TRANSPARENT_HUGEPAGE is not set # CONFIG_HUGETLBFS is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1933532/+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 1932367] Re: Pixel format change broken for Elgato Cam Link 4K
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Groovy) Status: New => Triaged ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => Triaged ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Status: New => Triaged -- 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/1932367 Title: Pixel format change broken for Elgato Cam Link 4K Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Focal: Triaged Status in linux source package in Groovy: Triaged Status in linux source package in Hirsute: Triaged Status in linux source package in Impish: Triaged Bug description: [Impact] The Elgato Cam Link 4K HDMI video capture card reports to support three different pixel formats, where the first format depends on the connected HDMI device. ``` $ v4l2-ctl -d /dev/video0 --list-formats-ext ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [1]: 'NV12' (Y/CbCr 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) [2]: 'YU12' (Planar YUV 4:2:0) Size: Discrete 3840x2160 Interval: Discrete 0.033s (29.970 fps) ``` Changing the pixel format to anything besides the first pixel format does not work: ``` $ v4l2-ctl -d /dev/video0 --try-fmt-video pixelformat=YU12 Format Video Capture: Width/Height : 3840/2160 Pixel Format : 'NV12' (Y/CbCr 4:2:0) Field : None Bytes per Line: 3840 Size Image: 12441600 Colorspace: sRGB Transfer Function : Rec. 709 YCbCr/HSV Encoding: Rec. 709 Quantization : Default (maps to Limited Range) Flags : ``` User space applications like VLC might show an error message on the terminal in that case: ``` libv4l2: error set_fmt gave us a different result than try_fmt! ``` Depending on the error handling of the user space applications, they might display a distorted video, because they use the wrong pixel format for decoding the stream. [Fix] The Elgato Cam Link 4K responds to the USB video probe VS_PROBE_CONTROL/VS_COMMIT_CONTROL with a malformed data structure: The second byte contains bFormatIndex (instead of being the second byte of bmHint). The first byte is always zero. The third byte is always 1. The firmware bug was reported to Elgato on 2020-12-01 and it was forwarded by the support team to the developers as feature request. There is no firmware update available since then. The latest firmware for Elgato Cam Link 4K as of 2021-03-23 has MCU 20.02.19 and FPGA 67. Therefore correct the malformed data structure for this device. The change was successfully tested with VLC, OBS, and Chromium using different pixel formats (YUYV, NV12, YU12), resolutions (3840x2160, 1920x1080), and frame rates (29.970 and 59.940 fps). [Test Case] Connect an input device to the Cam Link 4K and try all three pixel formats with VLC: vlc v4l2:///dev/video0 --v4l2-chroma=NV12 vlc v4l2:///dev/video0 --v4l2-chroma=YU12 [Other Info] The fix was reviewed and accepted by the subsystem maintainer and will be included upstream: https://git.linuxtv.org/media_stage.git/commit/?id=4c6e0976295add7f0ed94d276c04a3d6f1ea8f83 Attached a backported patch for Ubuntu. I successfully tested it with Linux 5.11 on Ubuntu 21.04 and Linux 5.8 on Ubuntu 20.10. It should work on older kernel versions as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932367/+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 1931072] Re: USB Type-C hotplug event not handled properly in TGL-H system during s2idle
** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1931072 Title: USB Type-C hotplug event not handled properly in TGL-H system during s2idle Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] The system will be hold by the infinite loop in ACPI method IPCS after exiting s2idle in TGL-H systems if the docking station with external display connected is unplugged when the system is still in s2idle. It's because the system is unaware of the unplug event and it seems keep something asserted which will never be released while the system trying to exit s2idle. [Fix] Disconnect TypeC PHYs during system suspend and shutdown, even with the corresponding TypeC sink still plugged to its connector. The HPD event is no longer triggered when the system is in s2idle so the resume process will not be hindered. [Test Case] 1. On all TigerLake-H and later platforms with NVIDIA GPU, make sure the NVIDIA GPU is running in either On-Demand mode or Performance mode. 2. Connect the docking station with the external display connected. 3. Suspend the system. 4. Remove the docking station when the system is suspended. 5. Press power button to wake up the system and wait > 1 minutes to make sure if the display comes back. [Where problems could occur] Low. This will only make a difference in the TypeC DP alternate mode, and the display driver will detect the display connector after resume. == Original Bug Description == [Summary] As mentioned in #1929166, the NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the USB Type-C docking/dongle with external display connected is unplugged when the system is still in s2idle. The system will be hold by the infinite loop in ACPI method IPCS and then the PCIe root port of NVIDIA gpu fails the power transition from D3cold to D0. It's because the display connector hotplug event not handled properly in graphics drivers and the system will freeze for > 30 seconds to wait for ACPI method IPCS to exit. [ 154.446781] [ 154.446783] [ 154.446783] Initialized Local Variables for Method [IPCS]: [ 154.446784] Local0: 9863e365 Integer 09C5 [ 154.446790] [ 154.446791] Initialized Arguments for Method [IPCS]: (7 arguments defined for method invocation) [ 154.446792] Arg0: 25568fbd Integer 00AC [ 154.446795] Arg1: 9ef30e76 Integer [ 154.446798] Arg2: fdf820f0 Integer 0010 [ 154.446801] Arg3: 9fc2a088 Integer 0001 [ 154.446804] Arg4: 3a3418f7 Integer 0001 [ 154.446807] Arg5: 20c4b87c Integer [ 154.446810] Arg6: 8b965a8a Integer [ 154.446813] [ 154.446815] ACPI Error: Aborting method \IPCS due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446824] ACPI Error: Aborting method \MCUI due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446829] ACPI Error: Aborting method \SPCX due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446835] ACPI Error: Aborting method \_SB.PC00.PGSC due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446841] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446846] ACPI Error: Aborting method \_SB.PC00.PEG1.NPON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446852] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_AML_LOOP_TIMEOUT) (20200925/psparse-529) [ 154.446860] acpi device:02: Failed to change power state to D0 [ 154.690760] video LNXVIDEO:00: Cannot transition to power state D0 for parent in (unknown) [Reproduce Steps] 1. Connect either Dell WD19SC/DC/TB docking station(USB Type-C) to the system. 2. Connect to external display to HDMI/DisplayPort of the docking 3. Suspend the system 4. Unplug the USB Type-C connector which connects to the system 5. Press power button to wake up the system 6. Check if the internal/external display come back within 10 seconds. [Results] Expected: System works with the internal/external display Actual: System takes > 30 seconds to get back the display. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1932577] Re: [Cezanne/Renoir] Adjust uPEP for different _HID behavior
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1932577 Title: [Cezanne/Renoir] Adjust uPEP for different _HID behavior Status in amd: Fix Committed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Committed Bug description: Feature: Correct uPEP support for all current ACPI _HID for AMD s2idle Code: Currently oem-5.10 carries hack ""platform/x86: force LPS0 functions for AMD"" which helps some RN platforms, but is not the correct solution. The code that is the correct solution has been submitted to linux-acpi: https://lore.kernel.org/linux-acpi/f50c6baf-a780-7a58-4083-88d539342...@gmail.com/T/#t This will fix RN properly and will also add support for the different variations used for CZN for uPEP. Please replace hack in oem-5.10, and also apply this series for oem-5.13. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1932577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
The current kernel was started using the kernel parameter, speeds where fine. I did hibernate, restart the laptop, and now network was broken. I did another reboot afterwards, booting clean with kernel parameter but now network connectivity is still broken. I am not able to spot the system behind all this. Sometimes the behaviour is predictable, sometimes it seems completely random. ** Attachment added: "dmesg-after-hibernate.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5506959/+files/dmesg-after-hibernate.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release:
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Any update on this please? Touchpad still not working on Thinkbook 14-IML on Kernel 5.8.0-55-generic #62-Ubuntu (Groovy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+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 1931442] Re: Fujitsu U7311 I219-LM wired onboard slow RX speeds
Thanks, please give this kernel a try: https://people.canonical.com/~khfeng/lp1931442-2/ -- 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/1931442 Title: Fujitsu U7311 I219-LM wired onboard slow RX speeds Status in linux package in Ubuntu: Confirmed Bug description: Hello, i am having problem with very low RX speeds on my Fujitsu U7130 laptop's wired network with Intel I219-LM chip. When i start downloading any larger content, the speed is very low (ranging from 150kbps-6Mbps) or even the transfer completely stops. RX_errors are rising as well as rx_crc_errors when checking with "ethtool -S enp0s31f6". Link speed is auto-negotiated to 1000Mbps and lowering the speed manually is not having any effects on this issue. Wired TX speeds seems to be unaffected. Wireless speeds on the AX201 are as expected too. I did try to solve this problem upgrading from Ubuntu 20.04 to 21.04 and using various kernels (5.8, 5.10, 5.11, 5.12.9). I also tried to compile e1000e driver from sourceforge version 3.8.7 (https://sourceforge.net/projects/e1000/) with no joy. Bug #1927925 seems to be related as the behavior is the same, but in this case booting with kernel parameter "intel_idle.max_cstate=1" will not resolve the issue. lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 uname -a Linux IO 5.11.0-18-generic #19-Ubuntu SMP Fri May 7 14:22:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux apt-cache policy linux-image-5.11.0-18-generic linux-image-5.11.0-18-generic: Installed: 5.11.0-18.19 Candidate: 5.11.0-18.19 Version table: *** 5.11.0-18.19 500 500 http://cz.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status Thank you. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lk7r 2095 F pulseaudio /dev/snd/controlC0: lk7r 2095 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-05-23 (17 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7311 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b9466f2a-0840-40f4-8131-9b64200e5618 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 Tags: wayland-session hirsute Uname: Linux 5.11.0-18-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-06-08 (1 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 2.14 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.14 dmi.board.name: FJNB2E7 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7311 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.14:bd04/20/2021:br2.14:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7311:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7311: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7311 dmi.product.sku: SK01 dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931442/+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 1928686] Re: Oracle kernel has Android related config options disabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1928686 Title: Oracle kernel has Android related config options disabled Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Bionic: New Status in linux-oracle source package in Focal: Fix Committed Status in linux-oracle source package in Groovy: Fix Committed Status in linux-oracle source package in Hirsute: Fix Committed Bug description: For Anbox Cloud we require certain CONFIG_ANDROID_* options to be enabled in the kernel. We do this already for most of our cloud kernels (GCE, AWS, Azure) and the generic kernel and should do so for the oracle (and possible others too). We have customers looking at running Anbox Cloud on OCI instances and having the ashmem and binder kernel modules available is a precondition for this to work. The following options are what we need CONFIG_ANDROID=y CONFIG_ANDROID_BINDER_IPC=m CONFIG_ANDROID_BINDERFS=m CONFIG_ANDROID_BINDER_DEVICES="" # CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set CONFIG_ASHMEM=m These should be the same across all our kernels where we're going to support Anbox Cloud. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1928686/+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 1933566] Re: XPS 9510 (TGL) Screen Brightness could not be changed
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1933566
Title:
XPS 9510 (TGL) Screen Brightness could not be changed
Status in HWE Next:
New
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Dell XPS 15 9510(TGL) uses DPCD to control backlight, and need to add this
panel to edid_quirk.
kernel: [ 1.719773] i915 :00:02.0: [drm] Panel advertises DPCD
backlight support, but VBT disagrees. If your backlight controls don't
work try booting with i915.enable_dpcd_backlight=1. If your machine
needs this, please file a _new_ bug report on drm/i915, see
https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs
for details.
Kernel 5.12+ support the backlight via:
commit: <4a8d79901d5b> ("drm/i915/dp: Enable Intel's HDR backlight interface
(only SDR for now)"), and doesn't need this quirk.
[Fix]
Adding the panel's MFG to edid_quirk makes system switch to use DPCD to
control backlight.
[Test]
Verified on Dell XPS 9510(TGL)
[Where problems could occur]
The quirk is for a dedicate panel, and won't affect other platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1933566/+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 1933508] Re: mute/micmute LEDs no function on HP EliteBook x360 830 G8
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1933508 Title: mute/micmute LEDs no function on HP EliteBook x360 830 G8 Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP EliteBook x360 830 G8 [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933508/+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 1933609] Re: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in
This journal log contains the nouveau backtrace after locking the computer ** Attachment added: "Journal log with kernel backtrace" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+attachment/5506901/+files/kernel_crash.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933609 Title: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia Quadro P2200 cards. Getting some odd crashes. If a single monitor is plugged and the workstation is power on you can then log in and plug a second monitor in and locking the screen DOES not crash X/Wayland/nouveau. If you boot the system with both monitors plugged in then logging in and locking the computer will cause X/Wayland/Nouveau to crash and only a reboot will fix it. You can still ssh into the box though. The monitors are connected via DisplayPort. There were no kernel backtraces in the journal when running this bug report. But in other cases there has been nouveau backtraces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 25 16:02:35 2021 InstallationDate: Installed on 2021-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+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 1933609] [NEW] Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in
Public bug reported: Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia Quadro P2200 cards. Getting some odd crashes. If a single monitor is plugged and the workstation is power on you can then log in and plug a second monitor in and locking the screen DOES not crash X/Wayland/nouveau. If you boot the system with both monitors plugged in then logging in and locking the computer will cause X/Wayland/Nouveau to crash and only a reboot will fix it. You can still ssh into the box though. The monitors are connected via DisplayPort. There were no kernel backtraces in the journal when running this bug report. But in other cases there has been nouveau backtraces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 25 16:02:35 2021 InstallationDate: Installed on 2021-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1933609 Title: Locking screen crashes X/Wayland with nouveau when multiple monitors are plugged in Status in linux-signed-hwe-5.8 package in Ubuntu: New Bug description: Trying to run Ubuntu 20.04 on some Dell workstations with Nvidia Quadro P2200 cards. Getting some odd crashes. If a single monitor is plugged and the workstation is power on you can then log in and plug a second monitor in and locking the screen DOES not crash X/Wayland/nouveau. If you boot the system with both monitors plugged in then logging in and locking the computer will cause X/Wayland/Nouveau to crash and only a reboot will fix it. You can still ssh into the box though. The monitors are connected via DisplayPort. There were no kernel backtraces in the journal when running this bug report. But in other cases there has been nouveau backtraces. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jun 25 16:02:35 2021 InstallationDate: Installed on 2021-06-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1933609/+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
