[Kernel-packages] [Bug 1927037] Re: ath9k driver: miniPCIe Atheros AR93xx not recognized
** Also affects: linux-raspi (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux-raspi (Ubuntu Focal) Status: New => In Progress -- 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/1927037 Title: ath9k driver: miniPCIe Atheros AR93xx not recognized Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: In Progress Status in linux-raspi source package in Groovy: In Progress Status in linux-raspi source package in Hirsute: In Progress Status in linux-raspi source package in Impish: Invalid Bug description: [Impact] PCIe cards based on ath9k chips are not recognized. [Test Case] Plug a ath9k based PCIe card into the PCIe slot of a CM4 IO board and: $ ls /sys/class/net/wlan0 ls: cannot access '/sys/class/net/wlan0': No such file or directory [Where Problems Could Occur] Buggy driver could result in crashes. [Original Description] Expected behavior: Network adapter should be visible via `iw list`, `iwconfig`, and `ifconfig`. Actual behavior: Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, `iwconfig`, or `ifconfig` Details: The Atheros network card is detected by the ath9k driver when installed into a machine with x86_64 architecture. When the same card is installed into a miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO breakout board, the network adapter can be seen via lspci and lshw but is not seen by iw, iwconfig, or ifconfig. lspci: ubuntu@ubuntu:~$ sudo lspci -v 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 41 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: -0fff [size=4K] Memory behind bridge: f800-f80f [size=1M] Prefetchable memory behind bridge: [disabled] Capabilities: [48] Power Management version 3 Capabilities: [ac] Express Root Port (Slot-), MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [180] Vendor Specific Information: ID= Rev=0 Len=028 Capabilities: [240] L1 PM Substates Kernel driver in use: pcieport 01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01) Subsystem: Qualcomm Atheros AR93xx Wireless Network Adapter Flags: fast devsel, IRQ 255 Memory at 6 (64-bit, non-prefetchable) [disabled] [size=128K] Expansion ROM at 60002 [virtual] [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00 - lshw: ubuntu@ubuntu:~$ sudo lshw -c net *-network UNCLAIMED description: Network controller product: AR93xx Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:01:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress cap_list configuration: latency=0 resources: memory:6-60001 memory:60002-60002 *-network description: Ethernet interface physical id: 1 logical name: eth0 serial: dc:a6:32:f4:69:36 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=bcmgenet driverversion=v2.0 duplex=full ip=REDACTED link=yes multicast=yes port=MII speed=1Gbit/s - iw list/iwconfig: ubuntu@ubuntu:~$ iw list ubuntu@ubuntu:~$ iwconfig lono wireless extensions. eth0 no wireless extensions. - ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-1034-raspi 5.4.0-1034.37 ProcVersionSignature: User Name 5.4.0-1034.37-raspi 5.4.101 Uname: Linux 5.4.0-1034-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: arm64 CasperMD5CheckResult: skip Date: Tue May 4 02:59:25 2021 ImageMediaBuild: 20210201.1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
Just a quick tip: to see all available 5.10.3* packages, printf '%s\0' linux-{image-unsigned,headers,modules}-5.10.{3,4} | xargs -0 -n 1 apt-cache pkgnames | LC_ALL=C sort | less @DanglingPointer the PPA is based on a Docker image which in turn is based on a GitHub project (see comment 11) of which the whole point is to build kernels. Now, short of a PPA, how do you propose keeping multiple systems up-to-date? Move around raw deb's? -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1929261] Re: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Low ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/1929261 Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: during update crash was occurred ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1084 F pulseaudio kanata 1823 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 22 13:00:02 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-07 (103 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Micro-Star International Co., Ltd. Prestige 14 A10SC PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=3557e517-3aa4-4d03-b2f0-73db0ec500f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.11 SourcePackage: linux-firmware Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.release: 1.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14C1IMS.106 dmi.board.asset.tag: Default string dmi.board.name: MS-14C1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14C1IMS.106:bd11/29/2019:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnPrestige14A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14C1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Prestige dmi.product.name: Prestige 14 A10SC dmi.product.sku: 14C1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1929261/+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 1929261] Re: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1929261 Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: during update crash was occurred ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1084 F pulseaudio kanata 1823 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 22 13:00:02 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-07 (103 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Micro-Star International Co., Ltd. Prestige 14 A10SC PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=3557e517-3aa4-4d03-b2f0-73db0ec500f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.11 SourcePackage: linux-firmware Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.release: 1.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14C1IMS.106 dmi.board.asset.tag: Default string dmi.board.name: MS-14C1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14C1IMS.106:bd11/29/2019:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnPrestige14A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14C1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Prestige dmi.product.name: Prestige 14 A10SC dmi.product.sku: 14C1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1929261/+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 1929261] [NEW] package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: during update crash was occurred ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1084 F pulseaudio kanata 1823 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 22 13:00:02 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-07 (103 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Micro-Star International Co., Ltd. Prestige 14 A10SC PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=3557e517-3aa4-4d03-b2f0-73db0ec500f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.11 SourcePackage: linux-firmware Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.release: 1.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14C1IMS.106 dmi.board.asset.tag: Default string dmi.board.name: MS-14C1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14C1IMS.106:bd11/29/2019:br1.6:svnMicro-StarInternationalCo.,Ltd.:pnPrestige14A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14C1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Prestige dmi.product.name: Prestige 14 A10SC dmi.product.sku: 14C1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1929261 Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: during update crash was occurred ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.12 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1084 F pulseaudio kanata 1823 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 22 13:00:02 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-02-07 (103 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: Micro-Star International Co., Ltd. Prestige 14 A10SC PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=3557e517-3aa4-4d03-b2f0-73db0ec500f8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.11 SourcePackage: linux-firmware Title: package linux-firmware 1.187.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.release: 1.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14C1IMS.106 dmi.board.asset.tag: Default string dmi.board.name: MS-14C1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star Inte
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-raspi/5.8.0.1025.28)
All autopkgtests for the newly accepted linux-meta-raspi (5.8.0.1025.28) for groovy have finished running. The following regressions have been reported in tests triggered by the package: dpdk/unknown (arm64) r8168/unknown (arm64) adv-17v35x/unknown (arm64) rtl8812au/unknown (arm64) v4l2loopback/unknown (arm64) xtrx-dkms/unknown (arm64) langford/unknown (arm64) xtables-addons/unknown (arm64) gost-crypto/unknown (arm64) virtualbox-hwe/unknown (arm64) west-chamber/unknown (arm64) openrazer/unknown (arm64) rtl8821ce/unknown (arm64) snapd/unknown (arm64) zfs-linux/unknown (arm64) systemd/unknown (arm64) fwts/unknown (arm64) lime-forensics/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/groovy/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 1786013] Autopkgtest regression report (linux-meta-oracle/5.11.0.1007.7)
All autopkgtests for the newly accepted linux-meta-oracle (5.11.0.1007.7) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: systemd/247.3-3ubuntu3 (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/hirsute/update_excuses.html#linux-meta-oracle [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.1036.38)
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1036.38) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-raspi-5.4/unknown (arm64) lttng-modules/unknown (arm64) rtl8812au/unknown (arm64) lime-forensics/unknown (arm64) systemd/unknown (arm64) west-chamber/unknown (arm64) fwts/unknown (arm64) dpdk/unknown (arm64) lxd/unknown (arm64) dm-writeboost/unknown (arm64) glibc/unknown (arm64) nat-rtsp/unknown (arm64) rtl8821ce/unknown (arm64) ddcci-driver-linux/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 1814295] Re: qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386
Still see this sometimes pop up, currently found on Bionic/linux 4.15.0-144.148 i386. found via ADT Kernel correctly calls access_ok on compat_alloc_userspace (CVE-2010-3081) ... ok == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 3002, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.Q9nQbe/build.SKg/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1181, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- Ran 125 tests in 51.673s FAILED (failures=1) 15:17:45 INFO | END ERROR ubuntu_qrt_kernel_security.test-kernel-security.py ubuntu_qrt_kernel_security.test-kernel-security.py timestamp=1621610265 localtime=May 21 15:17:45 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2010-3081 ** Tags added: 4.15 bionic sru-20210510 -- 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/1814295 Title: qa-regression-testing test_ulimit_stack_small fails on ppc64el/i386 Status in QA Regression Testing: Confirmed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/l/linux/20190201_153123_8340c@/log.gz == FAIL: test_ulimit_stack_small (__main__.KernelNonSecurityTest) Ensure small stack limits are enforced -- Traceback (most recent call last): File "./test-kernel-security.py", line 2847, in test_ulimit_stack_small self.assertShellExitIn(expected, self._unpriv_cmd(["sh", "-c", "ulimit -s 1 && /bin/true"])) File "/tmp/autopkgtest.aOkL2y/build.mxm/src/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1151, in assertShellExitIn self.assertIn(rc, expected, msg + result + report) AssertionError: Got exit code 0, expected one of 139 Command: 'sudo', '-u', 'ubuntu', 'sh', '-c', 'ulimit -s 1 && /bin/true' Output: -- To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1814295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: New Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920180] Re: Can't detect intel wifi 6235
There are still no responses from upstream so let me send SRU to Ubuntu kernels first. -- 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/1920180 Title: Can't detect intel wifi 6235 Status in linux package in Ubuntu: In Progress Bug description: [Impact] Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. [Fix] The patch adds the device ID 0x526A. [Test Case] Wifi works after installing test kernel (#19 & #20 in LP:1920180) [Regression Potential] Low to none. This adds a hardware ID and does not affects systems output such a wifi card. [Note] Patch was also sent for upstream reviews and can be viewed at https://www.spinics.net/lists/stable/msg452937.html == Original descriptions Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] Flags: fast devsel, IRQ 255 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgo1245 F pulseaudio /dev/snd/controlC0: sgo1245 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 20AWS0DS0T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: ulyssa Uname: Linux 5.4.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AWS0DS0T dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AWS0DS0T dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+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 1920180] Re: Can't detect intel wifi 6235
** Description changed: + [Impact] + + Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. + + [Fix] + + The patch adds the device ID 0x526A. + + [Test Case] + + Wifi works after installing test kernel (#19 & #20 in LP:1920180) + + [Regression Potential] + + Low to none. This adds a hardware ID and does not affects systems + output such a wifi card. + + [Note] + + Patch was also sent for upstream reviews and can be viewed at + https://www.spinics.net/lists/stable/msg452937.html + + Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) - Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] - Flags: fast devsel, IRQ 255 - Memory at e040 (64-bit, non-prefetchable) [size=8K] - Capabilities: - --- + Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] + Flags: fast devsel, IRQ 255 + Memory at e040 (64-bit, non-prefetchable) [size=8K] + Capabilities: + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: sgo1245 F pulseaudio - /dev/snd/controlC0: sgo1245 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: sgo1245 F pulseaudio + /dev/snd/controlC0: sgo1245 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: - enp0s25 no wireless extensions. - - lono wireless extensions. + enp0s25 no wireless extensions. + + lono wireless extensions. MachineType: LENOVO 20AWS0DS0T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 RelatedPackageVersions: - linux-restricted-modules-5.4.0-67-generic N/A - linux-backports-modules-5.4.0-67-generic N/A - linux-firmware1.187.10 + linux-restricted-modules-5.4.0-67-generic N/A + linux-backports-modules-5.4.0-67-generic N/A + linux-firmware1.187.10 RfKill: - 0: tpacpi_bluetooth_sw: Bluetooth - Soft blocked: yes - Hard blocked: no + 0: tpacpi_bluetooth_sw: Bluetooth + Soft blocked: yes + Hard blocked: no Tags: ulyssa Uname: Linux 5.4.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AWS0DS0T dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AWS0DS0T dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Description changed: [Impact] - Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. + Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. [Fix] - The patch adds the device ID 0x526A. + The patch adds the device ID 0x526A. [Test Case] - Wifi works after installing test kernel (#19 & #20 in LP:1920180) + Wifi works after installing test kernel (#19 & #20 in LP:1920180) [Regression Potential] - Low to none. This adds a hardware ID and does not affects systems - output such a wifi card. + Low to none. This adds a hardware ID and does not affects systems + output such a wifi card. [Note] - Patch was also sent for upstream reviews and can be viewed at - https://www.spinics.net/lists/stable/msg452937.html + Patch was also sent for upstream reviews and can be viewed at + https://www.spinics.net/lists/stable/msg452937.html + == + Original descriptions Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] Flags: fast devsel, IRQ 255 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/con
[Kernel-packages] [Bug 1928522] Re: seccomp_bpf:syscall_faked from kselftests fail on s390x
** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- 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/1928522 Title: seccomp_bpf:syscall_faked from kselftests fail on s390x Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] kselftests seccomp_bpf will start failing on s390x, though due to a test problem, not a kernel regression, thus wasting people's time doing test review. [Regression potential] Though this is only changing the test, we might be missing or miss failures in the future because some tests are not executed anymore. ptrace_syscall_faked, ptrace_syscall_errno and syscall_errno should all work just fine on s390x, but will be skipped as well with this change. [Fix] The fix is to consider that s390x cannot change syscall and errno at once by using ptrace. It can, however, change the errno at syscall exit time, which could even be used with seccomp SECCOMP_RET_TRACE as long as ptrace is used to track the exit transitions. But the test is not designed to deal with such situations. [Test case] seccomp_bpf was run, ptrace_faked passed and no new subtests have failed. --- This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928522] Re: seccomp_bpf:syscall_faked from kselftests fail on s390x
** Summary changed: - seccomp_bpf from ubuntu_kernel_selftests.seccomp in linux ADT test failure with linux/4.15.0-144.148 + seccomp_bpf:syscall_faked from kselftests fail on s390x ** Description changed: - This is a scripted bug report about ADT failures while running linux - tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the - dep8 tests of the tested source or the kernel has yet to be determined. + [Impact] + kselftests seccomp_bpf will start failing on s390x, though due to a test problem, not a kernel regression, thus wasting people's time doing test review. + + [Regression potential] + Though this is only changing the test, we might be missing or miss failures in the future because some tests are not executed anymore. + ptrace_syscall_faked, ptrace_syscall_errno and syscall_errno should all work just fine on s390x, but will be skipped as well with this change. + + [Fix] + The fix is to consider that s390x cannot change syscall and errno at once by using ptrace. It can, however, change the errno at syscall exit time, which could even be used with seccomp SECCOMP_RET_TRACE as long as ptrace is used to track the exit transitions. But the test is not designed to deal with such situations. + + [Test case] + seccomp_bpf was run, ptrace_faked passed and no new subtests have failed. + + + --- + + + This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928522 Title: seccomp_bpf:syscall_faked from kselftests fail on s390x Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux source package in Focal: New Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] kselftests seccomp_bpf will start failing on s390x, though due to a test problem, not a kernel regression, thus wasting people's time doing test review. [Regression potential] Though this is only changing the test, we might be missing or miss failures in the future because some tests are not executed anymore. ptrace_syscall_faked, ptrace_syscall_errno and syscall_errno should all work just fine on s390x, but will be skipped as well with this change. [Fix] The fix is to consider that s390x cannot change syscall and errno at once by using ptrace. It can, however, change the errno at syscall exit time, which could even be used with seccomp SECCOMP_RET_TRACE as long as ptrace is used to track the exit transitions. But the test is not designed to deal with such situations. [Test case] seccomp_bpf was run, ptrace_faked passed and no new subtests have failed. --- This is a scripted bug report about ADT failures while running linux tests for linux/4.15.0-144.148 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/l/linux/20210514_022345_e6f3c@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928522/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem here Ubuntu 20.04 kernel 5.8.0-53-generic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1929256] [NEW] Intel Bluetooth 8265/8275 not working properly
Public bug reported: Turning off the bluetooth from settings doesn't let me turn on the bluetooth again and I have to reboot my pc to make it to work again. I am running Ubuntu 21.04 and this bug is persistent since 20.04. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth intel iwlwifi ** Attachment added: "Screenshot from 2021-05-22 04-29-45.png" https://bugs.launchpad.net/bugs/1929256/+attachment/5499311/+files/Screenshot%20from%202021-05-22%2004-29-45.png -- 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/1929256 Title: Intel Bluetooth 8265/8275 not working properly Status in linux-firmware package in Ubuntu: New Bug description: Turning off the bluetooth from settings doesn't let me turn on the bluetooth again and I have to reboot my pc to make it to work again. I am running Ubuntu 21.04 and this bug is persistent since 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1929256/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929255] [NEW] update-initrd-links creates incorrect symlinks
Public bug reported: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description:Ubuntu 18.04.5 LTS Release:18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New ** Tags: bionic installkernel ** Patch added: "Proposed patch" https://bugs.launchpad.net/bugs/1929255/+attachment/5499310/+files/xx-update-initrd-links.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: New Bug description: ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. ## Solution A solution is proposed through the attached patch file. ## System information Description: Ubuntu 18.04.5 LTS Release: 18.04 Uname: Linux 5.3.0-53-generic x86_64 ## Package information Package: linux-base 4.5ubuntu1.5 PackageArchitecture: all SourcePackage: linux-base Tags: bionic package-from-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925522] Autopkgtest regression report (nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.21.04.2)
All autopkgtests for the newly accepted nvidia-graphics-drivers-450-server (450.119.04-0ubuntu0.21.04.2) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: pyopencl/2021.1.2-1build1 (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/hirsute/update_excuses.html#nvidia-graphics-drivers-450-server [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 nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team member
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed with timeout
Issue observed in B/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1748103 Title: apic test in kvm-unit-test failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+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 1845687] Re: memory test in ubuntu_kvm_unit tests fails linux-kvm (clflushopt absent)
Issue observed in B/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1845687 Title: memory test in ubuntu_kvm_unit tests fails linux-kvm (clflushopt absent) Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Eoan: Won't Fix Bug description: Series: Xenial Kernel: 4.4.0-1059.66 linux-kvm specifically clfushopt and clwb 09/23 08:43:08 DEBUG| utils:0116| Running 'kvm-ok' 09/23 08:43:08 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists 09/23 08:43:08 DEBUG| utils:0153| [stdout] KVM acceleration can be used 09/23 08:43:08 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory' 09/23 08:43:08 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4 09/23 08:43:09 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.HnxXwZrpQ9 -smp 1 -cpu host # -initrd /tmp/tmp.SL7FtNHKpq 09/23 08:43:09 DEBUG| utils:0153| [stdout] enabling apic 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: clflush (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: sfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: lfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: mfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clflushopt (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clwb (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: invalid clwb 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: pcommit (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] SUMMARY: 8 tests, 2 unexpected failures 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845687/+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 1822309] Re: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures
Issue observed in B/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1822309 Title: vmx_apic_passthrough_thread in kvm_unit_tests failed with 1 unexpected failures Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-aws source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux-oracle source package in Bionic: New Bug description: TESTNAME=vmx_apic_passthrough_thread TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 2 -cpu host,+vmx -m 2048 -append vmx_apic_passthrough_thread_test FAIL vmx_apic_passthrough_thread (5 tests, 1 unexpected failures) Detailed report will be appended later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822309/+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 1822308] Re: vmx_hlt_with_rvi_test in kvm_unit_tests fails
Issue observed in B/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1822308 Title: vmx_hlt_with_rvi_test in kvm_unit_tests fails Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_hlt_with_rvi_test' BUILD_HEAD=e2c275c4 timeout -k 1s --foreground 10 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.Jo9XTMTiTj -smp 1 -cpu host,+vmx -append vmx_hlt_with_rvi_test # -initrd /tmp/tmp.Y9HtqW5t9P enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: vmx_hlt_with_rvi_test qemu-system-x86_64: terminating on signal 15 from pid 24517 FAIL vmx_hlt_with_rvi_test (timeout; duration=10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822308/+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 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout
Issue observed in B/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1748105 Title: port80 test in ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test port80 test will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the port80 test as root: # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/port80.flat -smp 1 # -initrd /tmp/tmp.3p9PWc2SRi enabling apic begining port 0x80 write test qemu-system-x86_64: terminating on signal 15 from pid 7790 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:13:18 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+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 1925522] Autopkgtest regression report (nvidia-graphics-drivers-460/460.80-0ubuntu0.21.04.2)
All autopkgtests for the newly accepted nvidia-graphics-drivers-460 (460.80-0ubuntu0.21.04.2) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: pyopencl/2021.1.2-1build1 (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/hirsute/update_excuses.html#nvidia-graphics-drivers-460 [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 nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘v
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1016.17~18.04.17)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1016.17~18.04.17) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gkeop-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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 1845687] Re: memory test in ubuntu_kvm_unit tests fails linux-kvm (clflushopt absent)
** Summary changed: - memory test in ubuntu_kvm_unit tests fails linux-kvm + memory test in ubuntu_kvm_unit tests fails linux-kvm (clflushopt absent) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1845687 Title: memory test in ubuntu_kvm_unit tests fails linux-kvm (clflushopt absent) Status in ubuntu-kernel-tests: Triaged Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Eoan: Won't Fix Bug description: Series: Xenial Kernel: 4.4.0-1059.66 linux-kvm specifically clfushopt and clwb 09/23 08:43:08 DEBUG| utils:0116| Running 'kvm-ok' 09/23 08:43:08 DEBUG| utils:0153| [stdout] INFO: /dev/kvm exists 09/23 08:43:08 DEBUG| utils:0153| [stdout] KVM acceleration can be used 09/23 08:43:08 DEBUG| utils:0116| Running '/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/memory' 09/23 08:43:08 DEBUG| utils:0153| [stdout] BUILD_HEAD=e2c275c4 09/23 08:43:09 DEBUG| utils:0153| [stdout] timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel /tmp/tmp.HnxXwZrpQ9 -smp 1 -cpu host # -initrd /tmp/tmp.SL7FtNHKpq 09/23 08:43:09 DEBUG| utils:0153| [stdout] enabling apic 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: clflush (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: sfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: lfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: mfence (present) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clflushopt (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL: clwb (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: invalid clwb 09/23 08:43:09 DEBUG| utils:0153| [stdout] PASS: pcommit (ABSENT) 09/23 08:43:09 DEBUG| utils:0153| [stdout] SUMMARY: 8 tests, 2 unexpected failures 09/23 08:43:09 DEBUG| utils:0153| [stdout] FAIL memory (8 tests, 2 unexpected failures) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845687/+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 1896137] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1896137 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" Status in linux package in Ubuntu: Incomplete Bug description: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896137/+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 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
Observed on B/KVM, cycle sru-20210510 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+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 1927533] Re: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig
Observed in B/KVM cycle sru-20210510 . ** Tags added: linux-kvm sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1927533 Title: selftests/net/test_bpf fails for linux-kvm due to lack of Kconfig Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: New Bug description: Kernel selftest "test_bpf" fails for B/linux-kvm due to lack of Kconfig: grep -v "#" tools/testing/selftests/net/test_bpf.sh if /sbin/modprobe -q test_bpf ; then /sbin/modprobe -q -r test_bpf; echo "test_bpf: ok"; else echo "test_bpf: [FAIL]"; exit 1; fi Checking the config files, for example: # grep -n "TEST_BPF" /boot/config-4.15.0-1089-kvm 2310:# CONFIG_TEST_BPF is not set # grep -n "TEST_BPF" /boot/config-4.15.0-142-generic 9105:CONFIG_TEST_BPF=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927533/+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 1829849] Re: proc01 in fs from ubuntu_ltp failed
Observed in B/KVM, cycle sru-20210510. ** Tags added: linux-kvm sru-20210510 -- 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/1829849 Title: proc01 in fs from ubuntu_ltp failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: Triaged Status in linux-azure package in Ubuntu: Triaged Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
Observed in B/KVM, cycle sru-20210510. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829995 Title: getaddrinfo_01 from ipv6_lib test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Bug description: startup='Wed May 22 08:02:52 2019' getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4 canonical name ("curly.maas") doesn't match hostname ("curly") getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic lookup ("curly") returns -5 ("No address associated with hostname") tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 08:04:30 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+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 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Observed in B/KVM, cycle sru-20210510. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+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 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Observed in B/KVM, cycle sru-20210510. -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+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 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
nvidia-graphics-drivers-450-server, 450.119.04 results: The DKMS driver was tested via the cuda samples test. This passed for bionic, focal and groovy, but failed for hirsute and impish. This failure was expected as the nvidia_uvm module doens't currently load with the 5.11 kernel in hirsute and impish. The LRM driver was also tested via the cuda samples test. This passed for groovy, hirsute and impish, but failed on bionic and focal as there isn't yet a matching lrm package for the 450.119.04 driver. When these packages are available later in the kernel SRU cycle, it will be retested. fabric-manager-450 and libnvidia-nscq-450: These passed using the cuda samples test and 'dcgmi discovery -l' on a dgx-2 host using focal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts
[Kernel-packages] [Bug 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" Status in linux package in Ubuntu: New Bug description: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896137/+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 1896137] Re: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896137 Title: syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" Status in linux package in Ubuntu: New Bug description: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896137/+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 1896137] [NEW] syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
You have been subscribed to a public bug: When I close the lid on my laptop, syslog goes crazy with the message systemd-logind: hibernation is restricted; see man kernel_lockdown.7 repeated ad infinitum, using up all the CPU and GBs of disk space. I am not even trying to hibernate; everything in /etc/systemd/login.conf is commented out. So nothing much should happen when I close the lid, but systemd is trying to kill me with these messages. I am running Ubuntu 20.04. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- syslog flooded with "Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7" https://bugs.launchpad.net/bugs/1896137 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927272] Re: Some kernel selftests fail on linux-kvm
New observation: H/KVM (cycle 20210510) have seccomp_benchmark failing due to timeout. A manual run was successful. 02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # TIMEOUT 120 seconds Reference LP: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1929247 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: This is a catch-all Launchpad report to list the kernel selftests failures in linux-kvm kernel. The comments will be used to reference and discuss about the failures, pointing to individual issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+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 1929247] [NEW] kernel/selftests: seccomp_benchmark fails with timeout in H/KVM
Public bug reported: Found that on cycle sru-20210510, on H/KVM 5.11.0-1008.8 : 02:36:23 DEBUG| [stdout] # selftests: seccomp: seccomp_benchmark 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_enable: No such file or directory 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_harden: No such file or directory 02:38:23 DEBUG| [stdout] # 02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # TIMEOUT 120 seconds In the previous cycle this test worked, but this one failed due to timeout - I've manually executed in my Hirsute VM and it succeeded in ~100 seconds. Maybe we need to just bump the timeout. ** Affects: ubuntu-kernel-tests Importance: Low Status: Confirmed ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-kvm (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: 5.11 hirsute kvm linux-kvm sru-20210510 ubuntu-kernel-selftests ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: Guilherme G. Piccoli (gpiccoli) => (unassigned) ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1929247 Title: kernel/selftests: seccomp_benchmark fails with timeout in H/KVM Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Hirsute: New Bug description: Found that on cycle sru-20210510, on H/KVM 5.11.0-1008.8 : 02:36:23 DEBUG| [stdout] # selftests: seccomp: seccomp_benchmark 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_enable: No such file or directory 02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_harden: No such file or directory 02:38:23 DEBUG| [stdout] # 02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # TIMEOUT 120 seconds In the previous cycle this test worked, but this one failed due to timeout - I've manually executed in my Hirsute VM and it succeeded in ~100 seconds. Maybe we need to just bump the timeout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929247/+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 1909814] Re: Keyboard not working
Same thing here, last kernel doesn't produce any change. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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/5.11.0.1006.6)
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1006.6) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (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/hirsute/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 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
I can pair successfully if I enable LE Privacy: sudo btmgmt power off sudo btmgmt privacy on sudo btmgmt power on -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-23 (25 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 5590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Tags: groovy package-from-proposed Uname: Linux 5.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:F6:D8:6A:A3:F0 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0 TX bytes:18701 acl:357 sco:0 commands:841 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+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 1926501] Re: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set
New one, for hirsute: evdi-dkms fails to build [0]. This is due to t he lack of CONFIG_I2C in such kernel. I've hinted as NEVER in ADT tests. [0] /var/lib/dkms/evdi/1.9.1/build/evdi_i2c.c:49:9: error: implicit declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 49 | return i2c_add_adapter(adapter); | ^~~ | i2c_verify_adapter /var/lib/dkms/evdi/1.9.1/build/evdi_i2c.c: In function ‘evdi_i2c_remove’: /var/lib/dkms/evdi/1.9.1/build/evdi_i2c.c:54:2: error: implicit declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1926501 Title: ADT/hint: Multiple DKMS modules fail to build in linux-kvm due to lack of Kconfigs set Status in linux-kvm package in Ubuntu: Confirmed Bug description: This a catch-all Launchpad report regarding the build failures of some DKMS modules (like Nvidia drivers, virtualbox-hwe, ...) in linux-kvm. The goal of linux-kvm kernel is to be a *very* minimal kernel for virtualized environments (guests), with the bare minimum of Kconfigs enabled, in order to have it booting really fast and with a reduced attack surface. Given that, some DKMS may not work, like virtualbox- hwe (which requires CONFIG_DRM_*). The objective of this LP is to report such failures and use this information "database" to help us mark Autopackage testing (ADT) failures as _expected_, or else in every kernel cycle we will face the same issues that show up as regressions, when they are in fact incompatibilities between the test and the minimal linux-kvm kernel. We could use the comments to report individual failures / attach logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1926501/+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 1928888] Re: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19
Observed in H/KVM (ADT), cycle sru-20210510 . ** Tags added: kvm linux-kvm -- 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/192 Title: test_utils_testsuite from ubuntu_qrt_apparmor linux ADT test failure with linux/5.11.0-18.19 Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz test_zz_cleanup_source_tree (__main__.ApparmorTestsuites) Cleanup downloaded source ... ok == FAIL: test_utils_testsuite (__main__.ApparmorTestsuites) Run utils (make check) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1841, in test_utils_testsuite self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 == FAIL: test_utils_testsuite3 (__main__.ApparmorTestsuites) Run utils (make check with python3) -- Traceback (most recent call last): File "/tmp/autopkgtest.gBRfIs/build.V37/src/autotest/client/tmp/ubuntu_qrt_apparmor/src/qa-regression-testing/scripts/./test-apparmor.py", line 1862, in test_utils_testsuite3 self.assertEqual(expected, rc, result + report) AssertionError: 0 != 2 : Got exit code 2, expected 0 ERROR: capability CAP_CHECKPOINT_RESTORE not found in severity.db make: *** [Makefile:81: check_severity_db] Error 1 -- Ran 58 tests in 1448.768s FAILED (failures=2) 23:36:54 INFO | END ERROR ubuntu_qrt_apparmor.test-apparmor.py ubuntu_qrt_apparmor.test-apparmor.pytimestamp=1621035414localtime=May 14 23:36:54 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/192/+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-kvm/5.8.0.1028.30)
All autopkgtests for the newly accepted linux-meta-kvm (5.8.0.1028.30) for groovy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-460/460.73.01-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.10.2 (amd64) nvidia-graphics-drivers-390/390.143-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-450-server/450.119.03-0ubuntu0.20.10.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.10.1 (amd64) nvidia-graphics-drivers-418-server/418.197.02-0ubuntu0.20.10.1 (amd64) nvidia-graphics-drivers-450/450.119.03-0ubuntu0.20.10.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/groovy/update_excuses.html#linux-meta-kvm [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 1909005] Re: Ubuntu does not resume (wake up) from suspend
Same problem on Dell Inspiron 5558 with - latest bios - Ubuntu 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux-image-5.0.0-1070 -oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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.1036.71)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1036.71) for focal have finished running. The following regressions have been reported in tests triggered by the package: systemd/unknown (arm64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (armhf, arm64) west-chamber/unknown (arm64) v4l2loopback/unknown (arm64) zfs-linux/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/unknown (arm64) fwts/unknown (arm64) wireguard/unknown (arm64) evdi/unknown (arm64) dm-writeboost/unknown (arm64) gost-crypto/unknown (arm64) jool/unknown (arm64) dpdk/unknown (arm64) langford/unknown (arm64) r8168/unknown (arm64) lime-forensics/unknown (arm64) mali-midgard/unknown (arm64) rtl8812au/unknown (arm64) rtl8821ce/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 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Unfortunately it's not showing me the grid - back-light is not turning on. My laptop is UX393UA. Can it be fixed somehow? -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+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.1012.13)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1012.13) for focal have finished running. The following regressions have been reported in tests triggered by the package: wireguard-linux-compat/unknown (arm64) openafs/unknown (arm64) ddcci-driver-linux/unknown (arm64) dpdk/unknown (arm64) jool/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-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 1786013] Autopkgtest regression report (linux-meta-azure/5.4.0.1048.46)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1048.46) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.3 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.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 1786013] Autopkgtest regression report (linux-meta/5.4.0.74.77)
All autopkgtests for the newly accepted linux-meta (5.4.0.74.77) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (armhf, ppc64el, s390x) 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 [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.1027.28)
All autopkgtests for the newly accepted linux-meta-oem-5.10 (5.10.0.1027.28) for focal have finished running. The following regressions have been reported in tests triggered by the package: broadcom-sta/6.30.223.271-12 (amd64) nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.1 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.1 (amd64) dm-writeboost/2.2.9-1ubuntu1.1 (amd64) lime-forensics/1.9-1ubuntu0.1 (amd64) systemd/245.4-4ubuntu3.6 (amd64) xtables-addons/3.9-1ubuntu0.2~20.04.1 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.1 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.2 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.1 (amd64) bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.1 (amd64) openafs/1.8.4~pre1-1ubuntu2.1 (amd64) evdi/1.7.0+dfsg-1ubuntu1~20.04.2 (amd64) lttng-modules/2.12.2-1ubuntu1~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-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-aws/5.4.0.1049.50)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1049.50) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.3 (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-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 1786013] Autopkgtest regression report (linux-meta-hwe-5.8/5.8.0.54.61~20.04.38)
All autopkgtests for the newly accepted linux-meta-hwe-5.8 (5.8.0.54.61~20.04.38) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-54.61~20.04.1 (arm64, amd64, ppc64el, s390x) 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.8 [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-kvm/5.4.0.1040.38)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1040.38) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-460/460.73.01-0ubuntu0.20.04.1 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.1 (amd64) nvidia-graphics-drivers-450/450.119.03-0ubuntu0.20.04.1 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.2 (amd64) nvidia-graphics-drivers-450-server/450.119.03-0ubuntu0.20.04.1 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.1 (amd64) v4l2loopback/0.12.3-1ubuntu0.3 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.1 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.1 (amd64) glibc/2.31-0ubuntu9.2 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.1 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) evdi/1.7.0+dfsg-1ubuntu1~20.04.2 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (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-kvm [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 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
Thank you for your suggestion to test the latest kernel. Unfortunately, I am having trouble booting using the suggested kernel (5.13-rc2). I have downloaded the appropriate (I think) kernel packages from the link you provided: linux-modules-5.13.0-051300rc2-generic_5.13.0-051300rc2.202105162330_amd64.deb linux-image-unsigned-5.13.0-051300rc2-generic_5.13.0-051300rc2.202105162330_amd64.deb linux-headers-5.13.0-051300rc2-generic_5.13.0-051300rc2.202105162330_amd64.deb linux-headers-5.13.0-051300rc2_5.13.0-051300rc2.202105162330_all.deb I have verified the checksums, installed the packages, and configured them using dpkg --configure -a. When I try to boot using kernel 5.13-rc2, I receive the following errors: error: /boot/vmlinuz-5.13.0-051300rc2-generic has invalid signature. error: you need to load the kernel first Please advise. -- 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/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+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.11.0.1009.7)
All autopkgtests for the newly accepted linux-meta-raspi (5.11.0.1009.7) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: rtl8812au/unknown (arm64) openafs/unknown (arm64) xtables-addons/unknown (arm64) systemd/unknown (arm64) snapd/unknown (arm64) digimend-dkms/unknown (arm64) evdi/unknown (arm64) gost-crypto/unknown (arm64) wireguard-linux-compat/unknown (arm64) ddcci-driver-linux/unknown (arm64) openrazer/unknown (arm64) r8168/unknown (arm64) jool/unknown (arm64) xtrx-dkms/unknown (arm64) fwts/unknown (arm64) wireguard/unknown (arm64) rtl8821ce/unknown (arm64) libvpoll-eventfd/unknown (arm64) v4l2loopback/unknown (arm64) nat-rtsp/unknown (arm64) west-chamber/unknown (arm64) langford/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/hirsute/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 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.119.04-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migra
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.119.04-0ubuntu0.20.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migra
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.119.04-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate t
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-450-server into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-450-server/450.119.04-0ubuntu0.21.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also mi
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.20.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 ser
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 ser
[Kernel-packages] [Bug 1925522] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-460 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Committed Status in fabric-manager-460 source package in Bionic: Fix Committed Status in libnvidia-nscq-450 source package in Bionic: Fix Committed Status in libnvidia-nscq-460 source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Committed Status in fabric-manager-460 source package in Focal: Fix Committed Status in libnvidia-nscq-450 source package in Focal: Fix Committed Status in libnvidia-nscq-460 source package in Focal: Fix Committed Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-460 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-465 source package in Focal: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Committed Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Committed Status in fabric-manager-460 source package in Hirsute: Fix Committed Status in libnvidia-nscq-450 source package in Hirsute: Fix Committed Status in libnvidia-nscq-460 source package in Hirsute: Fix Committed Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.4/5.4.0.1049.31)
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1049.31) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-aws-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/4.15.0.144.131)
All autopkgtests for the newly accepted linux-meta (4.15.0.144.131) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux/4.15.0-144.148 (s390x, arm64, i386) 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 [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-hwe-5.4/5.4.0.74.83~18.04.67)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.74.83~18.04.67) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (s390x, ppc64el, amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) lxc/3.0.3-0ubuntu1~18.04.1 (s390x, ppc64el, i386, amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (i386, amd64) acpi-call/1.1.0-4 (s390x, ppc64el) asic0x/1.0.1-1 (s390x) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-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 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1008.8)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1008.8) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: oss4/4.2-build2010-5ubuntu8 (amd64) systemd/247.3-3ubuntu3 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) lttng-modules/2.12.2-1ubuntu3 (amd64) virtualbox/6.1.18-dfsg-5 (amd64) v4l2loopback/0.12.5-1ubuntu1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (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/hirsute/update_excuses.html#linux-meta-kvm [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-kvm/4.15.0.1092.88)
All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1092.88) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.18.04.1 (amd64) nvidia-graphics-drivers-460/460.73.01-0ubuntu0.18.04.1 (amd64) ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64) glibc/2.27-3ubuntu1.4 (amd64) lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) nvidia-graphics-drivers-450/450.119.03-0ubuntu0.18.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) nvidia-graphics-drivers-450-server/450.119.03-0ubuntu0.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-kvm [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-5.4/5.4.0.1048.27)
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1048.27) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) asic0x/1.0.1-1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) v4l2loopback/0.10.0-1ubuntu1.2 (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-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-gke-5.4/5.4.0.1044.46~18.04.10)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1044.46~18.04.10) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: 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 1905203] Re: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure
Observed on G/KVM, cycle sru-20210510 . ** Tags added: kvm linux-kvm sru-20210510 -- 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/1905203 Title: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/linux/20201119_073627_7226f@/log.gz 06:29:30 DEBUG| [stdout] # selftests: net: fib_nexthop_multiprefix.sh [...] 06:29:37 DEBUG| [stdout] # 06:29:37 DEBUG| [stdout] # IPv4 nexthop api compat mode 06:29:37 DEBUG| [stdout] # 06:29:37 DEBUG| [stdout] # TEST: IPv4 default nexthop compat mode check [ OK ] 06:29:37 DEBUG| [stdout] # TEST: IPv4 compat mode on - route add notification [FAIL] 06:29:37 DEBUG| [stdout] # TEST: IPv4 compat mode on - route dump [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode on - nexthop change [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 set compat mode - 0 [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - route add notification [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - route dump [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - nexthop change [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - nexthop delete [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 set compat mode - 1 [ OK ] [...] 06:39:44 DEBUG| [stdout] # Tests passed: 127 06:39:44 DEBUG| [stdout] # Tests failed: 1 06:39:44 DEBUG| [stdout] not ok 35 selftests: net: fib_nexthops.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905203/+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 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H
Observed on G/KVM, cycle sru-20210510 . ** Tags added: kvm linux-kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / G / H Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-signed-oem-5.6 package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-signed-oem-5.6 source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux-signed-oem-5.6 source package in Groovy: Invalid Bug description: Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Routing with nexthop objects and VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] Tests passed: 36 Tests failed: 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1011-oem 5.6.0-1011.11 ProcVersionSignature: User Name 5.6.0-1011.11-oem 5.6.14 Uname: Linux 5.6.0-1011-oem x86_64 ApportVersion: 2.20.
[Kernel-packages] [Bug 1927272] Re: Some kernel selftests fail on linux-kvm
Observed on G/KVM, cycle sru-20210510 . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: This is a catch-all Launchpad report to list the kernel selftests failures in linux-kvm kernel. The comments will be used to reference and discuss about the failures, pointing to individual issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+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 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
Observed on G/KVM, cycle sru-20210510 . ** Tags added: groovy linux-kvm -- 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/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions[SKIP] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation[ OK ] TEST: vti6: MTU setting on link creation[ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions[SKIP] TEST: ipv6: cleanup of cached exceptions[ OK ] TEST: ipv4: list and flush cached exceptions[ OK ] TEST: ipv6: list and flush cached exceptions[ OK ] ubuntu@selfprovisioned-phlin-b-5-4-net:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ echo $? 1 Probably a test case issue. This is not a regression as I can reproduce this on Bionic 5.4.0-1019-oracle as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-1019-oracle 5.4.0-1019.19~18.04.1 ProcVersionSignature: User Name 5.4.0-1019.19~18.04.1-oracle 5.4.44 Uname: Linux 5.4.0-1019-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jul 15 11:28:29 2020 SourcePackage: linux-signed-oracle-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887661/+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 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
Observed on G/KVM, cycle sru-20210510 . ** Tags added: groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+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 1856010] Re: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite
Observed on G/KVM, cycle sru-20210510 . ** Tags added: groovy kvm linux-kvm sru-20210510 -- 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/1856010 Title: xfrm_policy.sh / pmtu.sh / udpgso_bench.sh from net in ubuntu_kernel_selftests will fail if running the whole suite Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Opinion Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux source package in Focal: Opinion Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: Opinion Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Opinion Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Opinion Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] These 3 tests will fail with timeout error when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT They will pass if you run them manually. This is because of the default 45 seconds timeout in kselftest framework. A quick test shows these tests will take about: xfrm_policy.sh - 2m19.690s pmtu.sh - 3m6.832s udpgso_bench.sh - 0m57.985s [Fix] * b881d089c7c9c7 ("selftests/net: bump timeout to 5 minutes") We have commit 852c8cbf34d3b3 ("selftests/kselftest/runner.sh: Add 45 second timeout per test") for default timeout added since Bionic. However there is a SAUCE patch ("UBUNTU: SAUCE: selftests/net -- disable timeout") to disable timeout for the net test in newer releases. I think we can leave it as-is for the moment unless some test is hanging too long because of that. Therefore Only Bionic needs this patch, the patch can be applied with some context adjustment. [Test] With this patch applied, these tests should have a chance to finish. [Where problems could occur] The fix is just for testing tool, no actual impact to real kernel functions. If this 5 minutes timeout is not enough, we might still seeing this kind of failures in the test report. [Original Bug Report] These 3 tests will fail with timeout when running the whole "net" test in ubuntu_kernel_selftests: * not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT * not ok 16 selftests: net: pmtu.sh # TIMEOUT * not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT However they will pass if you run them manually. So there must be some test in net that will cause this. From the test result it looks like the test was executed in the following sequence: ok 1 selftests: net: reuseport_bpf ok 2 selftests: net: reuseport_bpf_cpu ok 3 selftests: net: reuseport_bpf_numa ok 4 selftests: net: reuseport_dualstack # Successok 5 selftests: net: reuseaddr_conflict ok 6 selftests: net: tls ok 7 selftests: net: run_netsocktests ok 8 selftests: net: run_afpackettests ok 9 selftests: net: test_bpf.sh ok 10 selftests: net: netdevice.sh ok 11 selftests: net: rtnetlink.sh not ok 12 selftests: net: xfrm_policy.sh # TIMEOUT not ok 13 selftests: net: test_blackhole_dev.sh # exit=1 ok 14 selftests: net: fib_tests.sh ok 15 selftests: net: fib-onlink-tests.sh not ok 16 selftests: net: pmtu.sh # TIMEOUT ok 17 selftests: net: udpgso.sh not ok 18 selftests: net: ip_defrag.sh # exit=255 not ok 19 selftests: net: udpgso_bench.sh # TIMEOUT ok 20 selftests: net: fib_rule_tests.sh not ok 21 selftests: net: msg_zerocopy.sh # exit=1 ok 22 selftests: net: psock_snd.sh ok 23 selftests: net: udpgro_bench.sh ok 24 selftests: net: udpgro.sh ok 25 selftests: net: test_vxlan_under_vrf.sh ok 26 selftests: net: reuseport_addr_any.sh ok 27 selftests: net: test_vxlan_fdb_changelink.sh ok 28 selftests: net: so_txtime.sh ok 29 selftests: net: ipv6_flowlabel.sh ok 30 selftests: net: tcp_fastopen_backup_key.sh ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1009-aws 5.3.0-1009.10 ProcVersionSignature: User Name 5.3.0-1009.10-aws 5.3.13 Uname: Linux 5.3.0-1009-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: arm64 Date: Wed Dec 11 06:42:39 2019 Ec2AMI: ami-047cec24582f6ae0d Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/18
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
Observed on G/KVM, cycle sru-20210510 . ** Tags added: linux-kvm -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bugs.
[Kernel-packages] [Bug 1898808] Re: unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
** Summary changed: - [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 + unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 -- 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/1898808 Title: unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version:
[Kernel-packages] [Bug 1929217] [NEW] Select correct boot VGA when BIOS doesn't do it properly
Public bug reported: [Impact] On HP EliteDesk 805 G7 desktop, when a add-in discrete GFX card is present but the display is connected to integrated GPU, BIOS cannot find the correct boot VGA. Hence, wrong OpenGL/Vulkan library is used, makes the desktop environment very laggy. [Fix] The current heuristic picks the fallback VGA device with lowest PCI device number. Based on the current heuristic, also check for ACPI video device which should be the integrated VGA device. [Test] Check if the integrated GPU is the boot VGA: $ cat /sys/bus/pci/devices/\:08\:00.0/boot_vga 0 After applying the patch: $ cat /sys/bus/pci/devices/\:08\:00.0/boot_vga 1 [Where problems could occur] When there are multiple GPUs that are ACPI video devices, and BIOS failed to find a VGA to POST, the new heuristic introduces new behavior. Since multiple ACPI video devices are on laptops, the EFI base should already be correct otherwise there's no POST. If that really happens the laptop is completely broken at first place. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1916427 stella ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Hirsute) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-1916427 stella -- 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/1929217 Title: Select correct boot VGA when BIOS doesn't do it properly 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: Confirmed Status in linux source package in Hirsute: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] On HP EliteDesk 805 G7 desktop, when a add-in discrete GFX card is present but the display is connected to integrated GPU, BIOS cannot find the correct boot VGA. Hence, wrong OpenGL/Vulkan library is used, makes the desktop environment very laggy. [Fix] The current heuristic picks the fallback VGA device with lowest PCI device number. Based on the current heuristic, also check for ACPI video device which should be the integrated VGA device. [Test] Check if the integrated GPU is the boot VGA: $ cat /sys/bus/pci/devices/\:08\:00.0/boot_vga 0 After applying the patch: $ cat /sys/bus/pci/devices/\:08\:00.0/boot_vga 1 [Where problems could occur] When there are multiple GPUs that are ACPI video devices, and BIOS failed to find a VGA to POST, the new heuristic introduces new behavior. Since multiple ACPI video devices are on laptops, the EFI base should already be correct otherwise there's no POST. If that really happens the laptop is completely broken at first place. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929217/+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 1927067] Re: Add s2idle support on AMD Renoir and Cezanne
** Tags removed: verification-needed-focal ** Tags added: verification-done-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/1927067 Title: Add s2idle support on AMD Renoir and Cezanne 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: Confirmed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] S2idle doesn't work on AMD Renoir and Cezanne. [Fix] Backport AMD PMC driver and pull many new patches let AMDGPU support s2idle. [Test] Suspend the laptop and the system freezes. With the patch applied, suspend works but with some caveats: 1) Keyboard sometimes can't wake up the laptop. 2) Touchpad sometimes can wake up the laptop. 3) RTC can't wake up the laptop. (Hardware Limitation) [Where problems could occur] Most changes are limited to logic of suspend/resume, and specific to Renoir GFX. However, there are some refactoring patches may cause unintended results, so AMDGPU may break for sleep/hibernation/runtime suspend on non-Renoir GFXs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927067/+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 1927272] Re: Some kernel selftests fail on linux-kvm
Observed on F/KVM, cycle sru-20210510. ** Tags added: focal linux-kvm sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1927272 Title: Some kernel selftests fail on linux-kvm Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: This is a catch-all Launchpad report to list the kernel selftests failures in linux-kvm kernel. The comments will be used to reference and discuss about the failures, pointing to individual issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927272/+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 1812194] Re: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled)
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: rtnetlink.sh in net from ubuntu_kernel_selftests failed on KVM kernels (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+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 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/linux Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: New Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage notifications about this bug go to: https://bug
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions[SKIP] TEST: IPv4 over geneve6: PMTU exceptions[ OK ] TEST: IPv6 over geneve6: PMTU exceptions[ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation[ OK ] TEST: vti6: MTU setting on link creation[ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions[SKIP] TEST: ipv6: cleanup of cached exceptions[ OK ] TEST: ipv4: list and flush cached exceptions[ OK ] TEST: ipv6: list and flush cached exceptions[ OK ] ubuntu@selfprovisioned-phlin-b-5-4-net:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ echo $? 1 Probably a test case issue. This is not a regression as I can reproduce this on Bionic 5.4.0-1019-oracle as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-1019-oracle 5.4.0-1019.19~18.04.1 ProcVersionSignature: User Name 5.4.0-1019.19~18.04.1-oracle 5.4.44 Uname: Linux 5.4.0-1019-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jul 15 11:28:29 2020 SourcePackage: linux-signed-oracle-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887661/+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 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+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 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Found on Focal/linux-kvm, cycle sru-20210510. ** Tags added: sru-20210510 -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+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 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829995 Title: getaddrinfo_01 from ipv6_lib test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Bug description: startup='Wed May 22 08:02:52 2019' getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4 canonical name ("curly.maas") doesn't match hostname ("curly") getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic lookup ("curly") returns -5 ("No address associated with hostname") tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 08:04:30 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+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 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
Observed in F/KVM, cycle sru-20210510. ** Tags added: sru-20210510 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+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 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Observed in F/KVM, cycle sru-20210510. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, just to make sure that I reinstalled one of the kernels that was supposed to be good (perhaps by accident I reinstalled a bad one), could you direct me to a good kernel on your ftp site? best, Jim -- 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/1896482 Title: acpi event detection crashes Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: = SRU Justification = [Impact] The bug causes the EC driver to fail and ACPI events are no longer handled by Linux kernel, i.e lid close no longer triggers suspends. [Fix] Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid initialisation failures. The other three patches are prerequisite to apply 03e9a0e05739cf on focal kernel. [Test] Tested with Lenovo ThinkPad X1 Carbon Gen 8 [Regression Potential] Low. The patches were cherry-picked from mainline kernel (two since 5.5 and two since 5.7) = Original Bug Report = Right after booting, acpi lid open/close is detected as it should be by the kernel, but some time later it crashes, so I have to manually suspend the system. The traceback is here: Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here ] Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwifi processor_thermal_device bluetooth videodev Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake pinctrl_intel Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query acpi_ec_event_processor Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: 0010:__queue_work+0x337/0x3f0 Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b e9 fd fd Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 EFLAGS: 00010087 Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: 0002 RCX: 0004 Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: 9a2475b03200 RDI: 9a2430215f00 Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: R09: 0007 Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: R12: 9a2475af4a00 Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: 2000 R15: 9a2475af4a90 Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () GS:9a247740() knlGS: Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: CR0: 80050033 Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: 00018520a003 CR4: 003606f0 Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Tra
[Kernel-packages] [Bug 1928047] Re: AX201 BT will cause system could not enter S0i3
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1928047 Title: AX201 BT will cause system could not enter S0i3 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-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: In Progress Bug description: [Impact] Platforms with AX201 BT fail to pass the power consumption tests [Fix] Intel provides us the patch to fix it. https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/ [Test] Verified on the Dell machines with AX201 BT on them. [Where problems may occur] This patch extend the s0ix fix for gen8 and gen11 to all PCHs. Not sure if it will lead to regressions on different PCH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928047/+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 1929166] Re: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station
** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1929166 Title: TGL-H system NV GPU fallen off the bus after resuming from s2idle with the external display connected via docking station Status in HWE Next: New Status in linux package in Ubuntu: Incomplete 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 Bug description: [SRU Justification] [Impact] The NVIDIA GPU will fall off the bus after exiting s2idle in TGL-H systems if the docking station 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. Then display managed by the NVDIA GPU shows nothing until system reboot. Note that it only happens when NVIDIA GPU in either Performance mode or On-Demand mode. [Fix] A BIOS workaround is used to skip the ACPI method PGSC which invokes IPCS to do source clock control of the PCIe root port with an _OSI string "Linux-Dell-USB4-NVWakeup". Should be removed until we get a generic fix for it. [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. [Regression Potential] Low. This only works on platforms supporting "Linux-Dell-USB4-NVWakeup". No other platforms will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1929166/+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 1925421] Re: arm64 support
** Changed in: linux-oracle-5.4 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1925421 Title: arm64 support Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-5.4 package in Ubuntu: New Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Committed Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+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 1925290] Re: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8
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/1925290 Title: hangup01 from pty in ubuntu_ltp_stable failed on G-5.8 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Testcase hangup01 from ubuntu_ltp_stable.pty is failing on Groovy 5.8.0-51.57. Test case failed with: hangup011 TFAIL : hangup01.c:132: unexpected message 3 tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1 It was found that the regression was introduced by the following commits applied via stable uddates: dd78b0c483e3 tty: implement read_iter 3b830a9c34d5 tty: convert tty_ldisc_ops 'read()' function to take a kernel pointer These patches were applied via bug 1921960 ("Groovy update: upstream stable patchset 2021-03-30"). [Fix] Revert the patches mentioned above until a fix can be found. [Test case] Run the pty testsuite from ubuntu_ltp_stable. [Where problems could occur] If reverting these two patches is not enough to bring the code to the behavior of the tty driver before 5.8.0-51.57 then remaining issues could still be present on the tty code. Those issues should be caught by the ltp testcases though. [Original Description] Issue found on Groovy 5.8.0-51.57 with P8 node "dryden" and ARM64 node "helo-kernel" and AMD64 node "onibi" Test case failed with: hangup011 TFAIL : hangup01.c:132: unexpected message 3 tag=hangup01 stime=1618856629 dur=1 exit=exited stat=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1925290/+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 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
** Description changed: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 450-server == - * New upstream release (LP: #1925522). - - Fixed an issue with the NSCQ library that caused clients such as - DCGM to fail to load the library. Since the NSCQ library version - needs to match the driver version, the user would encounter a - version mismatch issue when using DCGM. - - Fixed an ECC policy that caused a CUDA malloc failure after - encountering a single uncorrectable error. + * New upstream release (LP: #1925522). + - Fixed an issue with the NSCQ library that caused clients such as + DCGM to fail to load the library. Since the NSCQ library version + needs to match the driver version, the user would encounter a + version mismatch issue when using DCGM. + - Fixed an ECC policy that caused a CUDA malloc failure after + encountering a single uncorrectable error. == 460 == - * debian/templates/control.in: - - Make nvidia-dkms depend on its versioned nvidia-kernel-source - (LP: #1925386). - - Add transitional packages for the 450 series (LP: #1925522). + * debian/additional_card_ids: + - Add new IDs (LP: #1928808): + 1FB1 (Nvidia T600) + 2231 (Nvidia RTX A5000) + 24B7 (Nvidia RTX A4000 mobile) + 24B8 (Nvidia RTX A3000 mobile) + 25B8 (Nvidia RTX A2000 mobile) + * debian/templates/control.in: + - Make nvidia-dkms depend on its versioned nvidia-kernel-source + (LP: #1925386). + - Add transitional packages for the 450 series (LP: #1925522). == 465 == - * Initial release (LP: #1925522). + * Initial release (LP: #1925522). == nvidia-settings == - * New upstream release (LP: #1925522). [all releases] - * debian/patches/08_add_prime_support.patch: [all releases except for impish and hirsute] - - Stop the timeout after the child is done. This fixes an error - that g_type_check_instance_is_a() was throwing. + * New upstream release (LP: #1925522). [all releases] + * debian/patches/08_add_prime_support.patch: [all releases except for impish and hirsute] + - Stop the timeout after the child is done. This fixes an error + that g_type_check_instance_is_a() was throwing. == fabric-manager-450 and fabric-manager-460 == - * Initial release (LP: #1925522). + * Initial release (LP: #1925522). == libnvidia-nscq-450 and libnvidia-nscq-460 == - * Initial release (LP: #1925522). + * Initial release (LP: #1925522). ** Description changed: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 450-server == * New upstream release (LP: #1925522). - Fixed an issue with the NSCQ library that caused clients such as DCGM to fail to load the library. Since the NSCQ library version needs to match the driver version, the user would encounter a version mismatch issue when using DCGM. - Fixed an ECC policy that caused a CUDA mall
[Kernel-packages] [Bug 1928808] Re: Requiring extra device ID for nvidia-driver-460
** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1928808 Title: Requiring extra device ID for nvidia-driver-460 Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Bug description: There are some new nvidia graphics could be supported by nvidia-driver-460. Here are the list: 1fb1 (Nvidia T600) 2231 (Nvidia RTX A5000) 24b7 (Nvidia RTX A4000 mobile) 24b8 (Nvidia RTX A3000 mobile) 25b8 (Nvidia RTX A2000 mobile) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1928808/+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 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
All you guys mocking around with ppas could have compiled 5.12.5 by now 20x! The last working mainline kernel is 5.11.16. Nothing later works when installing into 18.04 LTS. I've been forced to compile each latest kernel since. But because of that predicament, I've now got it down to a fixed repeatable routine and can do it with my eyes closed or even script it at some point. Best thing about it is it is compiled against my cpu architecture and with -O3 optimisations (just like gentoo). -- 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+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 1928047] Re: AX201 BT will cause system could not enter S0i3
** Description changed: [Impact] - Platform with AX201 BT fail to pass the power consumption tests + Platforms with AX201 BT fail to pass the power consumption tests [Fix] Intel provides us the patch to fix it. https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/ [Test] Verified on the Dell machines with AX201 BT on them. [Where problems may occur] + This patch extend the s0ix fix for gen8 and gen11 to all PCHs. Not sure if it will lead to regressions on different PCH. -- 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/1928047 Title: AX201 BT will cause system could not enter S0i3 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-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Bug description: [Impact] Platforms with AX201 BT fail to pass the power consumption tests [Fix] Intel provides us the patch to fix it. https://patchwork.kernel.org/project/intel-gfx/patch/20210325120947.11950-1-anshuman.gu...@intel.com/ [Test] Verified on the Dell machines with AX201 BT on them. [Where problems may occur] This patch extend the s0ix fix for gen8 and gen11 to all PCHs. Not sure if it will lead to regressions on different PCH. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1928047/+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