[Kernel-packages] [Bug 2048087] Re: RM: obsolete & superseded nvidia-graphics-drivers, leftovers
Removing packages from noble: nvidia-graphics-drivers-515 515.105.01-0ubuntu3 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: Triaged => Fix Released -- 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: Triaged 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-530 530.41.03-0ubuntu2 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-530 (Ubuntu) Status: Triaged => Fix Released -- 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: Triaged 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
The other packages in this listed are reported by reverse-depends to have non-empty revdeps. However it looks like these all come from other packages that have just been removed. Rather than tracing this manually and possibly making a mistake, I'll let the others sit for another round. -- 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: Triaged 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-455 455.45.01-0ubuntu1 in noble libnvidia-cfg1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-435 455.45.01-0ubuntu1 in noble arm64 libnvidia-common-435 455.45.01-0ubuntu1 in noble armhf libnvidia-common-435 455.45.01-0ubuntu1 in noble i386 libnvidia-common-435 455.45.01-0ubuntu1 in noble ppc64el libnvidia-common-435 455.45.01-0ubuntu1 in noble riscv64 libnvidia-common-435 455.45.01-0ubuntu1 in noble s390x libnvidia-common-455 455.45.01-0ubuntu1 in noble amd64 libnvidia-common-455 455.45.01-0ubuntu1 in noble arm64 libnvidia-common-455 455.45.01-0ubuntu1 in noble armhf libnvidia-common-455 455.45.01-0ubuntu1 in noble i386 libnvidia-common-455 455.45.01-0ubuntu1 in noble ppc64el libnvidia-common-455 455.45.01-0ubuntu1 in noble riscv64 libnvidia-common-455 455.45.01-0ubuntu1 in noble s390x libnvidia-compute-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-compute-435 455.45.01-0ubuntu1 in noble i386 libnvidia-decode-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-decode-435 455.45.01-0ubuntu1 in noble i386 libnvidia-encode-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-encode-435 455.45.01-0ubuntu1 in noble i386 libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-fbc1-435 455.45.01-0ubuntu1 in noble i386 libnvidia-gl-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-gl-435 455.45.01-0ubuntu1 in noble i386 libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble amd64 libnvidia-ifr1-435 455.45.01-0ubuntu1 in noble i386 nvidia-compute-utils-435 455.45.01-0ubuntu1 in noble amd64 nvidia-dkms-435 455.45.01-0ubuntu1 in noble amd64 nvidia-driver-435 455.45.01-0ubuntu1 in noble amd64 nvidia-headless-435 455.45.01-0ubuntu1 in noble amd64 nvidia-headless-no-dkms-435 455.45.01-0ubuntu1 in noble amd64 nvidia-kernel-common-435 455.45.01-0ubuntu1 in noble amd64 nvidia-kernel-source-435 455.45.01-0ubuntu1 in noble amd64 nvidia-utils-435 455.45.01-0ubuntu1 in noble amd64 xserver-xorg-video-nvidia-435 455.45.01-0ubuntu1 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: Triaged => Fix Released -- 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: Triaged 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-510 510.108.03-0ubuntu3 in noble libnvidia-cfg1-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-495 510.108.03-0ubuntu3 in noble arm64 libnvidia-common-495 510.108.03-0ubuntu3 in noble armhf libnvidia-common-495 510.108.03-0ubuntu3 in noble i386 libnvidia-common-495 510.108.03-0ubuntu3 in noble ppc64el libnvidia-common-495 510.108.03-0ubuntu3 in noble riscv64 libnvidia-common-495 510.108.03-0ubuntu3 in noble s390x libnvidia-common-510 510.108.03-0ubuntu3 in noble amd64 libnvidia-common-510 510.108.03-0ubuntu3 in noble arm64 libnvidia-common-510 510.108.03-0ubuntu3 in noble armhf libnvidia-common-510 510.108.03-0ubuntu3 in noble i386 libnvidia-common-510 510.108.03-0ubuntu3 in noble ppc64el libnvidia-common-510 510.108.03-0ubuntu3 in noble riscv64 libnvidia-common-510 510.108.03-0ubuntu3 in noble s390x libnvidia-compute-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-compute-495 510.108.03-0ubuntu3 in noble i386 libnvidia-decode-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-decode-495 510.108.03-0ubuntu3 in noble i386 libnvidia-encode-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-encode-495 510.108.03-0ubuntu3 in noble i386 libnvidia-extra-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-extra-495 510.108.03-0ubuntu3 in noble i386 libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-fbc1-495 510.108.03-0ubuntu3 in noble i386 libnvidia-gl-495 510.108.03-0ubuntu3 in noble amd64 libnvidia-gl-495 510.108.03-0ubuntu3 in noble i386 nvidia-compute-utils-495 510.108.03-0ubuntu3 in noble amd64 nvidia-dkms-495 510.108.03-0ubuntu3 in noble amd64 nvidia-driver-495 510.108.03-0ubuntu3 in noble amd64 nvidia-headless-495 510.108.03-0ubuntu3 in noble amd64 nvidia-headless-no-dkms-495 510.108.03-0ubuntu3 in noble amd64 nvidia-kernel-common-495 510.108.03-0ubuntu3 in noble amd64 nvidia-kernel-source-495 510.108.03-0ubuntu3 in noble amd64 nvidia-utils-495 510.108.03-0ubuntu3 in noble amd64 xserver-xorg-video-nvidia-495 510.108.03-0ubuntu3 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: Triaged => Fix Released -- 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: Triaged 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-435 435.21-0ubuntu8 in noble Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Triaged => Fix Released -- 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: 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-340 340.108-0ubuntu8 in noble libcuda1-340 340.108-0ubuntu8 in noble amd64 libcuda1-340 340.108-0ubuntu8 in noble armhf nvidia-340 340.108-0ubuntu8 in noble amd64 nvidia-340 340.108-0ubuntu8 in noble armhf nvidia-340-dev 340.108-0ubuntu8 in noble amd64 nvidia-340-dev 340.108-0ubuntu8 in noble armhf nvidia-340-uvm 340.108-0ubuntu8 in noble amd64 nvidia-340-uvm 340.108-0ubuntu8 in noble armhf nvidia-libopencl1-340 340.108-0ubuntu8 in noble amd64 nvidia-opencl-icd-340 340.108-0ubuntu8 in noble amd64 Comment: Unsupported driver version; LP: #2048087 ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Triaged => Fix Released -- 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: 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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
Removing packages from noble: nvidia-graphics-drivers-430 430.50-0ubuntu3 in noble libnvidia-cfg1-418 430.50-0ubuntu3 in noble amd64 libnvidia-common-418 430.50-0ubuntu3 in noble amd64 libnvidia-common-418 430.50-0ubuntu3 in noble arm64 libnvidia-common-418 430.50-0ubuntu3 in noble armhf libnvidia-common-418 430.50-0ubuntu3 in noble i386 libnvidia-common-418 430.50-0ubuntu3 in noble ppc64el libnvidia-common-418 430.50-0ubuntu3 in noble riscv64 libnvidia-common-418 430.50-0ubuntu3 in noble s390x libnvidia-common-430 430.50-0ubuntu3 in noble amd64 libnvidia-common-430 430.50-0ubuntu3 in noble arm64 libnvidia-common-430 430.50-0ubuntu3 in noble armhf libnvidia-common-430 430.50-0ubuntu3 in noble i386 libnvidia-common-430 430.50-0ubuntu3 in noble ppc64el libnvidia-common-430 430.50-0ubuntu3 in noble riscv64 libnvidia-common-430 430.50-0ubuntu3 in noble s390x libnvidia-compute-418 430.50-0ubuntu3 in noble amd64 libnvidia-compute-418 430.50-0ubuntu3 in noble i386 libnvidia-decode-418 430.50-0ubuntu3 in noble amd64 libnvidia-decode-418 430.50-0ubuntu3 in noble i386 libnvidia-encode-418 430.50-0ubuntu3 in noble amd64 libnvidia-encode-418 430.50-0ubuntu3 in noble i386 libnvidia-fbc1-418 430.50-0ubuntu3 in noble amd64 libnvidia-fbc1-418 430.50-0ubuntu3 in noble i386 libnvidia-gl-418 430.50-0ubuntu3 in noble amd64 libnvidia-gl-418 430.50-0ubuntu3 in noble i386 libnvidia-ifr1-418 430.50-0ubuntu3 in noble amd64 libnvidia-ifr1-418 430.50-0ubuntu3 in noble i386 nvidia-compute-utils-418 430.50-0ubuntu3 in noble amd64 nvidia-dkms-418 430.50-0ubuntu3 in noble amd64 nvidia-driver-418 430.50-0ubuntu3 in noble amd64 nvidia-headless-418 430.50-0ubuntu3 in noble amd64 nvidia-headless-no-dkms-418 430.50-0ubuntu3 in noble amd64 nvidia-kernel-common-418 430.50-0ubuntu3 in noble amd64 nvidia-kernel-source-418 430.50-0ubuntu3 in noble amd64 nvidia-utils-418 430.50-0ubuntu3 in noble amd64 xserver-xorg-video-nvidia-418 430.50-0ubuntu3 in noble amd64 Comment: Unsupported driver version; LP: #2048087 1 package successfully removed. ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Triaged => Fix Released -- 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: 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§ion=all&arch=any&keywords=nvidia- graphics-drivers&searchon=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 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Lunar that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2017006] Proposed package removed from archive
The version of lttng-modules in the proposed pocket of Jammy that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
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/2017006
Title:
fix build issue for v5.19 kernels (jammy-hwe, kinetic, lunar-riscv)
Status in linux package in Ubuntu:
Invalid
Status in lttng-modules package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux source package in Jammy:
Invalid
Status in lttng-modules source package in Jammy:
Won't Fix
Status in linux source package in Kinetic:
Invalid
Status in lttng-modules source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Invalid
Status in lttng-modules source package in Lunar:
Won't Fix
Status in linux source package in Mantic:
Invalid
Bug description:
SRU Justification
[ Impact ]
Upstream stable added a change in the format of jbd2 in 5.15.87 that
was cherry-picked to kinetic:linux.
This is incompatible with the current changes in the lttng-module
kinetic.
We previously encountered this issue for focal
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2004644
and we proactively released a new version for kinetic.
The problem is the fix does not really work as expected.
As shown in the logs below,
The build error is triggered because some function declaration does not match
the kernel's.
In `include/instrumentation/events/jbd2.h` in lttng-modules, there is a
conditional declaration based on the kernel version. 5.19 is missing there,
therefore kinetic will fall back to the old declaration. The reason 5.19 is not
there is probably because this version has reached end of life last year.
Build logs:
35:35 DEBUG| [stdout] In file included from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/define_trace.h:87,
860 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:293,
861 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:29:
862 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:133:6:
error: conflicting types for ‘trace_jbd2_run_stats’; have ‘void(dev_t, long
unsigned int, struct transaction_run_stats_s *)’ {aka ‘void(unsigned int,
long unsigned int, struct transaction_run_stats_s *)’}
863 02:35:35 DEBUG| [stdout] 133 | void
trace_##_name(_proto);
864 02:35:35 DEBUG| [stdout] | ^~
865 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:45:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’
866 02:35:35 DEBUG| [stdout]45 |
LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args))
867 02:35:35 DEBUG| [stdout] |
^~~
868 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/lttng/tracepoint-event-impl.h:87:9:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’
869 02:35:35 DEBUG| [stdout]87 |
LTTNG_TRACEPOINT_EVENT_MAP(name, name, \
870 02:35:35 DEBUG| [stdout] |
^~
871 02:35:35 DEBUG| [stdout]
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/../../include/instrumentation/events/jbd2.h:180:1:
note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’
872 02:35:35 DEBUG| [stdout] 180 |
LTTNG_TRACEPOINT_EVENT(jbd2_run_stats,
873 02:35:35 DEBUG| [stdout] | ^~
874 02:35:35 DEBUG| [stdout] In file included from
./include/trace/events/jbd2.h:9,
875 02:35:35 DEBUG| [stdout] from
/var/lib/dkms/lttng-modules/2.13.8/build/src/probes/lttng-probe-jbd2.c:18:
876 02:35:35 DEBUG| [stdout]
./include/linux/tracepoint.h:245:28: note: previous definition of
‘trace_jbd2_run_stats’ with type ‘void(dev_t, tid_t, struct
transaction_run_stats_s *)’ {aka ‘void(unsigned int, unsigned int, struct
transaction_run_stats_s *)’}
877 02:35:35 DEBUG| [stdout] 245 | static inline
void trace_##name(proto) \
878 02:35:35 DEBUG| [stdout] |
^~
879
[Kernel-packages] [Bug 2048404] [NEW] Don't WARN_ON_ONCE() for a broken discovery table
Public bug reported:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore: Don't
WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has been
changed.
[Other Info]
SF: #00347830
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Description changed:
SRU Justification
- [Impacy]
+ [Impact]
- perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
-
- The kernel warning message is triggered, when SPR MCC is used.
-
- [ 17.945331] [ cut here ]
- [ 17.946305] WARNING: CPU: 65 PID: 1 at
- arch/x86/events/intel/uncore_discovery.c:184
- intel_uncore_has_discovery_tables+0x4c0/0x65c
- [ 17.946305] Modules linked in:
- [ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
- 5.4.17-2136.313.1-X10-2c+ #4
-
- It's caused by the broken discovery table of UPI.
-
- The discovery tables are from hardware. Except for dropping the broken
- information, there is nothing Linux can do. Using WARN_ON_ONCE() is
- overkilled.
-
- Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
- is dropped and the reason.
+ perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
+
+ The kernel warning message is triggered, when SPR MCC is used.
+
+ [ 17.945331] [ cut here ]
+ [ 17.946305] WARNING: CPU: 65 PID: 1 at
+ arch/x86/events/intel/uncore_discovery.c:184
+ intel_uncore_has_discovery_tables+0x4c0/0x65c
+ [ 17.946305] Modules linked in:
+ [ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
+ 5.4.17-2136.313.1-X10-2c+ #4
+
+ It's caused by the broken discovery table of UPI.
+
+ The discovery tables are from hardware. Except for dropping the broken
+ information, there is nothing Linux can do. Using WARN_ON_ONCE() is
+ overkilled.
+
+ Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
+ is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea5331998f27df7946a69f14dc3 ('perf/x86/uncore: Don't
WARN_ON_ONCE() for a broken discovery table')
[Test]
AWS tested
[Regression potential]
Low regression potential. Only the code that prints the warning has been
changed.
[Other Info]
SF: #00347830
--
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/2048404
Title:
Don't WARN_ON_ONCE() for a broken discovery table
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Bug description:
SRU Justification
[Impact]
perf/x86/uncore: Don't WARN_ON_ONCE() for a broken discovery table
The kernel warning message is triggered, when SPR MCC is used.
[ 17.945331] [ cut here ]
[ 17.946305] WARNING: CPU: 65 PID: 1 at
arch/x86/events/intel/uncore_discovery.c:184
intel_uncore_has_discovery_tables+0x4c0/0x65c
[ 17.946305] Modules linked in:
[ 17.946305] CPU: 65 PID: 1 Comm: swapper/0 Not tainted
5.4.17-2136.313.1-X10-2c+ #4
It's caused by the broken discovery table of UPI.
The discovery tables are from hardware. Except for dropping the broken
information, there is nothing Linux can do. Using WARN_ON_ONCE() is
overkilled.
Use the pr_info() to replace WARN_ON_ONCE(), and specify what uncore unit
is dropped and the reason.
[Fix]
Commit 5d515ee40cb57ea53
[Kernel-packages] [Bug 2046082] Re: zed.rc: typo in option ZED_POWER_OFF_ENCLO*US*RE_SLOT_ON_FAULT
Normally, changing a conffile in an SRU is iffy because this may result
in conffile prompts for the user on upgrade, and will cause unattended-
upgrades to hold the package back.
In this case we're fixing a regression in a conffile that was introduced
already in -updates. So, ok.
** Changed in: zfs-linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
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 2046082] Please test proposed package
Hello Mauricio, or anyone else affected,
Accepted zfs-linux into mantic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.2.0-0ubuntu1~23.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
mantic to verification-done-mantic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-mantic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to 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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted
Hello Guillaume, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.23 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837227 Title: systemd mount units fail during boot, while file system is correctly mounted Status in systemd: New Status in Ubuntu Pro: In Progress Status in Ubuntu Pro 18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in systemd source package in Bionic: Won't Fix Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [Impact] systemd mount units fail during boot, and the system boots into emergency mode [Test Plan] This issue seems to happen randomly, and doesn't seem related to a specific mount unit. We've used a test script with good results during investigation to reproduce similar mount failures in a running system, and have seen a strong correlation between the script failures and the boot time mount failures. The attached 'rep-tmpfs.sh' script should be used to validate that mount points are working correctly under stress. One can run through the different variants as below: # ./rep-tmpfs.sh --variant-0 # ./rep-tmpfs.sh --variant-1 # ./rep-tmpfs.sh --variant-2 # ./rep-tmpfs.sh --variant-3 # ./rep-tmpfs.sh --variant-4 All of these should run successfully without any reported errors. [Where problems could occur] The patches change the way systemd tracks and handles mount points in general, so potential regressions could affect other mount units. We should keep an eye out for any issues with mounting file systems, as well as rapid mount/unmount operations. Successful test runs with the reproducer script should increase reliability in having no new regressions. [Other Info] This has been tackled upstream with several attempts, which have resulted in the final patch from 2022: 01400460ae16 core/mount: adjust deserialized state based on /proc/self/mountinfo For Bionic, systemd requires several dependency patches as below: 6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a new unit cycle 7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the other way round 350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() results 1d086a6e5972 mount: mark an existing "mounting" unit from /proc/self/mountinfo as "just_mounted" Additionally, the kernel also requires the following patches: 28ca0d6d39ab list: introduce list_for_each_continue() 9f6c61f96f2d proc/mounts: add cursor [Original Description] In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1837227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.laun
[Kernel-packages] [Bug 2047208] Re: MaaS installed image unbootable on Ampere Altra
can you supply any more boot logs? ie: are you getting the same "You must load the kernel first" error as in https://bugs.launchpad.net/maas/+bug/2044169? I suspect this is a broken/malformed image ** Changed in: maas 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/2047208 Title: MaaS installed image unbootable on Ampere Altra Status in MAAS: Incomplete Status in linux package in Ubuntu: New Bug description: Over the past few days, I attempted to install a new ampere altra server with Ubuntu 22.04 via MaaS, the 22.04 arm image will not PXE boot/boot loops on the altra. 20.04 will PXE boot and install to the hard drive, but on subsequent boots, the image will not boot unless pxe booted first and then fall back to local GRUB on the disk - which seems to workaround the UEFI issue at boot. The system is running a supermicro build of the v2.10 altra SCP, and I think that's wherein the issue lays. There is a likely related patch here: https://lore.kernel.org/linux-arm- kernel/camj1kxety24d8syukkix7nr0pax2vzdvelnc64bz65ughup...@mail.gmail.com/T/ I am wondering if that or similar is incorporated/can be incorporated into the Ubuntu 22.04 LTS release image. Also, noted that the rescue image for MaaS fails with "bad magic number" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2047208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048373] Re: Copying big files to a mounted Synology NAS crashes the NAS
** Description changed: Situation: OS: Xubuntu 22.04.3 Kernel version: 6.2.0-39-generic Network driver: r8169 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) NAS model: Synology DiskStation DS223 - The problem: On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted a Synology DS223 NAS. It mounts without any problems and at first glance everything seems to be working fine, until you start uploading large(r) files (200MB+) to the NAS. The NAS will then randomly and for unknown reasons crash or halt, causing the Xubuntu OS to halt or crash in turn. It does so in any application (Thunar, copying files in bash, tuxcommander etc). So, this problem doesn't seem to be application-related. I tried mounting the NAS with different/additional mount-options and tried several network settings and even checked the physical cables but nothing had any effect. - The solution: Eventually, I managed to trace the problem to my network device and I replaced the r8169 driver for the r8168 version. This immediately solved my problem. Now, copying from-and-to the mounted NAS works as expected. Even though my problem is solved by installing the r8168 version of the driver, there probably still remains a bug in the default r8169 driver that causes this problem with my current setup. + + Note: The r8169 driver is integrated in the kernel whereas the r8168 + driver can be installed by installing the r8168-dkms package and + disabling (blacklisting) the r8169 driver in the kernel. -- 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/2048373 Title: Copying big files to a mounted Synology NAS crashes the NAS Status in linux package in Ubuntu: New Bug description: Situation: OS: Xubuntu 22.04.3 Kernel version: 6.2.0-39-generic Network driver: r8169 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) NAS model: Synology DiskStation DS223 The problem: On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted a Synology DS223 NAS. It mounts without any problems and at first glance everything seems to be working fine, until you start uploading large(r) files (200MB+) to the NAS. The NAS will then randomly and for unknown reasons crash or halt, causing the Xubuntu OS to halt or crash in turn. It does so in any application (Thunar, copying files in bash, tuxcommander etc). So, this problem doesn't seem to be application- related. I tried mounting the NAS with different/additional mount- options and tried several network settings and even checked the physical cables but nothing had any effect. The solution: Eventually, I managed to trace the problem to my network device and I replaced the r8169 driver for the r8168 version. This immediately solved my problem. Now, copying from-and-to the mounted NAS works as expected. Even though my problem is solved by installing the r8168 version of the driver, there probably still remains a bug in the default r8169 driver that causes this problem with my current setup. Note: The r8169 driver is integrated in the kernel whereas the r8168 driver can be installed by installing the r8168-dkms package and disabling (blacklisting) the r8169 driver in the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048373] [NEW] Copying big files to a mounted Synology NAS crashes the NAS
Public bug reported: Situation: OS: Xubuntu 22.04.3 Kernel version: 6.2.0-39-generic Network driver: r8169 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) NAS model: Synology DiskStation DS223 The problem: On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted a Synology DS223 NAS. It mounts without any problems and at first glance everything seems to be working fine, until you start uploading large(r) files (200MB+) to the NAS. The NAS will then randomly and for unknown reasons crash or halt, causing the Xubuntu OS to halt or crash in turn. It does so in any application (Thunar, copying files in bash, tuxcommander etc). So, this problem doesn't seem to be application-related. I tried mounting the NAS with different/additional mount-options and tried several network settings and even checked the physical cables but nothing had any effect. The solution: Eventually, I managed to trace the problem to my network device and I replaced the r8169 driver for the r8168 version. This immediately solved my problem. Now, copying from-and-to the mounted NAS works as expected. Even though my problem is solved by installing the r8168 version of the driver, there probably still remains a bug in the default r8169 driver that causes this problem with my current setup. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: r8169 -- 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/2048373 Title: Copying big files to a mounted Synology NAS crashes the NAS Status in linux package in Ubuntu: New Bug description: Situation: OS: Xubuntu 22.04.3 Kernel version: 6.2.0-39-generic Network driver: r8169 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01) NAS model: Synology DiskStation DS223 The problem: On a freshly installed Xubuntu 22.04.3, I use a cifs-mounted a Synology DS223 NAS. It mounts without any problems and at first glance everything seems to be working fine, until you start uploading large(r) files (200MB+) to the NAS. The NAS will then randomly and for unknown reasons crash or halt, causing the Xubuntu OS to halt or crash in turn. It does so in any application (Thunar, copying files in bash, tuxcommander etc). So, this problem doesn't seem to be application- related. I tried mounting the NAS with different/additional mount- options and tried several network settings and even checked the physical cables but nothing had any effect. The solution: Eventually, I managed to trace the problem to my network device and I replaced the r8169 driver for the r8168 version. This immediately solved my problem. Now, copying from-and-to the mounted NAS works as expected. Even though my problem is solved by installing the r8168 version of the driver, there probably still remains a bug in the default r8169 driver that causes this problem with my current setup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048376] [NEW] touchpad not working at all
Public bug reported: hey when i restarted my laptop my touchpad does not work at all i tried for solution in google it said to file a bug report on this problem so i am doing this ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 5 19:45:15 2024 InstallationDate: Installed on 2022-06-23 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2048376 Title: touchpad not working at all Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: hey when i restarted my laptop my touchpad does not work at all i tried for solution in google it said to file a bug report on this problem so i am doing this ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-39-generic 6.2.0-39.40~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 5 19:45:15 2024 InstallationDate: Installed on 2022-06-23 (561 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2048376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
Nevermind, found the relevant commit/revert https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=Ubuntu- hwe-6.5-6.5.0-14.14_22.04.1&id=21f3ac7412644fb59a13db2e3adbb8a38cba9923 -- 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/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: Fix Released Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- the-generation-in-ubuntu-23-10/38972 for the performance evaluation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2028568] Re: Ship kernel modules Zstd compressed
I spoted that for jammy hwe 6.5.0-14.14 the modules are still not compressed, albeit CONFIG_MODULE_COMPRESS_ZSTD is 'y' for amd64 in config/annotations. I also spotted that when the modules are compressed, DKMS compresses built modules too, but DKMS v2.8.7 (the version running in jammy) has a bug that compressed modules don't get MOK signed. -- 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/2028568 Title: Ship kernel modules Zstd compressed Status in linux package in Ubuntu: Fix Released Bug description: To reduce the size of the initramfs and also to speed up the boot (by only decompressing the modules that are needed), please compress the kernel modules. From size and speed perspective, either use zstd or xz. I suggest to go with zstd -19. This change is independent of the initramfs-tools version. Old initramfs-tools versions will decompress the kernel modules before putting them in the initramfs. New initramfs-tools versions will put the compressed kernel modules into an uncompressed cpio archive (see bug #2028567). See also https://lists.ubuntu.com/archives/ubuntu- devel/2023-July/042652.html and https://lists.ubuntu.com/archives/ubuntu-devel/2023-July/042707.html See https://discourse.ubuntu.com/t/reduce-initramfs-size-and-speed-up- the-generation-in-ubuntu-23-10/38972 for the performance evaluation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2028568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048234] [NEW] Jammy update: v6.1.70 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.70 upstream stable release from git://git.kernel.org/ Linux 6.1.70 loop: deprecate autoloading callback loop_probe() wifi: nl80211: fix deadlock in nl80211_set_cqm_rssi (6.6.x) wifi: cfg80211: fix CQM for non-range use fuse: share lookup state between submount and its parent mm/damon/core: make damon_start() waits until kdamond_fn() starts x86/alternatives: Sync core before enabling interrupts KVM: arm64: vgic: Force vcpu vgic teardown on vcpu destroy KVM: arm64: vgic: Add a non-locking primitive for kvm_vgic_vcpu_destroy() KVM: arm64: vgic: Simplify kvm_vgic_destroy() thunderbolt: Fix memory leak in margining_port_remove() lib/vsprintf: Fix %pfwf when current node refcount == 0 gpio: dwapb: mask/unmask IRQ when disable/enale it bus: ti-sysc: Flush posted write only after srst_udelay pinctrl: starfive: jh7100: ignore disabled device tree nodes dm-integrity: don't modify bio's immutable bio_vec in integrity_metadata() tracing / synthetic: Disable events after testing in synth_event_gen_test_init() scsi: core: Always send batch on reset or error handling command Revert "scsi: aacraid: Reply queue mapping to CPUs based on IRQ affinity" selftests: mptcp: join: fix subflow_send_ack lookup ublk: move ublk_cancel_dev() out of ub->mutex ubifs: fix possible dereference after free btrfs: zoned: no longer count fresh BG region as zone unusable Revert "drm/amd/display: Do not set DRR on pipe commit" dm thin metadata: Fix ABBA deadlock by resetting dm_bufio_client loop: do not enforce max_loop hard limit by (new) default RISC-V: Fix do_notify_resume / do_work_pending prototype 9p: prevent read overrun in protocol dump tracepoint drm/i915: Reject async flips with bigjoiner smb: client: fix OOB in smbCalcSize() smb: client: fix OOB in SMB2_query_info_init() smb: client: fix potential OOB in cifs_dump_detail() smb: client: fix OOB in cifsd when receiving compounded resps dt-bindings: nvmem: mxs-ocotp: Document fsl,ocotp net: ks8851: Fix TX stall caused by TX buffer overrun net: rfkill: gpio: set GPIO direction net: 9p: avoid freeing uninit memory in p9pdu_vreadf Input: soc_button_array - add mapping for airplane mode button net: usb: ax88179_178a: avoid failed operations when device is disconnected Bluetooth: Add more enc key size check Bluetooth: MGMT/SMP: Fix address type when using SMP over BREDR/LE Bluetooth: L2CAP: Send reject on command corrupted request Bluetooth: af_bluetooth: Fix Use-After-Free in bt_sock_recvmsg Bluetooth: hci_event: Fix not checking if HCI_OP_INQUIRY has been sent ALSA: hda/realtek: Add quirk for ASUS ROG GV302XA USB: serial: option: add Quectel RM500Q R13 firmware support USB: serial: option: add Foxconn T99W265 with new baseline USB: serial: option: add Quectel EG912Y module support USB: serial: ftdi_sio: update Actisense PIDs constant names wifi: cfg80211: fix certs build to not depend on file order wifi: cfg80211: Add my certificate usb-storage: Add quirk for incorrect WP on Kingston DT Ultimate 3.0 G3 ALSA: usb-audio: Increase delay in MOTU M quirk iio: triggered-buffer: prevent possible freeing of wrong buffer iio: adc: ti_am335x_adc: Fix return value check of tiadc_request_dma() iio: common: ms_sensors: ms_sensors_i2c: fix humidity conversion time table scsi: bnx2fc: Fix skb double free in bnx2fc_rcv() Input: ipaq-micro-keys - add error handling for devm_kmemdup interconnect: qcom: sm8250: Enable sync_state iio: imu: inv_mpu6050: fix an error code problem in inv_mpu6050_read_raw interconnect: Treat xlate() returning NULL node as an error drm/i915: Fix ADL+ tiled plane stride when the POT stride is smaller than the original drm/i915/mtl: Add MTL for remapping CCS FBs drm/i915/dpt: Only do the POT stride remap when using DPT drm/i915: Fix intel_atomic_setup_scalers() plane_state handling drm/i915: Relocate intel_atomic_setup_scalers() drm/i915/mtl: limit second scaler vertical scaling in ver >= 14 nvme-pci: fix sleeping function called from interrupt context gpiolib: cdev: add gpio_device locking wrapper around gpio_ioctl() pinctrl: at91-pio4: use dedicated lock class for IRQ x86/xen: add CPU dependencies for 32-bit build i2c: aspeed: Handle the coalesced stop conditions with the start conditions. ASoC: fsl_sai: Fix channel swap issue on i.MX8MP ASoC: hdmi-codec: fix missing report for jack initial status afs: Fix use-after-free due to get/remove race in volume tree afs: Fix overwriting of result of DNS query keys, dns: Allow key types (eg. DNS) to be reclaimed immediately on expiry net: che
[Kernel-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Same problem Razer Blade 16 2023 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035123] Re: scripts/pahole-flags.sh change return to exit 0
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2
verification-needed-focal-linux-nvidia-tegra-5.15
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2035123
Title:
scripts/pahole-flags.sh change return to exit 0
Status in linux package in Ubuntu:
Fix Released
Status in linux-bluefield package in Ubuntu:
Triaged
Status in linux source package in Jammy:
Fix Released
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2035123
[Impact]
When building the Jammy linux-bluefield kernel tree on a system
without pahole installed, the following warning is emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
scripts/pahole-flags.sh attempts to return from an if statement that
is not within a function, and generates a warning.
The fix is straightforward, changing return to an exit 0.
--- a/scripts/pahole-flags.sh
+++ b/scripts/pahole-flags.sh
@@ -4,7 +4,7 @@
extra_paholeopt=
if ! [ -x "$(command -v ${PAHOLE})" ]; then
- return
+ exit 0
fi
[Testcase]
Clone the linux-bluefield kernel tree and build it on a arm64 system without
pahole installed.
A test kernel is available with the fix applied in:
https://launchpad.net/~mruffell/+archive/ubuntu/sf368560-test
Both linux-bluefield and ubuntu-jammy build correctly.
[Fix]
This was fixed by Linus Torvalds in the following merge commit:
commit fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Merge: bfc484fe6abb 84882cf72cd7
Author: Linus Torvalds
Date: Tue Nov 2 06:20:58 2021 -0700
Subject: Merge tag 'net-next-for-5.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fc02cb2b37fe2cbf1d3334b9f0f0eab9431766c4
Note, the original commit does not have the fix included:
commit 9741e07ece7c247dd65e1aa01e16b683f01c05a8
Author: Jiri Olsa
Date: Fri Oct 29 14:57:29 2021 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9741e07ece7c247dd65e1aa01e16b683f01c05a8
The Ubuntu kernel cherry-picked the original commit and did not pick up the
silent fix made in the merge commit. Submitting the silent fix as a SAUCE
patch
with changelog describing the change.
Note: I know SAUCE patches are bad, but in this scenario, to revert
the initial commit and re-apply the fixed version would require us to
revert two additional dependency commits, making six patches to
review, vs, a one line change in a SAUCE commit that has a real
changelog entry.
[Where problems could occur]
The Ubuntu kernel is built with pahole enabled, and requires pahole to
be installed as a build dependency. It is extremely unlikely that any
users are disabling pahole at build time, apart from linux-bluefield
engineers.
If a regression were to occur, engineers would see errors during build
time about scripts/pahole-flags.sh not executing properly.
[Other info]
Linus remarked about the issue in the following lkml discussion:
https://lore.kernel.org/lkml/CAHk-=wgdE6=ob5nf60gvryag24mkajbgjf3jpufme1k_upb...@mail.gmail.com/
https://lore.kernel.org/lkml/CAHk-=wgPZM4bN=LUCrMkG3FX808QSLm6Uv6ixm5P350_7c=x...@mail.gmail.com/
This was silently Incorporated into the linux-stable commit:
commit 0baced0e0938f2895ceba54038eaf15ed91032e7 5.15.y
From: Jiri Olsa
Date: Sun, 4 Sep 2022 15:19:00 +0200
Subject: kbuild: Unify options for BTF generation for vmlinux and modules
Link:
https://github.com/gregkh/linux/commit/0baced0e0938f2895ceba54038eaf15ed91032e7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035123/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHe
[Kernel-packages] [Bug 2037513] Re: HP ProBook 450 G8 Notebook fail to wifi test
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2037513 Title: HP ProBook 450 G8 Notebook fail to wifi test Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-signed-hwe-5.15 source package in Jammy: Invalid Bug description: I'm reviewing the SRU test result on this machine. I found that this machine always fails to wifi test and also pop out a lot of error message in dmesg. It's not a regression, since according to previous test run it has failed already. Just because we missed reviewing it for a while. The journal log is attach, please check further hardware informations at https://certification.canonical.com/hardware/202106-29176/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-86-generic 5.15.0-86.96~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-86.96~20.04.1-generic 5.15.122 Uname: Linux 5.15.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 27 15:47:37 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20220621-7+pc-stella-cmit-focal-amd64+X00 InstallationDate: Installed on 2023-09-25 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220621-04:14 SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2037513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar, jammy and focal
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- 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/2043197 Title: USB bus error after upgrading to proposed kernel on lunar, jammy and focal Status in linux package in Ubuntu: Triaged Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Bug description: == SRU Justification == [Impact] USB SuperSpeed (3.0) devcies can't be enumerated on Lunar/Jammy kernel. [Fix] Use logarithmic encoding for the bMaxPacketSize0 value. [Test] With the patch applied, SuperSpeed devices can be enumerated across several reboots. [Where problems could occur] The switch case for Wireless USB (not USB WiFi dongle) was removed by the fix. I am not aware of the existence of any Wireless USB device. But if they do exist, this patch may the packet size encoding on them. == Original Bug Report == [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-module
[Kernel-packages] [Bug 2033406] Re: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- 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/2033406 Title: [SRU][J/L/M] UBUNTU: [Packaging] Make WWAN driver a loadable module Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: == SRU Justification == The CONFIG_WWAN config is set to 'Y' for the generic and most derivative kernels. This is affecting custom driver development for some partners. Change this config to be a loadable module and include it in linux- modules-*. Make this change to -generic kernels, so all derivatives will inherit it. == Fix == UBUNTU: [Packaging] Make WWAN driver loadable modules == Regression Potential == Medium. This change is only to WWAN, and is changing it to a loadable module and not removing it. == Test Case == A test kernel was built with this patch and tested by a partner. It was also compile and boot tested internally. Testing will also be performed on a WWAN device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040157] Re: Unable to use nvme drive to install Ubuntu 23.10
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-focal-linux-
nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'.
If the problem still exists, change the tag 'verification-needed-focal-
linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia-
tegra-5.15'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2
verification-needed-focal-linux-nvidia-tegra-5.15
--
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/2040157
Title:
Unable to use nvme drive to install Ubuntu 23.10
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Lunar:
Fix Released
Status in linux source package in Mantic:
Fix Committed
Bug description:
The 6.5 kernel in the 23.10 installer ISO is unable to work with an
NVME drive in the laptop, and it is not possible to install Ubuntu. It
might be related to Kernel bug
https://bugzilla.kernel.org/show_bug.cgi?id=217802 fixed in 6.5.6.
dmesg:
[ 42.116742] nvme nvme0: controller is down; will reset: CSTS=0x,
PCI_STATUS=0x
[ 42.116764] nvme nvme0: Does your device have a faulty power saving mode
enabled?
[ 42.116769] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
[ 42.149334] nvme0n1: I/O Cmd(0x2) @ LBA 370339840, 8 blocks, I/O Error
(sct 0x3 / sc 0x71)
[ 42.149357] I/O error, dev nvme0n1, sector 370339840 op 0x0:(READ) flags
0x80700 phys_seg 1 prio class 2
[ 42.164760] nvme :04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
[ 42.165160] nvme nvme0: Disabling device after reset failure: -19
[ 42.180818] Buffer I/O error on dev nvme0n1p7, logical block 0, async page
read
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 10:53:50 2023
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2023
dmi.bios.release: 1.33
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.33.0
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.33.0:bd07/04/2023:br1.33:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.product.sku: 07BF
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2040157/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039575] Re: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- 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/2039575 Title: SMC stats: Wrong bucket calculation for payload of exactly 4096 bytes Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification: [Impact] * There is a wrong bucket calculation for payload of exactly 4096 bytes in SMC stats counters. * SMC_STAT_PAYLOAD_SUB and SMC_STAT_RMB_SIZE_SUB have these issues. * The impact is that a system silently updates an incorrect stats counter in case the underlying kernel is not UBSAN enabled. (Difficult to detect.) * But if a kernel is UBSAN enabled, one will see a UBSAN 'array-index-out-of-bounds' warning every time this occurs, like: [ 26.335381] UBSAN: array-index-out-of-bounds in /build/linux-O6Qi7m/linux-5.15.0/net/smc/af_smc.c:2402:3 [ 26.335385] index -1 is out of range for type 'u64 [9]' [ 26.335388] CPU: 0 PID: 274 Comm: iperf3 Tainted: G E 5.15.0-79-generic #86-Ubuntu [ 26.335391] Hardware name: IBM 8561 T01 772 (KVM/Linux) [ 26.335393] Call Trace: [ 26.335397] [] dump_stack_lvl+0x62/0x80 [ 26.335404] [ ] ubsan_epilogue+0x1c/0x48 [ 26.335406] [ ] __ubsan_handle_out_of_bounds+0x94/0xa0 [ 26.335411] [<03ff8033f9da>] smc_sendmsg+0x2aa/0x2d0 [smc] [ 26.335425] [ ] sock_sendmsg+0x64/0x80 [ 26.335431] [ ] sock_write_iter+0x72/0xa0 [ 26.335433] [ ] new_sync_write+0x100/0x190 [ 26.335438] [ ] vfs_write+0x1e8/0x280 [ 26.335440] [ ] ksys_write+0xb4/0x100 [ 26.335442] [ ] __do_syscall+0x1bc/0x1f0 [ 26.335446] [ ] system_call+0x78/0xa0 [Fix] * a950a5921db4 a950a5921db450c74212327f69950ff03419483a "net/smc: Fix pos miscalculation in statistics" [Test Plan] * Since this got identified while the livepatch for jammy patches got added, one could run a simiar (or the same) test like mentioned at LP#1639924 (but only jammy comes with official livepatch support). * Alternatively a dedicated SMC stats counters test with a payload of exactly 4096 bytes could be done (which is probably easier): * Install uperf (https://uperf.org/ - https://github.com/uperf/uperf). (Wondering if it makes sense to pick this up as Debian/Ubuntu package ?!) * Reset SMC-D stats on client and server side. * Start uperf at the server side using: # uperf -vs * Update profile with remote IP (server IP) and start uperf at client: # uperf -vai 5 -m rr1c-4kx4k---1.xml with uperf profile: # cat rr1c-4kx4k---1.xml * The smcd stats output is: # smcd -d stats reset SMC-D Connections Summary Total connections handled 2 SMC connections 2 (client 2, server 0) v1 0 v2 2 Handshake errors 0 (client 0, server 0) Avg requests per SMC conn 14.0 TCP fallback 0 (client 0, server 0) RX Stats Data transmitted (Bytes) 5796 (5.796K) Total requests 9 Buffer full 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 0 0 2 0 0 0 1 Reqs 8 0 0 0 0 0 0 0 TX Stats Data transmitted (Bytes) 9960 (9.960K) Total requests 19 Buffer full 0 (0.00%) Buffer full (remote) 0 (0.00%) Buffer too small 0 (0.00%) Buffer too small (remote) 0 (0.00%) Buffer downgrades 0 Buffer reuses 0 8KB 16KB 32KB 64KB 128KB 256KB 512KB >512KB Bufs 0 2 0 0 0
[Kernel-packages] [Bug 2039439] Re: usbip: error: failed to open /usr/share/hwdata//usb.ids
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- 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/2039439 Title: usbip: error: failed to open /usr/share/hwdata//usb.ids Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Committed Bug description: [Impact] usbip from linux-tools tries to access /usr/share/hwdata/usb.ids which is provided by the hwdata package which is not installed by default. $ usbip list -l usbip: error: failed to open /usr/share/hwdata//usb.ids - busid 1-1.1.1 (0424:7800) unknown vendor : unknown product (0424:7800) [Test Case] $ apt install linux-tools- $ usbip list -l - busid 1-1.1.1 (0424:7800) Microchip Technology, Inc. (formerly SMSC) : unknown product (0424:7800) [Fix] Make hwdata a dependency of linux-tools-common. [Regression Potential] A trivial package (hwdata) is installed as a dependency. Can't think of any problems this could cause other than a theoretical package installation failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039439/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1
This bug is awaiting verification that the linux-nvidia- tegra-5.15/5.15.0-1020.20~20.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux- nvidia-tegra-5.15' to 'verification-done-focal-linux-nvidia-tegra-5.15'. If the problem still exists, change the tag 'verification-needed-focal- linux-nvidia-tegra-5.15' to 'verification-failed-focal-linux-nvidia- tegra-5.15'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-nvidia-tegra-5.15-v2 verification-needed-focal-linux-nvidia-tegra-5.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota Apply pull request from NVIDIA received on 2023-11-27 EJ Hsu (1): NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux Register Linus Walleij (1): Revert "pinctrl: tegra: Add support to display pin function" Penny Chiu (3): NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig NVIDIA: SAUCE: arm64: configs: Enable NFS server support NVIDIA: SAUCE: arm64: configs: Enable dm_multipath driver Thierry Reding (1): pinctrl: tegra: Display pin function in pinconf-groups Vince Hsu (1): NVIDIA: SAUCE: arm64: configs: enable few matches for netfliter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2042935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046534] Re: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2046534 Title: Page fault in RDMA ODP triggers BUG_ON during MMU notifier registration Status in linux package in Ubuntu: New Status in linux source package in Focal: Fix Committed Bug description: [Impact] When a page fault is triggered in RDMA ODP, it registers an MMU notifier during the process. Unfortunately, an error arises due to a race condition where the mm is released while attempting to register a notifier. == Oct 14 23:38:32 bnode001 kernel: [1576115.901880] kernel BUG at mm/mmu_notifier.c:255! Oct 14 23:38:32 bnode001 kernel: [1576115.909129] RSP: :bd3def843c90 EFLAGS: 00010246 Oct 14 23:38:32 bnode001 kernel: [1576115.912689] RAX: a11635d2 RBX: a0f913ba5800 RCX: Oct 14 23:38:32 bnode001 kernel: [1576115.912691] RDX: c0b666f0 RSI: c0b601c7 RDI: a0f913ba5850 Oct 14 23:38:32 bnode001 kernel: [1576115.913564] RAX: RBX: c0b5a060 RCX: Oct 14 23:38:32 bnode001 kernel: [1576115.913565] RDX: 0007 RSI: a1152ed3c400 RDI: a1102dcd4300 Oct 14 23:38:32 bnode001 kernel: [1576115.914431] RBP: bd3defcb7c88 R08: a1163f4f50e0 R09: a11638c072c0 Oct 14 23:38:32 bnode001 kernel: [1576115.914432] R10: a0fd99a0 R11: R12: a1152c923b80 Oct 14 23:38:32 bnode001 kernel: [1576115.915263] RBP: bd3def843cb0 R08: a1163f7350e0 R09: a11638c072c0 Oct 14 23:38:32 bnode001 kernel: [1576115.915265] R10: a1088d00 R11: R12: a1102dcd4300 Oct 14 23:38:32 bnode001 kernel: [1576115.916079] R13: a1152c923b80 R14: a1152c923bf8 R15: a114f8127800 Oct 14 23:38:32 bnode001 kernel: [1576115.916080] FS: () GS:a1163f4c() knlGS: Oct 14 23:38:32 bnode001 kernel: [1576115.917705] R13: a1152ed3c400 R14: a1152ed3c478 R15: a1101cbfbc00 Oct 14 23:38:32 bnode001 kernel: [1576115.917706] FS: () GS:a1163f70() knlGS: Oct 14 23:38:32 bnode001 kernel: [1576115.918506] CS: 0010 DS: ES: CR0: 80050033 Oct 14 23:38:32 bnode001 kernel: [1576115.918508] CR2: 7f94146af5e0 CR3: 001722472004 CR4: 00760ee0 Oct 14 23:38:32 bnode001 kernel: [1576115.919301] CS: 0010 DS: ES: CR0: 80050033 Oct 14 23:38:32 bnode001 kernel: [1576115.919302] CR2: 7f32f0a2dc80 CR3: 001f9f1fc004 CR4: 00760ee0 Oct 14 23:38:32 bnode001 kernel: [1576115.920082] DR0: DR1: DR2: Oct 14 23:38:32 bnode001 kernel: [1576115.920084] DR3: DR6: fffe07f0 DR7: 0400 Oct 14 23:38:32 bnode001 kernel: [1576115.920850] DR0: DR1: DR2: Oct 14 23:38:32 bnode001 kernel: [1576115.921604] PKRU: 5554 Oct 14 23:38:32 bnode001 kernel: [1576115.921605] Call Trace: Oct 14 23:38:32 bnode001 kernel: [1576115.922354] DR3: DR6: fffe07f0 DR7: 0400 Oct 14 23:38:32 bnode001 kernel: [1576115.922355] PKRU: 5554 Oct 14 23:38:32 bnode001 kernel: [1576115.923112] mmu_notifier_get_locked+0x5f/0xe0 Oct 14 23:38:32 bnode001 kernel: [1576115.923867] Call Trace: Oct 14 23:38:32 bnode001 kernel: [1576115.923870] ? mmu_notifier_get_locked+0x79/0xe0 Oct 14 23:38:32 bnode001 kernel: [1576115.924645] ib_umem_odp_alloc_child+0x15a/0x290 [ib_core] Oct 14 23:38:32 bnode001 kernel: [1576115.925409] ib_umem_odp_alloc_child+0x15a/0x290 [ib_core] Oct 14 23:38:32 bnode001 kernel: [1576115.926161] pagefault_mr+0x312/0x5d0 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.926906] pagefault_mr+0x312/0x5d0 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.927651] pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.928393] pagefault_single_data_segment.isra.0+0x284/0x490 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.929131] mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.929866] mlx5_ib_eqe_pf_action+0x7d5/0x990 [mlx5_ib] Oct 14 23:38:32 bnode001 kernel: [1576115.930610] process_one_work+0x1eb/0x3b0 Oct 14 23:38:32 bnode001 kernel: [1576115.931351] process_one_work+0x1eb/0x3b0 Oct 14 23:38:32 bnode001 kernel: [1576115.932084] worker_thread+0x4d/0x400 Oct 14 23:38:32 bnode001 kernel: [1576115.932813] worker_thread+0x4d/0x400 Oct 14 23:38:32 bnode001 kernel: [1576115.933543] kthread+0x104/0x140 Oct 14 23:38:32 bnode001 kernel: [1576115.934272] kthread+0x104/0x140 Oct 14 23:38:32 bnode001 kernel: [1576115.
[Kernel-packages] [Bug 2048230] [NEW] Jammy update: v6.1.69 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.69 upstream stable release from git://git.kernel.org/ Linux 6.1.69 r8152: fix the autosuspend doesn't work r8152: remove rtl_vendor_mode function r8152: avoid to change cfg for all devices net: tls, update curr on splice as well ring-buffer: Have rb_time_cmpxchg() set the msb counter too ring-buffer: Do not try to put back write_stamp ring-buffer: Fix a race in rb_time_cmpxchg() for 32 bit archs ring-buffer: Fix writing to the buffer with max_data_size ring-buffer: Have saved event hold the entire event ring-buffer: Do not update before stamp when switching sub-buffers tracing: Update snapshot buffer on resize if it is allocated ring-buffer: Fix memory leak of free page smb: client: fix OOB in smb2_query_reparse_point() smb: client: fix NULL deref in asn1_ber_decoder() smb: client: fix OOB in receive_encrypted_standard() drm/i915: Fix remapped stride with CCS on ADL+ drm/amd/display: Disable PSR-SU on Parade 0803 TCON again drm/amdgpu: fix tear down order in amdgpu_vm_pt_free btrfs: don't clear qgroup reserved bit in release_folio btrfs: free qgroup reserve when ORDERED_IOERR is set mm/shmem: fix race in shmem_undo_range w/THP mm/mglru: fix underprotected page cache dmaengine: stm32-dma: avoid bitfield overflow assertion drm/amdgpu/sdma5.2: add begin/end_use ring callbacks team: Fix use-after-free when an option instance allocation fails arm64: mm: Always make sw-dirty PTEs hw-dirty in pte_modify ext4: prevent the normalized size from exceeding EXT_MAX_BLOCKS soundwire: stream: fix NULL pointer dereference for multi_link btrfs: do not allow non subvolume root targets for snapshot perf: Fix perf_event_validate_size() lockdep splat HID: hid-asus: add const to read-only outgoing usb buffer arm64: add dependency between vmlinuz.efi and Image net: usb: qmi_wwan: claim interface 4 for ZTE MF290 asm-generic: qspinlock: fix queued_spin_value_unlocked() implementation HID: multitouch: Add quirk for HONOR GLO-GXXX touchpad HID: hid-asus: reset the backlight brightness level on resume nbd: pass nbd_sock to nbd_read_reply() instead of index HID: add ALWAYS_POLL quirk for Apple kb HID: glorious: fix Glorious Model I HID report platform/x86: intel_telemetry: Fix kernel doc descriptions LoongArch: Implement constant timer shutdown interface LoongArch: Add dependency between vmlinuz.efi and vmlinux.efi selftests/bpf: fix bpf_loop_bench for new callback verification scheme nvme: catch errors from nvme_configure_metadata() nvme-auth: set explanation code for failure2 msgs nbd: fold nbd config initialization into nbd_alloc_config() bcache: avoid NULL checking to c->root in run_cache_set() bcache: add code comments for bch_btree_node_get() and __bch_btree_node_alloc() bcache: remove redundant assignment to variable cur_idx bcache: avoid oversize memory allocation by small stripe_size blk-cgroup: bypass blkcg_deactivate_policy after destroying blk-throttle: fix lockdep warning of "cgroup_mutex or RCU read lock required!" stmmac: dwmac-loongson: Add architecture dependency usb: aqc111: check packet for fixup for true limit x86/hyperv: Fix the detection of E820_TYPE_PRAM in a Gen2 VM drm/mediatek: Add spinlock for setting vblank event in atomic_begin ksmbd: fix wrong name of SMB2_CREATE_ALLOCATION_SIZE PCI: loongson: Limit MRRS to 256 Revert "PCI: acpiphp: Reassign resources on bridge if necessary" ALSA: hda/realtek: Apply mute LED quirk for HP15-db ALSA: hda/hdmi: add force-connect quirks for ASUSTeK Z170 variants ALSA: hda/hdmi: add force-connect quirk for NUC5CPYB fuse: dax: set fc->dax to NULL in fuse_dax_conn_free() cred: switch to using atomic_long_t net: atlantic: fix double free in ring reinit logic appletalk: Fix Use-After-Free in atalk_ioctl net: stmmac: Handle disabled MDIO busses from devicetree dpaa2-switch: do not ask for MDB, VLAN and FDB replay dpaa2-switch: fix size of the dma_unmap vsock/virtio: Fix unsigned integer wrap around in virtio_transport_has_space() sign-file: Fix incorrect return values check stmmac: dwmac-loongson: Make sure MDIO is initialized before use net: ena: Fix XDP redirection error net: ena: Fix xdp drops handling due to multibuf packets net: ena: Destroy correct number of xdp queues upon failure net: Remove acked SYN flag from packet in the transmit queue correctly qed: Fix a potential use-after-free in qed_cxt_tables_alloc iavf: Handle ntuple on/off based on new state machines for flow director iavf: Introduce new state machines for flow director net/rose: Fix Use-After-Free in rose_ioctl at
[Kernel-packages] [Bug 2020022] Re: [SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD in UEFI setup
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2020022
Title:
[SRU][22.04.2 & 23.10] OS cannot boot successfully when enabling VMD
in UEFI setup
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
Won't Fix
Status in linux source package in Lunar:
Fix Committed
Status in linux source package in Mantic:
Fix Released
Status in linux source package in Noble:
Fix Released
Bug description:
[Impact]
When enabling VMD in UEFI setup, OS cannot boot successfully. And, the panic
leads to the system reboot. The following log is shown:
[ 166.605518] DMAR: VT-d detected Invalidation Queue Error: Reason f
[ 166.605522] DMAR: VT-d detected Invalidation Time-out Error: SID
[ 166.612445] DMAR: VT-d detected Invalidation Completion Error: SID
[ 166.612447] DMAR: QI HEAD: UNKNOWN qw0 = 0x0, qw1 = 0x0
[ 166.612449] DMAR: QI PRIOR: UNKNOWN qw0 = 0x0, qw1 = 0x0
...
Additional info:
* The issue happens on both Lenovo SE350 server and Lenovo SR850 v2 server.
Debugging info and fix commit info:
* `git bisect` indicates the offending commit is 6aab5622296b ("PCI: vmd:
Clean up domain before enumeration"). The root cause is that VMD driver tries
to clear a PCI configuration space range when resetting a VMD domain
(https://github.com/torvalds/linux/blob/master/drivers/pci/controller/vmd.c#L544),
which leads to the failure.
[Fix]
* Another `git bisect` indicates the fix commit is 20f3337d350c ("x86:
don't use REP_GOOD or ERMS for small memory clearing). I confirmed that this
commit can fix the issue.
Would it be possible to include the commit 20f3337d350c in Ubuntu
22.04.2/23.10 kernel?
[Test Plan]
Reproduce Step
1.Disable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Disabled
2.Install OS
3.Enable Intel VMD in BIOS settings
System Settings --> Devices and I/O Ports --> Intel VMD technology -->
Enable/Disable Intel VMD : Enabled
4.Rebooting will reproduce this issue
[ Where problems could occur ]
* Lenovo SE350 server and Lenovo SR850 v2 server
* The regression leads to the boot failure (cannot boot info OS successfully).
[ Other Info ]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/enable_vmd_lp_2020022
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020022/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047518] Re: Fix BCM57416 lost after resume
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045796] Re: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045796 Title: Update bnxt_en with bug fixes and support for Broadcom 5760X network adapters Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Confirmed Bug description: [IMPACT] This is requested by one of our larger server hardware partners and Broadcom to to update the bnxt_en network driver code to add some bug fixes and support for the newer 5760X adapters into Mantic. The goal is to have these land in 22.04.4 HWE and the installer environment via the HWE kernel. Missing these patches will mean customers running this hardware will not be able to use it with Ubuntu Server 22.04 LTS until the much later 22.04.5 point release, setting up a months-long gap in support for these adapters. [FIXES] These are all in mainline at 6.6-6.7 and linux-next queued for 6.8 and pick cleanly with the exception of the two noted at the end of this section. For Mantic all are picked. For Noble, only the subset currently in linux-next will be picked, depending on what happens in our Noble tree during the cycle. d007caaaf052 net: bnxt: fix a potential use-after-free in bnxt_init_tc 2012a6abc876 bnxt_en: Add 5760X (P7) PCI IDs 047a2d38e40c bnxt_en: Report the new ethtool link modes in the new firmware interface 7b60cf2b641a bnxt_en: Support force speed using the new HWRM fields 30c0bb63c2ea bnxt_en: Support new firmware link parameters cf47fa5ca5bb bnxt_en: Refactor ethtool speeds logic a7445d69809f bnxt_en: Add support for new RX and TPA_START completion types for P7 39b2e62be370 bnxt_en: Refactor and refine bnxt_tpa_start() and bnxt_tpa_end(). c2f8063309da bnxt_en: Refactor RX VLAN acceleration logic. 13d2d3d381ee bnxt_en: Add new P7 hardware interface definitions 8243345bfaec bnxt_en: Refactor RSS capability fields d846992e6387 bnxt_en: Implement the new toggle bit doorbell mechanism on P7 chips d3c16475dc06 bnxt_en: Consolidate DB offset calculation a432a45bdba4 bnxt_en: Define basic P7 macros 397d44bf1721 bnxt_en: Update firmware interface to 1.10.3.15 08b386b132c6 bnxt_en: Fix backing store V2 logic 1c7fd6ee2fe4 bnxt_en: Rename some macros for the P5 chips f94471f3ce74 bnxt_en: Modify the NAPI logic for the new P7 chips c09d22674b94 bnxt_en: Modify RX ring indexing logic. 6d1add95536b bnxt_en: Modify TX ring indexing logic. b9e0c47ee2ec bnxt_en: Add db_ring_mask and related macro to bnxt_db_info struct. 236e237f8ffe bnxt_en: Add support for HWRM_FUNC_BACKING_STORE_CFG_V2 firmware calls 6a4d0774f02d bnxt_en: Add support for new backing store query firmware API b098dc5a3357 bnxt_en: Add bnxt_setup_ctxm_pg_tbls() helper function 2ad67aea11f2 bnxt_en: Use the pg_info field in bnxt_ctx_mem_type struct 035c57615982 bnxt_en: Add page info to struct bnxt_ctx_mem_type 76087d997a84 bnxt_en: Restructure context memory data structures e50dc4c2206e bnxt_en: Free bp->ctx inside bnxt_free_ctx_mem() aa8460bacf49 bnxt_en: The caller of bnxt_alloc_ctx_mem() should always free bp->ctx c1056a59aee1 bnxt_en: Optimize xmit_more TX path ba098017791e bnxt_en: Use existing MSIX vectors for all mqprio TX rings f07b58801bef bnxt_en: Add macros related to TC and TX rings f5b29c6afe36 bnxt_en: Add helper to get the number of CP rings required for TX rings 0589a1ed4d33 bnxt_en: Support up to 8 TX rings per MSIX 877edb347323 bnxt_en: Refactor bnxt_hwrm_set_coal() 5a3c585fa83f bnxt_en: New encoding for the TX opaque field ebf72319cef6 bnxt_en: Refactor bnxt_tx_int() 9c0b06de6fb6 bnxt_en: Remove BNXT_RX_HDL and BNXT_TX_HDL 7845b8dfc713 bnxt_en: Add completion ring pointer in TX and RX ring structures d1eec614100c bnxt_en: Restructure cp_ring_arr in struct bnxt_cp_ring_info 7f0a168b0441 bnxt_en: Add completion ring pointer in TX and RX ring structures 34eec1f29a59 bnxt_en: Put the TX producer information in the TX BD opaque field 9cfe8cf5027b bnxt_en: Fix 2 stray ethtool -S counters 5d4e1bf60664 bnxt_en: extend media types to supported and autoneg modes 64d20aea6e4b bnxt_en: convert to linkmode_set_bit() API 5802e30317d9 bnxt_en: Refactor NRZ/PAM4 link speed related logic 94c89e73d377 bnxt_en: refactor speed independent ethtool modes d6263677bb1b bnxt_en: support lane configuration via ethtool ecdad2a69214 bnxt_en: add infrastructure to lookup ethtool link mode fd78ec3fbc47 bnxt_en: Fix invoking hwmon_notify_event 55862094a9d0 bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI 73b24e7ce8f1 eth: bnxt: fix backward compatibility with older devices c27153682eac Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN" cbdbf0aa41ba bnxt_en: Up
[Kernel-packages] [Bug 2047382] Re: Hotplugging SCSI disk in QEMU VM fails
** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047382 Title: Hotplugging SCSI disk in QEMU VM fails Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: In Progress Bug description: [Impact] Hot-plugging SCSI disks for QEMU VMs booting with UEFI and using guest kernels >= 6.5 might be broken. The inconsistency suggests a potential race condition. [Fix] Reverting the two specified commits appears to restore reliability. == cc22522fd55e2 PCI: acpiphp: Use pci_assign_unassigned_bridge_resources() only for non-root bus 40613da52b13f PCI: acpiphp: Reassign resources on bridge if necessary == Upstream has resolved the issue by reverting both commits through a commit placed below. == 5df12742b7e3a Revert "PCI: acpiphp: Reassign resources on bridge if necessary == [Test Plan] 1. Create a VM virt-install --name scsi_test --memory 2048 --vcpus 2 --boot uefi --disk path=/home/ubuntu/mantic-server-cloudimg-amd64.img,size=20,format=qcow2,bus=virtio -os-variant=ubuntu18.04 --graphics spice --network bridge=virbr0 2. Prepare two XMLs for adding two disk devices # cat disk_X.xml 3. Hotplug disks and check for success virsh attach-device scsi_test disk_X.xml [Where problems could occur] The patch reverts two commits that previously addressed long-standing issues related to hotplugging devices with large BARs. While this reversion may reintroduce legacy issues, it does not introduce new problems. The associated risks are deemed low, making it worthwhile to address timing issues during the hotplugging of SCSI disks in QEMU VM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047382/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047461] Re: drm: Update file owner during use
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907493] Re: wifi network keeps disconnecting
I had the same bug on Ubuntu 20.04 with a ThinkPad X230. appearing only in context of highly interferenced Wifi APs fixed after disabling wifi powersave by setting wifi.powersave=2 in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf previous log: NetworkManager[1597]: [] device (wlp3s0): supplicant interface state: associating -> associated kernel: [ 3325.856267] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by xx:xx:xx:xx:xx:xx kernel: [ 3328.773230] wlp3s0: disassociated from xx:xx:xx:xx:xx:xx (Reason: 8=DISASSOC_STA_HAS_LEFT) -- 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/1907493 Title: wifi network keeps disconnecting Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with the latest updates on a Thinkpad X220. Since about a week I keep having network disconnects. I am using an Intel Corporation Centrino Advanced-N 6205 wifi chip. Before it's been working great. There seem to be others with this recent problem. https://askubuntu.com/questions/1298278/i-keep-getting-disconnected $dmesg shows: [35764.191444] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready [35764.207135] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 5c:49:79:33:f5:69 [35770.664591] e1000e: enp0s25 NIC Link is Down [35823.702523] wlp3s0: disassociated from 5c:49:79:33:f5:69 (Reason: 33=DISASSOC_QAP_NO_BANDWIDTH) [35823.949141] wlp3s0: authenticate with 5c:49:79:33:f5:6a [35823.952112] wlp3s0: send auth to 5c:49:79:33:f5:6a (try 1/3) [35824.027366] wlp3s0: authenticated [35824.028058] wlp3s0: associate with 5c:49:79:33:f5:6a (try 1/3) [35824.031316] wlp3s0: RX AssocResp from 5c:49:79:33:f5:6a (capab=0x1511 status=0 aid=3) [35824.049972] wlp3s0: associated [35824.051644] wlp3s0: deauthenticating from 5c:49:79:33:f5:6a by local choice (Reason: 1=UNSPECIFIED) [35827.875982] wlp3s0: authenticate with 5c:49:79:33:f5:69 [35827.883980] wlp3s0: send auth to 5c:49:79:33:f5:69 (try 1/3) [35827.890394] wlp3s0: 5c:49:79:33:f5:69 denied authentication (status 34) [35828.966804] wlp3s0: authenticate with 5c:49:79:33:f5:6a [35828.971132] wlp3s0: send auth to 5c:49:79:33:f5:6a (try 1/3) [35829.043823] wlp3s0: authenticated [35829.044820] wlp3s0: associate with 5c:49:79:33:f5:6a (try 1/3) [35829.047162] wlp3s0: RX AssocResp from 5c:49:79:33:f5:6a (capab=0x1511 status=0 aid=3) [35829.065508] wlp3s0: associated [35829.144604] wlp3s0: Limiting TX power to 23 (23 - 0) dBm as advertised by 5c:49:79:33:f5:6a [35901.739236] wlp3s0: disconnect from AP 5c:49:79:33:f5:6a for new auth to 5c:49:79:33:f5:69 [35901.758760] wlp3s0: authenticate with 5c:49:79:33:f5:69 [35901.762063] wlp3s0: send auth to 5c:49:79:33:f5:69 (try 1/3) [35901.765779] wlp3s0: authenticated [35901.766059] wlp3s0: waiting for beacon from 5c:49:79:33:f5:69 [35901.831428] wlp3s0: associate with 5c:49:79:33:f5:69 (try 1/3) [35901.837432] wlp3s0: RX ReassocResp from 5c:49:79:33:f5:69 (capab=0x1431 status=0 aid=8) [35901.857282] wlp3s0: associated [35901.859310] wlp3s0: deauthenticating from 5c:49:79:33:f5:69 by local choice (Reason: 1=UNSPECIFIED) $journalctl --follow showed this: Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: Associated with 5c:49:79:33:f5:69 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=DE Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: l2_packet_send - sendto: No buffer space available Dez 09 20:29:05 meschi-ThinkPad-X220 kernel: wlp3s0: deauthenticating from 5c:49:79:33:f5:69 by local choice (Reason: 1=UNSPECIFIED) Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=5c:49:79:33:f5:69 reason=1 locally_generated=1 Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="wifi-name" auth_failures=1 duration=10 reason=WRONG_KEY Dez 09 20:29:05 meschi-ThinkPad-X220 wpa_supplicant[1012]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0780] device (wlp3s0): supplicant interface state: associating -> 4-way handshake Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0781] sup-iface[0x560dbca5e1e0,wlp3s0]: connection disconnected (reason -1) Dez 09 20:29:05 meschi-ThinkPad-X220 NetworkManager[141586]: [1607542145.0833] device (wlp3s0): supplicant interface state: 4-way handshake -> disconnected Dez 09 20:2
[Kernel-packages] [Bug 2045248] Re: focal: 5.15.0-91 crashes on boot as Xen PV guest
Based on a response to xen-devel post I've cherry-picked these commits
to our 5.15 kernel build and since then we have not encountered this
problem.
6cf3e4c0d29102c74aca1ce0c1710be9d02e440e # x86/entry: Cleanup PARAVIRT
1462eb381b4c27576a3e818bc9f918765d327fdf # x86/xen: Rework the
xen_{cpu,irq,mmu}_opsarrays
8b87d8cec1b31ea710568ae49ba5f5146318da0d # x86/entry,xen: Early rewrite of
restore_regs_and_return_to_kernel()
bbf92368b0b1fe472d489e62d3340d7897e9c697 # x86/text-patching: Make
text_gen_insn() play nice with ANNOTATE_NOENDBR
ba27d1a80871eb8dbeddf34ec7d396c149cbb8d7 # x86/ibt,paravirt: Use
text_gen_insn() for paravirt_patch()
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2045248
Title:
focal: 5.15.0-91 crashes on boot as Xen PV guest
Status in linux-meta package in Ubuntu:
New
Bug description:
We have a custom build of the kernel based on the Ubuntu-
hwe-5.15-5.15.0-91.101_20.04.1 tag. It includes a small number of
patches but nothing in the area of the early boot code. Xen is based
on the upstream 4.15.5 stable branch with all patches up to and
including XSA-444. In approximately 1% of pv guest boots we get the
following crash which looks like it involves the entry_64.S code. We
have seen this on different hardware models but only with an Intel
processor although we don't have any AMD based systems. The problem
was also observed with the 5.15.0-85 tag.
I have had a look on the main line kernel branch for arch/x86/entry
changes but I can't obviously connect this problem to anything there
based on the commit messages. I don't have the knowledge to
understand the code though and whether there is actually something
relevant.
```
[0.303715] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user
pointer sanitization
[0.303727] Spectre V2 : Mitigation: Enhanced IBRS
[0.303733] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB
on context switch
[0.303740] Spectre V2 : Spectre v2 / PBRSB-eIBRS: Retire a single CALL on
VMEXIT
[0.303746] RETBleed: Mitigation: Enhanced IBRS
[0.303752] Spectre V2 : mitigation: Enabling conditional Indirect Branch
Prediction Barrier
[0.303760] Speculative Store Bypass: Mitigation: Speculative Store Bypass
disabled via prctl and seccomp
[0.303771] MMIO Stale Data: Mitigation: Clear CPU buffers
[0.303777] GDS: Unknown: Dependent on hypervisor status
[0.303827] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[0.303835] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.303840] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.303846] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[0.303851] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[0.303857] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[0.303865] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[0.303871] x86/fpu: xstate_offset[5]: 1088, xstate_sizes[5]: 64
[0.303877] x86/fpu: xstate_offset[6]: 1152, xstate_sizes[6]: 512
[0.303882] x86/fpu: xstate_offset[7]: 1664, xstate_sizes[7]: 1024
[0.303888] x86/fpu: Enabled xstate features 0xe7, context size is 2688
bytes, using 'standard' format.
[0.327588] segment-related general protection fault: e030 [#1] SMP NOPTI
[0.327604] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.15.0-91-generic
#101~20.04.1custom1
[0.327614] RIP: e030:native_irq_return_iret+0x0/0x2
[0.327627] Code: 5b 41 5b 41 5a 41 59 41 58 58 59 5a 5e 5f 48 83 c4 08 eb
0f 0f 1f 00 90 66 66 2e 0f 1f 84 00 00 00 00 00 f6 44 24 20 04 75 02 <48> cf 57
0f 01 f8 eb 12 0f 20 df 90 90 90 90 90 48 81 e7 ff e7 ff
[0.327640] RSP: e02b:82e03bc8 EFLAGS: 00010046
[0.327647] RAX: RBX: 82e03c30 RCX:
81e01101
[0.327653] RDX: RSI: RDI:
001f
[0.327660] RBP: 82e03bf8 R08: 81e011ef R09:
0005
[0.327666] R10: 0006 R11: e8ae0feb75ccff49 R12:
81e011ef
[0.327672] R13: 0006 R14: 81e011f1 R15:
0002
[0.327684] FS: () GS:888015a0()
knlGS:
[0.327691] CS: 1e030 DS: ES: CR0: 80050033
[0.327696] CR2: CR3: 02e1 CR4:
00050660
[0.327705] Call Trace:
[0.327709]
[0.327713] ? show_trace_log_lvl+0x1d6/0x2ea
[0.327723] ? show_trace_log_lvl+0x1d6/0x2ea
[0.327729] ? insn_decode+0xec/0x100
[0.327738] ? show_regs.part.0+0x23/0x29
[0.327743] ? __die_body.cold+0x8/0xd
[0.327748] ? die_addr+0x3e/0x60
[0.327756] ? exc_general_protection+0x1c1/0x350
[0.3277
[Kernel-packages] [Bug 2044192] Re: Patches needed for AmpereOne (arm64)
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044192
Title:
Patches needed for AmpereOne (arm64)
Status in linux package in Ubuntu:
New
Status in linux-gcp package in Ubuntu:
Fix Released
Status in linux-gcp source package in Focal:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in linux-gcp source package in Jammy:
Fix Committed
Bug description:
[Impact]
* Google requested patches for AmpereOne machine type
[Fix]
* Changes already in Mantic, will be in Jammy 6.5 kernel, targeting Jammy
5.15 GCP and Focal 5.4 GCP for now
* Also submitting to Jammy 5.15 generic
* Cherry-picks from upstream
db26f8f2da92 ("clocksource/drivers/arch_arm_timer: Move workaround
synchronisation around")
c1153d52c414 ("clocksource/drivers/arm_arch_timer: Fix masking for high freq
counters")
ec8f7f3342c8 ("clocksource/drivers/arm_arch_timer: Drop unnecessary ISB on
CVAL programming")
41f8d02a6a55 ("clocksource/drivers/arm_arch_timer: Remove any trace of the
TVAL programming interface")
012f18850452 ("clocksource/drivers/arm_arch_timer: Work around broken CVAL
implementations")
30aa08da35e0 ("clocksource/drivers/arm_arch_timer: Advertise 56bit timer to
the core code")
8b82c4f883a7 ("clocksource/drivers/arm_arch_timer: Move MMIO timer
programming over to CVAL")
72f47a3f0ea4 ("clocksource/drivers/arm_arch_timer: Fix MMIO base address vs
callback ordering issue")
ac9ef4f24cb2 ("clocksource/drivers/arm_arch_timer: Move drop _tval from
erratum function names")
a38b71b0833e ("clocksource/drivers/arm_arch_timer: Move system register timer
programming over to CVAL")
1e8d929231cf ("clocksource/drivers/arm_arch_timer: Extend write side of timer
register accessors to u64")
d72689988d67 ("clocksource/drivers/arm_arch_timer: Drop CNT*_TVAL read
accessors")
4775bc63f880 ("clocksource/arm_arch_timer: Add build-time guards for
unhandled register accesses")
[Test Case]
* Compile tested
* Boot tested on GCP AmpereOne instance
[Where things could go wrong]
* Low chance of regression. Changes isolated to ARM timers.
[Other Info]
* SF #00372821
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2044192/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
** Changed in: linux (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: New Status in linux source package in Noble: Fix Released Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032641] Re: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Fix Released => Invalid -- 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/2032641 Title: kernel_selftests failures on kernel-P10d-LPAR10.ppc64el.10 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: [Impact] The powerpc tests from kernel selftests were unable to finish properly on Power10 VM with Focal 5.4 kernel. There will be lots of failures for powerpc/ptrace and powerpc/tm tests. For example the ptrace-tm-gpr: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:unknown # [FAIL] Test FAILED on line 94 # GPR[14]: 1 Expected: 2 # GPR[15]: 1 Expected: 2 # GPR[16]: 1 Expected: 2 # GPR[17]: 1 Expected: 2 # GPR[18]: 1 Expected: 2 # GPR[19]: 1 Expected: 2 # GPR[20]: 1 Expected: 2 # GPR[21]: 1 Expected: 2 # GPR[22]: 1 Expected: 2 # GPR[23]: 1 Expected: 2 # GPR[24]: 1 Expected: 2 # GPR[25]: 1 Expected: 2 # GPR[26]: 1 Expected: 2 # GPR[27]: 1 Expected: 2 # GPR[28]: 1 Expected: 2 # GPR[29]: 1 Expected: 2 # GPR[30]: 1 Expected: 2 # GPR[31]: 1 Expected: 2 # failure: ptrace_tm_gpr not ok 1 selftests: powerpc/ptrace: ptrace-tm-gpr # exit=1 [Fix] * 031fd80f87 selftests: Skip TM tests on synthetic TM implementations This patch has already landed on Jammy+. Only Focal will need this patch. And it needs to be backported to skip changes on the tm-signal-pagefault.c test, which does not exist on Focal tree. [Test Plan] Run the patched powerpc tests from kernel selftests: $ sudo make TARGETS=powerpc run_tests Previously failing powerpc/ptrace and powerpc/tm tests will be skipped. For example the ptrace-tm-gpr test: # selftests: powerpc/ptrace: ptrace-tm-gpr # test: ptrace_tm_gpr # tags: git_version:b315960-dirty # [SKIP] Test skipped on line 116 # skip: ptrace_tm_gpr ok 2 selftests: powerpc/ptrace: ptrace-tm-gpr [Where problems could occur] Change limited to testing tools, and it's just skipping unsuitable tests for specific architecture, no impact to real kernel functions. == Original Bug Report == First time seen on cycle 2023.08.10 because it was the first time we tested this instance. Tried previous focal version (5.4.09-156) and it seems it's happened before. The following tests are failing: * powerpc/ptrace:ptrace-tm-gpr FAIL * powerpc/ptrace:ptrace-tm-spd-gpr FAIL * powerpc/ptrace:ptrace-tm-tar timeout * powerpc/ptrace:ptrace-tm-spd-tar timeout * powerpc/ptrace:ptrace-tm-vsx timeout * powerpc/ptrace:ptrace-tm-spd-vsx timeout * powerpc/ptrace:ptrace-tm-spr timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2032641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044096] Re: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
** Changed in: linux (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2044096 Title: Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.5 package in Ubuntu: New Status in linux source package in Jammy: Invalid Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: New Status in linux-oem-6.5 source package in Noble: New Bug description: [Impact] Built-in audio speaker function not working on new Dell Oasis 13/14/16 laptops [Fix] Need to backport https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f0d9da19d7de9e845e7a93a901c4b9658df6b492 to support dual speaker configuration on Dell Oasis series [Test Case] 1. Power on the Dell Oasis 13/14/16 laptops with CS35L41 HDA. 2. Verify the audio functions, including playback and capture [Where problems could occur] Add CS35L41 support on specific Dell laptops. Risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2044096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
noble kernel will have this patch automatically since the version of noble kernel is v6.7 at least (Probably v6.8). ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High -- 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/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers
The usbio-drivers package that was uploaded to the noble NEW queue has been rejected due to an incorrect debian/copyright. The upstream copyright declarations all indicate that they are GPL 2.0, not GPL 2.0 or any later version. The debian/copyright uses the correct short name for the actual license, but includes "or any later version" text in the body of the license statement, which is incorrect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041800 Title: [needs-packaging] usbio-drivers Status in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice AIC This package provides kernel drivers for MIPI cameras through the Intel IPU6 on Intel MeteoLake platform with Lattice AIC. Upstream URL: https://github.com/intel/usbio-drivers Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms (to request usd-import after created) License: GPL v2 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2041800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047780] Re: BlueZ release 5.71
Turns out it's not as simple as the above comments suggest.
> https://salsa.debian.org/systemd-team/systemd/-/commit/ee83b5721
> https://salsa.debian.org/DebianOnMobile-team/modemmanager/-/commit/367180c3
udev changes are not relevant to the failures in
https://launchpad.net/ubuntu/+source/bluez/5.71-0ubuntu1 AFAICT
> https://salsa.debian.org/bluetooth-team/bluez/-/commit/f4d76255cdfa
Our dh doesn't seem to understand "${env:" in *.install, so using the
same approach as Debian doesn't seem to work. It always treats
"${env:..." as a literal path. And yes I did remember to export the
variable from debian/rules.
Just hard coding the service file paths to /usr would probably work for
Launchpad builds, but is not something I'm willing to do right now since
the path change hasn't graduated from proposed yet and I can't test it
locally. I'm only willing to upload changes I have tested locally so it
can wait till systemd has migrated... In the meantime, can anyone tell
me why "${env:..." isn't understood? Is it the compatibility level?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ release 5.71
Status in bluez package in Ubuntu:
Fix Committed
Bug description:
Release BlueZ 5.71 to noble.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers
verified linux-oem-6.5 version 6.5.0-1011.12 ** Tags removed: verification-needed-jammy-linux-oem-6.5 ** Tags added: verification-done-jammy-linux-oem-6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041800 Title: [needs-packaging] usbio-drivers Status in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice AIC This package provides kernel drivers for MIPI cameras through the Intel IPU6 on Intel MeteoLake platform with Lattice AIC. Upstream URL: https://github.com/intel/usbio-drivers Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms (to request usd-import after created) License: GPL v2 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2041800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047909] Re: Support standalone dkms source tree embedded in kernel source
verified linux-oem-6.5 version 6.5.0-1011.12
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2047909
Title:
Support standalone dkms source tree embedded in kernel source
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Committed
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
For a quick respin for oem-6.5 kernel with usbio-drivers (for bug
2041800 and a last minute fix bug 2047899), we're to embed usbio-
drivers into oem-6.5 and remove it when all the bits are in position
under formal process.
While IPU6 drivers are still under development, all the related dkms
packages were prebuilt as linux-modules-{ipu6,ivsc}, and we're
expecting a new linux-modules-usbio here. The `debian/scripts/dkms-
build` does not support this yet, so we are separating the mechanism
part here, and the usbio dkms source import in bug 2041800.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047909/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
Makes sense to me - I'm +1 for turning it off starting with 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 2047518] Re: Fix BCM57416 lost after resume
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047518 Title: Fix BCM57416 lost after resume Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] BCM57416 is lost after resume. Error log: [ 1261.429834] bnxt_en :82:00.1 enp130s0f1np1: hwrm req_type 0x50 seq id 0x125d error 0x4 [ 1261.429843] bnxt_en :82:00.1 enp130s0f1np1: hwrm_ring_alloc type 1 failed. rc:ffe4 err:4 [ 1261.429846] bnxt_en :82:00.1 enp130s0f1np1: hwrm ring alloc failure rc: fffb [ 1261.437389] bnxt_en :82:00.1 enp130s0f1np1: bnxt_init_nic err: fffb [Fix] Clear the reservations in driver after reset the ethernet card. [Test] Tested on hardware, after 10 times of suspend/resume, bnxt ethernet works fine. [Where problems could occur] It may break broadcom bnxt driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047504] Re: Mute/mic LEDs and speaker no function on some HP platforms
it ain't 'fix committed' before it's merged to git -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047504 Title: Mute/mic LEDs and speaker no function on some HP platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS and speaker are not work on some HP platforms. [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk, the audio/mic mute LEDs and speaker are working good. Applied on oem-6.5 and it works fine. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2047504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047634] Re: Reject connection when malformed L2CAP signal packet is received
The patch is merged to mainline kernel v6.7-rc7, and this patch is also CCed to sta...@vger.kernel.org, so in theory, this patch will be merged to ubuntu kernel (jammy & noble) automatically with the SRU update. ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047634 Title: Reject connection when malformed L2CAP signal packet is received Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Status in linux source package in Noble: New Bug description: [Impact] In the qualification test the from the Bluetooth SIG i.e. the Profile Testing Suite (PTS), in the L2CAP/COS/CED/BI-02-C, packet containing the following L2CAP packets are sent: 1. A malformed L2CAP_CONNECTION_REQ packet; and 2. An L2CAP packet with unknown command. For compliance to the L2CAP specification, BlueZ is expected to send: 1. An L2CAP_CONNECTION_RSP packet; and 2. An L2CAP_COMMAND_REJECT_RSP packet. However, the later one is not sent. [Fix] Clean cherry pick from commit 37b85190ca1ed790fe230f0ba134b10a3d3d1add (Bluetooth: L2CAP: Send reject on command corrupted request) [Test] After applying the patch, test it with PTS: 1. Configure the PTS: set PSM to 0x1011, so that it initiates L2CAP connection over PSM 0x1011, which is the default PSM for l2test, the testing tool for L2CAP layer provided by bluez. 2. Set device as connectable: $ sudo btmgmt connectable on 3. Run l2test on the device in preparation for testing: $ sudo l2test -d 4. Run the L2CAP/COS/CED/BI-02-C test on PTS. The test suite will initiate L2CAP connection automatically. 5. Verify that the test verdict on the PTS is PASS. [Where problems could occur] This makes L2CAP implementation more conforming to the specification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047461] Re: drm: Update file owner during use
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2047461 Title: drm: Update file owner during use Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Our testing tools need to check the app runs on which GPU, and now it only shows the processes as Xorg or XWayland $ cat /sys/kernel/debug/dri/0/clients command pid dev master a uid magic Xorg 2344 0 yy 0 0 Xorg 2344 0 ny 0 2 Xorg 2344 0 ny 0 3 Xorg 2344 0 ny 0 4 [Fix] The commit from v6.7-rc1 fixes the issue $ cat /sys/kernel/debug/dri/0/clients command tgid dev master a uid magic Xorg 830 0 yy 0 0 xfce4-session 880 0 ny 0 1 xfwm4 943 0 ny 0 2 neverball 1095 0 ny 0 3 [Test case] 1. check processes by 'cat /sys/kernel/debug/dri/0/clients' 2. runs glxgears(specify the GPU if needed) 3. check the precesses again and there should be a 'glxgears' process [Where problems could occur] This commit added some protections on read/write and only changes the process' pid, the worst case is that the process got the wrong pid as its owner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2047461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047389] Re: Fix AMDGPU crash on 6.5 kernel
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047389 Title: Fix AMDGPU crash on 6.5 kernel Status in HWE Next: In Progress Status in linux package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] AMD GPU crash with a message: " cp queue preemption timeout". [Fix] Disable MCBP(mid command buffer preemption) by default as old Mesa hangs with it. [Test] Tested on hardware, play web video for more than 1 hour OK. [Where problems could occur] It may break AMD GPU. This issue is only reproduced on v6.5+ kernel versions and fixes in v6.6, so SRU for oem-6.5, mantic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047398] Re: Add missing RPL P/U CPU IDs
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2047398 Title: Add missing RPL P/U CPU IDs Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in linux source package in Mantic: In Progress Status in linux-oem-6.5 source package in Mantic: Invalid Status in linux source package in Noble: In Progress Status in linux-oem-6.5 source package in Noble: Invalid Bug description: [Impact] Without the correct GPU ID in the driver, the system will default to framebuffer mode, and some graphics functions may not work properly. [Fix] Below commit included in v6.7-rc1 adds the missing IDs 5d5fea7c79a7 drm/i915/rpl: Update pci ids for RPL P/U [Test case] 1. check the system with GPU ID A7AC or A7AD 2. boot the system into desktop and connecting a monior by HDMI cable with HDMI port or Type-C port 3. make sure the external monitor works [Where problems could occur] Add only IDs; there is no potential for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2047398/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041800] Re: [needs-packaging] usbio-drivers
** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2041800 Title: [needs-packaging] usbio-drivers Status in Ubuntu: Fix Committed Status in linux-oem-6.5 package in Ubuntu: Invalid Status in The Jammy Jellyfish: New Status in linux-oem-6.5 source package in Jammy: Fix Committed Status in Noble: Fix Committed Status in linux-oem-6.5 source package in Noble: Invalid Bug description: Description: USBIO Bridge drivers for Intel MeteoLake platform with Lattice AIC This package provides kernel drivers for MIPI cameras through the Intel IPU6 on Intel MeteoLake platform with Lattice AIC. Upstream URL: https://github.com/intel/usbio-drivers Package source repo: https://code.launchpad.net/~vicamo/+git/intel-usbio-dkms (to request usd-import after created) License: GPL v2 PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2031412. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2041800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044003] Re: Don't produce linux-*-tools-{common, host} binary packages
** Description changed:
[Impact]
- Some kernels produce linux-*-tools-common and/or linux-*-tools-host
- binary deb packages. That is all wrong, only the primary/main linux
- source package should produce these. These packages result in install
- failures of the regular linux-tools-{common,host} packages.
+ Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
+ and/or linux-*-tools-host binary deb packages. That is all wrong, only
+ the primary/main linux source package should produce these. These
+ packages result in install failures of the regular
+ linux-{cloud-,}tools-{common,host} packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
** Summary changed:
- Don't produce linux-*-tools-{common,host} binary packages
+ Don't produce linux-*-{cloud-,}tools-{common,host} binary packages
** Summary changed:
- Don't produce linux-*-{cloud-,}tools-{common,host} binary packages
+ Don't produce linux-*-cloud-tools-common and linux-*-tools-{common,host}
binary packages
** Summary changed:
- Don't produce linux-*-cloud-tools-common and linux-*-tools-{common,host}
binary packages
+ Don't produce linux-*-cloud-tools-common and linux-*-tools-common and
linux-*-tools-host binary packages
** Summary changed:
- Don't produce linux-*-cloud-tools-common and linux-*-tools-common and
linux-*-tools-host binary packages
+ Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
** Description changed:
[Impact]
Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
and/or linux-*-tools-host binary deb packages. That is all wrong, only
the primary/main linux source package should produce these. These
- packages result in install failures of the regular
- linux-{cloud-,}tools-{common,host} packages.
+ packages result in install failures of the regular linux-cloud-tools-
+ common, linux-tools-common and linux-tools-host packages.
[Test Case]
Check list of built binary packages in LP and verify the packages are
not built.
[Where Problems Could Occur]
Already installed packages won't upgrade and become stale.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2044003
Title:
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
Status in linux-bluefield package in Ubuntu:
New
Status in linux-hwe-5.15 package in Ubuntu:
New
Status in linux-hwe-6.2 package in Ubuntu:
New
Status in linux-hwe-6.5 package in Ubuntu:
New
Status in linux-ibm package in Ubuntu:
New
Status in linux-intel-iotg package in Ubuntu:
New
Status in linux-intel-iotg-5.15 package in Ubuntu:
New
Status in linux-iot package in Ubuntu:
New
Status in linux-laptop package in Ubuntu:
Confirmed
Status in linux-lowlatency package in Ubuntu:
New
Status in linux-lowlatency-hwe-5.15 package in Ubuntu:
New
Status in linux-lowlatency-hwe-6.2 package in Ubuntu:
New
Status in linux-lowlatency-hwe-6.5 package in Ubuntu:
New
Status in linux-nvidia package in Ubuntu:
New
Status in linux-nvidia-6.2 package in Ubuntu:
New
Status in linux-oem-6.1 package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Status in linux-realtime package in Ubuntu:
New
Status in linux-hwe-5.15 source package in Focal:
New
Status in linux-intel-iotg-5.15 source package in Focal:
New
Status in linux-iot source package in Focal:
New
Status in linux-lowlatency-hwe-5.15 source package in Focal:
New
Status in linux-bluefield source package in Jammy:
New
Status in linux-hwe-6.2 source package in Jammy:
New
Status in linux-hwe-6.5 source package in Jammy:
New
Status in linux-ibm source package in Jammy:
New
Status in linux-intel-iotg source package in Jammy:
New
Status in linux-lowlatency source package in Jammy:
New
Status in linux-lowlatency-hwe-6.2 source package in Jammy:
New
Status in linux-lowlatency-hwe-6.5 source package in Jammy:
New
Status in linux-nvidia source package in Jammy:
New
Status in linux-nvidia-6.2 source package in Jammy:
New
Status in linux-oem-6.1 source package in Jammy:
New
Status in linux-oem-6.5 source package in Jammy:
New
Status in linux-realtime source package in Jammy:
New
Status in linux-laptop source package in Mantic:
Fix Released
Status in linux-lowlatency source package in Mantic:
New
Bug description:
[Impact]
Some kernels produce linux-*-cloud-tools-common, linux-*-tools-common
and/or linux-*-tools-host binary deb packages. That is all wrong, only
the primary/main linux source package should produce these. These
packages result in install failures of the regular linux-cloud-tools-
common, linux-tools-common and linux-
[Kernel-packages] [Bug 2048183] Re: Don't produce linux-*-cloud-tools-common, linux-*-tools-common and linux-*-tools-host binary packages
** Summary changed:
- Don't produce linux-*-tools-{common,host} binary packages
+ Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
** Description changed:
This is a duplicate bug report for bug 2044003. All duplicates are
linked to this bug because they cannot be linked to 2044003 (LP times
out due to too many bug tasks, sigh). See bug 2008514 for that problem.
- Problem: Some kernels incorrectly provide linux--tools-common and
- linux--tools-host binary packages that clash with the main linux-
- tools-{common,host} packages.
+ Problem: Some kernels incorrectly provide linux--cloud-tools-
+ common, linux--tools-common and linux--tools-host binary
+ packages that clash with the main linux-cloud-tools-commint, linux-
+ tools-common and linux-tools-host packages.
- Resolution: Uninstall linux--tools-common and linux--tools-
- host packages.
+ Resolution: Uninstall linux--cloud-tools-common, linux--tools-
+ common and linux--tools-host 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/2048183
Title:
Don't produce linux-*-cloud-tools-common, linux-*-tools-common and
linux-*-tools-host binary packages
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is a duplicate bug report for bug 2044003. All duplicates are
linked to this bug because they cannot be linked to 2044003 (LP times
out due to too many bug tasks, sigh). See bug 2008514 for that
problem.
Problem: Some kernels incorrectly provide linux--cloud-tools-
common, linux--tools-common and linux--tools-host binary
packages that clash with the main linux-cloud-tools-commint, linux-
tools-common and linux-tools-host packages.
Resolution: Uninstall linux--cloud-tools-common,
linux--tools-common and linux--tools-host packages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2048183/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
