[Kernel-packages] [Bug 2008245] Re: zfs-dkms: support linux 6.2
New debdiff on top of Debian zfs-linux 2.1.9-2. Smoke-tested in a local VM. Thanks! ** Patch added: "zfs-linux-2.1.9-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+attachment/5651251/+files/zfs-linux-2.1.9-2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008245 Title: zfs-dkms: support linux 6.2 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Lunar: New Bug description: [Impact] The current version of zfs-dkms available in lunar fails to build with kernels >= 6.2, reporting the following configure error: configure: error: *** None of the expected "iops->get_acl()" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or you are using a patched custom kernel with *** incompatible modifications. *** *** ZFS Version: zfs-2.1.7-1ubuntu1 *** Compatible Kernels: 3.10 - 6.0 [Test case] $ apt install zfs-dkms [Fix] Resync with zfs version in Debian (2.1.9) and apply the usual Ubuntu specific changes. [Regression potential] We may experience zfs regressions due to a new major version, especially on zfs volumes / filesystems created with the previous versions. However this goes in pair with the new major kernel version and we need to upgrade the version of zfs to properly support the new kernel 6.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: In Progress ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: In Progress => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Tags added: oem-priority originate-from-2002264 sutton -- 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
These packages do not show up as having mismatched components. https://people.canonical.com/~ubuntu-archive/component-mismatches- proposed.html They need to be seeded somewhere before we would promote these to main. ** Changed in: linux-meta-xilinx-zynqmp (Ubuntu) Status: Triaged => Incomplete ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Incomplete Status in linux-xilinx-zynqmp package in Ubuntu: Incomplete Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
the status does not need to be set to triaged to be in our queue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Incomplete Status in linux-xilinx-zynqmp package in Ubuntu: Incomplete Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] 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 2009118 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] [NEW] Fix mediatek wifi driver crash when loading wrong SAR table
Public bug reported: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
Sure, I'll try to find out but will take few days. Thanks again for your support and the above links. I'll report this to kernel graphics developers. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
If you can spare the time then the most useful thing to do would be to identify the exact kernel version where it stopped working: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Otherwise please report the issue to the kernel graphics developers at: https://gitlab.freedesktop.org/drm/intel/-/issues/new -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "lsmod515_dell_Ubuntu20.04.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651229/+files/lsmod515_dell_Ubuntu20.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "journal515_dell_Ubuntu20.04.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651228/+files/journal515_dell_Ubuntu20.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
Adding MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 to /etc/environment did not help for both 5.19 and 6.2 kernels. I am attaching logs for the Ubuntu version 20.04 in a Dell laptop with the same dock. This works flawlessly. subhajit@subhajit-Latitude-5300:~$ lsb_release -rv LSB Version:security-11.1.0ubuntu2-noarch Release:20.04 Thanks for the quick response. Hope these logs help. ** Attachment added: "lspcik515_dell_Ubuntu20.04.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651227/+files/lspcik515_dell_Ubuntu20.04.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1989578 Title: Add HDMI codec ID for Intel Raptor Lake Status in HWE Next: Fix Released Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] The HDAudio is not functional on some RaptorLake machines. The audio codec is failed to be probed so no PCM stream available for audio functions. [Fix] Backport the patch from upstream which adds the support for the HDMI codec ID on RaptorLake. [Test] Power on the machine and check if the audio function's working with alsa utilities. [Where problems could occur] The change only applies to the new RaptorLake Intel HDA controller and HDMI codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991365] Re: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1991365 Title: Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] turbostat doesn't show the correct fields for RPL-S. This's a wrong column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,CPU%LPI,SYS%LPI [Fix] Add RPL-S support in turbostat [Test Case] 1. run "turbostat --list" 2. check the output, this is a correct column. usec,Time_Of_Day_Seconds,Core,CPU,APIC,X2APIC,Avg_MHz,Busy%,Bzy_MHz,TSC_MHz,IPC,IRQ,SMI,POLL,C1ACPI,C2ACPI,C3ACPI,POLL%,C1ACPI%,C2ACPI%,C3ACPI%,CPU%c1,CPU%c6,CPU%c7,CoreTmp,CoreThr,PkgTmp,GFX%rc6,GFXMHz,GFXAMHz,Totl%C0,Any%C0,GFX%C0,CPUGFX%,Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI,PkgWatt,CorWatt,GFXWatt,RAMWatt,PKG_%,RAM_% [Where problems could occur] Low, just add a devcie id to support RPL-S. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1995453 Title: Add some ACPI device IDs for Intel HID device Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] Add the ACPI devices IDs for Intel JasonLake, MeteorLake and RaptorLake [Fix] ACPI devices IDs are add the the related Intel HID devices on these platforms can work. [Test] Verified the Intel HID events can work such as power button for suspend and wake. [Where problems could occur] Add the ACPI device IDs for support Intel HID devices, so chance of problems should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: New Status in oem-somerville-tentacool-meta package in Ubuntu: New Bug description: I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002968 Title: Fix flicker display problem on some panels which support PSR2 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some PSR2 supported panels, which connects to Intel Graphics has flicker symptom. It gets normal after booting the kernel with parameter `i915. enable_psr=0` [Fix] Backport one patch from upstream. https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87 [Test] Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if the display has abnormal flickering problem on graphics interfaces. [Where problems could occur] The risk of regression is low. It only fixes problem on panels which support PSR2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "lsmod62.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651226/+files/lsmod62.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
Thanks you for the links. Tried the above mainline kernel 6.2.1: subhajit@subhajit-ThinkPad-Yoga-370:~$ uname -a Linux subhajit-ThinkPad-Yoga-370 6.2.1-060201-generic #202302251141 SMP PREEMPT_DYNAMIC Sat Feb 25 11:49:50 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Same issues as kernel 5.19 Reconnecting the USB-C cable does not help. Attached are the logs. ** Attachment added: "journal62.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651225/+files/journal62.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: High Assignee: Kai-Heng Feng (kaihengfeng) Status: Invalid ** Also affects: mutter (Ubuntu Lunar) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: Opinion ** Also affects: mesa (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Changed in: mesa (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mesa (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: mesa (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu Lunar) 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode Status in Linux: New Status in Mutter: Fix Released Status in OEM Priority Project: Incomplete Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Opinion Status in linux source package in Jammy: New Status in mesa source package in Jammy: Confirmed Status in mutter source package in Jammy: New Status in linux source package in Kinetic: New Status in mesa source package in Kinetic: Confirmed Status in mutter source package in Kinetic: New Status in linux source package in Lunar: Invalid Status in mesa source package in Lunar: Confirmed Status in mutter source package in Lunar: Opinion Bug description: [Steps to reproduce] (disable systemd-oomd or executing over ssh) (below command allocates a lot of memory to stress kernel page fault) 1. stress-ng --stack 0 --timeout 300 2. check the screen [Expected result] Screen will update slowly when performing the stress-test. but screen needs back to work after stress. [Actual result] Screen freeze after stress test. [Additional information] kernel version: vmlinuz-5.17.0-1017-oem kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic Mesa version: 22.0.5-0ubuntu0.1 Mutter version: 42.2-0ubuntu1 Gnome-shell version: 42.2-0ubuntu0.2 * Issue happens in Wayland only * gnome-shell keeps issuing ioctl() ``` (gdb) bt #0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at ../sysdeps/unix/sysv/linux/ioctl.c:36 #1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75 #2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229 #3 iris_wait_syncobj (bufmgr=, syncobj=, timeout_nsec=timeout_nsec@entry=9223372036854775807) at ../src/gallium/drivers/iris/iris_fence.c:215 #4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, wait=, query=0x55774159b800, ctx=) at ../src/gallium/drivers/iris/iris_query.c:635 #5 iris_get_query_result (ctx=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/drivers/iris/iris_query.c:601 #6 0x7fcaca405e89 in tc_get_query_result (_pipe=, query=0x55774159b800, wait=, result=0x7fffc5404e50) at ../src/gallium/auxiliary/util/u_threaded_context.c:881 #7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at ../src/mesa/main/queryobj.c:266 #8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344 #9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 "glGetQueryObjecti64v", id=, pname=34918, ptype=ptype@entry=5134, buf=0x0, offset=140736502714192) at ../src/mesa/main/queryobj.c:1174 #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, pname=, params=) at ../src/mesa/main/queryobj.c:1257 #11 0x7fcadfa39b90 in ?? () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from /usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0 #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 #14 0x7fcadfa6e7a2 in
[Kernel-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)
Given the Bug Description says the problem doesn't occur in the live installer session, that suggests this is Wayland specific or even specific to atomic KMS. So please try the workaround from comment #19. -- 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/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed) Status in GNOME Shell: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
Does the situation improve if you add this to /etc/environment and reboot? MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
It sounds like 5.15 is hitting bug 1970495 but you found a workaround in re-plugging the cable. As for 5.19, I see nothing in the log to explain it so this seems like an opaque kernel bug. As such I recommend trying newer kernels like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.2.1/amd64/ But you will need to disable Secure Boot in your BIOS to run them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
All required files are attached. Sorry, I was not able to attach multiple files at one go. Edit: In the 5.15.0-60-generic working kernel, I still have to unplug and plug the USB-C cable once after bootup to get the external monitor working. No hardware issue (No USB-C connector issue): I have another SSD with Windows 10 installation which works perfectly with this laptop and dock combination. I have another Dell laptop with Ubuntu 20.04 which works beautifully on this dock. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-450-server - 450.216.04-0ubuntu1 --- nvidia-graphics-drivers-450-server (450.216.04-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #1997087). -- Alberto Milone Thu, 24 Nov 2022 09:46:52 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42263, CVE-2022-42264, CVE-2022-42265 R510 CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684,
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.86.01-0ubuntu1 --- nvidia-graphics-drivers-515 (515.86.01-0ubuntu1) lunar; urgency=medium * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_6.0.patch. * New upstream release (LP: #1997087). -- Alberto Milone Tue, 22 Nov 2022 15:24:16 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-450-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254,
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651202/+files/lspcik.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "lsmod519.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651201/+files/lsmod519.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "journal519.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651199/+files/journal519.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "lsmod515.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651200/+files/lsmod515.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
** Attachment added: "journal515.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+attachment/5651198/+files/journal515.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009044] Re: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0
** Description changed: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. also clean up the FPU codes on dcn folder. [Test Case] - 1. Install the X200 manifest and the AMD W6800 on the system. - 2. Boot into desktop and check the dmesg + 1. boot a machine the AMD W6800/W6400. + 2. get into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. [Misc Info] all patches have been landed on Unstable/Lunar so SRU only for Kinetic. -- 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/2009044 Title: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: In Progress Bug description: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. also clean up the FPU codes on dcn folder. [Test Case] 1. boot a machine the AMD W6800/W6400. 2. get into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. [Misc Info] all patches have been landed on Unstable/Lunar so SRU only for Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009044] 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 2009044 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/2009044 Title: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: In Progress Bug description: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. also clean up the FPU codes on dcn folder. [Test Case] 1. boot a machine the AMD W6800/W6400. 2. get into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. [Misc Info] all patches have been landed on Unstable/Lunar so SRU only for Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009044] Re: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0
** Description changed: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. - also clean up the FPU codes on dcn folder. + also clean up the FPU codes on dcn folder. [Test Case] 1. Install the X200 manifest and the AMD W6800 on the system. 2. Boot into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. + + [Misc Info] + all patches have been landed on Unstable/Lunar so SRU only for Kinetic. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009044 Title: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: In Progress Bug description: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. also clean up the FPU codes on dcn folder. [Test Case] 1. boot a machine the AMD W6800/W6400. 2. get into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. [Misc Info] all patches have been landed on Unstable/Lunar so SRU only for Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] Re: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
Thanks for the bug report. Please run the following commands on the failing 5.19 kernel: journalctl -b0 > journal519.txt lspci -k > lspcik.txt lsmod > lsmod519.txt Please also run these commands on the working 5.15 kernel: journalctl -b0 > journal515.txt lsmod > lsmod515.txt and attach all the resulting text files here. ** Tags added: jammy ** Package changed: mutter (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Tags added: dock multimonitor regression-release ** Tags added: mst ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009105 Title: External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock Status in linux-hwe-5.19 package in Ubuntu: Incomplete Bug description: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2009105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958973] Re: icmp.sh from selftests.net fails
** Summary changed: - impish:linux: icmp.sh from selftests.net fails + icmp.sh from selftests.net fails -- 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/1958973 Title: icmp.sh from selftests.net fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Won't Fix Bug description: icmp.sh from selftests.net is a relatively new testcase which started to be run on impish (5.13) kernels only in the latest builds after commit "ca3676f94b8f kselftests/net: add missed icmp.sh test to Makefile". With impish:linux-riscv kernel version 5.13.0-1011.12 the testcase fails with the following error: 19:41:38 DEBUG| Running 'make run_tests -C net TEST_PROGS=icmp.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' 19:41:38 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 19:41:38 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install 19:41:38 DEBUG| [stdout] make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 19:41:46 DEBUG| [stdout] INSTALL ./usr/include 19:41:47 DEBUG| [stdout] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 19:41:47 DEBUG| [stdout] TAP version 13 19:41:47 DEBUG| [stdout] 1..1 19:41:48 DEBUG| [stdout] # selftests: net: icmp.sh 19:41:49 DEBUG| [stdout] # FAIL - got ICMP response from , should be 192.0.0.8 19:41:52 DEBUG| [stdout] not ok 1 selftests: net: icmp.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009105] [NEW] External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock
You have been subscribed to a public bug: Hardware: Lenovo Yoga 370 with Lenovo USB-C dock 40A9 with dual monitors on Display Ports. Hardware updates: All bios, thunderbolt, dock firmware are updated with latest versions. Distribution: Ubuntu 22.04.2 LTS Kernel: 5.19.0-35-generic Issue: No display on external monitors. The monitors are getting detected in Display Settings but there is no video. Temporary fix: Switch to the previous kernel: 5.15.0-60-generic Attachment: A complete dmesg output is attached. dmesg -l err output when I plug in my USB-C connector of the doc: subhajit@subhajit-ThinkPad-Yoga-370:~$ sudo dmesg -l err [ 1128.136192] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95) [ 1128.192050] ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x7) is beyond end of object (length 0x5) (20220331/exoparg2-393) [ 1128.192180] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC.BRNS due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) [ 1128.192207] ACPI Error: Aborting method \_SB.PCI0.LPCB.EC._Q26 due to previous error (AE_AML_PACKAGE_LIMIT) (20220331/psparse-529) ** Affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- External Monitors not working on Ubuntu 22.04.2 with kernel 5.19.0-35 with USB-C dock https://bugs.launchpad.net/bugs/2009105 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 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 1995511] Re: net-build failed in ubuntu_kernel_selftests with 6.0 kernel
** Tags added: sru-20230130 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1995511 Title: net-build failed in ubuntu_kernel_selftests with 6.0 kernel Status in ubuntu-kernel-tests: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.0 source package in Jammy: New Bug description: Issue found with J-oem-6.0.0-1007.7 This is not a regression, issue exists before this kernel. make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_cpu.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_cpu gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_bpf_numa.c -lnuma -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf_numa gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseport_dualstack.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_dualstack gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include reuseaddr_conflict.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseaddr_conflict gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ -isystem /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/usr/include tls.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/tls make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: tls.c:32:50: error: field ‘sm4gcm’ has incomplete type 32 | struct tls12_crypto_info_sm4_gcm sm4gcm; | ^~ tls.c:33:50: error: field ‘sm4ccm’ has incomplete type 33 | struct tls12_crypto_info_sm4_ccm sm4ccm; | ^~ tls.c: In function ‘tls_crypto_info_init’: tls.c:56:14: error: ‘TLS_CIPHER_SM4_GCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 56 | case TLS_CIPHER_SM4_GCM: | ^~ | TLS_CIPHER_AES_GCM_256 tls.c:56:14: note: each undeclared identifier is reported only once for each function it appears in tls.c:57:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_gcm’ 57 | tls12->len = sizeof(struct tls12_crypto_info_sm4_gcm); | ^~ tls.c:61:14: error: ‘TLS_CIPHER_SM4_CCM’ undeclared (first use in this function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 61 | case TLS_CIPHER_SM4_CCM: | ^~ | TLS_CIPHER_AES_CCM_128 tls.c:62:37: error: invalid application of ‘sizeof’ to incomplete type ‘struct tls12_crypto_info_sm4_ccm’ 62 | tls12->len = sizeof(struct tls12_crypto_info_sm4_ccm); | ^~ tls.c: At top level: tls.c:268:24: error: ‘TLS_CIPHER_SM4_GCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_GCM_256’? 268 | .cipher_type = TLS_CIPHER_SM4_GCM, |^~ |TLS_CIPHER_AES_GCM_256 tls.c:274:24: error: ‘TLS_CIPHER_SM4_CCM’ undeclared here (not in a function); did you mean ‘TLS_CIPHER_AES_CCM_128’? 274 | .cipher_type = TLS_CIPHER_SM4_CCM, |^~ |TLS_CIPHER_AES_CCM_128 tls.c: In function ‘tls_setup’: tls.c:329:54: error: ‘TLS_RX_EXPECT_NO_PAD’ undeclared
[Kernel-packages] [Bug 1958973] Re: impish:linux: icmp.sh from selftests.net fails
** Tags added: 5.19 jammy ** Tags added: sru-20230102 -- 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/1958973 Title: impish:linux: icmp.sh from selftests.net fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Won't Fix Bug description: icmp.sh from selftests.net is a relatively new testcase which started to be run on impish (5.13) kernels only in the latest builds after commit "ca3676f94b8f kselftests/net: add missed icmp.sh test to Makefile". With impish:linux-riscv kernel version 5.13.0-1011.12 the testcase fails with the following error: 19:41:38 DEBUG| Running 'make run_tests -C net TEST_PROGS=icmp.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' 19:41:38 DEBUG| [stdout] make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 19:41:38 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install 19:41:38 DEBUG| [stdout] make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 19:41:46 DEBUG| [stdout] INSTALL ./usr/include 19:41:47 DEBUG| [stdout] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' 19:41:47 DEBUG| [stdout] TAP version 13 19:41:47 DEBUG| [stdout] 1..1 19:41:48 DEBUG| [stdout] # selftests: net: icmp.sh 19:41:49 DEBUG| [stdout] # FAIL - got ICMP response from , should be 192.0.0.8 19:41:52 DEBUG| [stdout] not ok 1 selftests: net: icmp.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958973/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995956] Re: amdgpu no-retry page fault resulting in black screen and unresponsive system
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1995956 Title: amdgpu no-retry page fault resulting in black screen and unresponsive system Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: When using Skype in snap, amdgpu crashed, resulting in black screen and unresponsive system. Happened on Kinetic Kudu 5.19.0-23-generic with or without latest amdgpu firmware. Affected laptop is T14 with Ryzen 5850U. Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142c000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00540051 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x5 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x1 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: [mmhub0] no-retry page fault (src_id:0 ring:40 vmid:5 pasid:0, for process pid 0 thread pid 0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: in page starting at address 0x80010142d000 from IH client 0x12 (VMC) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: Faulty UTCL2 client ID: MP1 (0x0) Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MORE_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: WALKER_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: PERMISSION_FAULTS: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: MAPPING_ERROR: 0x0 Nov 03 16:35:44 laptop kernel: amdgpu :07:00.0: amdgpu: RW: 0x0 This happens in a loop and eventually leads to GPU reset, which fails. Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=211509, emitted seq=211512 Nov 03 16:35:55 laptop kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process skypeforlinux pid 154554 thread skypeforli:cs0 pid 154558 Nov 03 16:35:55 laptop kernel: amdgpu :07:00.0: amdgpu: GPU reset begin! Nov 03 16:35:55 laptop kernel: [drm] free
[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
Hints removed, closing this bug.
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2000667
Title:
cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
ubuntu_kernel_selftests hang with non-amd64
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
non-amd64 systems and eventually causing "Incomplete" test results on
RISCV kernels due to the timeout setting.
This is because of an infinity while loop caused by a char variable
used here to take the getopt() return value in cmsg_sender.c, it should
be an int instead.
[Fix]
* 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
This patch can be cherry-picked into both Kinetic and Lunar, these test
cases are only available in these newer kernels.
[Test]
Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
tests will no longer hanging.
[Where problems could occur ]
Change limited to testing tools, no actual impact to real functions.
[Original Bug Report]
Issue found with 5.19.0-1010.11, 5.19.0-1011.12
This issue does not exist in 5.19.0-1009.10 because the net test can't
be built by that time.
Test output:
Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..1
# selftests: net: cmsg_so_mark.sh
Timer expired (5400 sec.), nuking pid 82951
A manual test shows it will stuck with:
$ sudo ./cmsg_so_mark.sh
+ NS=ns
+ IP4=172.16.0.1/24
+ TGT4=172.16.0.2
+ IP6=2001:db8:1::1/64
+ TGT6=2001:db8:1::2
+ MARK=1000
+ trap cleanup EXIT
+ ip netns add ns
+ ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
+ ip -netns ns link add type dummy
+ ip -netns ns link set dev dummy0 up
+ ip -netns ns addr add 172.16.0.1/24 dev dummy0
+ ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
+ ip -netns ns rule add fwmark 1000 lookup 300
+ ip -6 -netns ns rule add fwmark 1000 lookup 300
+ ip -netns ns route add prohibit any table 300
+ ip -6 -netns ns route add prohibit any table 300
+ BAD=0
+ TOTAL=0
+ for ovr in setsock cmsg both
+ for i in 4 6
+ '[' 4 == 4 ']'
+ TGT=172.16.0.2
+ for p in u i r
+ '[' u == u ']'
+ prot=UDP
+ '[' u == i ']'
+ '[' u == r ']'
+ '[' setsock == setsock ']'
+ m=-M
+ '[' setsock == cmsg ']'
+ '[' setsock == both ']'
+ ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
(test stuck here)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-510 - 510.108.03-0ubuntu1 --- nvidia-graphics-drivers-510 (510.108.03-0ubuntu1) lunar; urgency=medium * debian/templates/dkms_nvidia.conf.in: - Drop buildfix_kernel_6.0.patch. * New upstream release (LP: #1997087). -- Alberto Milone Fri, 18 Nov 2022 17:09:05 + ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42263,
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.161.03-0ubuntu1 --- nvidia-graphics-drivers-470 (470.161.03-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #1997087). -- Alberto Milone Tue, 22 Nov 2022 16:43:40 + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42263, CVE-2022-42264, CVE-2022-42265 R510 CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254,
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.157-0ubuntu3 --- nvidia-graphics-drivers-390 (390.157-0ubuntu3) lunar; urgency=medium * debian/templates/control.in: - Drop armhf and i386, except for the i386 compatibility libraries. The driver is no longer supported by NVIDIA, and this should solve the kernel build failures (LP: #2006695). -- Alberto Milone Mon, 20 Feb 2023 14:45:32 + ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255,
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.161.03-0ubuntu1 --- nvidia-graphics-drivers-470-server (470.161.03-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #1997087). -- Alberto Milone Wed, 23 Nov 2022 16:03:44 + ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42263, CVE-2022-42264, CVE-2022-42265 R510 CVE-2022-34670, CVE-2022-34674,
[Kernel-packages] [Bug 2009090] Re: usb ports and bluetooth not working
** Description changed: USB Ports, like when using mouse device works only on reboot for a short while (in the login screen) then ultimately stops after login. Same happens to bluetooth also. I checked the logs and it says, usb device - descriptor error -71. This happened after upgrading to ubuntu 22.04 + descriptor error -71. When plugged to AC and mouse is connected before + boot, issue doesn't occur. This happened after upgrading to ubuntu 22.04 Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Mar 3 09:34:37 2023 InstallationDate: Installed on 2022-09-06 (177 days ago) InstallationMedia: Zorin-OS 16 Core 64bit SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-03-01 (1 days ago) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009090 Title: usb ports and bluetooth not working Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: USB Ports, like when using mouse device works only on reboot for a short while (in the login screen) then ultimately stops after login. Same happens to bluetooth also. I checked the logs and it says, usb device descriptor error -71. When plugged to AC and mouse is connected before boot, issue doesn't occur. This happened after upgrading to ubuntu 22.04 Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Mar 3 09:34:37 2023 InstallationDate: Installed on 2022-09-06 (177 days ago) InstallationMedia: Zorin-OS 16 Core 64bit SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-03-01 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997087] Re: NVIDIA CVE-2022 November 28
This bug was fixed in the package nvidia-graphics-drivers-515-server - 515.86.01-0ubuntu2 --- nvidia-graphics-drivers-515-server (515.86.01-0ubuntu2) lunar; urgency=medium * debian/templates/control.in: - Add Conflicts, Replaces, Provides up to libcuda-11.7-1 (LP: #2003995). -- Alberto Milone Wed, 01 Feb 2023 10:36:07 + ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1997087 Title: NVIDIA CVE-2022 November 28 Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-510-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-520 package in Ubuntu: In Progress Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-520 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-510 source package in Focal: Fix Released Status in nvidia-graphics-drivers-510-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-520 source package in Focal: Fix Released Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-390 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-510-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-520 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-390 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-510-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-520 source package in Kinetic: Fix Released Bug description: R515 (likely, also R520) CVE-2022-34670, CVE-2022-34673, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-34684, CVE-2022-42254,
[Kernel-packages] [Bug 2006695] Re: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar
This bug was fixed in the package nvidia-graphics-drivers-390 - 390.157-0ubuntu3 --- nvidia-graphics-drivers-390 (390.157-0ubuntu3) lunar; urgency=medium * debian/templates/control.in: - Drop armhf and i386, except for the i386 compatibility libraries. The driver is no longer supported by NVIDIA, and this should solve the kernel build failures (LP: #2006695). -- Alberto Milone Mon, 20 Feb 2023 14:45:32 + ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006695 Title: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 source package in Lunar: Fix Released Bug description: [Impact] Trying to install nvidia-dkms-390 with linux 6.1 in lunar produces the following error: error: ‘struct acpi_device’ has no member named ‘children’ This is due to the kernel ABI changes in the ACPI layer (along with other dependencies on GPL-only symbols). [Test case] $ sudo apt install nvidia-dkms-390 [Fix] Support linux 6.1 ABI by disabling ACPI support with kernels >= 6.0, until nvidia releases a new driver with the proper support for 6.x kernels. [Regression potential] We may experience regressions (crashes, graphic issues or incorrect behaviors) with 6.1 kernels that are using nvidia-dkms-390. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006695/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981089] Re: Please have linux-tools-common Provide: bpftool
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Triaged => 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/1981089 Title: Please have linux-tools-common Provide: bpftool Status in bpfcc package in Ubuntu: Fix Released Status in bpftrace package in Ubuntu: New Status in lava package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Released Status in bpfcc source package in Kinetic: New Status in bpftrace source package in Kinetic: New Status in lava source package in Kinetic: New Status in linux source package in Kinetic: New Status in bpfcc source package in Lunar: Fix Released Status in bpftrace source package in Lunar: New Status in lava source package in Lunar: Triaged Status in linux source package in Lunar: Fix Released Bug description: In Debian, 'bpftool' is provided as a separate binary package. There are other packages in the archive (bpfcc, lava-dispatcher-host) which reference this package. Rather than patching each package in Ubuntu to know the different Ubuntu name for the package (linux-tools- common), we should make linux-tools-common Provides: bpftool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bpfcc/+bug/1981089/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989041] Re: Add iommu passthrough quirk for Intel IPU6 on RaptorLake
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1989041 Title: Add iommu passthrough quirk for Intel IPU6 on RaptorLake Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Intel iommu was turned on by default in mainline build v5.15.5 or jammy -generic kernel 5.15.0-12.12. This would breaks IPU6. For TGL and ADL platforms, it has been fixed in bug 1958004 for oem-5.14 and above. This patch adds a new ID for RPL. [Fix] Use IOMMU passthrough mode for IPU6 as it has its own iommu hardware. [Test Case] Apply the fix and kernel should print a new info line: Passthrough IOMMU for integrated Intel IPU and IPU6 camera should continue to work without intel_iommu=off work-around. [Where problems could occur] No. That's what it should have been done. [Other Info] Nominates only oem-6.0 and unstable for we have RPL IPU6 enabled on oem-6.0 and newer. == original bug report == Per https://github.com/intel/ipu6-drivers/commit/89c6b99e4bec00a04b53f37cd8c3c01ce824a4ab, an additional quirk is necessary for Intel IPU6 on Raptor Lake as previous TGL/ADL do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Invalid => 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993148] Re: Support Icicle Kit reference design v2022.10
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Invalid => 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/1993148 Title: Support Icicle Kit reference design v2022.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * The Michochip PolarFire SoC on the Icicle Kit is an FPGA with 4 + 1 RISC-V cores. So the memory map and some peripherals depend on the FPGA design loaded. * Microchip releases reference designs and are upstreaming support for running Linux on it. Unfortunately the upcoming v2022.10 release changes the memory layout compared to earlier versions, but v6.1-rc1 contains patches for it. * We'd like to support the v2022.10 release and hopefully future versions by backporting these changes. [ Test Plan ] * Update the Icicle Kit to the v2022.10 reference design and check that the generic riscv64 kernel boots. [ Where problems could occur ] * Users who are running v2022.9 or older versions of the reference design may have trouble booting, but the Icicle Kit was never officially supported by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993148/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994078] Re: Kinetic update: v5.19.15 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16
---
linux (6.1.0-16.16) lunar; urgency=medium
* lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- temporarily drop broken dkms
-- Andrea Righi Fri, 24 Feb 2023 14:24:48
+0100
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1994078
Title:
Kinetic update: v5.19.15 upstream stable release
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.19.15 upstream stable release
from git://git.kernel.org/
sparc: Unbreak the build
Makefile.extrawarn: Move -Wcast-function-type-strict to W=1
UBUNTU: [Config] updateconfigs for CC_HAS_AUTO_VAR_INIT_ZERO_ENABLER
hardening: Remove Clang's enable flag for -ftrivial-auto-var-init=zero
docs: update mediator information in CoC docs
xsk: Inherit need_wakeup flag for shared sockets
firmware: arm_scmi: Improve checks in the info_get operations
firmware: arm_scmi: Harden accesses to the sensor domains
firmware: arm_scmi: Add SCMI PM driver remove routine
arm64: dts: rockchip: fix upper usb port on BPI-R2-Pro
dmaengine: xilinx_dma: Fix devm_platform_ioremap_resource error handling
dmaengine: xilinx_dma: cleanup for fetching xlnx,num-fstores property
dmaengine: xilinx_dma: Report error in case of dma_set_mask_and_coherent API
failure
wifi: iwlwifi: don't spam logs with NSS>2 messages
ARM: dts: fix Moxa SDIO 'compatible', remove 'sdhci' misnomer
drm/amdgpu/mes: zero the sdma_hqd_mask of 2nd SDMA engine for SDMA 6.0.1
scsi: qedf: Fix a UAF bug in __qedf_probe()
net/ieee802154: fix uninit value bug in dgram_sendmsg
net: marvell: prestera: add support for for Aldrin2
ALSA: hda/hdmi: Fix the converter reuse for the silent stream
um: Cleanup syscall_handler_t cast in syscalls_32.h
um: Cleanup compiler warning in arch/x86/um/tls_32.c
gpio: ftgpio010: Make irqchip immutable
arch: um: Mark the stack non-executable to fix a binutils warning
net: atlantic: fix potential memory leak in aq_ndev_close()
KVM: s390: Pass initialized arg even if unused
drm/amd/display: Fix double cursor on non-video RGB MPO
drm/amd/display: Assume an LTTPR is always present on fixed_vs links
drm/amd/display: update gamut remap if plane has changed
drm/amd/display: skip audio setup when audio stream is enabled
drm/amd/display: Fix DP MST timeslot issue when fallback happened
drm/amd/display: increase dcn315 pstate change latency
perf/x86/intel: Fix unchecked MSR access error for Alder Lake N
don't use __kernel_write() on kmap_local_page()
i2c: davinci: fix PM disable depth imbalance in davinci_i2c_probe
usb: mon: make mmapped memory read only
USB: serial: ftdi_sio: fix 300 bps rate for SIO
gpiolib: acpi: Add support to ignore programming an interrupt
gpiolib: acpi: Add a quirk for Asus UM325UAZ
mmc: core: Replace with already defined values for readability
mmc: core: Terminate infinite loop in SD-UHS voltage switch
rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
bpf: Gate dynptr API behind CAP_BPF
net: ethernet: mtk_eth_soc: fix state in __mtk_foe_entry_clear
bpf: Fix resetting logic for unreferenced kptrs
Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
Revert "clk: ti: Stop using legacy clkctrl names for omap4 and 5"
Linux 5.19.15
UBUNTU: Upstream stable to v5.19.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994078/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994179] Re: Kinetic update: v5.19.17 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994179 Title: Kinetic update: v5.19.17 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.19.17 upstream stable release from git://git.kernel.org/ Revert "fs: check FMODE_LSEEK to control internal pipe splicing" ALSA: oss: Fix potential deadlock at unregistration ALSA: rawmidi: Drop register_mutex in snd_rawmidi_free() ALSA: usb-audio: Fix potential memory leaks ALSA: usb-audio: Fix NULL dererence at error path ALSA: hda/realtek: remove ALC289_FIXUP_DUAL_SPK for Dell 5530 ALSA: hda/realtek: Correct pin configs for ASUS G533Z ALSA: hda/realtek: Add quirk for ASUS GV601R laptop ALSA: hda/realtek: Add Intel Reference SSID to support headset keys mtd: rawnand: atmel: Unmap streaming DMA mappings io_uring/rw: fix unexpected link breakage io_uring/net: fix fast_iov assignment in io_setup_async_msg() io_uring/net: don't update msg_name if not provided io_uring: correct pinned_vm accounting hv_netvsc: Fix race between VF offering and VF association message from host cifs: destage dirty pages before re-reading them for cache=none cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message iio: dac: ad5593r: Fix i2c read protocol requirements iio: ltc2497: Fix reading conversion results iio: adc: ad7923: fix channel readings for some variants iio: pressure: dps310: Refactor startup procedure iio: pressure: dps310: Reset chip after timeout xhci: dbc: Fix memory leak in xhci_alloc_dbc() usb: gadget: uvc: Fix argument to sizeof() in uvc_register_video() usb: add quirks for Lenovo OneLink+ Dock mmc: core: Add SD card quirk for broken discard can: kvaser_usb: Fix use of uninitialized completion can: kvaser_usb_leaf: Fix overread with an invalid command can: kvaser_usb_leaf: Fix TX queue out of sync after restart can: kvaser_usb_leaf: Fix CAN state after restart mmc: renesas_sdhi: Fix rounding errors mmc: sdhci-tegra: Use actual clock rate for SW tuning correction mmc: sdhci-sprd: Fix minimum clock limit i2c: designware: Fix handling of real but unexpected device interrupts fs: dlm: fix race between test_bit() and queue_work() fs: dlm: handle -EBUSY first in lock arg validation fs: dlm: fix invalid derefence of sb_lvbptr btf: Export bpf_dynptr definition HID: multitouch: Add memory barriers quota: Check next/prev free block number after reading from quota file platform/chrome: cros_ec_proto: Update version on GET_NEXT_EVENT failure arm64: dts: qcom: sdm845-mtp: correct ADC settle time ASoC: wcd9335: fix order of Slimbus unprepare/disable ASoC: wcd934x: fix order of Slimbus unprepare/disable hwmon: (gsc-hwmon) Call of_node_get() before of_find_xxx API net: thunderbolt: Enable DMA paths only after rings are enabled regulator: qcom_rpm: Fix circular deferral regression arm64: topology: move store_cpu_topology() to shared code riscv: topology: fix default topology reporting RISC-V: Re-enable counter access from userspace RISC-V: Make port I/O string accessors actually work parisc: fbdev/stifb: Align graphics memory size to 4MB parisc: Fix userspace graphics card breakage due to pgtable special bit riscv: vdso: fix NULL deference in vdso_join_timens() when vfork riscv: Make VM_WRITE imply VM_READ riscv: always honor the CONFIG_CMDLINE_FORCE when parsing dtb riscv: Pass -mno-relax only on lld < 15.0.0 UM: cpuinfo: Fix a warning for CONFIG_CPUMASK_OFFSTACK nvmem: core: Fix memleak in nvmem_register() nvme-multipath: fix possible hang in live ns resize with ANA access dmaengine: mxs: use platform_driver_register dmaengine: qcom-adm: fix wrong sizeof config in slave_config dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg drm/virtio: Check whether transferred 2D BO is shmem drm/virtio: Unlock reservations on virtio_gpu_object_shmem_init() error drm/virtio:
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996112 Title: Virtual GPU driver packaging regression Status in linux package in Ubuntu: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Several virtual machine GPU drivers were moved from linux-modules- extra to linux-modules in bug #1960633 so that users running virtualized Linux would not need to install the drivers for real hardware in linux-modules-extra. linux-modules-5.19.0-23-generic in Kinetic (22.10) does not have these drivers, but linux-modules-extra-5.19.0-23-generic does. This is a regression. Impact: When I upgraded from 22.04 to 22.10, my VMWare instance was limited to sub-HD resolutions until I installed linux-modules- extra-5.19.0-23-generic. A previous kernel (5.15) had the modules in linux-modules: $ dpkg -L linux-modules-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.15.0-52-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko $ dpkg -L linux-modules-extra-5.15.0-52-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ The current kernel (5.19) has the modules in linux-modules-extra: $ dpkg -L linux-modules-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' $ $ dpkg -L linux-modules-extra-5.19.0-23-generic | grep -E 'drivers/gpu/drm/(vmwgfx|xen|virtio).*\.ko' /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/virtio/virtio-gpu.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/vmwgfx/vmwgfx.ko /lib/modules/5.19.0-23-generic/kernel/drivers/gpu/drm/xen/drm_xen_front.ko --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ccherlin 2582 F wireplumber /dev/snd/seq:ccherlin 2580 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2021-01-05 (675 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=24bdcc30-04b8-446e-93e6-b23683ad4034 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet zswap.enabled=1 zswap.compressor=lz4 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware N/A RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-11-09 (1 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias:
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997686] Re: Enable Intel FM350 wwan CCCI driver port logging
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1997686 Title: Enable Intel FM350 wwan CCCI driver port logging Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missed Modem Logging support. [Fix] Two upstream commits currently in linux-next for maybe v6.2. [Test Case] With corresponding libmbim fix in https://gitlab.freedesktop.org/mobile-broadband/libmbim/-/merge_requests/161, $ mbimcli -d query-trace-config [Where problems could occur] This adds an logging channel that is only compiled when WWAN_DEBUGFS is on, and takes a specific command to enable logging. Should be no harm in general, and might have side-effects when turned on. [Other Info] This is not yet available in mainline kernel but in linux-next, so Unstable, Lunar and OEM-6.0 are all nominated for fix. == original bug report == To enable CCCI driver Modem Logging (MDL) Port for debugging purposes: https://patchwork.kernel.org/project/netdevbpf/patch/20221028153534.1789295-1-m.chetan.ku...@linux.intel.com/ [patchwork.kernel.org] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993665] Re: Update the 470-server NVIDIA driver
This bug was fixed in the package nvidia-graphics-drivers-470-server - 470.161.03-0ubuntu1 --- nvidia-graphics-drivers-470-server (470.161.03-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #1997087). -- Alberto Milone Wed, 23 Nov 2022 16:03:44 + ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: In Progress Status in libnvidia-nscq-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: Fix Released Status in libnvidia-nscq-470 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Kinetic: Fix Released Bug description: [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] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998727] Re: Fix System cannot detect bluetooth after running suspend stress test
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998727 Title: Fix System cannot detect bluetooth after running suspend stress test Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] System cannot detect bluetooth after running power-management/suspend-30-cycles-with-reboots [Fix] Enable BT recovery on Realtek 8852CE FW, FW would detect and recover. [Test Case] 1. checkbox-cli run com.canonical.certification::power-management/suspend_30_cycles_with_reboots 2. check settings > bluetooth [Where problems could occur] just enable a function from kernel and run the code in the fw. the main risk would be related to FW. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997944] Re: Soundwire support for the Intel RPL Gen platforms
This bug was fixed in the package linux - 6.1.0-16.16
---
linux (6.1.0-16.16) lunar; urgency=medium
* lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- temporarily drop broken dkms
-- Andrea Righi Fri, 24 Feb 2023 14:24:48
+0100
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1997944
Title:
Soundwire support for the Intel RPL Gen platforms
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Released
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in firmware-sof source package in Lunar:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justfication]
[Impact]
Need soundwire support for the Intel RPL Gen platforms, specifically
0C10/0C4F/0C11. 0C40 added due to dependency.
[Fix]
Fixes from linux-next for v6.2, as well as those for firmware-sof and
alsa-ucm-conf.
[Test Case]
All the fixes are currently packaged in experimental kernel/firmware
PPAs. Install the latest ones and check audio functions.
[Where problems could occur]
Most of the patches add model information only, and they'd only take
effect on platforms with the corresponding hardware pieces.
[Other Info]
Nominated for Unstable/Lunar and OEM-6.0.
== original bug report ==
Include the support for Soundwire of RPL Gen platforms
Related components/fixes:
* kernel:
* b07908ab26ce ALSA: hda: intel-dsp-config: Add RaptorLake PCI IDs
* d608bc44181c ASoC: Intel: sof_sdw: Add support for SKU 0C10 product
* 55fc03445e2c ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration
* 880bf4b47fc1 ASoC: Intel: sof_sdw: Add support for SKU 0C40 product
* 97b5fbf44c00 ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration
* a9248c868c39 ASoC: Intel: sof_sdw: Add support for SKU 0C4F product
* 6ad73a2b42ea ASoC: rt1318: Add RT1318 SDCA vendor-specific driver
* 8c4b3a8ea2c0 ASoC: intel: sof_sdw: add rt1318 codec support.
* d84e10da17e7 ASoC: Intel: sof_sdw: Add support for SKU 0C11 product
* 0050e3d3d43d ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration
* SOF Audio firmware and topology support for Intel RPL Mobiles
* https://github.com/thesofproject/sof/releases/tag/v2.2.3
* https://github.com/thesofproject/sof-bin/pull/108
* https://github.com/alsa-project/alsa-ucm-conf
* c82c400fb653 ucm2: sof-soundwire: add basic settings for RT1318 SDCA
device
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1337 F pulseaudio
/dev/snd/pcmC0D4c: ubuntu 1337 F...m pulseaudio
/dev/snd/pcmC0D2p: ubuntu 1337 F...m pulseaudio
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-torchic+X72
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-25 (25 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
MachineType: Dell Inc. Precision 5480
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-9009-oem
root=UUID=58df5e81-0c25-471c-ace5-4decd3bcf449 ro automatic-oem-config quiet
splash
ProcVersionSignature: Ubuntu 6.0.0-9009.9+exp.25-oem 6.0.10
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-9009-oem N/A
linux-backports-modules-6.0.0-9009-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy apport-hook-error
Uname: Linux 6.0.0-9009-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 11/01/2022
dmi.bios.release: 88.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 88.3.29
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: RUNNING
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
[Kernel-packages] [Bug 1998882] Re: Mute/mic LEDs no function on a HP platfrom
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998882 Title: Mute/mic LEDs no function on a HP platfrom Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on HP ProBook Notebook PC [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] Apply this patch on OEM-6.0, and after applying the quirk, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998905] Re: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic)
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1998905 Title: Rear Audio port sometimes has no audio output after reboot(Cirrus Logic) Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] On the development, we found sometimes there is no audio output device when headphone is connected to the rear audio jack. [Fix] Cirrus Logic provides a patch to fix this https://patchwork.kernel.org/project/alsa-devel/patch/20221205145713.23852-1-vita...@opensource.cirrus.com/ The patch is included in v6.2-rc1 9fb9fa18fb50 ALSA: hda/cirrus: Add extra 10 ms delay to allow PLL settle and lock. [Test] Verified by our QA and ODM. [Where problems could occur] It extends the delay time, should be no harm for existing platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998905/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998885] Re: Add additional Mediatek MT7922 BT device ID
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1998885 Title: Add additional Mediatek MT7922 BT device ID Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] A Mediatek MT7922 Bluetooth doesn't work out of box. [Fix] One ID for Foxconn / Hon Hai was included in upstream, add the ID to support this BT device. [Test Case] Apply this patch on OEM-6.0 and bring up MT7922 Bluetooth. Check BD address from output of `hciconfig`. [Where problems could occur] This brings up new devices that wasn't working. After being up and running, we may face some other runtime issue, e.g. power consumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1998885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999528 Title: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [SRU Justification] == Impact == Since we split the lowlatency kernel into its own source package the check in the regression test suite is missing a case and will not run, even though the kernel can be booted in a VM instance. == Fix == Add the missing case to the test script which is used by ADT testing. The test scripts are inherited from the primary/distro kernel. The fix should be made there instead of changing the lowlatency tree. == Test == Inspecting the ADT logs we should start to see tests executed instead of: autopkgtest [19:22:21]: test ubuntu-regression-suite: [- ubuntu-regression-suite is pointless, if one cannot boot the kernel == Regression Potential == There are a couple of flaky tests which will start to show up, rather than only successful runs (which should have been a suspicious thing). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999556] Re: commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in kinetic master to remove "hio" reference from Makefile
This bug was fixed in the package linux - 6.1.0-16.16
---
linux (6.1.0-16.16) lunar; urgency=medium
* lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- temporarily drop broken dkms
-- Andrea Righi Fri, 24 Feb 2023 14:24:48
+0100
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999556
Title:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7 seems to be missing in
kinetic master to remove "hio" reference from Makefile
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
Added Linux kernel remote branch for Kinetic raspi to test with 22.04
install (both master and master-next branches). When running "make
clean" noticed error referencing "hio" driver that's been removed from
Jammy kernels:
$ make clean
scripts/Makefile.clean:15: ubuntu/hio/Makefile: No such file or directory
make[2]: *** No rule to make target 'ubuntu/hio/Makefile'. Stop.
make[1]: *** [scripts/Makefile.clean:62: ubuntu/hio] Error 2
make: *** [Makefile:1858: _clean_ubuntu] Error 2
Found that commit cf58599cded35cf4affed1e659c0e2c742d3fda7 missing:
commit cf58599cded35cf4affed1e659c0e2c742d3fda7
Author: Thomas Lamprecht
Date: Sat Mar 12 16:19:10 2022 +0100
Ubuntu: remove leftover reference to ubuntu/hio driver
A single reference to the hio driver was forgotten when it was removed
recently. While this reference is not a problem for the build itself, it
breaks the __clean target from 'scripts/Makefile.clean' here, as make
cannot enter the "ubuntu/hio" folder for cleaning due to ENOENT.
Fixes: 4ea6dd9afa0a0d ("UBUNTU: Remove ubuntu/hio driver")
Signed-off-by: Thomas Lamprecht
Acked-by: Tim Gardner
Signed-off-by: Paolo Pisati
Here's some additional information for code repositories (didn't know
if this was helpful),
remote.kinetic-raspi.url=https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/kinetic
remote.kinetic-raspi.fetch=+refs/heads/*:refs/remotes/kinetic-raspi/*
branch.kinetic-master-next.remote=kinetic-raspi
branch.kinetic-master-next.merge=refs/heads/master-next
branch.kinetic-master.remote=kinetic-raspi
branch.kinetic-master.merge=refs/heads/master
[Test Case]
See above.
[Fix]
Pick commit cf58599cded35cf4affed1e659c0e2c742d3fda7 from jammy.
[Where Problems Could Occur]
Build failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999556/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003524] Re: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2003524 Title: amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] From "Mario Limonciello mario.limonciello at amd.com" https://lists.ubuntu.com/archives/kernel-team/2023-January/136434.html. There is a problem in amdgpu that if not all of IP blocks are supported or not all of the firmware is present then the framebuffer is destroyed and the screen freezes. In more recent kernels the amdgpu driver loads for all PCI VGA class AMD devices. This effectively means that unless you have all the pieces you need to support a GPU then the installer freezes unless you do nomodeset. This problem is to be fully fixed in kernel 6.3 with a ~47 patch series that is currently in drm-next. This does two basic things: 1) If the IP blocks isn't supported, don't destroy the framebuffer. 2) If firmware for any IP blocks aren't present, don't destroy the framebuffer. The whole patch series still needs more time to back in drm-next, but the most important part of the series is the first patch which accomplishes "1". This patch went out to stable 6.1.y as well: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.1.y=dcfeba477b3e3df526e0f543b58fa71c045dff8b My reasoning is that it will ensure that if someone picks up a newer GPU such as Ryzen 7000 desktop or RDNA3 based they can at least install Ubuntu without needing to use "Safe Graphics Mode" at the installer. Sure; they won't have hardware acceleration without the rest of the kernel and framework, but that's a separate problem to a basic display. [Fix] Cherry-pick/backport commit 1923bc5a56daeeabd7e9093bad2febcd6af2416a "drm/amd: Delay removal of the firmware framebuffer" to Ubuntu Kinetic 5.19 kernel. [Test case] Boot kernel in a system with one of the amdgpu affected adapters. [Where problems can occur] The aforementioned commit could introduce other regressions on the support for AMD GPUs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999750] Re: Set explicit CC in the headers package
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1999750 Title: Set explicit CC in the headers package Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.19 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-hwe-5.19 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-hwe-5.19 source package in Lunar: Invalid Bug description: [ Impact ] * Currently Ubuntu Linux kernel header packages use stock Makefile as shipped by upstream kernel. During linux kernel package build however HOSTCC and CC are typically overridden to use explicit complier version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module build failures as despite all efforts to reuse matching gcc version out of .config, various shell scripts / build systems / makefiles do not pass the CC variable as a make variable to the end make call that is used to build dkms modules. To avoid this, hardcode the correct compiler in the linux headers package shipped Makefile. This is similar to the Makefile includes that debian ships, albeit with less indirections. [ Test Plan ] * adt-matrix for dkms modules should start to pass correctly [ Where problems could occur ] * headers package for hwe kernels may demand a newer compiler, for which runtime dependency does not exist. dkms package in jammy-updates already has explicit dependency on gcc-12 for that reason. Installing build-deps of the kernel package will install correct/required compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000667] Re: cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from ubuntu_kernel_selftests hang with non-amd64
This bug was fixed in the package linux - 6.1.0-16.16
---
linux (6.1.0-16.16) lunar; urgency=medium
* lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- temporarily drop broken dkms
-- Andrea Righi Fri, 24 Feb 2023 14:24:48
+0100
** Changed in: linux (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2000667
Title:
cmsg_so_mark.sh / cmsg_time.sh / cmsg_ipv6.sh in net from
ubuntu_kernel_selftests hang with non-amd64
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux source package in Lunar:
Fix Released
Bug description:
[Impact]
cmsg_* tests in net tests from ubuntu_kernel_selftests will hang on
non-amd64 systems and eventually causing "Incomplete" test results on
RISCV kernels due to the timeout setting.
This is because of an infinity while loop caused by a char variable
used here to take the getopt() return value in cmsg_sender.c, it should
be an int instead.
[Fix]
* 1573c68820 ("selftests: net: fix cmsg_so_mark.sh test hang")
This patch can be cherry-picked into both Kinetic and Lunar, these test
cases are only available in these newer kernels.
[Test]
Compile the patched cmsg_sender.c on a non-amd64 system, and the cmsg_*
tests will no longer hanging.
[Where problems could occur ]
Change limited to testing tools, no actual impact to real functions.
[Original Bug Report]
Issue found with 5.19.0-1010.11, 5.19.0-1011.12
This issue does not exist in 5.19.0-1009.10 because the net test can't
be built by that time.
Test output:
Running 'make run_tests -C net TEST_PROGS=cmsg_so_mark.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net'
make --no-builtin-rules ARCH=riscv -C ../../../.. headers_install
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
INSTALL ./usr/include
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
TAP version 13
1..1
# selftests: net: cmsg_so_mark.sh
Timer expired (5400 sec.), nuking pid 82951
A manual test shows it will stuck with:
$ sudo ./cmsg_so_mark.sh
+ NS=ns
+ IP4=172.16.0.1/24
+ TGT4=172.16.0.2
+ IP6=2001:db8:1::1/64
+ TGT6=2001:db8:1::2
+ MARK=1000
+ trap cleanup EXIT
+ ip netns add ns
+ ip netns exec ns sysctl -w 'net.ipv4.ping_group_range=0 2147483647'
+ ip -netns ns link add type dummy
+ ip -netns ns link set dev dummy0 up
+ ip -netns ns addr add 172.16.0.1/24 dev dummy0
+ ip -netns ns addr add 2001:db8:1::1/64 dev dummy0
+ ip -netns ns rule add fwmark 1000 lookup 300
+ ip -6 -netns ns rule add fwmark 1000 lookup 300
+ ip -netns ns route add prohibit any table 300
+ ip -6 -netns ns route add prohibit any table 300
+ BAD=0
+ TOTAL=0
+ for ovr in setsock cmsg both
+ for i in 4 6
+ '[' 4 == 4 ']'
+ TGT=172.16.0.2
+ for p in u i r
+ '[' u == u ']'
+ prot=UDP
+ '[' u == i ']'
+ '[' u == r ']'
+ '[' setsock == setsock ']'
+ m=-M
+ '[' setsock == cmsg ']'
+ '[' setsock == both ']'
+ ip netns exec ns ./cmsg_sender -4 -p u -M 1001 172.16.0.2 1234
(test stuck here)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000667/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000706] Re: Lunar update: v6.1.1 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2000706 Title: Lunar update: v6.1.1 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.1 upstream stable release from git://git.kernel.org/ x86/vdso: Conditionally export __vdso_sgx_enter_enclave() libbpf: Fix uninitialized warning in btf_dump_dump_type_data PCI: mt7621: Add sentinel to quirks table mips: ralink: mt7621: define MT7621_SYSC_BASE with __iomem mips: ralink: mt7621: soc queries and tests as functions mips: ralink: mt7621: do not use kzalloc too early irqchip/ls-extirq: Fix endianness detection udf: Discard preallocation before extending file with a hole udf: Fix preallocation discarding at indirect extent boundary udf: Do not bother looking for prealloc extents if i_lenExtents matches i_size udf: Fix extending file within last block usb: gadget: uvc: Prevent buffer overflow in setup handler USB: serial: option: add Quectel EM05-G modem USB: serial: cp210x: add Kamstrup RF sniffer PIDs USB: serial: f81232: fix division by zero on line-speed change USB: serial: f81534: fix division by zero on line-speed change xhci: Apply XHCI_RESET_TO_DEFAULT quirk to ADL-N staging: r8188eu: fix led register settings igb: Initialize mailbox message for VF reset usb: typec: ucsi: Resume in separate work usb: dwc3: pci: Update PCIe device ID for USB3 controller on CPU sub-system for Raptor Lake cifs: fix oops during encryption KEYS: encrypted: fix key instantiation with user-provided data Linux 6.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000706/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002079] Re: Lunar update: v6.1.2 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002079 Title: Lunar update: v6.1.2 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.2 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu) Status: Triaged => 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/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003686] Re: Lunar update: v6.1.3 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003686 Title: Lunar update: v6.1.3 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.3 upstream stable release from git://git.kernel.org/ Linux 6.1.3 kcsan: Instrument memcpy/memset/memmove with newer Clang SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak tpm: tpm_crb: Add the missed acpi_put_table() to fix memory leak tpm: acpi: Call acpi_put_table() to fix memory leak mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING block: Do not reread partition table on exclusively open device f2fs: allow to read node block after shutdown f2fs: should put a page when checking the summary info mm, compaction: fix fast_isolate_around() to stay within boundaries md: fix a crash in mempool_free mfd: mt6360: Add bounds checking in Regmap read/write call-backs pnode: terminate at peers of source ALSA: hda/hdmi: Static PCM mapping again with AMD HDMI codecs ALSA: line6: fix stack overflow in line6_midi_transmit ALSA: line6: correct midi status byte when receiving data from podxt ovl: update ->f_iocb_flags when ovl_change_flags() modifies ->f_flags ovl: Use ovl mounter's fsuid and fsgid in ovl_link() binfmt: Fix error return code in load_elf_fdpic_binary() ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+ ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865 hfsplus: fix bug causing custom uid and gid being unable to be assigned with mount pstore/zone: Use GFP_ATOMIC to allocate zone buffer pstore: Properly assign mem_type property kmsan: include linux/vmalloc.h kmsan: export kmsan_handle_urb mm/mempolicy: fix memory leak in set_mempolicy_home_node system call mm, mremap: fix mremap() expanding vma with addr inside vma rtmutex: Add acquire semantics for rtmutex lock acquisition slow path futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error HID: plantronics: Additional PIDs for double volume key presses quirk HID: multitouch: fix Asus ExpertBook P2 P2451FA trackpoint kprobes: kretprobe events missing on 2-core KVM guest NFSD: fix use-after-free in __nfs42_ssc_open() rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe() powerpc/rtas: avoid scheduling in rtas_os_term() powerpc/rtas: avoid device tree lookups in rtas_os_term() iommu/mediatek: Fix crash on isr after kexec() objtool: Fix SEGFAULT fs/ntfs3: Fix slab-out-of-bounds in r_page fs/ntfs3: Delete duplicate condition in ntfs_read_mft() fs/ntfs3: Use __GFP_NOWARN allocation at ntfs_fill_super() fs/ntfs3: Use __GFP_NOWARN allocation at wnd_init() fs/ntfs3: Validate index root when initialize NTFS security phy: sun4i-usb: Add support for the H616 USB PHY phy: sun4i-usb: Introduce port2 SIDDQ quirk soundwire: dmi-quirks: add quirk variant for LAPBC710 NUC15 fs/ntfs3: Fix slab-out-of-bounds read in run_unpack fs/ntfs3: Validate resident attribute name fs/ntfs3: Validate buffer length while parsing index fs/ntfs3: Validate attribute name offset fs/ntfs3: Add null pointer check for inode operations fs/ntfs3: Fix memory leak on ntfs_fill_super() error path fs/ntfs3: Add null pointer check to attr_load_runs_vcn fs/ntfs3: Validate data run offset fs/ntfs3: Add overflow check for attribute size fs/ntfs3: Validate BOOT record_size nvmet: don't defer passthrough commands with trivial effects to the workqueue nvme: fix the NVME_CMD_EFFECTS_CSE_MASK definition ata: ahci: Fix PCS quirk application for suspend block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq ACPI: video: Fix Apple GMUX backlight detection ACPI: resource: Add Asus ExpertBook B2502 to Asus quirks ACPI: resource: do IRQ override on Lenovo 14ALC7 ACPI: resource: do IRQ override on XMG Core 15
[Kernel-packages] [Bug 2003687] Re: Lunar update: v6.1.4 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003687 Title: Lunar update: v6.1.4 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.4 upstream stable release from git://git.kernel.org/ Linux 6.1.4 drm/amd/pm: correct the fan speed retrieving in PWM for some SMU13 asics drm/amd/pm: bump SMU13.0.0 driver_if header to version 0x34 drm/amd/pm: add missing SMU13.0.7 mm_dpm feature mapping drm/amd/pm: add missing SMU13.0.0 mm_dpm feature mapping drm/i915/migrate: Account for the reserved_space drm/i915: improve the catch-all evict to handle lock contention drm/amdgpu: make display pinning more flexible (v2) drm/amdgpu: handle polaris10/11 overlap asics (v2) drm/amd/display: Add DCN314 display SG Support drm/i915/ttm: consider CCS for backup objects ext4: allocate extended attribute value in vmalloc area ext4: avoid unaccounted block allocation when expanding inode ext4: initialize quota before expanding inode in setproject ioctl ext4: fix inode leak in ext4_xattr_inode_create() on an error path ext4: fix kernel BUG in 'ext4_write_inline_data_end()' ext4: fix deadlock due to mbcache entry corruption ext4: avoid BUG_ON when creating xattrs ext4: fix corrupt backup group descriptors after online resize ext4: dont return EINVAL from GETFSUUID when reporting UUID length ext4: fix bad checksum after online resize ext4: fix error code return to user-space in ext4_get_branch() ext4: fix corruption when online resizing a 1K bigalloc fs ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline ext4: don't fail GETFSUUID when the caller provides a long buffer ext4: init quota for 'old.inode' in 'ext4_rename' ext4: fix uninititialized value in 'ext4_evict_inode' ext4: fix off-by-one errors in fast-commit block filling ext4: fix unaligned memory access in ext4_fc_reserve_space() ext4: add missing validation of fast-commit record lengths ext4: don't set up encryption key during jbd2 transaction ext4: fix leaking uninitialized memory in fast-commit journal ext4: disable fast-commit of encrypted dir operations ext4: don't allow journal inode to have encrypt flag ext4: fix bug_on in __es_tree_search caused by bad boot loader inode ext4: check and assert if marking an no_delete evicting inode dirty ext4: journal_path mount options should follow links ext4: fix reserved cluster accounting in __es_remove_extent() ext4: fix bug_on in __es_tree_search caused by bad quota inode ext4: add helper to check quota inums ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode ext4: fix undefined behavior in bit shift for ext4_check_flag_values ext4: fix use-after-free in ext4_orphan_cleanup fs: ext4: initialize fsdata in pagecache_write() ext4: correct inconsistent error msg in nojournal mode ext4: remove trailing newline from ext4_msg() message ext4: add inode table check in __ext4_get_inode_loc to aovid possible infinite loop ext4: silence the warning when evicting inode with dioread_nolock drm/etnaviv: reap idle mapping if it doesn't match the softpin address drm/ingenic: Fix missing platform_driver_unregister() call in ingenic_drm_init() drm/i915/dsi: fix VBT send packet port selection for dual link DSI drm/etnaviv: move idle mapping reaping into separate function drm/mgag200: Fix PLL setup for G200_SE_A rev >=4 drm/vmwgfx: Validate the box size for the snooped cursor drm/connector: send hotplug uevent on connector cleanup device_cgroup: Roll back to original exceptions after copy failure parisc: Drop PMD_SHIFT from calculation in pgtable.h parisc: Drop duplicate kgdb_pdc console parisc: Add missing FORCE prerequisites in Makefile parisc: Fix locking in pdc_iodc_print() firmware call parisc: Drop locking in pdc console code parisc: led: Fix potential null-ptr-deref in start_task()
[Kernel-packages] [Bug 2003688] Re: Lunar update: v6.1.5 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003688 Title: Lunar update: v6.1.5 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.5 upstream stable release from git://git.kernel.org/ Linux 6.1.5 wifi: ath11k: Send PME message during wakeup from D3cold efi: random: combine bootloader provided RNG seed with RNG protocol output drm/i915/dsi: fix MIPI_BKLT_EN_1 native GPIO index drm/i915/dsi: add support for ICL+ native MIPI GPIO sequence ksmbd: check nt_len to be at least CIFS_ENCPWD_SIZE in ksmbd_decode_ntlmssp_auth_blob ksmbd: send proper error response in smb2_tree_connect() ksmbd: fix infinite loop in ksmbd_conn_handler_loop() btrfs: handle case when repair happens with dev-replace drm/amd/display: Uninitialized variables causing 4k60 UCLK to stay at DPM1 and not DPM0 drm/amd/display: Add check for DET fetch latency hiding for dcn32 virtio_blk: Fix signedness bug in virtblk_prep_rq() virtio-blk: use a helper to handle request queuing errors drm/i915/gvt: fix vgpu debugfs clean in remove drm/i915/gvt: fix gvt debugfs destroy drm/amdkfd: Fix kernel warning during topology setup drm/plane-helper: Add the missing declaration of drm_atomic_state of/fdt: run soc memory setup when early_init_dt_scan_memory fails riscv, kprobes: Stricter c.jr/c.jalr decoding riscv: uaccess: fix type of 0 variable on error in get_user() thermal: int340x: Add missing attribute for data rate base vhost_vdpa: fix the crash in unmap a large memory tpm: Allow system suspend to continue when TPM suspend fails io_uring: fix CQ waiting timeout handling io_uring: pin context while queueing deferred tw block: don't allow splitting of a REQ_NOWAIT bio net: dsa: tag_qca: fix wrong MGMT_DATA2 size net: dsa: qca8k: fix wrong length value for mgmt eth packet Revert "net: dsa: qca8k: cache lo and hi for mdio write" Revert "drm/amd/display: Enable Freesync Video Mode by default" bpf: Fix panic due to wrong pageattr of im->image fbdev: matroxfb: G200eW: Increase max memory from 1 MB to 16 MB nfsd: fix handling of readdir in v4root vs. mount upcall timeout x86/bugs: Flush IBP in ib_prctl_set() x86/kexec: Fix double-free of elf header buffer ASoC: SOF: Intel: pci-tgl: unblock S5 entry if DMA stop has failed" nvme: also return I/O command effects from nvme_command_effects nvmet: use NVME_CMD_EFFECTS_CSUPP instead of open coding it kunit: alloc_string_stream_fragment error handling bug fix io_uring: check for valid register opcode earlier ACPI: video: Don't enable fallback path for creating ACPI backlight by default drm/amd/display: Report to ACPI video if no panels were found ACPI: video: Allow GPU drivers to report no panels nvme: fix multipath crash caused by flush request when blktrace is enabled io_uring/cancel: re-grab ctx mutex after finishing wait drm/amdkfd: Fix double release compute pasid drm/amdkfd: Fix kfd_process_device_init_vm error handling drm/amdgpu: Fix size validation for non-exclusive domains (v4) ASoC: SOF: mediatek: initialize panic_info to zero ASoC: Intel: bytcr_rt5640: Add quirk for the Advantech MICA-071 tablet 9p/client: fix data race on req->status ASoC: SOF: Revert: "core: unregister clients and machine drivers in .shutdown" hfs/hfsplus: avoid WARN_ON() for sanity check, use proper error handling usb: dwc3: xilinx: include linux/gpio/consumer.h udf: Fix extension of the last extent in the file caif: fix memory leak in cfctrl_linkup_request() net/ulp: prevent ULP without clone op from entering the LISTEN status qed: allow sleep in qed_mcp_trace_dump() ublk: honor IO_URING_F_NONBLOCK for handling control command drm/i915/gvt: fix double free bug in split_2MB_gtt_entry drm/i915: unpin on error in intel_vgpu_shadow_mm_pin() perf stat: Fix handling of --for-each-cgroup with --bpf-counters to match
[Kernel-packages] [Bug 2003689] Re: Lunar update: v6.1.6 upstream stable release
This bug was fixed in the package linux - 6.1.0-16.16 --- linux (6.1.0-16.16) lunar; urgency=medium * lunar/linux: 6.1.0-16.16 -proposed tracker (LP: #2008480) * Packaging resync (LP: #1786013) - debian/dkms-versions -- temporarily drop broken dkms -- Andrea Righi Fri, 24 Feb 2023 14:24:48 +0100 ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003689 Title: Lunar update: v6.1.6 upstream stable release Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.6 upstream stable release from git://git.kernel.org/ Linux 6.1.6 ALSA: hda: cs35l41: Check runtime suspend capability at runtime_idle ALSA: hda - Enable headset mic on another Dell laptop with ALC3254 ALSA: hda: cs35l41: Don't return -EINVAL from system suspend/resume ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform ALSA: hda/hdmi: Add a HP device 0x8715 to force connect list ALSA: pcm: Move rwsem lock inside snd_ctl_elem_read to prevent UAF net: sched: disallow noqueue for qdisc classes gcc: disable -Warray-bounds for gcc-11 too Revert "SUNRPC: Use RMW bitops in single-threaded hot paths" selftests/vm/pkeys: Add a regression test for setting PKRU through ptrace x86/fpu: Emulate XRSTOR's behavior if the xfeatures PKRU bit is not set x86/fpu: Allow PKRU to be (once again) written by ptrace. x86/fpu: Add a pkru argument to copy_uabi_to_xstate() x86/fpu: Add a pkru argument to copy_uabi_from_kernel_to_xstate(). x86/fpu: Take task_struct* in copy_sigframe_from_user_to_xstate() parisc: Align parisc MADV_XXX constants with all other architectures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic
This bug was fixed in the package nvidia-graphics-drivers-515-server - 515.86.01-0ubuntu2 --- nvidia-graphics-drivers-515-server (515.86.01-0ubuntu2) lunar; urgency=medium * debian/templates/control.in: - Add Conflicts, Replaces, Provides up to libcuda-11.7-1 (LP: #2003995). -- Alberto Milone Wed, 01 Feb 2023 10:36:07 + ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2003995 Title: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic Status in fabric-manager-515 package in Ubuntu: Fix Released Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-515 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: New Status in linux-restricted-modules-hwe package in Ubuntu: New Status in nvidia-graphics-drivers-515-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-525-server package in Ubuntu: Fix Released Status in fabric-manager-515 source package in Bionic: Fix Released Status in fabric-manager-525 source package in Bionic: Fix Released Status in libnvidia-nscq-515 source package in Bionic: Fix Released Status in libnvidia-nscq-525 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: New Status in linux-restricted-modules-hwe source package in Bionic: New Status in nvidia-graphics-drivers-515-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Bionic: Fix Released Status in fabric-manager-515 source package in Focal: Fix Released Status in fabric-manager-525 source package in Focal: Fix Released Status in libnvidia-nscq-515 source package in Focal: Fix Released Status in libnvidia-nscq-525 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: New Status in linux-restricted-modules-hwe source package in Focal: New Status in nvidia-graphics-drivers-515-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-525 source package in Focal: Fix Released Status in nvidia-graphics-drivers-525-server source package in Focal: Fix Released Status in fabric-manager-515 source package in Jammy: Fix Released Status in fabric-manager-525 source package in Jammy: Fix Released Status in libnvidia-nscq-515 source package in Jammy: Fix Released Status in libnvidia-nscq-525 source package in Jammy: Fix Released Status in linux-restricted-modules source package in Jammy: New Status in linux-restricted-modules-hwe source package in Jammy: New Status in nvidia-graphics-drivers-515-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-525-server source package in Jammy: Fix Released Status in fabric-manager-515 source package in Kinetic: Fix Released Status in fabric-manager-525 source package in Kinetic: Fix Released Status in libnvidia-nscq-515 source package in Kinetic: Fix Released Status in libnvidia-nscq-525 source package in Kinetic: Fix Released Status in linux-restricted-modules source package in Kinetic: New Status in linux-restricted-modules-hwe source package in Kinetic: New Status in nvidia-graphics-drivers-515-server source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Kinetic: Fix Released Bug description: [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] 525 * New upstream release (LP: #2003995): - Improved the reliability
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
Didn't see this failure with 5.4.0-145.162 ** 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
Didn't see this failure with 5.15.0-68.75 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
Didn't see this failure with 4.15.0-207.218 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009090] [NEW] usb ports and bluetooth not working
Public bug reported: USB Ports, like when using mouse device works only on reboot for a short while (in the login screen) then ultimately stops after login. Same happens to bluetooth also. I checked the logs and it says, usb device descriptor error -71. This happened after upgrading to ubuntu 22.04 Description:Ubuntu 22.04.2 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Mar 3 09:34:37 2023 InstallationDate: Installed on 2022-09-06 (177 days ago) InstallationMedia: Zorin-OS 16 Core 64bit SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-03-01 (1 days ago) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009090 Title: usb ports and bluetooth not working Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: USB Ports, like when using mouse device works only on reboot for a short while (in the login screen) then ultimately stops after login. Same happens to bluetooth also. I checked the logs and it says, usb device descriptor error -71. This happened after upgrading to ubuntu 22.04 Description: Ubuntu 22.04.2 LTS Release: 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Mar 3 09:34:37 2023 InstallationDate: Installed on 2022-09-06 (177 days ago) InstallationMedia: Zorin-OS 16 Core 64bit SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: Upgraded to jammy on 2023-03-01 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995903] Re: Can't boot with kernel 5.15.0-52
** Package changed: linux (Ubuntu) => nvidia-graphics-drivers (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/1995903 Title: Can't boot with kernel 5.15.0-52 Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: These packages are installed: linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 amd64 [installed,automatic] linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 amd64 [installed,automatic] After grub and booting, there's some text appears, and then the screen goes blank. After forcing the computer to turn off, I boot again but using 5.15.0-50, it can boot like usual. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 2015 F pulseaudio /dev/snd/controlC0: fikr4n 2015 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 8 08:57:48 2022 InstallationDate: Installed on 2021-06-05 (520 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1995903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
I can see this test failing with Focal 5.4.0-145.162, thanks! ** 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006453] Re: Fix selftests/ftracetests/Meta-selftests
ftracttest is green with 5.4.0-145.162, thanks! ** 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/2006453 Title: Fix selftests/ftracetests/Meta-selftests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [SRU Justification] == Impact == This subtest checks for bashisms in the test scripts of ftracetests. A recent stable change added such a case. This is harmless but causes the Meta-selftests to fail. The offending commit is "selftests/ftrace: event_triggers: wait longer for test_event_enable" which adds: + if [ "$e" == $val ]; then == Fix == Replace the test with + if [ "$e" = $val ]; then == Testcase == Running the kernel selftests/ftracetest (done in ADT and RT) should no longer show "Meta-selftests" as FAILed. == Regression Potential == This affects only the selftest suite and only ftrace subtests. Any change would only be observable there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946433] Re: Can only reach PC3 when ethernet is plugged r8169
** Changed in: linux (Ubuntu Kinetic) Status: In Progress => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1946433 Title: Can only reach PC3 when ethernet is plugged r8169 Status in HWE Next: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Triaged Status in linux-oem-5.13 source package in Kinetic: Invalid Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-5.13 source package in Lunar: Invalid Status in linux-oem-5.14 source package in Lunar: Invalid Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] System only can reach PC3, and it affects power consumption alot. [Fix] Kaiheng implemented a dynamic ASPM for r8169, it not only fixes the PC state issue, but also fixes network speed issue. V7: https://patchwork.kernel.org/project/netdevbpf/patch/20211016075442.650311-5-kai.heng.f...@canonical.com/ V6: https://patchwork.ozlabs.org/project/linux-pci/cover/20211007161552.272771-1-kai.heng.f...@canonical.com/ [Test] Verified on 2 different systems which has PC state issue and has network speed issue, these patches fix both issues. [Where problems could occur] It toggles ASPM on and off depends on the network traffic during runtime, I don't think it'll lead to any regressions. Some potential issues have been addressed during the patch submitting. It's v6 now and accepted by upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1946433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995903] Re: Can't boot with kernel 5.15.0-52
Btw it always happens, now it happens to kernel 5.19.0-35. -- 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/1995903 Title: Can't boot with kernel 5.15.0-52 Status in linux package in Ubuntu: Confirmed Bug description: These packages are installed: linux-image-5.15.0-50-generic/jammy-updates,jammy-security,now 5.15.0-50.56 amd64 [installed,automatic] linux-image-5.15.0-52-generic/jammy-updates,jammy-security,now 5.15.0-52.58 amd64 [installed,automatic] After grub and booting, there's some text appears, and then the screen goes blank. After forcing the computer to turn off, I boot again but using 5.15.0-50, it can boot like usual. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fikr4n 2015 F pulseaudio /dev/snd/controlC0: fikr4n 2015 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 8 08:57:48 2022 InstallationDate: Installed on 2021-06-05 (520 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HP HP ENVY Laptop 15-ep0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=34001051-5122-4187-b21f-2032a99219e8 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-28 (71 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 15.7 dmi.bios.vendor: AMI dmi.bios.version: F.07 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 878E dmi.board.vendor: HP dmi.board.version: 18.33 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 18.33 dmi.modalias: dmi:bvnAMI:bvrF.07:bd07/30/2021:br15.7:efr18.33:svnHP:pnHPENVYLaptop15-ep0xxx:pvr:rvnHP:rn878E:rvr18.33:cvnHP:ct10:cvrChassisVersion:sku16P91PA#AR6: dmi.product.family: 103C_5335KV HP ENVY dmi.product.name: HP ENVY Laptop 15-ep0xxx dmi.product.sku: 16P91PA#AR6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
Works as expected with Focal 5.4.0-145.162 ** 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/2006391 Title: net:fcnal-test.sh 'nettest' command not found on F/K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Kinetic: Fix Committed Bug description: On Focal and Kinetic the fcnal-test.sh does not run because it reports that 'nettest' command not found; skipping tests This is due to the nettest binary not being found in the path and skipping the tests, but it is built and exists in the net directory where the tests are run. There are also other tests in selftests/net that are skipped due to the binary being missing. There is a patch upstream "selftests/net: Find nettest in current directory" (bd5e1e42826f18147afb0) that fixes this by looking in the current directory. The patch is in Jammy through stable updates, but the patch hasnt made it to the other stable trees yet for whatever reasons so might as well just cherry-pick them into F/K. - [Impact] fcnal-test.sh in selftests/net gets skipped with 'nettest' command not found because its looking for the nettest binary in the path and not in the current directory where the binary is built and run from. There are also other tests in net that are skipped due to this binary not being found. [Fix] Add the current directory to the path and check again. This patch exists in Jammy through a stable update but hasn't made it to the other upstream-stable trees yet, but might as well get the patch in our other trees to enable this test to run. [Backport] For focal patch skip the pmtu.sh file as nettest is not run there and is not checked. Also minor context adjustments on return variable. [Potential regression] None. Just enabling the tests to run. [Tests] Verified tests are now not skipped and run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964916] Re: [HP Omni 120-2110il AIO] Flickering white lines on screen
Please try the workaround in comment #13. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1964916 Title: [HP Omni 120-2110il AIO] Flickering white lines on screen Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: https://www.youtube.com/watch?v=GcAXAicoZqY this is the video of my error i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04.. i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 14:59:57 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2022-03-05 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Hewlett-Packard 120-2110il ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 101 dmi.chassis.asset.tag: 4CS2040B0F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-2110il dmi.product.sku: QF135AA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
That kernel is actually older than the Ubuntu 5.19 kernels. But there's always a chance it will work around the bug by pre-dating it... Not likely in this case though since we have two duplicate bugs showing it was an issue as far back as kernel 5.11. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009085] [NEW] nvidia-libopencl1-384, nvidia-opencl-icd-384 binaries need dropping on i386
Public bug reported: The set of binaries from nvidia-graphics-drivers-390 on i386 has been reduced to: libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-encode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-fbc1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-gl-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-ifr1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 However, the *opencl*384 transitional packages are still being generated: nvidia-libopencl1-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 nvidia-opencl-icd-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 And these now become uninstallable because they depend on nvidia- headless-390 that has been dropped on i386. This is the last piece blocking us from having updated nvidia + lrm + kernels in lunar so I have manually deleted the binaries from the archive to allow it to migrate. They also need to be dropped from the source. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: High Assignee: Alberto Milone (albertomilone) Status: Triaged ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged ** Description changed: The set of binaries from nvidia-graphics-drivers-390 on i386 has been reduced to: - libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - libnvidia-encode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - libnvidia-fbc1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - libnvidia-gl-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - libnvidia-ifr1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-encode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-fbc1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-gl-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 + libnvidia-ifr1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 - However, the *opencl*384 compatibility packages are still being + However, the *opencl*384 transitional packages are still being generated: - nvidia-libopencl1-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 - nvidia-opencl-icd-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 + nvidia-libopencl1-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 + nvidia-opencl-icd-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 And these now become uninstallable because they depend on nvidia- headless-390 that has been dropped on i386. This is the last piece blocking us from having updated nvidia + lrm + kernels in lunar so I have manually deleted the binaries from the archive to allow it to migrate. They also need to be dropped from the source. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009085 Title: nvidia-libopencl1-384, nvidia-opencl-icd-384 binaries need dropping on i386 Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: The set of binaries from nvidia-graphics-drivers-390 on i386 has been reduced to: libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-encode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-fbc1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-gl-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386 libnvidia-ifr1-390| 390.157-0ubuntu3 | lunar-proposed/restricted | i386 However, the *opencl*384 transitional packages are still being generated: nvidia-libopencl1-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 nvidia-opencl-icd-384 | 390.157-0ubuntu3 | lunar-proposed/multiverse | i386 And these now become uninstallable because they depend on nvidia- headless-390 that has been dropped on i386. This is the last piece blocking us from having updated nvidia + lrm + kernels in lunar so I have manually deleted the binaries from the archive to allow it to migrate. They also need to be dropped from the source. To manage notifications about this bug go to:
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
I have created a test kernel. Please test. https://people.canonical.com/~mreed/hpe/lp_2008745_config_numa_emu/ -- 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some case, Intel's SPR-HBM needs this. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970957] Re: suspend problem
I too am experiencing this problem on my Lenovo Yoga 6. -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-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: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008269] Re: dkms prevents installing vendored-in dkms packages
This bug was fixed in the package dkms - 3.0.10-6ubuntu1 --- dkms (3.0.10-6ubuntu1) lunar; urgency=medium * Please do not forcesync any new uploads of dkms, without prior testing in Ubuntu with Ubuntu packages (i.e. bileto ADT). * Fix release regression preventing co-installing in-archive dkms packages with kernels that built-in identical or newer versions of the same dkms package. LP: #2008269 -- Dimitri John Ledkov Thu, 23 Feb 2023 15:26:12 + ** Changed in: dkms (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2008269 Title: dkms prevents installing vendored-in dkms packages Status in dkms package in Ubuntu: Fix Released Bug description: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964916] Re: [HP Omni 120-2110il AIO] Flickering white lines on screen
I also have the same issue. It is the same as described in the the original post. My screen looks exactly like the video attached above. I am running Ubuntu 22.04.1 on an HP All in One 120-1031. If I use NOMODSET the lines do not appear but the screen is too large to use. Also if I use VNC to view the desktop remotely Everything looks good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1964916 Title: [HP Omni 120-2110il AIO] Flickering white lines on screen Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: https://www.youtube.com/watch?v=GcAXAicoZqY this is the video of my error i am having this issue on all versions of ubuntu-- i have tried installing versions 20.04, 18.04.06, 12.04.. i have intel pentium g630 processor with intel graphics 2000 (Vram-256M). I used Windows 10 on my PC but i thought of switching to ubuntu when this problem arose.. The glitch shows up on ubuntu splash screen and remains there until i restart my pc with nomodeset parameter...i have reinstalled windows 10 but i want this issue to get fixed.. i need to use ubuntu ...pls ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 14:59:57 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ac5] InstallationDate: Installed on 2022-03-05 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Hewlett-Packard 120-2110il ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=54d1c05e-a544-4510-8da7-87e1a7242e0f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2011 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: LEO_707 dmi.board.name: 2AC5 dmi.board.vendor: Quanta dmi.board.version: 101 dmi.chassis.asset.tag: 4CS2040B0F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvrLEO_707:bd11/17/2011:br4.6:svnHewlett-Packard:pn120-2110il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 120-2110il dmi.product.sku: QF135AA#ACJ dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1964916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
https://lists.ubuntu.com/archives/kernel-team/2023-March/137464.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
** Patch added:
"0001-UBUNTU-SAUCE-overlayfs-handle-idmapped-mounts-in-ovl.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+attachment/5651146/+files/0001-UBUNTU-SAUCE-overlayfs-handle-idmapped-mounts-in-ovl.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007001] Re: Blank console display with aarch64 kernel 5.19.0-31
This same issue impacts Ubuntu 22.04.2 HWE 5.19.0-32 kernels on aarch64. -- 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/2007001 Title: Blank console display with aarch64 kernel 5.19.0-31 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded the kernel on 22.10 aarch64 (running in a VM on VMware Fusion 13.0.1 on Apple Silicon_ from 5.19.0-29 to 5.19.0-31. After the upgrade and after rebooting the VM no text or graphical console appears on the VM. The VM is running and can be accessed through SSH. Rebooting the VM with kernel 5.19.0-29 - everything is working as expected. Text and graphical consoles now display properly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-31-generic 5.19.0-31.32 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic aarch64 ApportVersion: 2.23.1-0ubuntu3 Architecture: arm64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Sat Feb 11 13:04:22 2023 InstallationDate: Installed on 2022-09-11 (153 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha arm64 (20220911) IwConfig: lono wireless extensions. ens160no wireless extensions. MachineType: VMware, Inc. VMware20,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=UUID=5e9795ee-63e3-4df1-93e9-c36cd88c726c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-31-generic N/A linux-backports-modules-5.19.0-31-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2022 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW201.00V.20904234.BA64.2212051119 dmi.board.name: VBSA dmi.board.vendor: VMware, Inc. dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware, Inc. dmi.chassis.version: VMware20,1 dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW201.00V.20904234.BA64.2212051119:bd12/05/2022:svnVMware,Inc.:pnVMware20,1:pvr1:rvnVMware,Inc.:rnVBSA:rvr1:cvnVMware,Inc.:ct1:cvrVMware20,1:sku0001: dmi.product.family: VMware dmi.product.name: VMware20,1 dmi.product.sku: 0001 dmi.product.version: 1 dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.15.0.1035.31)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1035.31) for jammy have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.13.1-1ubuntu0.22.04.3 (arm64, amd64) digimend-dkms/10-4 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/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: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging 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-restricted-modules-azure-5.15/5.15.0-1035.42~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 (5.15.0-1035.42~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (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/focal/update_excuses.html#linux-restricted-modules-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging 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 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1035.42~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 (5.15.0-1035.42~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (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/focal/update_excuses.html#linux-restricted-modules-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
