[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 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 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 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 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 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 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 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 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 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 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 :
[Kernel-packages] [Bug 2048782] [NEW] RM obsolete auxiliary packages for removed nvidia server ERD drivers
Public bug reported: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too ** Affects: fabric-manager-450 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: fabric-manager-460 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: fabric-manager-510 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: fabric-manager-515 (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: libnvidia-nscq-450 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: libnvidia-nscq-460 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: libnvidia-nscq-510 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: libnvidia-nscq-515 (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: libnvidia-nscq-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: fabric-manager-510 (Ubuntu) Status: New => Triaged ** Changed in: libnvidia-nscq-510 (Ubuntu) Status: New => Triaged ** Also affects: fabric-manager-515 (Ubuntu) Importance: Undecided Status: New ** Changed in: fabric-manager-515 (Ubuntu) Status: New => Incomplete ** Also affects: libnvidia-nscq-515 (Ubuntu) Importance: Undecided Status: New ** Changed in: libnvidia-nscq-515 (Ubuntu) Status: New => Incomplete ** Also affects: fabric-manager-460 (Ubuntu) Importance: Undecided Status: New ** Changed in: fabric-manager-460 (Ubuntu) Status: New => Triaged ** Also affects: libnvidia-nscq-460 (Ubuntu) Importance: Undecided Status: New ** Changed in: libnvidia-nscq-460 (Ubuntu) Status: New => Triaged ** Also affects: libnvidia-nscq-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: libnvidia-nscq-450 (Ubuntu) Status: New => Triaged ** Also affects: fabric-manager-450 (Ubuntu) Importance: Undecided Status: New ** Changed in: fabric-manager-450 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to fabric-manager-515 in Ubuntu. https://bugs.launchpad.net/bugs/2048782 Title: RM obsolete auxiliary packages for removed nvidia server ERD drivers Status in fabric-manager-450 package in Ubuntu: Triaged Status in fabric-manager-460 package in Ubuntu: Triaged Status in fabric-manager-510 package in Ubuntu: Triaged Status in fabric-manager-515 package in Ubuntu: Incomplete Status in libnvidia-nscq-450 package in Ubuntu: Triaged Status in libnvidia-nscq-460 package in Ubuntu: Triaged Status in libnvidia-nscq-510 package in Ubuntu: Triaged Status in libnvidia-nscq-515 package in Ubuntu: Incomplete Bug description: RM obsolete auxiliary packages for removed nvidia server ERD drivers. libnvidia-nscq & fabric-manager are userspace packages related to the ERD drivers. Once ERD drivers are removed from the archive so should these packages too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450/+bug/2048782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
i think src:nvidia-graphics-drivers-450 is ready to go -- 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: Triaged 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 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
IBM Z are deployed for longer timeframes than usually anticipated. And I don't think we will ever be able to get a straight answer about this. I am proposing to turn off both COMPAT and COMPAT_32BIT_TIME on s390x in noble. If any useful production instances of software are identified that require either of these; and cannot run on Jammy, or in a VM, I will gladly SRU kernel config change to turn either or both of these options back on in noble. -- 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/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Description changed: 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-525 - nvidia-graphics-drivers-535 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server - nvidia-graphics-drivers-535-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. -- 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: Triaged Status in nvidia-graphics-drivers-430 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged 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
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-515-server (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: New => Triaged -- 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: Triaged Status in nvidia-graphics-drivers-430 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-455 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-515-server package in Ubuntu: Triaged Status in nvidia-graphics-drivers-530 package in Ubuntu: Triaged 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-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-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] [NEW] RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Public bug reported: 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-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-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. ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-515-server (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-440 (Ubuntu) Importance: Undecided Status: New ** Description changed: https://packages.ubuntu.com/search?suite=noble=all=any=nvidia- graphics-drivers=sourcenames - 450 & 470-server are the oldest supported nvidia graphics drivers by the - kernel team + Currently supported drivers are: + nvidia-graphics-drivers-470 + nvidia-graphics-drivers-525 + nvidia-graphics-drivers-525 + nvidia-graphics-drivers-535 + nvidia-graphics-drivers-535 + nvidia-graphics-drivers-470-server + nvidia-graphics-drivers-525-server + nvidia-graphics-drivers-535-server + nvidia-graphics-drivers-535-server - superseded binaries, from obsolete nvidia-graphics-drivers are however still published in the archive. + superseded binaries, from obsolete and/or short-lived nvidia-graphics- + drivers are however still published in the archive. + please remove them. ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-515-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-530 (Ubuntu) Importance: Undecided Status: New ** Description changed: 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-525 nvidia-graphics-drivers-535 nvidia-graphics-drivers-535 nvidia-graphics-drivers-470-server nvidia-graphics-drivers-525-server nvidia-graphics-drivers-535-server nvidia-graphics-drivers-535-server - superseded binaries, from obsolete and/or short-lived nvidia-graphics- - drivers are however still published in the archive. + 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. -- 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: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in nvidia-graphics-drivers-450 package in Ubuntu: New Status in nvidia-graphics-drivers-455 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package
[Kernel-packages] [Bug 2045913] Re: Update the NVIDIA 535 driver
** Changed in: nvidia-graphics-drivers-535 (Ubuntu Mantic) Status: In Progress => Fix Committed ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-535 (Ubuntu Noble) Importance: High Assignee: Alberto Milone (albertomilone) Status: In Progress ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Noble) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) 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/2045913 Title: Update the NVIDIA 535 driver Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Committed Status in nvidia-graphics-drivers-535 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Committed Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Committed Status in nvidia-graphics-drivers-535 source package in Mantic: Fix Committed Status in nvidia-graphics-drivers-535 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] 535.146.02 * New upstream release (LP: #2045913): - Fixed a bug that could cause some multi-GPU systems to crash on suspend. - Fixed a bug that could cause the system to crash when an application is run with __NV_PRIME_RENDER_OFFLOAD=1. - Fixed a bug which prevented application profiles from getting applied to PRIME Render Offloaded applications running via Wine. - Disabled PRIME Display Offload Sink support for virtual displays on datacenter GPUs. This prevents unusable desktop layouts from getting automatically configured on systems with a mix of physical and virtual displays. - Fixed a bug that caused high CPU usage during system suspend, which could lead to the system not entering s2idle in some cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2045913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046444] Re: Missing tp_smapi dkms module in 6.5-hwe
duplicate of https://bugs.launchpad.net/ubuntu/+source/tp- smapi/+bug/2046450 ** Package changed: linux-signed-hwe-6.5 (Ubuntu) => linux-hwe-6.5 (Ubuntu) ** Package changed: linux-hwe-6.5 (Ubuntu) => tp-smapi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2046444 Title: Missing tp_smapi dkms module in 6.5-hwe Status in tp-smapi package in Ubuntu: New Bug description: During the 6.5-hwe migration test, I found that there was a missing dkms which is tp_smapi. I just randomly picked some test results for your reference. https://certification.canonical.com/hardware/202106-29206/submission/344990/test/71814/result/37864278/ https://certification.canonical.com/hardware/202005-27944/submission/344995/test/71814/result/37864862/ https://certification.canonical.com/hardware/202008-28111/submission/344988/test/71814/result/37863988/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/2046444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046440] Re: Enforce RETPOLINE and SLS mitigrations
** Description changed: + [ Impact ] + Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. + + [ Test Plan ] + + * Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += + $(RETPOLINE_CFLAGS) + + This simulate a build infrastructure, or toolchain regression, or hand- + written assembly code that is susceptible to speculative attacks. + + Attempt to build the kernel. + + The kernel build must fail. Currently it doesn't, and retpoline ABI + checks do not catch it. + + + [ Where problems could occur ] + + * This change will make our kernel build more strict, especially for + dkms packages. dkms packages that ship in Ubuntu archive have been build + tested to pass with these more strict requirements in place. Other + external modules that fail with such strict configuration should either + fix their code to be retpoline/redbleed safe - or use a config override + CONFIG_RETPOLINE=n to disable retpoline during their build, or otherwise + use one of the OBJTOOL_ settings in their dkms Makefiles to skip objtool + on given portions of code, or otherwise mark things as retpoline_safe / + noreturn / etc. See examples in the linux upstream source code. + + [ Other Info ] + + * This work was done as part of hackathon questioning abi checks usefulness, given I have never experienced retpoline check failure. And they have always been empty since early v4.15 days https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/abi/4.15.0-13.14/amd64/generic.retpoline?h=Ubuntu-4.15.0-14.15 ** Description changed: [ Impact ] Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. [ Test Plan ] - * Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += + Hack arch/x86/Makefile and comment out KBUILD_CFLAGS += $(RETPOLINE_CFLAGS) This simulate a build infrastructure, or toolchain regression, or hand- written assembly code that is susceptible to speculative attacks. Attempt to build the kernel. The kernel build must fail. Currently it doesn't, and retpoline ABI checks do not catch it. + Another approach is to build a known buggy dkms modules on x86 - for + example zfs-dkms with ret -> RET changes reverted in assembly + accelerated code. [ Where problems could occur ] - * This change will make our kernel build more strict, especially for - dkms packages. dkms packages that ship in Ubuntu archive have been build + This change will make our kernel build more strict, especially for dkms + packages. dkms packages that ship in Ubuntu archive have been build tested to pass with these more strict requirements in place. Other external modules that fail with such strict configuration should either fix their code to be retpoline/redbleed safe - or use a config override CONFIG_RETPOLINE=n to disable retpoline during their build, or otherwise use one of the OBJTOOL_ settings in their dkms Makefiles to skip objtool on given portions of code, or otherwise mark things as retpoline_safe / noreturn / etc. See examples in the linux upstream source code. [ Other Info ] - - * This work was done as part of hackathon questioning abi checks usefulness, given I have never experienced retpoline check failure. And they have always been empty since early v4.15 days https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/tree/debian.master/abi/4.15.0-13.14/amd64/generic.retpoline?h=Ubuntu-4.15.0-14.15 + + This work was done as part of hackathon
[Kernel-packages] [Bug 2046440] [NEW] Enforce RETPOLINE and SLS mitigrations
Public bug reported: Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. ** 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/2046440 Title: Enforce RETPOLINE and SLS mitigrations Status in linux package in Ubuntu: New Bug description: Enforce RETPOLINE and SLS mitigrations Currently retpoline ABI checks in the kernel build do nothing. They produce no output, as if everything is fine. And if one manually hacks makefile to "forget" retpoline & SLS mitigration flags, objtool prints lots of warnings, retpoline ABI check passes and the build is succesful. Yet totally vulnerable. Proposal is to enforce objtool warnings as fatal errors for RETPOLINE and SLS, as tested to be passed on mantic for both kernel and all available dkms. And otherwise rip out custom Ubuntu retpoline abi checks. I have prepared this for noble v6.7 kernel, once this lands, I will make appropriate backports for earlier series as we likely want usable retpoline build time enforcement in earlier series too where possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
If/when this lands in jammy 5.15 it will affect snapd-preseed status in livecd-rootfs which will need to have appropriate adjustment as well, at the same time. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Also affects: livecd-rootfs (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/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 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 2044657] Re: Multiple data corruption issues in zfs
** Changed in: zfs-linux (Ubuntu Noble) Status: Fix Committed => 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/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: Confirmed 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). [ 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
Re: [Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
On Fri, 8 Dec 2023 at 23:35, Steve Langasek <2044...@bugs.launchpad.net> wrote: > > zfs-linux (2.2.2-0ubuntu1~23.10) mantic; urgency=medium > > * New upstream release. LP: #2044657 > - Address potential data corruption > > I'm assuming the plan for fixing it on earlier releases does not involve > updating to 2.2.2. > > And this does not fall under a hardware enablement exception. AND there > are packaging changes under debian/. > > The diff for this new upstream release is 9kloc. I would expect a > cherry-picked fix here for mantic, not a full upstream backport - just > as will be required for releases prior to mantic. My plan was to do updates as follows: - upgrade to 2.2.2 for mantic - upgrade to 2.1.14 for jammy (to cover this issue, but also potential straight line speculation fixes) - cherry-pick of individual bug fix for focal and earlier I also do not understand why I ended up maintaining any of zfs-linux anymore btw. Especially the userspace side of things. I am happy to SRU just the kernel code changes alone, and let foundations handle the zfs userspace fixes. Separately, do note that lxd snap builds and vendors the full multiple zfs userspace tooling. So i'm not sure there is any stability value in not taking the full point releases for the userspace tooling changes in the classic ubuntu release - or try to untangle them. Regards, Dimitri. -- 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 Committed 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: Confirmed Status in zfs-linux source package in Mantic: Incomplete Status in zfs-linux source package in Noble: Fix Committed 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). [ 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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble
my expectation is that udev should be running (somewhere, not sure if it needs to be both the host and the lxd guest) and that it should process the device using locks https://systemd.io/BLOCK_DEVICE_LOCKING/. After that is done, the device should be safe to operate on, in a consistent manner. After all, -P, --partscan Force the kernel to scan the partition table on a newly created loop device. Note that the partition table parsing depends on sector sizes. The default is sector size is 512 bytes, otherwise you need to use the option --sector-size together with --partscan. Is only asking kernel to scan the device; to then generate "kernel udev" events; for then udev to wakeup and process/emit "udev udev" events; and create the required device nodes. We have always been fixing and supporting running udev inside the lxd containers, because of such things (in contexts of priviledged containers, but outside of lp-buildd) to make all of this work. -- 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/2045586 Title: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble Status in linux package in Ubuntu: New Status in livecd-rootfs package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: In mantic, we migrated livecd-rootfs to use losetup -P instead of kpartx, with the expectation that this would give us a reliable, race- free way of loop-mounting partitions from a disk image during image build. In noble, we are finding that it is no longer reliable, and in fact fails rather often. It is most noticeable with riscv64 builds, which is the architecture where we most frequently ran into problems before with kpartx. The first riscv64+generic build in noble where the expected loop partition device is not available is https://launchpad.net/~ubuntu- cdimage/+livefs/ubuntu/noble/cpc/+build/531790 The failure is however not unique to riscv64, and the autopkgtest for the latest version of livecd-rootfs (24.04.7) - an update that specifically tries to add more debugging code for this scenario - has also failed on ppc64el. https://autopkgtest.ubuntu.com/packages/l/livecd- rootfs/noble/ppc64el The first failure happened on November 16. While there has been an update to the util-linux package in noble, this did not land until November 23. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: Confirmed => In Progress -- 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 Committed 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: Confirmed Status in zfs-linux source package in Mantic: In Progress Status in zfs-linux source package in Noble: Fix Committed 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). [ 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: - OpenZFS linux kernel module currently has multiple potential data - corruption issues identified to have been present since at least 0.6 - (?!). + [ Impact ] - This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR - backport/cherry-pick of dirty dnode patch. + * 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). + + [ 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 -- 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 Committed 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: Confirmed Status in zfs-linux source package in Mantic: Confirmed Status in zfs-linux source package in Noble: Fix Committed 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). [ 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:
[Kernel-packages] [Bug 2045384] Re: AppArmor patch for mq-posix interface is missing in jammy
Please use 22-hwe/stable if you can, please let us know if that's acceptable. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045384 Title: AppArmor patch for mq-posix interface is missing in jammy Status in linux package in Ubuntu: Incomplete 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 2035971] Re: linux tools packages for derived kernels refuse to install simultaneously due to libcpupower name collision
** Description changed:
+ [ 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
+ 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
+ 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.
--
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:
In Progress
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
[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final
Note the 10.30 cycle mantic kernels were built with this zfs-linux dkms prebuilt, vendored in, and passing kernel regresstion testing, adt- matrix testing and so on, for all kernels. Mantic kernels that contain this update of zfs.ko have now been mostly released. * autopkgtest pass As seen on https://ubuntu-archive-team.ubuntu.com/proposed-migration/mantic/update_excuses.html#zfs-linux And due to lack of automated comments of autopkgtest regressions And also via adt matrix at for example https://kernel.ubuntu.com/adt-matrix/mantic-linux-meta.html for zfs-linux results with generic kernel, but also all other mantic kernels. * kernel regression zfs testsuite pass (Canonical only URL i believe) http://10.246.75.167/2023.10.30/tc-stats- lvl1.html shows all RT testing stats for the 2013.10.30 cycle, and you can see that zfs ones are all green (apart from one stress-ng test case which seems to have passed, but failed to clean up with a timeout, and is being investigated). Clicking through to the zfs test case name you can see break-down of tests per release / kernel flavour / target hardware / arch etc. For this SRU only mantic one matters. * zsys integration test pass Tested that existing installs upgrade fine, and new ones are also possible by upgrading zfs-linux userspace tooling in live desktop session to proposed. * LXD support retested That was done by lxd team, and they have shipped upgrade to 2.0 final inside lxd snap already. In practice this SRU is already released to most users via LXD and via kernel upgrades. The change this sru release will introduce is userspace tooling update, which was minor in this update. Note there will be a new zfs-linux sru, right after this one to address the recently identified and patched up issues. See https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657 It is still worth it to release this sru, before staging the next one in proposed. ** Tags removed: verification-needed verification-needed-mantic ** Tags added: verification-done verification-done-mantic -- 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/2040181 Title: upgrade zfs-linux to 2.2.0 final 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 ] * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to update to final * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional cherrypicks, or kernel team created fixes that got contributed & accepted upstream. At the time this was the only way to get zfs working with v6.5 kernels and also drop the need for shiftfs (due to zfs impovements). Since us shipping this package, upstream has identified and fixed multiple small bugfixes in the subsequent RC and the final releases, including one bug fix that can lead to potential data loss. * The 2.2.0 release branch was frozen for a long time already, and outstanding number of commits of fixes that Mantic does not have is less than 30 small patches. * Proposal to upgrade our build to 2.2.0 final, pick up all the regression fixes, and drop all the cherrypicked patches that enable v6.5 support. This will give us the best kernel driver to support in the runnup to next Ubuntu LTS. [ Test Plan ] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass * LXD support retested [ Where problems could occur ] * LXD snap in edge shipped zfs tooling of RC5 version until 16th October when they upgraded to 2.2.0 final, there are no kernel- userspace incompatiblities between RC & final, but we should explicitly test this. [ Other Info ] * Upstream is alerting us to the potential data loss and requesting upgrade to 2.2.0-rc5 or better. [ Abbriviated changes being introduced ] $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | grep -v compat 810fc49a3e Ensure we call fput when cloning fails due to different devices. a80e1f1c90 zvol: Temporally disable blk-mq 33d7c2d165 import: require force when cachefile hostid doesn't match on-disk 8015e2ea66 Add '-u' - nomount flag for zfs set c53bc3837c Improve the handling of sharesmb,sharenfs properties e9dc31c74e Update the behavior of mountpoint property 608741d062 Report ashift of L2ARC devices in zdb 0ce1b2ca19 Invoke zdb by guid to avoid import errors 0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data() a199cac6cd status: report pool suspension state under failmode=continue 729507d309 Fix occasional rsend test crashes 3af63683fe cmd: add 'help' subcommand to zpool and zfs 9aa1a2878e Fix incorrect expected error in ztest f7a07d76ee Retire z_nr_znodes 54c6fbd378 zed: Allow autoreplace and fault LEDs for
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
** CVE removed: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3646 ** Changed in: zfs-linux (Ubuntu) Importance: High => Undecided -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: Fix Released Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: Confirmed Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc305a905d7 [ 967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX:
[Kernel-packages] [Bug 1976248] Re: Revert PPC get_user workaround
** Changed in: zfs-linux (Ubuntu Jammy) Importance: Undecided => High -- 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/1976248 Title: Revert PPC get_user workaround Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Released Status in zfs-linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Status in linux source package in Kinetic: Won't Fix Status in zfs-linux source package in Kinetic: Fix Committed Bug description: [Impact] * A change of kernel symbol license allows to drop a PPC specific workaround in zfs-dkms to use the regular (better) code paths. * See details in: https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242 [Test Plan] * linux: apply https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch * Build on kernel with zfs module on ppc * Ensure that zfs.ko successfully loads and works * Test that root on zfs installations work on ppc (however, Ubuntu currently doesn't provide an installation method to achieve this, so this bit of verification might be hard to complete) [Where problems could occur] * linux: the patch only changes the symbol licensing and the potential tainteness status of the kernel, without any observable user or kernel space impacts * zfs-dkms: The PPC workaround patch is known to be buggy, and the new arch-independent codepath may now use optimized codepaths inside kernel resulting in a different behavior as observed by user-space (operation successful, EFAULT not returned) matching the behavior of all other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
** Changed in: zfs-linux (Ubuntu Lunar) Status: Confirmed => Invalid ** Changed in: zfs-linux (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Invalid -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: Invalid Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in zfs-linux source package in Lunar: Invalid Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: zfs-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: zfs-linux (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: zfs-linux (Ubuntu Lunar) Importance: High => Medium -- 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 Committed 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: Confirmed Status in zfs-linux source package in Mantic: Confirmed Status in zfs-linux source package in Noble: Fix Committed Bug description: OpenZFS linux kernel module currently has multiple potential data corruption issues identified to have been present since at least 0.6 (?!). This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR backport/cherry-pick of dirty dnode patch. 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 1976248] Re: Revert PPC get_user workaround
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: zfs-linux (Ubuntu Impish) Status: New => Won't Fix ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu Jammy) 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/1976248 Title: Revert PPC get_user workaround Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Released Status in zfs-linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: New Status in linux source package in Kinetic: Won't Fix Status in zfs-linux source package in Kinetic: Fix Committed Bug description: [Impact] * A change of kernel symbol license allows to drop a PPC specific workaround in zfs-dkms to use the regular (better) code paths. * See details in: https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009242 [Test Plan] * linux: apply https://github.com/torvalds/linux/commit/d9e5c3e9e75162f845880535957b7fd0b4637d23 * zfs-dkms: revert https://git.launchpad.net/ubuntu/+source/zfs- linux/tree/debian/patches/4900-ppc-get-user-workaround.patch * Build on kernel with zfs module on ppc * Ensure that zfs.ko successfully loads and works * Test that root on zfs installations work on ppc (however, Ubuntu currently doesn't provide an installation method to achieve this, so this bit of verification might be hard to complete) [Where problems could occur] * linux: the patch only changes the symbol licensing and the potential tainteness status of the kernel, without any observable user or kernel space impacts * zfs-dkms: The PPC workaround patch is known to be buggy, and the new arch-independent codepath may now use optimized codepaths inside kernel resulting in a different behavior as observed by user-space (operation successful, EFAULT not returned) matching the behavior of all other architectures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881810] Re: ZFS import cause panic
** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: Triaged => Invalid -- 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/1881810 Title: ZFS import cause panic Status in zfs-linux package in Ubuntu: Invalid Bug description: 1) Ubuntu 20.04 LTS 2) apt policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate:0.8.3-1ubuntu12 3) ZFS pool not possible to import, unless using read only. If trying to import normal way as write/read, casing panic message Expected to be able to import zpool without panic. Expected that scrub should not be able to run in read only. Expected that somehow be able to restore the zpool somehow. 4) # zpool status no pools available # zpool import pool: datastore id: 3190464655986727485 state: ONLINE status: Some supported features are not enabled on the pool. action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: datastore ONLINE raidz2-0 ONLINE sdb ONLINE sdc ONLINE sdd ONLINE sde ONLINE sdf ONLINE sdg ONLINE # zpool import -o readonly=on datastore # zpool status pool: datastore state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub in progress since Sun May 10 00:24:01 2020 15,1T scanned at 0B/s, 15,1T issued at 0B/s, 15,1T total 1,44M repaired, 100,01% done, no estimated completion time config: NAMESTATE READ WRITE CKSUM datastore ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 sde ONLINE 0 0 0 sdf ONLINE 0 0 0 sdg ONLINE 0 0 0 errors: No known data errors Running zdb it always stops ad 2,23T and then aborts. # zdb -e -bcsvL datastore Traversing all blocks to verify checksums ... 2.23T completed ( 149MB/s) estimated time remaining: 25hr 06min 25sec free(): invalid pointer Abort (SIGABRT) #zpool import datastore VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (36028797018963967 < 32768) PANIC at zio.c:293:zio_buf_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920956] Re: ZFS module cannot be loaded after Kernel 5.4.0-67-generic release AND if the system has zfs-dkms and spl-dkms packages installed
Removing all dkms, or installing and compiling all dkms are the only two viable options. Incomplete installs or mix of both can lead to issues. More recently zfs upstream switched to not shipping many small modules precisely because of issues like these. ** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: Triaged => Invalid -- 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/1920956 Title: ZFS module cannot be loaded after Kernel 5.4.0-67-generic release AND if the system has zfs-dkms and spl-dkms packages installed Status in zfs-linux package in Ubuntu: Invalid Bug description: WARNING: The current bug will only occur under the following conditions: 1- You have a system running on Bionic Release (18.04). Other systems seems to be unaffected for now; 2- This system have 'spl-dkms' and 'zfs-dkms' packages installed. This triggers both SPL and ZFS to be recompiled from source if we have a new Kernel Image being installed; 3- You didn't patched your system kernel to either "linux-modules-5.4.0-67-generic" or "linux-modules-5.4.0-1039-aws". You are running an earlier kernel version, which can be from 5.3.0-XXX or 5.4.0-60 for example and you need to upgrade your system to the latest 'kernel-image' release. ALTERNATIVELY: 1- When creating a new OS image based on the Bionic and it's already running kernel 5.4.0-67 or 5.4.0-1030-aws, you decide to install 'spl-dkms' and 'zfs-dkms'. SCENARIO: We have systems running on Xenial, Bionic, and Focal Fossa releases. We also have the 'Unattended Upgrades' on and we use ZFS. Every time that Ubuntu releases kernel updates, they are updated on our systems and both the new kernel and its modules will be active on the next reboot. Or if you run your workload on AWS and uses Canonical images, this is happening also on the image tagged as 'ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20210224' on AWS Ireland / eu-west-1 Region (AMI ID = ami-0d75330b9efa7072d) for fresh installs. Some days ago, Ubuntu releases a new Linux Kernel update for the 5.4.0 release, and this is happening on both "linux- modules-5.4.0-67-generic" and "linux-modules-5.4.0-1039-aws" (this might be true on GKE, Azure and other public cloud providers kernel releases, but I didn't test them). I have noticed that both EC2 instances that were rebooted after the kernel upgrade or if we are baking a new OS image based on the latest Canonical images I was unable to get the ZFS module loaded. The error message is showed below: $ sudo modprobe zfs modprobe: ERROR: could not insert 'zfs': Invalid argument When checking the 'dmesg', we can see the errors below (or even when booting up if you have the 'zfs-load-module.service' active on your system). [ 51.358828] icp: disagrees about version of symbol __kstat_create [ 51.358830] icp: Unknown symbol __kstat_create (err -22) [ 51.358925] icp: disagrees about version of symbol __kstat_install [ 51.358927] icp: Unknown symbol __kstat_install (err -22) [ 79.196638] icp: disagrees about version of symbol __kstat_delete [ 79.196643] icp: Unknown symbol __kstat_delete (err -22) [ 79.196687] icp: disagrees about version of symbol __kstat_create [ 79.196689] icp: Unknown symbol __kstat_create (err -22) [ 79.196765] icp: disagrees about version of symbol __kstat_install [ 79.196766] icp: Unknown symbol __kstat_install (err -22) On Bionic release, both th ZFS and the SPL modules comes with version '0.7.5'. $ dpkg -l |grep 0.7.5-1ubuntu16.9 ii libnvpair1linux 0.7.5-1ubuntu16.9 amd64Solaris name-value library for Linux ii libuutil1linux 0.7.5-1ubuntu16.9 amd64Solaris userland utility library for Linux ii libzfs2linux 0.7.5-1ubuntu16.9 amd64OpenZFS filesystem library for Linux ii libzpool2linux 0.7.5-1ubuntu16.9 amd64OpenZFS pool library for Linux ii zfs-dkms 0.7.5-1ubuntu16.9 all OpenZFS filesystem kernel modules for Linux ii zfs-initramfs0.7.5-1ubuntu16.9 all OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed 0.7.5-1ubuntu16.9 amd64OpenZFS Event Daemon ii zfsutils-linux 0.7.5-1ubuntu16.9 amd64command-line tools to manage OpenZFS filesystems On systems running kernel 5.4.0 already have the modules compiled on version 0.8.1, which can vary depending on the active kernel.
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) -- 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/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: Fix Released Status in zfs-linux package in Ubuntu: Incomplete Status in zfs-linux source package in Bionic: Confirmed Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc305a905d7 [ 967.637940] RSP: 002b:7ffc45e39618 EFLAGS: 0246 ORIG_RAX: 0010 [ 967.6379
[Kernel-packages] [Bug 1881748] Re: Slow ZFS Diff with very large datasets
No progress upstream ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Won't Fix -- 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/1881748 Title: Slow ZFS Diff with very large datasets Status in zfs-linux package in Ubuntu: Won't Fix Bug description: When running zfs diff it can take a couple hours in an environment with lots of files/directories. Is it possible to pull in this patch: https://github.com/openzfs/zfs/pull/10391 To address that issue? Using ubuntu 20.04 at the moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881748/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889110] Re: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. "
** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Invalid -- 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/1889110 Title: zfs pool locks and see "INFO: task txg_sync:4307 blocked for more than 120 seconds. " Status in zfs-linux package in Ubuntu: Invalid Bug description: ZFS filesystem becomes unresponsive and subsequent NFS shares unresponsive. ESXi sees all paths down. See this error 3 times in a row. [184383.479511] INFO: task txg_sync:4307 blocked for more than 120 seconds. [184383.479565] Tainted: P IO 5.4.0-42-generic #46-Ubuntu [184383.479607] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [184383.479655] txg_syncD0 4307 2 0x80004000 [184383.479658] Call Trace: [184383.479670] __schedule+0x2e3/0x740 [184383.479673] schedule+0x42/0xb0 [184383.479676] schedule_timeout+0x152/0x2f0 [184383.479683] ? __next_timer_interrupt+0xe0/0xe0 [184383.479685] io_schedule_timeout+0x1e/0x50 [184383.479697] __cv_timedwait_common+0x15e/0x1c0 [spl] [184383.479702] ? wait_woken+0x80/0x80 [184383.479710] __cv_timedwait_io+0x19/0x20 [spl] [184383.479816] zio_wait+0x11b/0x230 [zfs] [184383.479905] ? __raw_spin_unlock+0x9/0x10 [zfs] [184383.479983] dsl_pool_sync+0xbc/0x410 [zfs] [184383.480069] spa_sync_iterate_to_convergence+0xe0/0x1c0 [zfs] [184383.480156] spa_sync+0x312/0x5b0 [zfs] [184383.480245] txg_sync_thread+0x27a/0x310 [zfs] [184383.480334] ? txg_dispatch_callbacks+0x100/0x100 [zfs] [184383.480344] thread_g
[Kernel-packages] [Bug 1907854] Re: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Invalid -- 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/1907854 Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Invalid Bug description: After update zfsutils-linux, the update process tries to mount zfs file in /mnt but since in /mnt there are another disk mount fails with: Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2020-12-11 21:05:24 CET; 8ms ago Docs: man:zfs(8) Process: 177294 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 177294 (code=exited, status=1/FAILURE) dic 11 21:05:24 serv systemd[1]: Starting Mount ZFS filesystems... dic 11 21:05:24 serv zfs[177294]: cannot mount '/mnt': directory is not empty dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE dic 11 21:05:24 serv systemd[1]: zfs-mount.service: Failed with result 'exit-code'. dic 11 21:05:24 serv systemd[1]: Failed to start Mount ZFS filesystems. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.5 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: python3-aptdaemon.gtk3widgets:amd64: Install aptdaemon:amd64: Install python3-aptdaemon:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 20:56:40 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-24 (261 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.8, Python 3.8.5, 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 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-19 (206 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1907854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008268] Re: Check abi compatiblity between Lunar and Jammy
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => 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/2008268 Title: Check abi compatiblity between Lunar and Jammy Status in zfs-linux package in Ubuntu: Fix Released Bug description: Check abi compatiblity between Lunar and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791143] Re: Suggestion to make zfsutils-linux a snap
LXD actually vendors multiple copies of zfs-utils tooling to be compatible with every target version of zfs they want to support. Coinstalling multiple snaps and versioning functionality has been deprecated for snaps. Adding tooling only snaps, or single or rainbow of versions might not gain much compared with an hwe deb. And even there things are questionable w.r.t. unintended pool upgrades. ** Changed in: zfs-linux (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) ** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Opinion -- 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/1791143 Title: Suggestion to make zfsutils-linux a snap Status in zfs-linux package in Ubuntu: Opinion Bug description: This circumvents the need to keep it on the same major version throughout the LTS cycle. LXD is doing snaps, perhaps for zfs this is the best approach as well. Xenial still has zfsutils on generation 0.6, with the module on 0.7. Even when patches are applied as needed that approach has its limitations. E.g. the Bionic cycle might possibly see 2 major zfs releases, who'll say. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1791143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862302] Re: zfs 0.8.1 requires new userland tools for Ubunt 18.04
** Changed in: zfs-linux (Ubuntu) Status: Confirmed => Opinion -- 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/1862302 Title: zfs 0.8.1 requires new userland tools for Ubunt 18.04 Status in zfs-linux package in Ubuntu: Opinion Bug description: I am running Ubuntu 18.04: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 Ever since HWE Kernel 5.3 images were introduced, ZFS module is shipped in version 0.8.1 . modinfo /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko |head filename: /lib/modules/5.3.0-28-generic/kernel/zfs/zfs.ko version:0.8.1-1ubuntu14.3 license:CDDL author: OpenZFS on Linux description:ZFS alias: devname:zfs alias: char-major-10-249 srcversion: F3C94D5226BB5E654A00EF1 depends:zlua,spl,znvpair,zcommon,icp,zunicode,zavl retpoline: Y Unfortuanetly all userland tools for zfs are still for ZFS 0.7.5. apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.7.5-1ubuntu16.7 Candidate: 0.7.5-1ubuntu16.7 Could you please provide 0.8.1 userland tools for 18.04 HWE kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1862302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: zfs block cloning file system corruption
this bug report will now be limited to things that are presumed to be fixed by 2.2.2 or 2.1.14, or the dirty dnode patch backport alone. ** CVE removed: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2023-49298 ** Description changed: - OpenZFS 2.2 reportedly has a bug where block cloning might lead to file - system corruption and data loss. This was fixed in OpenZFS 2.2.1. + OpenZFS linux kernel module currently has multiple potential data + corruption issues identified to have been present in at least 0.8 and + up. - Original bug report: https://github.com/openzfs/zfs/issues/15526 - - and 2.2.1 release notes: - https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 + This bug report will track upgrades to releases 2.2.2, or 2.1.14, or + backport/cherry-pick of dirty dnode patch. ** Summary changed: - zfs block cloning file system corruption + Multiple data corruption issues in zfs ** Description changed: OpenZFS linux kernel module currently has multiple potential data - corruption issues identified to have been present in at least 0.8 and - up. + corruption issues identified to have been present since at least 0.6 + (?!). - This bug report will track upgrades to releases 2.2.2, or 2.1.14, or + This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR backport/cherry-pick of dirty dnode patch. ** Changed in: zfs-linux (Ubuntu Noble) Status: Confirmed => Fix Committed ** Patch removed: "0001-Fix-block-cloning-corruption-bug.patch" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+attachment/5723679/+files/0001-Fix-block-cloning-corruption-bug.patch ** Patch removed: "Patch for OpenZFS 2.1" https://github.com/openzfs/zfs/commit/e49b10f57c770a03217e6537252c90550aadb538.patch ** Patch removed: "Patch from OpenZFS master branch" https://github.com/openzfs/zfs/commit/30d581121bb122c90959658e7b28b1672d342897.patch -- 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 Committed 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: Confirmed Status in zfs-linux source package in Mantic: Confirmed Status in zfs-linux source package in Noble: Fix Committed Bug description: OpenZFS linux kernel module currently has multiple potential data corruption issues identified to have been present since at least 0.6 (?!). This bug report will track upgrades to releases 2.2.2, OR 2.1.14, OR backport/cherry-pick of dirty dnode patch. 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: zfs block cloning file system corruption
seth-arnold: yes, I do think we need to backport it all the way back. And since it is kernel code, it sort of should go via normal SRU, and be integrated into a kernel cycle and release over time. As actually releasing zfs-linux into security pocket will not actually do much for most users that are running kernel compiled in zfs. I will discuss with kernel cycle leads to see how to fit this in. ** No longer affects: linux-hwe-6.2 (Ubuntu) ** No longer affects: linux-hwe-6.5 (Ubuntu) ** Also affects: zfs-linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Noble) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu Mantic) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu Lunar) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu Jammy) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Xenial: New Status in zfs-linux source package in Bionic: New Status in zfs-linux source package in Focal: New Status in zfs-linux source package in Jammy: New Status in zfs-linux source package in Lunar: New Status in zfs-linux source package in Mantic: New Status in zfs-linux source package in Noble: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 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 2045684] Re: ARM64 signed linux-images packages have arbitrary timestamp
https://lists.ubuntu.com/archives/kernel-team/2023-December/147467.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2045684 Title: ARM64 signed linux-images packages have arbitrary timestamp Status in linux-signed package in Ubuntu: In Progress Bug description: ARM64 signed linux-images packages encode arbitrary timestamp $ file /boot/vmlinuz-6.6.0-14-generic /boot/vmlinuz-6.6.0-14-generic: gzip compressed data, was "vmlinuz-6.6.0-14-generic.efi.signed", last modified: Fri Dec 1 18:54:57 2023, max compression, from Unix, original size modulo 2^32 56127880 Note that original filename and timestamp are encoded in the gzip content header which is not reproducible and not roundtrip safe. This make it difficult to do gymnastics to convert for linux linux- unsgined, to linux-signed, to kernel.efi, and back and preserve the same checksum or HMAC of the file, as needed by FIPS or just pure curiosity to confirm that the kernel image is the same across all image formats we ship. The fix is to use -n (--no-name) option to gzip to compress the file without filename nor timestamp. $ file linux-image/boot/vmlinuz-6.6.0-14-generic.new /boot/vmlinuz-6.6.0-14-generic.new: gzip compressed data, max compression, from Unix, original size modulo 2^32 56127880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2045684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045684] [NEW] ARM64 signed linux-images packages have arbitrary timestamp
Public bug reported: ARM64 signed linux-images packages encode arbitrary timestamp $ file /boot/vmlinuz-6.6.0-14-generic /boot/vmlinuz-6.6.0-14-generic: gzip compressed data, was "vmlinuz-6.6.0-14-generic.efi.signed", last modified: Fri Dec 1 18:54:57 2023, max compression, from Unix, original size modulo 2^32 56127880 Note that original filename and timestamp are encoded in the gzip content header which is not reproducible and not roundtrip safe. This make it difficult to do gymnastics to convert for linux linux-unsgined, to linux-signed, to kernel.efi, and back and preserve the same checksum or HMAC of the file, as needed by FIPS or just pure curiosity to confirm that the kernel image is the same across all image formats we ship. The fix is to use -n (--no-name) option to gzip to compress the file without filename nor timestamp. $ file linux-image/boot/vmlinuz-6.6.0-14-generic.new /boot/vmlinuz-6.6.0-14-generic.new: gzip compressed data, max compression, from Unix, original size modulo 2^32 56127880 ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: In Progress ** Description changed: - ARM64 signed linux-images packages have arbitrary timestamp + ARM64 signed linux-images packages encode arbitrary timestamp - $ file /boot/vmlinuz-6.6.0-14-generic + $ file /boot/vmlinuz-6.6.0-14-generic /boot/vmlinuz-6.6.0-14-generic: gzip compressed data, was "vmlinuz-6.6.0-14-generic.efi.signed", last modified: Fri Dec 1 18:54:57 2023, max compression, from Unix, original size modulo 2^32 56127880 Note that original filename and timestamp are encoded in the gzip content header which is not reproducible and not roundtrip safe. This make it difficult to do gymnastics to convert for linux linux-unsgined, to linux-signed, to kernel.efi, and back and preserve the same checksum or HMAC of the file, as needed by FIPS or just pure curiosity to confirm that the kernel image is the same across all image formats we ship. The fix is to use -n (--no-name) option to gzip to compress the file without filename nor timestamp. $ file linux-image/boot/vmlinuz-6.6.0-14-generic.new /boot/vmlinuz-6.6.0-14-generic.new: gzip compressed data, max compression, from Unix, original size modulo 2^32 56127880 ** Changed in: linux-signed (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2045684 Title: ARM64 signed linux-images packages have arbitrary timestamp Status in linux-signed package in Ubuntu: In Progress Bug description: ARM64 signed linux-images packages encode arbitrary timestamp $ file /boot/vmlinuz-6.6.0-14-generic /boot/vmlinuz-6.6.0-14-generic: gzip compressed data, was "vmlinuz-6.6.0-14-generic.efi.signed", last modified: Fri Dec 1 18:54:57 2023, max compression, from Unix, original size modulo 2^32 56127880 Note that original filename and timestamp are encoded in the gzip content header which is not reproducible and not roundtrip safe. This make it difficult to do gymnastics to convert for linux linux- unsgined, to linux-signed, to kernel.efi, and back and preserve the same checksum or HMAC of the file, as needed by FIPS or just pure curiosity to confirm that the kernel image is the same across all image formats we ship. The fix is to use -n (--no-name) option to gzip to compress the file without filename nor timestamp. $ file linux-image/boot/vmlinuz-6.6.0-14-generic.new /boot/vmlinuz-6.6.0-14-generic.new: gzip compressed data, max compression, from Unix, original size modulo 2^32 56127880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/2045684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045561] Re: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support
> Thanks - what about Jammy? please use linux-virtual instead of linux-kvm. the original intend for linux-kvm was to not have UEFI nor SMBIOS support at all, as was needed at the time by the original kata- containers / clearlinux containers. ** No longer affects: linux-kvm (Ubuntu Mantic) ** No longer affects: linux-kvm (Ubuntu Noble) ** Changed in: linux-kvm (Ubuntu) Status: New => Fix Released ** Changed in: linux-kvm (Ubuntu Jammy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2045561 Title: linux-kvm: please enable CONFIG_DMI_SYSFS for SMBIOS support Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Jammy: Won't Fix Bug description: SRU Justification [Impact] The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops VMs using these kernels from being configurable using qemu or cloud- hypervisor's SMBIOS type 11 strings. This feature is supported and used widely by systemd: https://www.freedesktop.org/software/systemd/man/latest/smbios-type-11.html https://systemd.io/CREDENTIALS/ A user launching a VM using the linux-kvm kernel image is not able to specify SMBIOS strings to automatically configured userspace services and programs due to the lack of this kconfig. We make extensive use of these in systemd's upstream CI, which is running on Github Actions, which uses Jammy, so it would be great to have this kconfig enabled and backported. For example: qemu-system-x86_64 \ -machine type=q35,accel=kvm,smm=on \ -smp 2 \ -m 1G \ -cpu host \ -nographic \ -nodefaults \ -serial mon:stdio \ -drive if=none,id=hd,file=ubuntu_jammy.raw,format=raw \ -device virtio-scsi-pci,id=scsi \ -device scsi-hd,drive=hd,bootindex=1 \ -smbios type=11,value=io.systemd.credential:mycred=supersecret [Fix] Please consider enabling the following kconfigs: CONFIG_DMI_SYSFS These are already enabled in the 'main' kernel config, and in other distros. To verify this works, it is sufficient to check that the /sys/firmware/dmi/entries/ directory in sysfs is present: $ ls /sys/firmware/dmi/entries/ 0-0126-1 126-4 126-8 130-0 133-0 136-0 140-2 15-0 18-0 21-1 221-1 24-0 7-1 8-2 8-6 1-0126-10 126-5 126-9 131-0 134-0 14-0 140-3 16-0 19-0 219-0 221-2 3-0 7-2 8-3 9-0 12-0 126-2 126-6 127-0 131-1 135-0 140-0 140-4 17-0 2-0 22-0 221-3 4-0 8-0 8-4 9-1 126-0 126-3 126-7 13-0 132-0 135-1 140-1 14-1 17-1 21-0 221-0 222-0 7-0 8-1 8-5 Without this kconfig, the directory won't be there. Once enabled, it will be there. [Regression Potential] Enabling a new DMI option could affect the DMI subsystem in unforeseen ways. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/2045561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045593] [NEW] back-out zstd module compression automatic for backports
Public bug reported: back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - back zstd module compression automatic for backports + back-out zstd module compression automatic for backports ** Description changed: - back zstd module compression automatic for backports + back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. -- 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/2045593 Title: back-out zstd module compression automatic for backports Status in linux package in Ubuntu: New Bug description: back-out zstd module compression automatic for backports we decided to have kernel modules zstd compressed in mantic+, and keep them uncompressed in jammy backports. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038583] Re: Turning COMPAT_32BIT_TIME off on s390x
> TODO: Need to check if we can still compile and run 31bit xenial s390 binaries, on a kernel with COMPAT_32BIT_TIME turned off, to support launchpad build farm itself. This is now complete. I believe we are capable of continue to building ESM/EOL releases, even with COMPAT turned off. Specifically to like continue building xenials' libc-s390 even if the host kernel in the build farm is noble+ kernel with compat turned off. If it helps your analysis i can provide you a jammy kernel in a ppa that has compat turned off, such that you can empirically run anything you want and observe if things you think you might care about still work or not. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ubuntu-z-systems Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038583 Title: Turning COMPAT_32BIT_TIME off on s390x Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This will prevent existing s390 binaries to operate correctly, if they are still using 32bit time. 24.04 LTS is likely to be used for 10 years. And if allowed to overrun and remain active in the field in 2038 can lead to catastrophic failure in the field due to these syscalls enabled and used. I would like to request if we can turn off COMPAT_32BIT_TIME on every architecture, thus this will be arch by arch bug report, and arch by arch decision. This needs to be a per-arch decision, potentially taking into consideration bi-arch userspace support. config COMPAT_32BIT_TIME bool "Provide system calls for 32-bit time_t" default !64BIT || COMPAT help This enables 32 bit time_t support in addition to 64 bit time_t support. This is relevant on all 32-bit architectures, and 64-bit architectures as part of compat syscall handling. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2038583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: zfs block cloning file system corruption
I'm not sure why linux-hwe-6.2 is marked as affected. hwe-6.2 use 2.1.9 based zfs-linux and will not be upgraded to use 2.2.0 series. ** Package changed: linux-hwe-6.2 (Ubuntu) => linux-hwe-6.5 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044657 Title: zfs block cloning file system corruption Status in linux-hwe-6.5 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+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: zfs block cloning file system corruption
zfs-linux (2.2.1-0ubuntu1) noble; urgency=medium * New upstream release. Uploaded. But I don't want to close this bug report, because it is not clear if that is everything yet or not. -- 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: zfs block cloning file system corruption Status in zfs-linux package in Ubuntu: Confirmed Bug description: OpenZFS 2.2 reportedly has a bug where block cloning might lead to file system corruption and data loss. This was fixed in OpenZFS 2.2.1. Original bug report: https://github.com/openzfs/zfs/issues/15526 and 2.2.1 release notes: https://github.com/openzfs/zfs/releases/tag/zfs-2.2.1 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 2044554] [NEW] Turn off non-zynqmp arch support
Public bug reported: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance ** Affects: linux-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2044554 Title: Turn off non-zynqmp arch support Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: [ Impact ] * This is an optimized kernel for zynqmp range of devices. * Currently about 14% of kernel build is targeting non-zynqmp devices, which is dead code unused in production * This reduces kernel build time, kernel image & modules size, amount of required firmware, and makes initrd smaller. * This reduces peak memory usage on boot as well * This will loose ability to execute this exact same kernel build on non-zynqmp device, for benchmarking purposes generic kernel should be used instead. [ Test Plan ] * Ensure newly produced kernel installs and boots on Ubuntu Server and Ubuntu Core target devices without any loss of peripherals and stock devices. [ Where problems could occur ] * This changes may limit ability to smoke-test this kernel on non-zynqmp devices, if needed support for individual CPUs can be turned back on. Or ideally any such testing should move to zynqmp devices. (examples of potentially interesting things to turn back on upon request are QCOM APPLE suppport for running this kernel on Arm Laptops for developer convenience) * It is expected for KVM and QEMU to continue to work as both host and guest [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2044554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
