[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
FWIW I also just tried 24.04 as well as the latest BIOS update (1.37). The issue appears to be significantly worse. I was initially unable to boot into a desktop environment at all. Changing the BIOS setting for Display to Discrete (from Hybrid) meant that everything worked but monitor detection was broken in Wayland so I've stayed with Xorg where it is only partially broken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
** Changed in: zfs-linux (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: zfs-linux (Ubuntu Noble)
Assignee: (unassigned) => John Cabaj (john-cabaj)
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
In Progress
Status in systemd source package in Noble:
Triaged
Status in zfs-linux source package in Noble:
In Progress
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I've tested an initial version with the upstream patch and attached the
debdiff here. Will work to get this uploaded.
** Patch added: "zfs-linux_2.2.2-0ubuntu9.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2058179/+attachment/5767995/+files/zfs-linux_2.2.2-0ubuntu9.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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Triaged
Status in zfs-linux package in Ubuntu:
Confirmed
Status in systemd source package in Noble:
Triaged
Status in zfs-linux source package in Noble:
Confirmed
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
This is likely a dup of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061851 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3
the kernel team is already rolling kernels with the fix for 2061851 but it is also building in https://launchpad.net/~apparmor- dev/+archive/ubuntu/apparmor-devel ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2061869 Title: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3 Status in apparmor package in Ubuntu: New Status in linux-lowlatency package in Ubuntu: New Bug description: After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no longer connect to network. I tried downgrading snapd from edge, still no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll also add apparmor in case this is an apparmor issue as well. Marking as "critical" priority as this affects all installs of Ubuntu Studio and affects Firefox and Thunderbird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 I will add here as well that we have an update of the firefox profile coming that supports the /opt/firefox/firefox location used as the default install for the firefox downloaded directly from mozilla.org -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056297] Re: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04
*** This bug is a duplicate of bug 2046844 *** https://bugs.launchpad.net/bugs/2046844 Hi cipricus, can you specify how and where your firefox was installed? We are trying to support multiple variations including downloading directly from mozilla if it is installed to the standard location? mruffell is correct in his assessment that this is due to firefox not correctly handling user namespace mediation. This can be seen in your dmesg with the following messages [ 69.033622] audit: type=1400 audit(1709714939.278:138): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=2922 comm=495043204C61756E6368 requested="userns_create" target="unprivileged_userns" [ 69.037108] audit: type=1400 audit(1709714939.282:139): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=2982 comm=53616E64626F7820466F726B6564 capability=21 capname="sys_admin" Unfortunately firefox does not handle the error returned when it tries an operation that require sys_admin capability gracefully resulting in the crash. mruffell has already provided all the relevant links so I will just supplement that information 1. The recommended way is updating the firefox profile in /etc/apparmor.d/firefox by adding the location you have firefox installed, and then reloading the profile with sudo apparmor_parser -r /etc/apparmor.d/firefox 2. You can disable user namespaces, this will keep firefox from trying to use them as part of ts sandbox https://lwn.net/Articles/673597/ 3. the least recommended way to fix this is you can disable the finer grained user namespace restrictions as outlined in https://ubuntu.com/blog/ubuntu-23-10-restricted-unprivileged-user- namespaces -- 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/2056297 Title: Non-flatpak Firefox-based browsers crash with kernel 6.8.0-11-generic in 24.04 Status in linux package in Ubuntu: New Bug description: All details are to be found in my previous bug report (https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2056190). Given that simply reverting to kernel 6.5.0-17-generic fixes the problem, the bug seems to be with the 6.8.0 kernel. Therefore I'm posting this. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-11-generic 6.8.0-11.11 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed Mar 6 09:49:36 2024 InstallationDate: Installed on 2023-10-04 (154 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Sony Corporation VPCSB2P9E ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=0dbb7177-a759-43f8-86d2-53e3253805d5 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240202.git36777504-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-03-04 (2 days ago) dmi.bios.date: 11/16/2011 dmi.bios.release: 20.85 dmi.bios.vendor: INSYDE dmi.bios.version: R2085H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 20.85 dmi.modalias: dmi:bvnINSYDE:bvrR2085H4:bd11/16/2011:br20.85:efr20.85:svnSonyCorporation:pnVPCSB2P9E:pvrC609DJQ5:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:skuN/A: dmi.product.family: VAIO dmi.product.name: VPCSB2P9E dmi.product.sku: N/A dmi.product.version: C609DJQ5 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
** Changed in: linux (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Focal: Invalid Status in linux-hwe source package in Focal: New Status in livecd-rootfs source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-hwe source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
1. Yes. The backport was for 5.15 jammy kernels including HWE derivatives. The user space SRU was done in bug https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146 which included Focal. The intent being Focal will only support mqueue if it is using and HWE kernel. 2. Yes that makes sense. I have added a linux-hwe entry for focal ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Jammy) Status: New => Invalid ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Focal: New Status in linux-hwe source package in Focal: New Status in livecd-rootfs source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-hwe source package in Jammy: Invalid Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Question -- this has landed in various jammy-5.15 kernels. This rolled downstream to the focal HWE kernels (specifically the cloud kernels) 1. was this intentional? 2. if so, could we add an affects for focal as well? it'll help us with tracking downstream dependency changes, specifically in livecd-rootfs: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2052789 -- 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/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Triaged Status in livecd-rootfs package in Ubuntu: New Status in linux source package in Jammy: Fix Released Status in livecd-rootfs source package in Jammy: New Bug description: [ Impact ] mq-posix snapd interface does not work on Ubuntu Core 22. It results in permission denied even all interfaces are connected. Our brandstore customer is using posix message queue for IPC between snaps. They added mq-posix interface and connected them properly but getting permission denied error. The AppArmor patch for posix message queue created for other customer did not land in the standard jammy kernel. Userspace support for AppArmor message queue handling is already present in Ubuntu Core 22, it is just missing from the kernel. [ Test Plan ] * Create snaps using the posix-mq snapd interface on Ubuntu Core 22 or Classic 22.04 with the standard kernel. * Example snaps for testing: https://code.launchpad.net/~itrue/+git/mqtest-provider and https://code.launchpad.net/~itrue/+git/mqtest-client [ Where problems could occur ] * The patches already exist for 5.15 and have been used on other private customer kernels and all kernels released after 22.04, so there is already a good track record for this patchset and it shouldn't create any issues. [ Other Info ] * This is a time-sensitive issue for a paying customer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045384/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Assignee: (unassigned) => John Cabaj (john-cabaj) -- 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/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056616] Re: left-over ceph debugging printks
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2056616 Title: left-over ceph debugging printks Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Hello, a pal recently mentioned some debugging printk statements in our kernels, eg: evict_inodes inode d69da69b, i_count = 1, was skipped! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214 has some additional details. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2041613 looks like an effort to remove it? This apparently hasn't been finished yet, and it's in the middle of a big run of actual real work, so it might not be super-easy to just yank this out, it might also justify a larger look at the surrounding context. In noble master-next: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/noble/commit/fs/inode.c?h=master- next=603b74b4176fdf6ab2fb83306136947296e7aeb4 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
All 64k packages being correctly produced from arm64. ** Tags removed: verification-needed-mantic-linux-oracle ** Tags added: verification-done-mantic-linux-oracle -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle-6.5 package in Ubuntu: Invalid Status in linux-oracle source package in Jammy: Invalid Status in linux-oracle-6.5 source package in Jammy: Fix Committed Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle-6.5 source package in Mantic: Invalid Status in linux-oracle source package in Noble: In Progress Status in linux-oracle-6.5 source package in Noble: Invalid Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052576] Re: GCP TDX Support
Google tested packages from build PPA. ** Tags removed: verification-needed-mantic-linux-gcp ** Tags added: verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055473] [NEW] mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU
Public bug reported: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Attachment added: "rt.log" https://bugs.launchpad.net/bugs/2055473/+attachment/5750793/+files/rt.log ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2055473 Title: mtu.sh net selftest fail with PMTU exception wasn't created after exceeding MTU Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Status in linux source package in Noble: New Bug description: 19:48:21 DEBUG| [stdout] # selftests: net: pmtu.sh 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions [ OK ] 19:48:21 DEBUG| [stdout] # TEST: ipv4: PMTU exceptions - nexthop objects [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions [ OK ] 19:48:22 DEBUG| [stdout] # TEST: ipv6: PMTU exceptions - nexthop objects [ OK ] 19:48:23 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:23 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:24 DEBUG| [stdout] # TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects [FAIL] 19:48:24 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions [FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU 19:48:25 DEBUG| [stdout] # TEST: UDPv4 with DSCP and ECN: PMTU exceptions - nexthop objects[FAIL] 19:48:25 DEBUG| [stdout] # PMTU exception wasn't created after exceeding MTU Logfile also attached (rt.log) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2055473/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052967] Re: Provide all available pkcs11 userspace binaries for container consumption
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2052967 Title: Provide all available pkcs11 userspace binaries for container consumption Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 source package in Bionic: New Status in nvidia-graphics-drivers-535-server source package in Bionic: New Status in nvidia-graphics-drivers-535 source package in Focal: New Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535 source package in Jammy: New Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535 source package in Mantic: New Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535 source package in Noble: New Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Committed Bug description: [ Impact ] * NVIDIA ERD drivers provide userspace libraries for consumption. * One of them is pkcs11 plugin compiled against openssl v3 or openssl v1.1 abi * A host system only needs one of them, that matches the host os OpenSSL ABI * However, if a given host system launches containers of a different releases series, it may require the other abi pkcs11 plugin. * It is common to pass userspace libraries from host to container guest (i.e. docker, k8s, lxd all have tooling to do so). * Thus to better support running ancient and obsolete containers on modern hostos; or vice versa run modern containers on ancient hostos; ship both variants of the library always in the ERD drivers. * Most urgently this affects the longterm ERD driver production branch 535-server * Shipping this update as packaging revision only, allows releasing this update without rebuilding LRM packages. [ Test Plan ] * Observe that ERD driver packages ship all available libnvidia-pkcs11-openssl*.so* libraries * Check that launching a docker container with userspace libraries passthrough results in both available in the guest * Ensuring that matching libssl/libcrypto is available in the guest container, remains exercise for the container operator. [ Where problems could occur ] * Lintian warnings will be generated w.r.t. missing library dependencies * One must ensure shlib dependency is not generated for the other library, as those will not be satisfied. [ Other Info ] * All other projects that try to be universal against multiple openssl ABIs typically use dlopen and make appropriate function calls from a single library build. I encourage NVIDIA upstream to adapt this strategy. A C language example of achieving this, licensed under MIT license, is available here https://github.com/golang-fips/openssl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2052967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052640] Re: New NVIDIA release 470.239.06
** Changed in: fabric-manager-470 (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: fabric-manager-470 (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: fabric-manager-470 (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: fabric-manager-470 (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: fabric-manager-470 (Ubuntu Noble) Status: Confirmed => In Progress ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2052640 Title: New NVIDIA release 470.239.06 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 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in fabric-manager-470 source package in Bionic: In Progress Status in libnvidia-nscq-470 source package in Bionic: In Progress Status in nvidia-graphics-drivers-470 source package in Bionic: In Progress Status in nvidia-graphics-drivers-470-server source package in Bionic: In Progress Status in fabric-manager-470 source package in Focal: In Progress Status in libnvidia-nscq-470 source package in Focal: In Progress Status in nvidia-graphics-drivers-470 source package in Focal: In Progress Status in nvidia-graphics-drivers-470-server source package in Focal: In Progress Status in fabric-manager-470 source package in Jammy: In Progress Status in libnvidia-nscq-470 source package in Jammy: In Progress Status in nvidia-graphics-drivers-470 source package in Jammy: In Progress Status in nvidia-graphics-drivers-470-server source package in Jammy: In Progress Status in fabric-manager-470 source package in Mantic: In Progress Status in libnvidia-nscq-470 source package in Mantic: In Progress Status in nvidia-graphics-drivers-470 source package in Mantic: In Progress Status in nvidia-graphics-drivers-470-server source package in Mantic: In Progress Status in fabric-manager-470 source package in Noble: In Progress Status in libnvidia-nscq-470 source package in Noble: In Progress Status in nvidia-graphics-drivers-470 source package in Noble: In Progress Status in nvidia-graphics-drivers-470-server source package in Noble: In Progress 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. Note as this is a legacy driver, the QA team available hardware might be limited if not existent. Tests on GKE might be suitable, as they still default to 470 series. [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/2052640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930745] Re: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key
A temporary fix is to fold down the screen of the laptop and then reopen it. This may provide a clue as to the underlying problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1930745 Title: AT Translated Set 2 keyboard locks up seemingly randomly, infinitely repeating last pressed key Status in linux-signed-hwe-5.8 package in Ubuntu: Confirmed Bug description: I am running Ubuntu 20.04.2 LTS on my ThinkPad L15 laptop. From time to time the keyboard gets stuck / locked up. Sometimes it takes days to happen, sometimes it happens within a few minutes. It also does not seem to depend on the programs I am running, it seems to be entirely random. Basically, I am working/playing on the laptop and then suddenly the key I pressed last "gets stuck" and the keyboard does not respond any more. Other than that everything is running fine and I can still use the mouse and so on, but logging out does not resolve the issue and only a restart seems to work. I have also tried connecting a USB keyboard while the problem is occurring. The external keyboard is then detected and works fine, the built-in keyboard stops sending the signal and remains unresponsive. I have already mentioned the problem here, but it could not be resolved: https://ubuntuforums.org/showthread.php?t=2460675 I have also contacted Lenovo Hardware Support, and ran their tests, but those did not return anything, so they said it was not a hardware issue. My best guess is that it is a bug in the driver for the AT Translated Set 2 keyboard (I have the German keyboard layout), which is listed as supported hardware. Current and latest driver version is 1.0.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 3 13:45:29 2021 InstallationDate: Installed on 2020-12-29 (156 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1930745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
I struggle to reproduce the issue on focal with v5.4 and
0.8.3-1ubuntu12.16 zfs
but also see no regressions with the proposed 12.17 update.
** 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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054439] Re: RM obsolete binaries from noble to allow linux to migrate
unless linux-meta is buggy and produces non-installable packages -- 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/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054439] [NEW] RM obsolete binaries from noble to allow linux to migrate
Public bug reported: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Noble) 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/2054439 Title: RM obsolete binaries from noble to allow linux to migrate Status in linux package in Ubuntu: Incomplete Status in linux source package in Noble: Incomplete Bug description: currently linux is stuck from migrating because of * amd64: linux-modules-ipu6-oem-22.04, linux-modules-ivsc-oem-22.04, linux-modules-nvidia-440-oem-20.04, linux-modules-nvidia-450-oem-20.04 - splitting the component into single items and retrying them ipu6 / ivsc are curretnly broken and will be re-introduced once fixed. nvidia-440 and nvidia-450 are obsolete and remove from the archive and so is oem-20.04 kernel flavour which stopped being a thing in jammy. Please remove all of those packages from noble & noble-proposed to allow linux to migrate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054296] Re: Don't restrict to linux-laptop
** Changed in: qrtr (Ubuntu) Status: New => Fix Committed ** Changed in: protection-domain-mapper (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: Fix Committed Status in qrtr package in Ubuntu: Fix Committed Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054296] Re: Don't restrict to linux-laptop
This was done for mantic release due to lack of time, and inability to verify if unrestricted access will be harmful in any way to any generic implementations. I hope we have time to test that this doesn't cause any issues, or failed unit starts on Pi Desktop and Qemu Desktop systmes which are not qcom based and that the service exits gracefully. If not, we agree to add more targetted conditionals for example test for a certain sysfs path to exist that indicates that a given booted system has qrtr / protection-domain-mapper compatible support. Let's upload this, test how these units behave on Pi and Qemu, and if needed improve the systemd unit with more targetted conditionals. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2054296 Title: Don't restrict to linux-laptop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The generic arm64 kernel now support some Qualcomm platforms so the services need to run with that kernel as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2054296/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052469] Re: Provide an arm64 linux-oracle 64k kernel variant
** Changed in: linux-oracle (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Mantic: Fix Committed Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052576] Re: GCP TDX Support
** Changed in: linux-gcp (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052967] [NEW] Provide all available pkcs11 userspace binaries for container consumption
Public bug reported: [ Impact ] * NVIDIA ERD drivers provide userspace libraries for consumption. * One of them is pkcs11 plugin compiled against openssl v3 or openssl v1.1 abi * A host system only needs one of them, that matches the host os OpenSSL ABI * However, if a given host system launches containers of a different releases series, it may require the other abi pkcs11 plugin. * It is common to pass userspace libraries from host to container guest (i.e. docker, k8s, lxd all have tooling to do so). * Thus to better support running ancient and obsolete containers on modern hostos; or vice versa run modern containers on ancient hostos; ship both variants of the library always in the ERD drivers. * Most urgently this affects the longterm ERD driver production branch 535-server * Shipping this update as packaging revision only, allows releasing this update without rebuilding LRM packages. [ Test Plan ] * Observe that ERD driver packages ship all available libnvidia-pkcs11-openssl*.so* libraries * Check that launching a docker container with userspace libraries passthrough results in both available in the guest * Ensuring that matching libssl/libcrypto is available in the guest container, remains exercise for the container operator. [ Where problems could occur ] * Lintian warnings will be generated w.r.t. missing library dependencies * One must ensure shlib dependency is not generated for the other library, as those will not be satisfied. [ Other Info ] * All other projects that try to be universal against multiple openssl ABIs typically use dlopen and make appropriate function calls from a single library build. I encourage NVIDIA upstream to adapt this strategy. A C language example of achieving this, licensed under MIT license, is available here https://github.com/golang-fips/openssl ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2052967 Title: Provide all available pkcs11 userspace binaries for container consumption Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in nvidia-graphics-drivers-535-server source package in Bionic: New Status in nvidia-graphics-drivers-535-server source package in Focal: New Status in nvidia-graphics-drivers-535-server source package in Jammy: New Status in nvidia-graphics-drivers-535-server source package in Mantic: New Status in nvidia-graphics-drivers-535-server source package in Noble: New Bug description: [ Impact ] * NVIDIA ERD drivers provide userspace libraries for consumption. * One of them is pkcs11 plugin compiled against openssl v3 or openssl v1.1 abi * A host system only needs one of them, that matches the host os OpenSSL ABI * However, if a given host system launches containers of a different releases series, it may require the other abi pkcs11 plugin. * It is common to pass userspace libraries from host to container guest (i.e. docker, k8s, lxd all have tooling to do so). * Thus to better support running ancient and obsolete containers on modern hostos; or vice versa run modern containers on ancient hostos; ship both variants of the library always in the ERD drivers. * Most urgently this affects the longterm ERD driver production branch 535-server * Shipping this update as packaging revision only, allows releasing this update without rebuilding LRM packages. [ Test Plan ] * Observe that ERD driver packages ship all available libnvidia-pkcs11-openssl*.so* libraries * Check that launching a docker container with userspace libraries passthrough results in both available in the guest * Ensuring that
[Kernel-packages] [Bug 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Assignee: You-Sheng Yang (vicamo) => (unassigned)
--
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/2035971
Title:
linux tools packages for derived kernels refuse to install
simultaneously due to libcpupower name collision
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Mantic:
Fix Released
Bug description:
[ Impact ]
* Multiple kernel flavours are conflicting with each on .deb / file
level via their tools packages
* Resolve the conflicting private libcpupower.so by statically
linking it into the only C binary that uses said library in the linux-
tools
[ Test Plan ]
* co-install tools packages from multiple kernel flavours of the same
major version and abi, it should be successful
[ Where problems could occur ]
* If one tries really hard to find the private location of
libcpupower.so and dlopen it by ever changing abi name, that will not
be possible, until the separate bug report is fixed to introduce the
public stable libcpupower.so.1 which so far ubuntu has never yet
provided.
[ Other Info ]
* original bug report
Taking linux-kvm and linux-gcp for example:
$ dpkg-deb --contents linux-gcp-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103384 2023-07-25 20:00
./usr/lib/libcpupower.so.6.2.0-1011
$ dpkg-deb --contents linux-kvm-tools-6.2.0-1011_6.2.0-1011.11_amd64.deb |
grep libcpupower
-rw-r--r-- root/root103392 2023-08-16 15:08
./usr/lib/libcpupower.so.6.2.0-1011
linux-gcp-tools-6.2.0-1011 and linux-kvm-tools-6.2.0-1011 both contain
a libcpupower.so.6.2.0-1011 shared library used by their own cpupower
utilities, and yet files of the same full path cannot be installed
from two distinct debian packages, which follows we won't be able to
install two linux-tools packages of two different derived kernels on
the same system.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-kvm-tools-6.2.0-1011 6.2.0-1011.11
ProcVersionSignature: Ubuntu 6.5.0-9004.4+exp.9-generic 6.5.0-rc7
Uname: Linux 6.5.0-9004-generic x86_64
NonfreeKernelModules: zfs wl
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vicamo 6331 F wireplumber
/dev/snd/controlC0: vicamo 6331 F wireplumber
/dev/snd/seq:vicamo 6315 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Sep 14 23:31:16 2023
InstallationDate: Installed on 2022-04-10 (522 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64
(20220329.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9004-generic
root=UUID=2382e73d-78cd-4dfd-b12e-cae1153e3667 ro rootflags=subvol=@
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9004-generic N/A
linux-backports-modules-6.5.0-9004-generic N/A
linux-firmware 20230815.git0e048b06-0ubuntu1
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2021
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 432.60.3.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias:
dmi:bvnAppleInc.:bvr432.60.3.0.0:bd10/27/2021:br0.1:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:skuSystemSKU#:
dmi.product.family: Mac
dmi.product.name: MacBookPro11,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035971/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1628204] Re: linux: 4.4.0-41.61 -proposed tracker
Great Information you can also checkout http://carxstreetsapk.com/ -- 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/1628204 Title: linux: 4.4.0-41.61 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: This bug is for tracking the 4.4.0-41.61 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1628204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
responding to @intrigeri (sorry this got lost some how).
tldr: yes we are basically on the same page.
AppArmor does not fit into the 1400 range formats, every one of our
messages have some custom fields. Some of them could be
reformated/reworked to share more, but we would still need custom
fields.
Our message fields are in the common name=value format. So in that sense
they do fit in.
Kernel side this is fairly easy, we use common lsm_audit for the
messages we share in common, the code provides a callback to add your
own fields. Basically all that is needed is patch to allow different
number ranges to be used.
Userspace there needs to be some patching so LSM specific fields are
known about.
Whether is best to allocate new fields in a single number (say 1500),
with no fixed number of fields to output or it better to split into a
range of based on message type, I am not picky. When 1500 was taken away
from us I think it was 1500-1505 that we used, but expect we wouldn't
use the same mappings today if we had a choice.
so we have the generic audit type that is carried { audit, allowed,
denied, killed, prompt, hint, status, error }
this could carried as a common field, or we could use an allocated block
for
we have rule class, which is another way things are broken down, its
things like { file, cap, network, dbus, ...} there are currently about
25 of them currently.
common fields that can occur within apparmor messages { operation, info,
error, namespace, profile, label }, some fields aren't output if not
needed. Eg. we are auditing an access to say /etc/shadow that is allowed
but we want an audit trail for error won't be output, if its a system
status message that is not generated by a profiles rule set, profile=
won't be used. This set does not lend itself to an audit range as they
each take on basically a string value.
Then within a given class there are set of fields, some of them are shared by
several classes, but not all, and there are some that are only used by a single
class. Some examples would be, most mediation class share requested= and
denied= the values are class depended even those may be shared by a subset of
classes.
--
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/1117804
Title:
ausearch doesn't show AppArmor denial messages
Status in AppArmor:
Confirmed
Status in audit package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
The following command should display all AVC denials:
ausearch -m avc
However, it doesn't work with AppArmor denials. Here's a quick test
case to generate a denial, search for it with ausearch, and see that
no messages are displayed:
$ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current
cat: /proc/self/attr/current: Permission denied
$ sudo ausearch -m avc -c cat
ausearch claims that there are no matches, but there's a matching
audit message if you look in audit.log:
type=AVC msg=audit(1360193426.539:64): apparmor="DENIED"
operation="open" parent=8253 profile="/usr/sbin/tcpdump"
name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=1000
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1117804/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973098] Re: [i915] Intermittent freezing and LSPCON init failed kernel messages
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: [i915] Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052744] Re: nouveau breaks 24.04 desktop
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052744/+attachment/5745301/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2052744 Title: nouveau breaks 24.04 desktop Status in linux package in Ubuntu: New Bug description: nouveau: detected PR support, will not use DSM nouveau :01:00.0: NVIDIA GP107 (137000a1) usb 3-3: new high-speed USB device number 2 using xhci_hcd nouveau :01:00.0: bios: version 86.07.90.00.51 nouveau :01:00.0: pmu: firmware unavailable nouveau :01:00.0: fb: 2048 MiB GDDR5 nouveau :01:00.0: DRM: VRAM: 2048 MiB nouveau :01:00.0: DRM: GART: 536870912 MiB nouveau :01:00.0: DRM: BIT table 'A' not found nouveau :01:00.0: DRM: BIT table 'L' not found nouveau :01:00.0: DRM: Pointer to TMDS table not found nouveau :01:00.0: DRM: DCB version 4.1 nouveau :01:00.0: DRM: MM: using COPY for buffer copies [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 nouveau :01:00.0: [drm] No compatible format found nouveau :01:00.0: [drm] Cannot find any crtc or sizes nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ PRIVRING ] nouveau :01:00.0: bus: MMIO read of FAULT at 122124 [ PRIVRING ] # above two repeat a lot And also stuff like this nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ TIMEOUT ] [ cut here ] nouveau :01:00.0: timeout WARNING: CPU: 3 PID: 6419 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer nft_masq vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal snd_hda_c odec intel_powerclamp snd_hda_core coretemp snd_hwdep snd_pcm uvcvideo kvm_intel snd_seq_midi iwlmvm btusb videobuf2_vmalloc snd_seq_midi_event btrtl uvc cmdlinepart kvm snd_rawmidi videobuf2_memops btintel dell_laptop spi_nor videobuf2_v4l2 mac80211 snd_seq irqbypass btbcm processor_thermal_device_pci_legacy dell_wmi mtd videodev snd_seq_device rapl btmtk processor_thermal_device pmt_telemetry dell_smbios libarc4 mei_hdcp mei_pxp bluetooth pmt_class intel_rapl_msr dell_smm_hwmon iwlwifi videobuf2_common dcdbas snd_timer i2c_i801 dell_wmi_sysman spi_intel_pci intel_cstate processor_thermal_rfim dell_wmi_ddv ecdh_generic mc ecc ledtrig_audio firmware_attributes_class dell_wmi_descriptor wmi_bmof snd i2c_smbus spi_intel mei_me cfg80211 processor_thermal_mbox soundcore essiv mei authenc processor_thermal_rapl intel_rapl_common intel_skl_int3472_tps68470 intel_soc_dts_iosf intel_vsec igen6_edac tps68470_regulator int3403_thermal clk_tps68470 int340x_thermal_zone int3400_thermal intel_hid intel_skl_int3472_ discrete input_leds acpi_thermal_rel sparse_keymap acpi_pad joydev acpi_tad serio_raw mac_hid nbd msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 dm_crypt zfs(PO) spl(O) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom nvme hid_sensor_hub nvme_core nvme_common intel_ishtp_hid hid_multitouch ahci hid_generic libahci i915 nouveau crct10dif_pclmul crc32_pclmul polyval_clmulni mxm_wmi polyval_generic drm_exec ghash_clmulni_intel gpu_sched drm_buddy sha256_ssse3 drm_ttm_helper i2c_algo_bit sha1_ssse3 ttm aesni_intel drm_display_helper cec i2c_hid_acpi rc_core intel_lpss_pci crypto_simd i2c_hid ucsi_acpi intel_ish_ipc drm_kms_helper hid typec_ucsi xhci_pci cryptd intel_lpss psmouse thunderbolt video idma64 intel_ishtp vmd drm xhci_pci_renesas typec wmi pinctrl_tigerlake CPU: 3 PID: 6419 Comm: gnome-shell Tainted: P O 6.6.0-14-generic #14-Ubuntu Hardware name: Dell Inc. Inspiron 7400/072W08, BIOS 1.16.0 04/13/2022 RIP: 0010:gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Code: 8b 40 10 48
[Kernel-packages] [Bug 2052744] [NEW] nouveau breaks 24.04 desktop
Public bug reported: nouveau: detected PR support, will not use DSM nouveau :01:00.0: NVIDIA GP107 (137000a1) usb 3-3: new high-speed USB device number 2 using xhci_hcd nouveau :01:00.0: bios: version 86.07.90.00.51 nouveau :01:00.0: pmu: firmware unavailable nouveau :01:00.0: fb: 2048 MiB GDDR5 nouveau :01:00.0: DRM: VRAM: 2048 MiB nouveau :01:00.0: DRM: GART: 536870912 MiB nouveau :01:00.0: DRM: BIT table 'A' not found nouveau :01:00.0: DRM: BIT table 'L' not found nouveau :01:00.0: DRM: Pointer to TMDS table not found nouveau :01:00.0: DRM: DCB version 4.1 nouveau :01:00.0: DRM: MM: using COPY for buffer copies [drm] Initialized nouveau 1.3.1 20120801 for :01:00.0 on minor 0 nouveau :01:00.0: [drm] No compatible format found nouveau :01:00.0: [drm] Cannot find any crtc or sizes nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ PRIVRING ] nouveau :01:00.0: bus: MMIO read of FAULT at 122124 [ PRIVRING ] # above two repeat a lot And also stuff like this nouveau :01:00.0: bus: MMIO read of FAULT at 6013d4 [ TIMEOUT ] [ cut here ] nouveau :01:00.0: timeout WARNING: CPU: 3 PID: 6419 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer nft_masq vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock ccm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_generic_allocation soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi x86_pkg_temp_thermal snd_hda_cod ec intel_powerclamp snd_hda_core coretemp snd_hwdep snd_pcm uvcvideo kvm_intel snd_seq_midi iwlmvm btusb videobuf2_vmalloc snd_seq_midi_event btrtl uvc cmdlinepart kvm snd_rawmidi videobuf2_memops btintel dell_laptop spi_nor videobuf2_v4l2 mac80211 snd_seq irqbypass btbcm processor_thermal_device_pci_legacy dell_wmi mtd videodev snd_seq_device rapl btmtk processor_thermal_device pmt_telemetry dell_smbios libarc4 mei_hdcp mei_pxp bluetooth pmt_class intel_rapl_msr dell_smm_hwmon iwlwifi videobuf2_common dcdbas snd_timer i2c_i801 dell_wmi_sysman spi_intel_pci intel_cstate processor_thermal_rfim dell_wmi_ddv ecdh_generic mc ecc ledtrig_audio firmware_attributes_class dell_wmi_descriptor wmi_bmof snd i2c_smbus spi_intel mei_me cfg80211 processor_thermal_mbox soundcore essiv mei authenc processor_thermal_rapl intel_rapl_common intel_skl_int3472_tps68470 intel_soc_dts_iosf intel_vsec igen6_edac tps68470_regulator int3403_thermal clk_tps68470 int340x_thermal_zone int3400_thermal intel_hid intel_skl_int3472_di screte input_leds acpi_thermal_rel sparse_keymap acpi_pad joydev acpi_tad serio_raw mac_hid nbd msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 dm_crypt zfs(PO) spl(O) raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_sensor_custom nvme hid_sensor_hub nvme_core nvme_common intel_ishtp_hid hid_multitouch ahci hid_generic libahci i915 nouveau crct10dif_pclmul crc32_pclmul polyval_clmulni mxm_wmi polyval_generic drm_exec ghash_clmulni_intel gpu_sched drm_buddy sha256_ssse3 drm_ttm_helper i2c_algo_bit sha1_ssse3 ttm aesni_intel drm_display_helper cec i2c_hid_acpi rc_core intel_lpss_pci crypto_simd i2c_hid ucsi_acpi intel_ish_ipc drm_kms_helper hid typec_ucsi xhci_pci cryptd intel_lpss psmouse thunderbolt video idma64 intel_ishtp vmd drm xhci_pci_renesas typec wmi pinctrl_tigerlake CPU: 3 PID: 6419 Comm: gnome-shell Tainted: P O 6.6.0-14-generic #14-Ubuntu Hardware name: Dell Inc. Inspiron 7400/072W08, BIOS 1.16.0 04/13/2022 RIP: 0010:gf100_gr_init_ctxctl_ext+0x573/0x590 [nouveau] Code: 8b 40 10 48 8b 78 10 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 6f c0 b6 ed 48 89 da 48 c7 c7 f5 22 99 c0 48 89 c6 e8 0d 05 13 ed <0f> 0b b8 f0 ff ff ff e9 f7 fd ff ff e8 5c 97 18 ee 66 66 2e 0f 1f RSP: 0018:c9000e67bb50 EFLAGS: 00010246 RAX: RBX: 8881022dec30 RCX: RDX: RSI: RDI: RBP: c9000e67bba0 R08: R09: R10:
[Kernel-packages] [Bug 2052637] [NEW] [i386] please add 550-server to the i386 seed
Public bug reported: Please add the following packages to i386 seed: - nvidia-graphics-drivers-550-server The other one: - nvidia-graphics-drivers-550 is already included. such that beta driver can be packaged and built for i386. ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Description changed: Please add the following packages to i386 seed: - - nvidia-graphics-drivers-550 - nvidia-graphics-drivers-550-server + The other one: + + - nvidia-graphics-drivers-550 is already included. + + such that beta driver can be packaged and built for i386. ** Summary changed: - [i386] please add 550 & 550-server to the i386 seed + [i386] please add 550-server to the i386 seed ** Package changed: nvidia-graphics-drivers-545 (Ubuntu) => nvidia- graphics-drivers-535-server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2052637 Title: [i386] please add 550-server to the i386 seed Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Please add the following packages to i386 seed: - nvidia-graphics-drivers-550-server The other one: - nvidia-graphics-drivers-550 is already included. such that beta driver can be packaged and built for i386. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2052637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052576] Re: GCP TDX Support
** Description changed: [Impact] - * Google requested TDX guest features. + * Google requested TDX guest features to be added to GCP kernel. [Fix] - * Add flavour and configs for 64k flavour + * 16 clean cherry-picks from upstream + * 2 backports from upstream + * 11 backports from Intel + * 1 config change to enable support [Test Case] * Compile tested * Boot tested + * Tested internally at various stages of development * Tested by Google [Where things could go wrong] - * Low chance of regression. Isolated logic fix. + * Majority of patches come from upstream with minimal backporting. + * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 ** Description changed: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] - * 16 clean cherry-picks from upstream - * 2 backports from upstream + * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested TDX guest features to be added to GCP kernel. [Fix] * 16 clean cherry-picks, 2 backports from upstream * 11 backports from Intel * 1 config change to enable support [Test Case] * Compile tested * Boot tested * Tested internally at various stages of development * Tested by Google [Where things could go wrong] * Majority of patches come from upstream with minimal backporting. * Some patches sourced from Intel, and differ from upstream counterparts. However, these patches have been extensively tested in other kernels already released. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052576] [NEW] GCP TDX Support
Public bug reported: [Impact] * Google requested TDX guest features. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00363309 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052576 Title: GCP TDX Support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Google requested TDX guest features. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00363309 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052576/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051468] Re: Fix snapcraftyaml.yaml for jammy:linux-raspi
the same is true for unstable and generic pc-kernel too ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2051468 Title: Fix snapcraftyaml.yaml for jammy:linux-raspi Status in linux package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Bug description: jammy:linux-raspi has snapcraft.yaml. This file was added more than a decade ago. It does not produce any sensible kernel snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: New => Fix Committed -- 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/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470 source package in Noble: Fix Committed Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
@fl140 i have previously prepared upgrades to new point release from
2.1.x and 2.2.x series all of those SRUs got rejected.
@mfo all dkms based kernel modules that kernel packages prebuild get
picked up every kernel sru cycle, including zfs, which will be picked in
a future kernel sru cycle.
** Tags added: verification-done-mantic verification-needed-focal
verification-needed-jammy
--
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/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052420] Re: nvidia-dkms-* FTBS with linux 6.8
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Noble) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-470-server (Ubuntu) Status: New => Fix Committed -- 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/2052420 Title: nvidia-dkms-* FTBS with linux 6.8 Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in nvidia-graphics-drivers-545 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Noble: Fix Committed Bug description: [Impact] ... In file included from /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:60: /var/lib/dkms/nvidia/470.223.02/build/nvidia-drm/nvidia-drm-drv.c:748:40: error: ‘DRM_UNLOCKED’ undeclared here (not in a function); did you mean ‘VM_LOCKED’? 748 | DRM_RENDER_ALLOW|DRM_UNLOCKED), |^~~~ ... [Fix] Apply the attached debdiff. [How to test] Install (and rebuild) the patched package. [Regression potential] Two patches, none originating from NVidia and both touching locking: there's definitely regression potential here, hence i'm proposing this upload *only* for Noble and as a way to move forward (and not stall) until NVidia drops a new version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2052420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: In Progress Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052469] [NEW] Provide an arm64 linux-oracle 64k kernel variant
Public bug reported: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 ** Affects: linux-oracle (Ubuntu) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Affects: linux-oracle (Ubuntu Noble) Importance: Undecided Assignee: John Cabaj (john-cabaj) Status: In Progress ** Also affects: linux-oracle (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oracle (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-oracle (Ubuntu Noble) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2052469 Title: Provide an arm64 linux-oracle 64k kernel variant Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Mantic: In Progress Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Oracle requested 64k page size flavour. [Fix] * Add flavour and configs for 64k flavour [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Isolated logic fix. [Other Info] * SF #00377602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2052469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052451] Re: Incorrect argument to notify_page_enc_status_changed()
** Description changed: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] - * Include change from upstream 064ce6c550a06 + * 27ba8c7 modified notify_page_enc_status_changed(), when it should not + have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * 27ba8c7 modified notify_page_enc_status_changed(), when it should not have [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052451] [NEW] Incorrect argument to notify_page_enc_status_changed()
Public bug reported: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * Include change from upstream 064ce6c550a06 [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2052451 Title: Incorrect argument to notify_page_enc_status_changed() Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Bug description: [Impact] * Google requested fix to notify_page_enc_status_changed() passing incorrect argument. [Fix] * Include change from upstream 064ce6c550a06 [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Isolated logic fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2052451/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040522] Re: gVNIC DQO-QPL feature
Verified by Google as part of SF#00366697. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
Verified by Google as part of SF#00368902 as well as internally on GCE instance. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046184] Re: [arm64] Increase max CPU count to 512
** Changed in: linux-oracle (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/2046184 Title: [arm64] Increase max CPU count to 512 Status in linux-oracle package in Ubuntu: In Progress Status in linux-oracle source package in Jammy: Fix Released Status in linux-oracle source package in Mantic: Fix Released Status in linux-oracle source package in Noble: In Progress Bug description: [Impact] * Request to accommodate new shape with 320 CPUs, greater than current max value of 256. [Fix] * Update CONFIG_NR_CPUS from 256 to 512 for arm64 arch. [Test Case] * Compile tested * Boot tested [Where things could go wrong] * Low chance of regression. Simple config change. [Other Info] * Change proposed in Debian unstable (https://salsa.debian.org/kernel-team/linux/-/merge_requests/937?commit_id=8dfba66465dbf4c3c8ef8998065805b852b34e22#fc973071e6f4da49be1ec7a17e00635dd41dcaf1), but was denied due to additional kernel size. This shouldn't affect Ubuntu kernel so much as it's compressed. * SF #00375112 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/2046184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
** Changed in: zfs-linux (Ubuntu Mantic) Status: Incomplete => In Progress ** Changed in: zfs-linux (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: zfs-linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: zfs-linux (Ubuntu Lunar) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu Focal) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: In Progress Status in zfs-linux source package in Jammy: In Progress Status in zfs-linux source package in Lunar: Won't Fix Status in zfs-linux source package in Mantic: In Progress Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). * In the absence of the upgrade a cherry-pick will address this particular popular issue alone - without addressing other issues w.r.t. Redbleed / SLS, bugfixes around trim support, and other related improvements that were discovered and fixed around the same time as this popular issue. [ Test Plan ] * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) * zsys integration test pass (upgrade of zsys installed systems for all releases) * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) [ Where problems could occur ] * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code- paths only in the encryption primitives) * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. [ Other Info ] * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
** Description changed: [ Impact ] - * Multiple data corruption issues have been identified and fixed in + * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. - * For jammy the 2.1.14 upgrade will bring HWE kernel support and also + * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). + * In the absence of the upgrade a cherry-pick will address this + particular popular issue alone - without addressing other issues w.r.t. + Redbleed / SLS, bugfixes around trim support, and other related + improvements that were discovered and fixed around the same time as this + popular issue. + [ Test Plan ] - * !!! Danger !!! use reproducer from + * !!! Danger !!! use reproducer from https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb and confirm if that issue is resolved or not. Do not run on production ZFS pools / systems. - * autopkgtest pass (from https://ubuntu-archive- + * autopkgtest pass (from https://ubuntu-archive- team.ubuntu.com/proposed-migration/ ) - * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) + * adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ ) - * kernel regression zfs testsuite pass (from Kernel team RT test + * kernel regression zfs testsuite pass (from Kernel team RT test results summary, private) - * zsys integration test pass (upgrade of zsys installed systems for all + * zsys integration test pass (upgrade of zsys installed systems for all releases) - * zsys install test pass (for daily images of LTS releases only that + * zsys install test pass (for daily images of LTS releases only that have such installer support, as per iso tracker test case) - * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and + * LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and 2.1.14, and test LXD on these updated kernels) - [ Where problems could occur ] - * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will introduce slight slow down on amd64 (for hw accelerated assembly code-paths only in the encryption primitives) - - * Uncertain of the perfomance impact of the extra checks in dnat patch fix itself. Possibly affecting speed of operation, at the benefit of correctness. + * Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will + introduce slight slow down on amd64 (for hw accelerated assembly code- + paths only in the encryption primitives) + + * Uncertain of the perfomance impact of the extra checks in dnat patch + fix itself. Possibly affecting speed of operation, at the benefit of + correctness. [ Other Info ] - - * https://github.com/openzfs/zfs/pull/15571 is most current consideration of affairs + + * https://github.com/openzfs/zfs/pull/15571 is most current + consideration of affairs -- 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/2044657 Title: Multiple data corruption issues in zfs Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux source package in Jammy: Confirmed Status in zfs-linux source package in Lunar: Won't Fix Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Multiple data corruption issues have been identified and fixed in ZFS. Some of them, at varying real-life reproducibility frequency have been deterimed to affect very old zfs releases. Recommendation is to upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to ensure users get other potentially related fixes and runtime tunables to possibly mitigate other bugs that are related and are being fixed upstream for future releases. * For jammy the 2.1.14 upgrade will bring HWE kernel support and also compatiblity/support for hardened kernel builds that mitigate SLS (straight-line-speculation). * In the absence of the upgrade a cherry-pick will address this particular popular issue alone - without addressing other issues w.r.t. Redbleed / SLS, bugfixes around trim support, and other related improvements that were discovered and fixed around the same time as this popular issue. [
[Kernel-packages] [Bug 2031492] Re: zfs-dkms: support Linux 6.5
** Changed in: zfs-linux (Ubuntu Mantic) Status: New => Fix Released ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released -- 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/2031492 Title: zfs-dkms: support Linux 6.5 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Mantic: Fix Released Bug description: [Impact] zfs-dkms fails to build with the latest 6.5 kernel in Mantic: configure: error: *** None of the expected "bops->release()" 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.2.0~rc1-0ubuntu2 *** Compatible Kernels: 3.10 - 6.3 [Test case] $ sudo apt install zfs-dkms [Fix] Upstream zfs can now be compiled with kernel 6.5, cherry pick the minimum subset of patches to support the new kernel ABI. [Regression potential] We may experience filesystem regressions or potentially kernel crashes with kernels >= 6.5. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: zfs-dkms 2.2.0~rc1-0ubuntu2 ProcVersionSignature: User Name 6.5.0-4.4-generic 6.5.0-rc6 Uname: Linux 6.5.0-4-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSerial: 20230801 CloudSubPlatform: config-disk (/dev/vdb) Date: Wed Aug 16 07:45:37 2023 PackageArchitecture: all ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2031492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908090] Re: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04)
** Also affects: kdump-tools (Ubuntu Noble) Importance: Medium Status: Confirmed ** Also affects: kdump-tools (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: kdump-tools (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: kdump-tools (Ubuntu Focal) Importance: Undecided Status: New ** Summary changed: - Default 192MB crashkernel reservation is never enough (kdump fails on 20.04) + kdump-gaps: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/1908090 Title: kdump-gaps: Default 192MB crashkernel reservation is never enough (kdump fails on 20.04) Status in kdump-tools package in Ubuntu: Confirmed Status in kdump-tools source package in Focal: New Status in kdump-tools source package in Jammy: New Status in kdump-tools source package in Mantic: New Status in kdump-tools source package in Noble: Confirmed Bug description: When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS, everything appears to be in good working order, according to "systemctl status kdump-tools" and "kdump-config status". However, upon an actual crash, the system hangs, and no crash files are produced. I've investigated and have learned that the capture kernel does indeed start, but it is unable to unpack the rootfs/initrd, and thus fails and hangs. [1.070469] Trying to unpack rootfs image as initramfs... [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), order=0, oom_score_adj=0 [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.336396] Call Trace: [1.336396] dump_stack+0x6d/0x9a [1.336396] dump_header+0x4f/0x1eb [1.336396] out_of_memory.part.0.cold+0x39/0x83 [1.336396] out_of_memory+0x6d/0xd0 ... [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]--- On this system with 8G of memory, the crash memory as specified on the kernel command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now kdump works. Not sure how the 192M value is chosen, but it does not work. I think this used value used to work for 16.04 and maybe 18.04 (I didn't try), but is no longer useful for 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/1908090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051682] [NEW] kdump-gaps: does it work on riscv64 with u-boot-menu?
Public bug reported: kdump-gaps: does it work with riscv64 u-boot-menu? I don't see any integration with u-boot-menu on riscv64, and also many boards have very little RAM not sure it will be ever possible to kdump the small riscv64 boards ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2051682 Title: kdump-gaps: does it work on riscv64 with u-boot-menu? Status in kdump-tools package in Ubuntu: New Bug description: kdump-gaps: does it work with riscv64 u-boot-menu? I don't see any integration with u-boot-menu on riscv64, and also many boards have very little RAM not sure it will be ever possible to kdump the small riscv64 boards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2051682/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051679] [NEW] kdump-gaps: does not work on Azure CVM
Public bug reported: Azure CVM uses kernel.efi which currently lacks kexec capability. Unless a second vmlinuz image is installed to support kdump only. ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2051679 Title: kdump-gaps: does not work on Azure CVM Status in kdump-tools package in Ubuntu: New Bug description: Azure CVM uses kernel.efi which currently lacks kexec capability. Unless a second vmlinuz image is installed to support kdump only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2051679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051680] [NEW] kdump-gaps: Does not work on Desktop FDE
Public bug reported: kdump-gaps: Does not work on Desktop FDE similar to azure-cvm & ubuntu core, there is no kexec/kdump support for kernel.efi ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2051680 Title: kdump-gaps: Does not work on Desktop FDE Status in kdump-tools package in Ubuntu: New Bug description: kdump-gaps: Does not work on Desktop FDE similar to azure-cvm & ubuntu core, there is no kexec/kdump support for kernel.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2051680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051681] [NEW] kdump-gaps: does it work on raspberry-pi with piboot?
Public bug reported: kdump-gaps: does it work on raspberry-pi with piboot? I don't see any integration with raspberry-pi using piboot, either should be automatic, or documentation provided. ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2051681 Title: kdump-gaps: does it work on raspberry-pi with piboot? Status in kdump-tools package in Ubuntu: New Bug description: kdump-gaps: does it work on raspberry-pi with piboot? I don't see any integration with raspberry-pi using piboot, either should be automatic, or documentation provided. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2051681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051678] [NEW] kdump-gaps: does not work on Ubuntu core
Public bug reported: I am not sure that kdump can at all work on ubuntu core. bootloader integration is very different, and the kernel image types are very different as follows: * initramfs/system - lack kexec tooling * uefi - no kexec support of kernel.efi * pi - no integration with piboot * u-boot - no kexec support of FIT Also not sure what the expectations are with respect to production systems and full disk encryption keys, as far as I understand it should be possible to extract raw volume encryption master key from the successful kernel dump. ** Affects: kdump-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kdump-tools in Ubuntu. Matching subscriptions: Maintainer https://bugs.launchpad.net/bugs/2051678 Title: kdump-gaps: does not work on Ubuntu core Status in kdump-tools package in Ubuntu: New Bug description: I am not sure that kdump can at all work on ubuntu core. bootloader integration is very different, and the kernel image types are very different as follows: * initramfs/system - lack kexec tooling * uefi - no kexec support of kernel.efi * pi - no integration with piboot * u-boot - no kexec support of FIT Also not sure what the expectations are with respect to production systems and full disk encryption keys, as far as I understand it should be possible to extract raw volume encryption master key from the successful kernel dump. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2051678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux-aws (Ubuntu) Status: Confirmed => Incomplete ** Also affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: Incomplete Status in linux-hwe-6.5 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-525-server package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Confirmed Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27:
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
removing block, as that condition no longer applied due to reject.
** Tags removed: block-proposed-mantic
** Tags added: verification-done
--
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/2046082
Title:
zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[Impact]
* There's a typo in user-visible option (/etc/zfs/zed.d/zed.rc)
ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT introduced upstream
in 2.2.0-rc4 and SRU-ed to Mantic with 2.2.0-0ubuntu1~23.10.
* This could be fixed in Ubuntu before users start adopting it.
[Test Plan]
* Check whether /etc/zfs/zed.d/zed.rc ships the correct option.
* Actual:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOUSRE_SLOT_ON_FAULT=1
* Expected:
$ grep ZED_POWER_OFF_ENCLO /etc/zfs/zed.d/zed.rc
#ZED_POWER_OFF_ENCLOSURE_SLOT_ON_FAULT=1
[Regression Potential]
* Users of Mantic who upgraded to zfs-linux 2.2.0-0ubuntu1~23.10
(published to mantic-updates on 2023-12-08) _and_ enabled the
option (with typo) would have such functionality disabled.
[Other Info]
* This option (with typo) was introduced in commit d19304ffeec5
("zed: Add zedlet to power off slot when drive is faulted"),
and is present in:
- ZFS 2.2: zfs-2.2.0-rc4 (mantic-updates)
- ZFS 2.1: zfs-2.1.13
* It affects Ubuntu Noble and Mantic, but not Lunar or older.
* Fixed upstream with commit 3c7650491b9a ("zed: fix typo in
variable ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2046082/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
I am surprised that `ubuntu-drivers list` doesn't provide any drivers to install, when it really should. To install pre-built drivers I use $ sudo apt install linux-modules-nvidia-535-server-aws nvidia- headless-535-server Such that signed nvidia modules provided by Canonical are installed. Similarly to upgrade to edge variant I did: $ sudo apt install linux-aws-edge linux-modules-nvidia-535-server-aws- edge -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954] x26:
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
I wonder if the bug is with trying to install self-built dkms modules, instead of pre-built ones, and how come ubuntu-drivers is not offering pre-built ones... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954] x26: 00056d1d76c8 x25: c87cf18bdd10 x24: 0003 [ 384.007527] x23: 0001 x22: 00056d1d76c8 x21: c87cf18c2690 [ 384.008086] x20: 00056d1fafa0 x19: 00056d1d76c0 x18: 8896d058 [ 384.008645] x17:
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
and everything seems to work fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954] x26: 00056d1d76c8 x25: c87cf18bdd10 x24: 0003 [ 384.007527] x23: 0001 x22: 00056d1d76c8 x21: c87cf18c2690 [ 384.008086] x20: 00056d1fafa0 x19: 00056d1d76c0 x18: 8896d058 [ 384.008645] x17: x16: x15: 617362755f5f0073 [ 384.009209] x14: 0001 x13: 0006 x12:
[Kernel-packages] [Bug 2051242] [NEW] Use consistent non-free/kernel Section
Public bug reported: Launchpad publication automatically publishes `Section: non-free/` to multiverse (with possibility to promote to restricted). Adding this in the packaging will help preventing LRM ever landing in universe or main by accident. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- 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/2051242 Title: Use consistent non-free/kernel Section Status in linux-restricted-modules package in Ubuntu: New Bug description: Launchpad publication automatically publishes `Section: non-free/` to multiverse (with possibility to promote to restricted). Adding this in the packaging will help preventing LRM ever landing in universe or main by accident. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2051242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
** Changed in: fabric-manager-525 (Ubuntu)
Status: New => Fix Released
** Changed in: libnvidia-nscq-450 (Ubuntu)
Status: New => Invalid
** Changed in: libnvidia-nscq-470 (Ubuntu)
Status: New => Invalid
--
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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
Invalid
Status in fabric-manager-470 package in Ubuntu:
Fix Released
Status in fabric-manager-515 package in Ubuntu:
Fix Released
Status in fabric-manager-525 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Invalid
Status in libnvidia-nscq-470 package in Ubuntu:
Invalid
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:
Triaged
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-515 package in Ubuntu:
Fix Released
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-450 source package in Bionic:
Fix Released
Status in fabric-manager-470 source package in Bionic:
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-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-470 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 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-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-525 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-470 source package in Focal:
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-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-470 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 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-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-525 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Jammy:
Fix Released
Status in fabric-manager-470 source package in Jammy:
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-450 source package in Jammy:
Fix Released
Status in libnvidia-nscq-470 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 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-515 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-515-server source package in Jammy:
Fix Released
Status in
[Kernel-packages] [Bug 2012529] Re: NVIDIA CVE-2023-{0180 to 0195}
** Changed in: fabric-manager-450 (Ubuntu)
Status: New => Invalid
** Changed in: fabric-manager-470 (Ubuntu)
Status: New => 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/2012529
Title:
NVIDIA CVE-2023-{0180 to 0195}
Status in fabric-manager-450 package in Ubuntu:
Invalid
Status in fabric-manager-470 package in Ubuntu:
Fix Released
Status in fabric-manager-515 package in Ubuntu:
Fix Released
Status in fabric-manager-525 package in Ubuntu:
New
Status in libnvidia-nscq-450 package in Ubuntu:
New
Status in libnvidia-nscq-470 package in Ubuntu:
New
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:
Triaged
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-515 package in Ubuntu:
Fix Released
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-450 source package in Bionic:
Fix Released
Status in fabric-manager-470 source package in Bionic:
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-450 source package in Bionic:
Fix Released
Status in libnvidia-nscq-470 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 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-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-525 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-470 source package in Focal:
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-450 source package in Focal:
Fix Released
Status in libnvidia-nscq-470 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 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-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-525 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-525-server source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Jammy:
Fix Released
Status in fabric-manager-470 source package in Jammy:
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-450 source package in Jammy:
Fix Released
Status in libnvidia-nscq-470 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 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-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-525 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-525-server
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038288] Re: Failed to start thermald.service
This bug exists on Kubuntu 23.10 as well, and, Fix: Run `sudo apt install dptfxtract` ... DOES work, on it as well. Kernel: 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/2038288 Title: Failed to start thermald.service Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: In Progress Bug description: Get lot of thermald errors logged with that Mate session on Mantic dbus-broker-launch[775]: Invalid group-name in /usr/share/dbus-1/system.d/org.freedesktop.thermald.conf +19: group="power" systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: sensor id 10 : No temp sysfs for reading raw temp thermald[892]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: Failed to start thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[982]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp thermald[982]: sensor id 10 : No temp sysfs for reading raw temp systemd[1]: thermald.service: Main process exited, code=killed, status=6/ABRT systemd[1]: thermald.service: Failed with result 'signal'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 2. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: sensor id 10 : No temp sysfs for reading raw temp thermald[1049]: *** stack smashing detected ***: terminated systemd[1]: Started thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 3. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: sensor id 10 : No temp sysfs for reading raw temp thermald[1117]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 4. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: Starting thermald.service - Thermal Daemon Service... systemd[1]: Started thermald.service - Thermal Daemon Service. thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: 24 CPUID levels; family:model:stepping 0x6:7a:1 (6:122:1) thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: sensor id 10 : No temp sysfs for reading raw temp thermald[1180]: *** stack smashing detected ***: terminated systemd[1]: thermald.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: thermald.service: Failed with result 'core-dump'. systemd[1]: thermald.service: Scheduled restart job, restart counter is at 5. systemd[1]: Stopped thermald.service - Thermal Daemon Service. systemd[1]: thermald.service: Start request repeated too quickly. systemd[1]: thermald.service: Failed
[Kernel-packages] [Bug 2051044] [NEW] missing depends on libnvidia-fbc1-545
Public bug reported:
[ Impact ]
* missing libnvidia-fbc1-545 library
[ Test Plan ]
* install 545 drivers, and observe that libnvidia-fbc1-545 is installed
[ Where problems could occur ]
* this fixes regression versus all other driver series
[ Other Info ]
Removal of ppc64le packaging incorrectly dropped
> Depends: libnvidia-fbc1-545 (= ${binary:Version}) [!ppc64el],
when clearly only the `[!ppc64el]` tag should have been dropped, as this
library does exist on all supported architectures.
reported via irc
** Affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
** Affects: nvidia-graphics-drivers-545 (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-545 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-545 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-545 (Ubuntu Noble)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Jammy)
** No longer affects: nvidia-graphics-drivers-545 (Ubuntu Mantic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu.
https://bugs.launchpad.net/bugs/2051044
Title:
missing depends on libnvidia-fbc1-545
Status in nvidia-graphics-drivers-545 package in Ubuntu:
New
Status in nvidia-graphics-drivers-545 source package in Noble:
New
Bug description:
[ Impact ]
* missing libnvidia-fbc1-545 library
[ Test Plan ]
* install 545 drivers, and observe that libnvidia-fbc1-545 is
installed
[ Where problems could occur ]
* this fixes regression versus all other driver series
[ Other Info ]
Removal of ppc64le packaging incorrectly dropped
> Depends: libnvidia-fbc1-545 (= ${binary:Version}) [!ppc64el],
when clearly only the `[!ppc64el]` tag should have been dropped, as
this library does exist on all supported architectures.
reported via irc
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2051044/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049688] Re: nvidia stoped working, , package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subp
copy of log file ** Attachment added: "gpu-manager-switch.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+attachment/5741801/+files/gpu-manager-switch.log -- 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/2049688 Title: nvidia stoped working,, package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia- dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: after latest update on 22.04 nvidia driver stoped working, gpu not found, cannot reinstall, even after upgrade I get : package nvidia- dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10. I also had errors with dependencies, when trying to reinstall and with kernel headers. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: nvidia-dkms-390 390.157-0ubuntu5.23.04.1 ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jan 17 22:54:39 2024 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-11-28 (50 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0ubuntu0.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu5.23.04.1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to lunar on 2024-01-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2049688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028985] Re: package libnvidia-compute-535-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also in packag
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2028985 Title: package libnvidia-compute-535-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/aarch64-linux- gnu/libcuda.so', which is also in package nvidia-l4t-cuda 35.3.1-20230319081403 Status in nvidia-graphics-drivers-535-server package in Ubuntu: Invalid Bug description: in an attempt to activate pytorch within current enviroment. after a failure to install nvidia-smi ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-535-server (not installed) Uname: Linux 5.10.104-tegra aarch64 ApportVersion: 2.20.11-0ubuntu27.27 AptOrdering: libnvidia-compute-535-server:arm64: Install nvidia-utils-535-server:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: skip Date: Fri Jul 28 14:54:25 2023 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-535-server_535.54.03-0ubuntu0.20.04.1_arm64.deb ... Unpacking libnvidia-compute-535-server:arm64 (535.54.03-0ubuntu0.20.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.20.04.1_arm64.deb (--unpack): trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also in package nvidia-l4t-cuda 35.3.1-20230319081403 ErrorMessage: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also in package nvidia-l4t-cuda 35.3.1-20230319081403 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-535-server Title: package libnvidia-compute-535-server (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/aarch64-linux-gnu/libcuda.so', which is also in package nvidia-l4t-cuda 35.3.1-20230319081403 UpgradeStatus: Upgraded to focal on 2023-07-24 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2028985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
Newer drivers are available now, and i'm not sure what is expected here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418
Title:
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
default
Status in linux-nvidia package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Incomplete
Bug description:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
on the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by
installing a service that generates an xorg config file dynamically
based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
I'll attach samples of those files here. Replacing the default Ubuntu
xorg.conf file with the sample xorg-nvidia.conf file on a default
Ubuntu Desktop install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2033418/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535
** Package changed: fabric-manager-535 (Ubuntu) => fabric-manager-525 (Ubuntu) ** Package changed: libnvidia-nscq-535 (Ubuntu) => libnvidia-nscq-525 (Ubuntu) ** Package changed: nvidia-graphics-drivers-535-server (Ubuntu) => nvidia-graphics-drivers-525-server (Ubuntu) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-525 package in Ubuntu: New Status in libnvidia-nscq-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: New Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2049635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033418] Re: Ubuntu desktop does not appear on DGX Station A100 discrete GPU by default
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: New => Incomplete
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-nvidia (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
https://bugs.launchpad.net/bugs/2033418
Title:
Ubuntu desktop does not appear on DGX Station A100 discrete GPU by
default
Status in linux-nvidia package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Incomplete
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Incomplete
Bug description:
The DGX Station A10 has various display options. The BMC provides an
emulated device (Aspeed controller), a physical BMC controller (NVIDIA
Quadro T1000 Mobile), and a discrete GPU card with 4 DisplayPort
outputs (A100 SXM4 80GB). See the user guide[*] for a diagram.
In a default Ubuntu Desktop 22.04 ('jammy') install, nothing appears
on the A100 DisplayPort output.
NVIDIA DGX OS - a derivative of Ubuntu - works around this by
installing a service that generates an xorg config file dynamically
based on the "OnBrd/Ext VGA Select" setting (aka "dmidecode -t 11").
I'll attach samples of those files here. Replacing the default Ubuntu
xorg.conf file with the sample xorg-nvidia.conf file on a default
Ubuntu Desktop install is confirmed to enable output.
[*] https://docs.nvidia.com/dgx/dgx-station-a100-user-guide/getting-
started-station-a100.html
(Note: split from bug 2031367)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2033418/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049603] Re: nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble)
Status: New => Fix Released
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Noble)
Status: New => Fix Released
** Changed in: nvidia-graphics-drivers-545 (Ubuntu Noble)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2049603
Title:
nvidia-dkms-535 FTBS on noble with the latest 6.7 kernel on arm64
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-545 package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-535 source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Noble:
Fix Released
Status in nvidia-graphics-drivers-545 source package in Noble:
Triaged
Bug description:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only
in the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
<>/build/nvidia/535.146.02/build/Module.symvers -T
<>/build/nvidia/535.146.02/build/modules.order -i Module.symvers -e
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol
'screen_info'
This change was introduced by: b8466fe82b79 ("efi: move screen_info
into efi init code")
This happens only on arm64, where the symbol is defined.
[Fix]
Avoid using screen_info in the nvidia-dkms-535 driver.
[Regression potential]
We may disable certain features in the 535 driver, or even have an
unusable driver, unless a proper workaround/solution is provided.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2049603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028770] Re: package nvidia-dkms-525-server (not installed) failed to install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возврати
no support is provided for non-ubuntu-archive kernels. please use precompiled nvidia drivers for Ubuntu Archive kernel via `ubuntu-drivers` ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525-server in Ubuntu. https://bugs.launchpad.net/bugs/2028770 Title: package nvidia-dkms-525-server (not installed) failed to install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возвратил код ошибки 10 Status in nvidia-graphics-drivers-525-server package in Ubuntu: Invalid Bug description: 1 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525-server (not installed) ProcVersionSignature: Ubuntu 5.19.0-50.50-generic 5.19.17 Uname: Linux 5.19.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Jul 26 11:57:56 2023 ErrorMessage: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возвратил код ошибки 10 InstallationDate: Installed on 2023-04-13 (104 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-525-server Title: package nvidia-dkms-525-server (not installed) failed to install/upgrade: подпроцесс из пакета nvidia-dkms-525-server установлен сценарий post-installation возвратил код ошибки 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2028770/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2029934] Re: arm64 AWS host hangs during modprobe nvidia on lunar and mantic
since then, we had multiple glibc srus; kernel sru's and most recently new release of 535-server. can i request for this to be retested again? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2029934 Title: arm64 AWS host hangs during modprobe nvidia on lunar and mantic Status in linux-aws package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-525-server package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: Loading the nvidia driver dkms modules with "modprove nvidia" will result in the host hanging and being completely unusable. This was reproduced using both the linux generic and linux-aws kernels on lunar and mantic using an AWS g5g.xlarge instance. To reproduce using the generic kernel: # Deploy a arm64 host with an nvidia gpu, such as an AWS g5g.xlarge. # Install the linux generic kernel from lunar-updates: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y -o DPkg::Options::=--force-confold linux-generic # Boot to the linux-generic kernel (this can be accomplished by removing the existing kernel, in this case it was the linux-aws 6.2.0-1008-aws kernel) $ sudo DEBIAN_FRONTEND=noninteractive apt-get purge -y -o DPkg::Options::=--force-confold linux-aws linux-aws-headers-6.2.0-1008 linux-headers-6.2.0-1008-aws linux-headers-aws linux-image-6.2.0-1008-aws linux-image-aws linux-modules-6.2.0-1008-aws linux-headers-6.2.0-1008-aws linux-image-6.2.0-1008-aws linux-modules-6.2.0-1008-aws $ reboot # Install the Nvidia 535-server driver DKMS package: $ sudo DEBIAN_FRONTEND=noninteractive apt-get install -y nvidia-driver-535-server # Enable the driver $ sudo modprobe nvidia # At this point the system will hang and never return. # A reboot instead of a modprobe will result in a system that never boots up all the way. I was able to recover the console logs from such a system and found (the full captured log is attached): [1.964942] nvidia: loading out-of-tree module taints kernel. [1.965475] nvidia: module license 'NVIDIA' taints kernel. [1.965905] Disabling lock debugging due to kernel taint [1.980905] nvidia: module verification failed: signature and/or required key missing - tainting kernel [2.012067] nvidia-nvlink: Nvlink Core is being initialized, major device number 510 [2.012715] [ 62.025143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 62.025807] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=3301 [ 62.026516](detected by 0, t=15003 jiffies, g=-699, q=216 ncpus=4) [ 62.027018] Task dump for CPU 3: [ 62.027290] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000e [ 62.028066] Call trace: [ 62.028273] __switch_to+0xbc/0x100 [ 62.028567] 0x228 Timed out for waiting the udev queue being empty. Timed out for waiting the udev queue being empty. [ 242.045143] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks: [ 242.045655] rcu: 3-...0: (14 ticks this GP) idle=c04c/1/0x4000 softirq=653/654 fqs=12303 [ 242.046373](detected by 1, t=60008 jiffies, g=-699, q=937 ncpus=4) [ 242.046874] Task dump for CPU 3: [ 242.047146] task:systemd-udevd state:R running task stack:0 pid:164 ppid:144flags:0x000f [ 242.047922] Call trace: [ 242.048128] __switch_to+0xbc/0x100 [ 242.048417] 0x228 Timed out for waiting the udev queue being empty. Begin: Loading essential drivers ... [ 384.001142] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [modprobe:215] [ 384.001738] Modules linked in: nvidia(POE+) crct10dif_ce video polyval_ce polyval_generic drm_kms_helper ghash_ce syscopyarea sm4 sysfillrect sha2_ce sysimgblt sha256_arm64 sha1_ce drm nvme nvme_core ena nvme_common aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 384.003513] CPU: 2 PID: 215 Comm: modprobe Tainted: P OE 6.2.0-26-generic #26-Ubuntu [ 384.004210] Hardware name: Amazon EC2 g5g.xlarge/, BIOS 1.0 11/1/2018 [ 384.004715] pstate: 8045 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 384.005259] pc : smp_call_function_many_cond+0x1b4/0x4b4 [ 384.005683] lr : smp_call_function_many_cond+0x1d0/0x4b4 [ 384.006108] sp : 889a3a70 [ 384.006381] x29: 889a3a70 x28: 0003 x27: 00056d1fafa0 [ 384.006954] x26: 00056d1d76c8 x25: c87cf18bdd10 x24: 0003 [ 384.007527] x23: 0001 x22: 00056d1d76c8 x21: c87cf18c2690 [ 384.008086] x20: 00056d1fafa0 x19: 00056d1d76c0 x18: 8896d058 [ 384.008645] x17: x16:
[Kernel-packages] [Bug 2016329] Re: package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to install/upgrade: nvidia-dkms-525-server paketi post-installation betiği kuruldu alt süreci 10 h
please reboot, and upgrade your kernel. please use precompiled nvidia drivers for Ubuntu Archive kernels via `ubuntu-drivers` or "Additional Drivers" GUI. ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525-server in Ubuntu. https://bugs.launchpad.net/bugs/2016329 Title: package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to install/upgrade: nvidia-dkms-525-server paketi post-installation betiği kuruldu alt süreci 10 hatalı çıkış kodu ile sona erdi Status in nvidia-graphics-drivers-525-server package in Ubuntu: Invalid Bug description: ı dont understand much ProblemType: Package DistroRelease: Ubuntu 22.10 Package: nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87 Uname: Linux 5.15.0-69-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 14 21:50:14 2023 ErrorMessage: nvidia-dkms-525-server paketi post-installation betiği kuruldu alt süreci 10 hatalı çıkış kodu ile sona erdi InstallationDate: Installed on 2023-04-13 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: nvidia-graphics-drivers-525-server Title: package nvidia-dkms-525-server 525.105.17-0ubuntu0.22.10.1 failed to install/upgrade: nvidia-dkms-525-server paketi post-installation betiği kuruldu alt süreci 10 hatalı çıkış kodu ile sona erdi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2016329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039470] Re: package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-525-server script post-installatio
ERROR (dkms apport): kernel package linux-headers-6.4.9-060409-generic is not supported no support is provided for non-ubuntu-archive kernels. please use precompiled nvidia drivers for Ubuntu Archive kernel via `ubuntu-drivers` ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525-server in Ubuntu. https://bugs.launchpad.net/bugs/2039470 Title: package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia- dkms-525-server script post-installation devolvió el código de salida de error 10 Status in nvidia-graphics-drivers-525-server package in Ubuntu: Invalid Bug description: I tried to install the driver for my GTM-1650 video card and received the following error: pk-client-error-quark ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 Uname: Linux 6.4.9-060409-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Oct 16 09:58:54 2023 ErrorMessage: el subproceso instalado paquete nvidia-dkms-525-server script post-installation devolvió el código de salida de error 10 InstallationDate: Installed on 2023-01-04 (284 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: nvidia-graphics-drivers-525-server Title: package nvidia-dkms-525-server 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: el subproceso instalado paquete nvidia-dkms-525-server script post-installation devolvió el código de salida de error 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-525-server/+bug/2039470/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2025243] Re: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal
** Changed in: fabric-manager-525 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libnvidia-nscq-525 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Kinetic) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525 (Ubuntu Lunar) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-525-server (Ubuntu Jammy) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-525-server (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-525 in Ubuntu. https://bugs.launchpad.net/bugs/2025243 Title: Introduce the NVIDIA 535-server ERD driver series, and enable arm64 for 535, 525, 525-server in Focal Status in fabric-manager-525 package in Ubuntu: Fix Released Status in libnvidia-nscq-525 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 nvidia-graphics-drivers-535 package in Ubuntu: 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 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 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 nvidia-graphics-drivers-525 source package in Kinetic: Fix Released Status in nvidia-graphics-drivers-525-server source package in Kinetic: Won't Fix Status in nvidia-graphics-drivers-525 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-525-server source package in Lunar: Fix Released Bug description: Introduce the NVIDIA 535-server ERD driver series, enabling the -open kernel module. Release notes: https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-54-03/index.html Changelogs for the drivers in focal: nvidia-graphics-drivers-525 (525.125.06-0ubuntu0.20.04.3) focal; urgency=medium [ Dimitri John Ledkov ] * debian: - Enable arm64 builds (LP: #2025243). * debian/templates: - Encode amd64-only libraries and binaries. nvidia-graphics-drivers-535 (535.54.03-0ubuntu0.20.04.4) focal; urgency=medium [ Dimitri John Ledkov ] * templates: encode amd64-only libraries and binaries * debian: Enable arm64 builds (LP: #2025243). -- Alberto Milone Mon, 03 Jul 2023 13:34:05 + nvidia-graphics-drivers-525-server (525.125.06-0ubuntu0.20.04.2) focal; urgency=medium [ Alberto Milone ] * debian/rules: - Drop the unused generate-nvidia-icd-json target; [ Dimitri John Ledkov ] * debian: - Enable arm64 builds (LP: #2025243). * debian/templates: - Encode amd64-only libraries and binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-525/+bug/2025243/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049635] Re: Roll UDA & ERD drivers from 525 to 535
** Also affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-535 package in Ubuntu: New Status in libnvidia-nscq-535 package in Ubuntu: New Status in nvidia-graphics-drivers-525 package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2049635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Same for 515-server: $ reverse-depends src:nvidia-graphics-drivers-515-server Reverse-Depends === * libnvidia-decode-510-server (for libnvidia-decode-515-server) * libnvidia-encode-510-server (for libnvidia-encode-515-server) these too have transitionals via 515-server to 525-server, in a similar manner, in jammy chroot: # apt install libnvidia-decode-510-server libnvidia-encode-510-server Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libbsd0 libmd0 libnvidia-compute-525-server libnvidia-decode-515-server libnvidia-decode-525-server libnvidia-encode-515-server libnvidia-encode-525-server libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 The following NEW packages will be installed: libbsd0 libmd0 libnvidia-compute-525-server libnvidia-decode-510-server libnvidia-decode-515-server libnvidia-decode-525-server libnvidia-encode-510-server libnvidia-encode-515-server libnvidia-encode-525-server libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: Incomplete => Triaged ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
About this: $ reverse-depends src:nvidia-graphics-drivers-460 Reverse-Depends === * libnvidia-decode-455 (for libnvidia-decode-460) * libnvidia-encode-455 (for libnvidia-encode-460) * nvidia-headless-455 [amd64] (for nvidia-headless-460) * nvidia-kernel-common-455 [amd64] Packages without architectures listed are reverse-dependencies in: amd64, i386 in all rmadison releases the above -455 binary packages have versions 460.91.03-*, meaning they got transitioned / taken over by nvidia-graphics-drivers-460. in turn the equivalent -460 packages, have versions 470.* meaning they all got taken over by nvidia-graphics-drivers-470 (still supported). This is true in all updates, but also jammy release pocket. This means it is safe to drop them from noble. In jammy chroot: (jammy-amd64)root@xnox-Inspiron-7400:~# apt install libnvidia-decode-455 libnvidia-encode-455 nvidia-headless-455 nvidia-kernel-common-455 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: cpp-12 dctrl-tools dkms gcc-12 kmod libasan8 libbsd0 libgcc-12-dev libmd0 libnvidia-cfg1-470 libnvidia-compute-470 libnvidia-decode-460 libnvidia-decode-470 libnvidia-encode-460 libnvidia-encode-470 libpciaccess0 libtsan2 libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxext6 nvidia-compute-utils-470 nvidia-dkms-470 nvidia-headless-460 nvidia-headless-470 nvidia-headless-no-dkms-470 nvidia-kernel-common-460 nvidia-kernel-common-470 nvidia-kernel-source-470 Please let me know if above inspection is sufficient, or if you want me to upload nvidia-graphics-drivers-470 that explicitly produces the 455 transitionals, to avoid double source/binary package jump chain? ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Incomplete => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/2048087 Title: RM: obsolete & superseded nvidia-graphics-drivers, leftovers Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Fix Released Bug description: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames Currently supported drivers are: nvidia-graphics-drivers-470 nvidia-graphics-drivers-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server all other drivers are superseded binaries, from obsolete and/or short- lived nvidia-graphics-drivers are however still published in the archive. please remove them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2048087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048901] Re: Update the NVIDIA ERD 535 series to 535.154.05
** Changed in: fabric-manager-535 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: libnvidia-nscq-535 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2048901 Title: Update the NVIDIA ERD 535 series to 535.154.05 Status in fabric-manager-535 package in Ubuntu: Fix Released Status in libnvidia-nscq-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Committed Status in fabric-manager-535 source package in Bionic: Fix Released Status in libnvidia-nscq-535 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-535 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Bionic: Fix Released Status in fabric-manager-535 source package in Focal: Fix Released Status in libnvidia-nscq-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in fabric-manager-535 source package in Jammy: Fix Released Status in libnvidia-nscq-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in fabric-manager-535 source package in Mantic: Fix Released Status in libnvidia-nscq-535 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Released Status in nvidia-graphics-drivers-535-server source package in Mantic: Fix Released Status in fabric-manager-535 source package in Noble: Fix Released Status in libnvidia-nscq-535 source package in Noble: Fix Released Status in nvidia-graphics-drivers-535 source package in Noble: Fix Committed Status in nvidia-graphics-drivers-535-server source package in Noble: Fix Committed 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-535/+bug/2048901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace
AppArmor does mediation post symlink resolution. Using symlinks to move a file or directories location means the profile for the application needs to be updated. That is why you see the failure when using symlinks to move those folders, those applications have not been give access to the location you have moved the files to. -- 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/1991691 Title: cannot change mount namespace Status in Linux: Fix Released Status in linux package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049922] [NEW] PCI ATS quirk patch needed for IDPF
Public bug reported: [Impact] * Request from Google to include Intel patches for IDPF support if used from out-of-tree module to prevent system instability [Fix] * Upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd [Test Case] * Compile test * Boot test * Test on non-IDPF instance [Where things could go wrong] * Low chance of regression, changes very isolated [Other Info] * SF #00376470 ** Affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2049922 Title: PCI ATS quirk patch needed for IDPF Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Bionic: New Status in linux-gcp source package in Focal: New Bug description: [Impact] * Request from Google to include Intel patches for IDPF support if used from out-of-tree module to prevent system instability [Fix] * Upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.7=a18615b1cfc04f00548c60eb9a77e0ce56e848fd [Test Case] * Compile test * Boot test * Test on non-IDPF instance [Where things could go wrong] * Low chance of regression, changes very isolated [Other Info] * SF #00376470 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2049922/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
** Description changed: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] - * Cherry pick commits from net-next, - b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 + * Mantic - 24 clean cherry-picks, 1 backport from upstream + * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested - * To be tested by Google + * Tested internally and by Google using neper (https://github.com/google/neper) + * Networking is functional and throughput is as expected [Where things could go wrong] - * Low chance of regression, new driver is isolated and will be tested by - Google + * Low chance of regression, changes have been upstream since 6.6 kernel + * Bulk of changes in IDPF driver + * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
** No longer affects: linux-gcp (Ubuntu Focal) ** No longer affects: linux-gcp (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: New Status in linux-gcp source package in Mantic: New Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Cherry pick commits from net-next, b6a7eeb44a6a8b1ea2dea78b5de448d86eb0bd96 [Test Case] * Compile tested * Boot tested * To be tested by Google [Where things could go wrong] * Low chance of regression, new driver is isolated and will be tested by Google [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049390] Re: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3
I am not sure, which will need to be doublechecked but this may affect boot testing, regression testing, device cert testing that do look for these messages. Hopefully they all know how to hunt for these messages elsehow, rather than via the graphical console log capture. -- 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/2049390 Title: Please change CONFIG_CONSOLE_LOGLEVEL_QUIET to 3 Status in linux package in Ubuntu: Confirmed Bug description: The Ubuntu Desktop boot isn't flickerfree today as reported on bug #1970069 , one of the reason is that kernel error messages are often being logged and not filtered out by our default loglevel (one example with usb messages on https://launchpadlibrarian.net/598152686/20220422_014058.jpg) Fedora is using CONFIG_CONSOLE_LOGLEVEL_QUIET=3 (instead of 4 which is the default), they change it 5 years ago (https://src.fedoraproject.org/rpms/kernel/c/838818e5), the rational is in the commit message that added the configuration option to the kernel > This for example will allow distros which want quiet to really mean quiet to set > CONSOLE_LOGLEVEL_QUIET so that only messages with a higher severity then KERN_ERR (CRIT, ALERT, EMERG) > get printed, avoiding an endless game of whack-a-mole silencing harmless error messages. ' Could we also get the default change to 3 in Ubuntu? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049390/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049635] [NEW] Roll UDA & ERD drivers from 525 to 535
Public bug reported: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. ** Affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: fabric-manager-535 (Ubuntu) Importance: Undecided Status: New ** Also affects: libnvidia-nscq-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2049635 Title: Roll UDA & ERD drivers from 525 to 535 Status in fabric-manager-535 package in Ubuntu: New Status in libnvidia-nscq-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: [ Impact ] * 525 series of drivers is now end of life, roll these to 535 via transitional packages * 535 is a longterm branch [ Test Plan ] * Install 525, 525-open, 525-server drivers with LRM using ubuntu-drivers * Enable proposed * apt full-upgrade should upgrade both userspace drivers and LRM to respective 535, 535-open, 535-server drivers [ Where problems could occur ] * Virtual provides in the past have caused kernel flavour switch during such rolls before, this remains unresolved. * All cards supported by 525 series of the driver are supported by the 535 driver, thus there is no loss of functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-535/+bug/2049635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032672] Re: Update the 535 UDA and 535 ERD NVIDIA driver series in Bionic, Focal, and Jammy, Lunar
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-535-server (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-535 in Ubuntu.
https://bugs.launchpad.net/bugs/2032672
Title:
Update the 535 UDA and 535 ERD NVIDIA driver series in Bionic, Focal,
and Jammy, Lunar
Status in nvidia-graphics-drivers-535 package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535-server package in Ubuntu:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-535-server source package in Bionic:
In Progress
Status in nvidia-graphics-drivers-535 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Jammy:
Fix Released
Status in nvidia-graphics-drivers-535 source package in Lunar:
Fix Released
Status in nvidia-graphics-drivers-535-server source package in Lunar:
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]
[ Alberto Milone ]
* New upstream release (LP: #2025243).
* debian/rules{.defs}:
- Adjust to the changes on the Nvidia servers.
* debian/rules:
- Do not start the systemd services on installation or upgrade, as this
can
lead to a black screen.
[ Dimitri John Ledkov ]
* debian/templates/control.in:
- Add breaks on identical firmware files from other flavour.
When 535 & 535-server driver versions happen to be at an identical
upstream version, they both ship identical firmware files on disk at
the same path. When a user attempts to install two drivers at the same
time, this results in dpkg file conflict. Allow replacing one firmware
with another (LP: #2026622).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2032672/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027746] Re: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2027746 Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 Status in nvidia-graphics-drivers-535-server package in Ubuntu: Fix Released Bug description: It occurs on start up[ ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 13 16:04:37 2023 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking libnvidia-compute-535-server:amd64 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 InstallationDate: Installed on 2023-06-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535-server Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2027746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042426] Re: Introduce the new NVIDIA 545 driver series
** Package changed: nvidia-graphics-drivers-535 (Ubuntu) => nvidia- graphics-drivers-545 (Ubuntu) ** Changed in: nvidia-graphics-drivers-545 (Ubuntu) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Lunar) Status: In Progress => Won't Fix ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-545 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042426 Title: Introduce the new NVIDIA 545 driver series Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-545 source package in Lunar: Won't Fix Status in nvidia-graphics-drivers-545 source package in Mantic: Fix Committed Bug description: Introduce the new NVIDIA 545 driver series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545/+bug/2042426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => John Cabaj (john-cabaj) ** Changed in: linux-gcp (Ubuntu Mantic) Assignee: (unassigned) => John Cabaj (john-cabaj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040522] Re: gVNIC DQO-QPL feature
** Changed in: linux-gcp (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux-gcp (Ubuntu Lunar) Status: New => Won't Fix ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Mantic) Status: New => In Progress ** Description changed: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * All cherry-picks from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] - * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. + * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 ** Description changed: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] - * All cherry-picks from upstream + * Mantic: all clean cherry-picks from upstream + * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: In Progress Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: In Progress Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049082] [NEW] FIPS kernels should default to fips mode
Public bug reported: [ Impact ] * Ubuntu builds regular kernels without FIPS configuration enabled at compile time * Canonical also builds FIPS kernels with FIPS configuration enabled at compile time, intended to only be used in FIPS mode * Currently, due to upstream patches, this thus requires additional runtime configuration of bootloader to always specify `fips=1` to turn on FIPS mode at runtime, as it is off by default * This adds additional complexity when performing autopkgtests, creating Ubuntu Core images, switching to/from Pro FIPS, drafting and verify security policy * Instead all of this can be avoided, if fips=1 is the implicit default for the FIPS kernels. * This has no effect on regular kernels [ Test Plan ] * generic kernel build should have no effect / no changes, as dead code is patched. I.e. /proc/sys/crypto/fips_enabled not present * fips kernel build should have the following content in the /proc/sys/crypto/fips_enabled file: + without any fips= setting fips_enabled should be set to 1 (new behaviour) + with fips=1 setting fips_enabled should be set to 1 (double check existing behaviour) + with fips=0 setting fips_enabled should be set to 0 (double check existing behaviour) * pro client can continue to set fips=1, just in case, as older certified fips kernels still require this setting. [ Where problems could occur ] * Some 3rd party tools do not consult /proc/sys/crypto/fips_enabled and rely on access to the kernel cmdline "fips=1", they are wrong, but also there is no current intention to break any such users, as pro client will continue to set fips=1 for now. [ Other Info ] * Intention is to land this for noble; for the future noble fips kernels. FIPS Updates kernels, if at all possible. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: fips -- 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/2049082 Title: FIPS kernels should default to fips mode Status in linux package in Ubuntu: New Bug description: [ Impact ] * Ubuntu builds regular kernels without FIPS configuration enabled at compile time * Canonical also builds FIPS kernels with FIPS configuration enabled at compile time, intended to only be used in FIPS mode * Currently, due to upstream patches, this thus requires additional runtime configuration of bootloader to always specify `fips=1` to turn on FIPS mode at runtime, as it is off by default * This adds additional complexity when performing autopkgtests, creating Ubuntu Core images, switching to/from Pro FIPS, drafting and verify security policy * Instead all of this can be avoided, if fips=1 is the implicit default for the FIPS kernels. * This has no effect on regular kernels [ Test Plan ] * generic kernel build should have no effect / no changes, as dead code is patched. I.e. /proc/sys/crypto/fips_enabled not present * fips kernel build should have the following content in the /proc/sys/crypto/fips_enabled file: + without any fips= setting fips_enabled should be set to 1 (new behaviour) + with fips=1 setting fips_enabled should be set to 1 (double check existing behaviour) + with fips=0 setting fips_enabled should be set to 0 (double check existing behaviour) * pro client can continue to set fips=1, just in case, as older certified fips kernels still require this setting. [ Where problems could occur ] * Some 3rd party tools do not consult /proc/sys/crypto/fips_enabled and rely on access to the kernel cmdline "fips=1", they are wrong, but also there is no current intention to break any such users, as pro client will continue to set fips=1 for now. [ Other Info ] * Intention is to land this for noble; for the future noble fips kernels. FIPS Updates kernels, if at all possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042426] Re: Introduce the new NVIDIA 545 driver series
** No longer affects: nvidia-graphics-drivers-535 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2042426 Title: Introduce the new NVIDIA 545 driver series Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Jammy: In Progress Status in nvidia-graphics-drivers-535 source package in Lunar: In Progress Status in nvidia-graphics-drivers-535 source package in Mantic: In Progress Bug description: Introduce the new NVIDIA 545 driver series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2042426/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028125] Re: Update the NVIDIA 535 series to 535.86.05
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu) Status: Triaged => Invalid ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Status: New => Invalid ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2028125 Title: Update the NVIDIA 535 series to 535.86.05 Status in fabric-manager-535 package in Ubuntu: Fix Released Status in libnvidia-nscq-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-535-server package in Ubuntu: Invalid Status in fabric-manager-535 source package in Focal: Fix Released Status in libnvidia-nscq-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Invalid Status in fabric-manager-535 source package in Jammy: Fix Released Status in libnvidia-nscq-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Invalid Status in fabric-manager-535 source package in Kinetic: Won't Fix Status in libnvidia-nscq-535 source package in Kinetic: Won't Fix Status in nvidia-graphics-drivers-535 source package in Kinetic: Won't Fix Status in nvidia-graphics-drivers-535-server source package in Kinetic: Won't Fix Status in fabric-manager-535 source package in Lunar: Fix Released Status in libnvidia-nscq-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Invalid 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-535/+bug/2028125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048768] Re: Autopkgtest failures on amd64
we area bout to move to v6.7 kernel as v6.6 is sort of dead to us already. Are you able to test with linux-generic-wip (linux-unstable source) from this ppa https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/unstable?field.series_filter=noble ? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2048768 Title: Autopkgtest failures on amd64 Status in linux package in Ubuntu: New Status in llvm-toolchain-14 package in Ubuntu: New Status in linux source package in Noble: New Status in llvm-toolchain-14 source package in Noble: New Bug description: Some tests related to the address sanitizer are occasionally failing on amd64 (also for llvm-toolchain-15 and 16): -- FAIL: LLVM regression suite :: test_leaksan.c (38 of 45) 746s TEST 'LLVM regression suite :: test_leaksan.c' FAILED 746s Script: 746s -- 746s : 'RUN: at line 4'; /usr/bin/clang-14 -o /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp -fsanitize=address -g /tmp/autopkgtest.gHVujV/autopkgtest_tmp/tests/test_leaksan.c 746s : 'RUN: at line 5'; env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s : 'RUN: at line 6'; grep -q "detected memory leaks" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out 746s -- 746s Exit Code: 139 746s 746s Command Output (stderr): 746s -- 746s /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.script: line 3: 3335 Segmentation fault (core dumped) env ASAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp 2>&1 > /tmp/autopkgtest.gHVujV/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp.out -- If you run the test manually you'll notice that it works but eventually crashes: ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8631==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5e9c3441ed12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5e9c3445acb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x7e84e1e280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp = ==8634==ERROR: LeakSanitizer: detected memory leaks Direct leak of 7 byte(s) in 1 object(s) allocated from: #0 0x5f19be5f6d12 in __interceptor_malloc (/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output/test_leaksan.c.tmp+0xa3d12) (BuildId: 6f71ac388125722ade1ea86ee3661c0d884dd193) #1 0x5f19be632cb8 in main /tmp/autopkgtest.oXC2FP/autopkgtest_tmp/tests/test_leaksan.c:13:7 #2 0x77c7d3c280cf (/lib/x86_64-linux-gnu/libc.so.6+0x280cf) (BuildId: f0b834daa3d05a80967e9ec2f990a1ea71c958fa) SUMMARY: AddressSanitizer: 7 byte(s) leaked in 1 allocation(s). ubuntu@autopkgtest:/tmp/autopkgtest.oXC2FP/autopkgtest_tmp/build/tests/Output$ ./test_leaksan.c.tmp Segmentation fault (core dumped) After some investigation I found that it will not fail with ASLR disabled: sudo sysctl kernel.randomize_va_space=0 while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done If you enable ASLR it will start to crash: $ sudo sysctl kernel.randomize_va_space=2 $ while : ; do env ASAN_OPTIONS="log_path=stdout:exitcode=0" ./test_leaksan.c.tmp >/dev/null; if [ $? -ne 0 ] ; then echo crashed ; fi done Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed Segmentation fault (core dumped) crashed If you enable ASLR again and run it with "setarch -R" (to disable ASLR for this binary), it will also not crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
