[Kernel-packages] [Bug 2052332] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15.
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2052332 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15. Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I reverted to 6.2.0-39 and purged headers and image for 6.5 since my computer cannot boot with 6.5+nvidia390 and when I use nouveau, my resolution is 640x320 and I can't proceed like this. Good luck with this one, thanks in advance. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 2 21:56:15 2024 DpkgHistoryLog: Start-Date: 2024-02-02 21:53:50 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-extra-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-hwe-6.5-headers-6.5.0-15:amd64 (6.5.0-15.15~22.04.1, automatic), linux-modules-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-image-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-headers-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic) Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-headers-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8) ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2023-02-25 (342 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2052332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052341] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
*** This bug is a duplicate of bug 2028165 *** https://bugs.launchpad.net/bugs/2028165 ** This bug has been marked a duplicate of bug 2028165 nvidia-dkms-* FTBS with linux 6.5 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2052341 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: dpkg: dependency problems prevent configuration of nvidia-driver-390: nvidia-driver-390 depends on nvidia-dkms-390 (<= 390.157-1); however: Package nvidia-dkms-390 is not configured yet. nvidia-driver-390 depends on nvidia-dkms-390 (>= 390.157); however: Package nvidia-dkms-390 is not configured yet. dpkg: error processing package nvidia-driver-390 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. /var/crash reads: # CC [M] /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o x86_64-linux-gnu-gcc-12 -Wp,-MMD,/var/lib/dkms/nvidia/390.157/build/nvidia/.nv-dma.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=1024 -fstack-protector-strong -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -g -gdwarf-5 -I/var/lib/dkms/nvidia/390.157/build/common/inc -I/var/lib/dkms/nvidia/390.157/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"390.157\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Wno-sign-compare -Wno-format-extra-args -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/390.157/build/nvidia -DNV_BUILD_MODULE_INSTANCES=0 -DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nv_dma"' -DKBUILD_MODNAME='"nvidia"' -D__KBUILD_MODNAME=kmod_nvidia -c -o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-gpu-numa.c:24: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ |
[Kernel-packages] [Bug 2052341] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error e
Public bug reported: dpkg: dependency problems prevent configuration of nvidia-driver-390: nvidia-driver-390 depends on nvidia-dkms-390 (<= 390.157-1); however: Package nvidia-dkms-390 is not configured yet. nvidia-driver-390 depends on nvidia-dkms-390 (>= 390.157); however: Package nvidia-dkms-390 is not configured yet. dpkg: error processing package nvidia-driver-390 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. /var/crash reads: # CC [M] /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o x86_64-linux-gnu-gcc-12 -Wp,-MMD,/var/lib/dkms/nvidia/390.157/build/nvidia/.nv-dma.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=1024 -fstack-protector-strong -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -g -gdwarf-5 -I/var/lib/dkms/nvidia/390.157/build/common/inc -I/var/lib/dkms/nvidia/390.157/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"390.157\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Wno-sign-compare -Wno-format-extra-args -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/390.157/build/nvidia -DNV_BUILD_MODULE_INSTANCES=0 -DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nv_dma"' -DKBUILD_MODNAME='"nvidia"' -D__KBUILD_MODNAME=kmod_nvidia -c -o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-gpu-numa.c:24: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-pgprot.h:17, from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:20: ./include/linux/mm.h:2397:46: note: expected ‘struct mm_struct *’ but argument is of type ‘struct task_struct *’ 2397 | long get_user_pages_remote(struct mm_struct *mm, |~~^~ /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:50: warning: passing argument 2 of ‘get_user_pages_remote’ makes integer from pointer
[Kernel-packages] [Bug 2052341] Re: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exi
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2052341 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: dpkg: dependency problems prevent configuration of nvidia-driver-390: nvidia-driver-390 depends on nvidia-dkms-390 (<= 390.157-1); however: Package nvidia-dkms-390 is not configured yet. nvidia-driver-390 depends on nvidia-dkms-390 (>= 390.157); however: Package nvidia-dkms-390 is not configured yet. dpkg: error processing package nvidia-driver-390 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. /var/crash reads: # CC [M] /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o x86_64-linux-gnu-gcc-12 -Wp,-MMD,/var/lib/dkms/nvidia/390.157/build/nvidia/.nv-dma.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=1024 -fstack-protector-strong -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-dangling-pointer -fno-omit-frame-pointer -fno-optimize-sibling-calls -ftrivial-auto-var-init=zero -fno-stack-clash-protection -fzero-call-used-regs=used-gpr -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -Wvla -Wno-pointer-sign -Wcast-function-type -Wno-stringop-truncation -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-array-bounds -Wno-alloc-size-larger-than -Wimplicit-fallthrough=5 -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -g -gdwarf-5 -I/var/lib/dkms/nvidia/390.157/build/common/inc -I/var/lib/dkms/nvidia/390.157/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error -D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"390.157\" -Wno-unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone -mcmodel=kernel -DNV_UVM_ENABLE -Wno-sign-compare -Wno-format-extra-args -Werror=undef -DNV_SPECTRE_V2=0 -DNV_KERNEL_INTERFACE_LAYER -I/var/lib/dkms/nvidia/390.157/build/nvidia -DNV_BUILD_MODULE_INSTANCES=0 -DNVIDIA_UNDEF_LEGACY_BIT_MACROS -UDEBUG -U_DEBUG -DNDEBUG -fsanitize=bounds-strict -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"nv_dma"' -DKBUILD_MODNAME='"nvidia"' -D__KBUILD_MODNAME=kmod_nvidia -c -o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.c ; ./tools/objtool/objtool --hacks=jump_label --hacks=noinstr --hacks=skylake --retpoline --rethunk --sls --stackval --static-call --uaccess --prefix=16 --module /var/lib/dkms/nvidia/390.157/build/nvidia/nv-dma.o In file included from /var/lib/dkms/nvidia/390.157/build/common/inc/nv-linux.h:21, from /var/lib/dkms/nvidia/390.157/build/nvidia/nv-gpu-numa.c:24: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h: In function ‘NV_GET_USER_PAGES_REMOTE’: /var/lib/dkms/nvidia/390.157/build/common/inc/nv-mm.h:164:45: error: passing argument 1 of ‘get_user_pages_remote’ from incompatible pointer type [-Werror=incompatible-pointer-types] 164 |return get_user_pages_remote(tsk, mm, start, nr_pages, flags, | ^~~ | | | struct task_struct * In file included from
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
Unfortunately I don't feel like I have enough understanding of why things are working for you given the versions you are dealing with. The whole thing seems like a complex compatibility matrix of client version, server version, and negotiated SMB protocol version. I've seen enough code changes and similar problems to now have validating timestamp behavior on my to-do checklist on any server (Samba) or client (cifs- utils) version upgrade. In general I would say the more recent you are with both, the more likely it seems that modtimes will work. In my limited experience, the latest cifs-utils emitted significantly cleaner SMB requests when preserving modification times. -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,iocharset=utf8,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) the remote NAS is a synology appliance, running Samba version 4.10.18. SMB version 3 Steps to reproduce: 1. Similar setup, 1 device running 20.04, another running 22.04, otherwise up to date. 2. mount the NAS on both devices the exact same way $ sudo mount -t cifs -o vers=3.0,credentials=/etc/samba/smbcreds,iocharset=utf8,rw,uid=1000,gid=1000,dir_mode=0775,file_mode=0664 //nas/backup /media/scratch 3. on the 20.04 older desktop, create a test file and show the modify time $ fallocate -l 1M test1.txt $ stat test1.txt File: test1.txt Size: 1048576 Blocks: 2048 IO Block: 4096 regular file Device: 801h/2049d Inode: 13634663Links: 1 Access: (0664/-rw-rw-r--) Uid: ( 1000/desktop_user) Gid: ( 1000/desktop_user) Access: 2023-02-12 18:35:48.978743377 -0700 Modify: 2023-02-12
[Kernel-packages] [Bug 2007055] Re: cifs/samba mount not preserving file timestamps
I kept digging into my specific issue, and now have to add a 4th dimension to the matrix of variables to consider that can affect modtime preservation: Samba configuration values. Here are the details. For my issue, modtimes are not preserved on Synology devices due to the Synology's default SMB Advanced Setting in the "Others" section of its UI, "Synchronize data to drive immediately upon SMB client request" This preference controls the smb "strict sync" configuration value. It was changed from False to True 6 years ago in Samba 4.7.0: https://gitlab.com/samba- team/samba/-/commit/ed483d8e570700a303e11bc03d6250cd0ae4aaed Synology devices still default this value to False though. Unfortunately, the False value causes a Samba bugfix that helped with correct modtimes to not work. This bugfix is here: https://gitlab.com/samba- team/samba/-/merge_requests/1210/diffs?commit_id=945158c7652bd0580828fb620afc722bc8a05967 . Unfortunately that bugfix does not work when strict sync is disabled, because smbd_smb2_flush_send checks lp_strict_sync and returns early instead of setting the smbd_smb2_flush_done callback to run; smbd_smb2_flush_done is where one of the modtime-related fixes was made. (I've double validated that it is this setting that makes the difference. Setting it to True on the Synology device causes modtimes to be preserved. Setting it to False on an Ubuntu VM that was preserving modtimes causes it to stop.) I passed this info on to Synology in case they are interested in changing the default value to match what Samba defaults to. I'll also mention the issue with the Samba bugfix for modtimes to the Samba project in case they are interested. -- 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/2007055 Title: cifs/samba mount not preserving file timestamps Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Incomplete Bug description: I think I've found a bug or regression in something when trying to mount a remote samba share. Modified/Created times are not properly preserved in newer versions of Ubuntu. Because of this, rsync thinks files are different based on their modified times and keeps re-syncing them. I have a NAS on my network, running samba. I have two devices, a desktop and laptop. Both are running Ubuntu, and set up the exact same way. The desktop is running ubuntu 20.04, the laptop 22.04. I have mounted the NAS on both devices the exact same way. I attempt to copy a file (rsync) the exact same way. On the 20.04 desktop, this works perfectly fine. On the 22.04 laptop, the modified times are not preserved and set to the current time, preventing things like rsync -t from working. The only difference i can find is that between the two systems, the newer laptop 22.04 mount adds a few more options than the older system to the cifs mount options. These are added automatically without being specified explicitly (see the mount -v output below): * 'forceuid'/'forcegid' are changed to 'noforceuid'/'noforcegid * iocharset=utf8 added * serverino added desktop: $ lsb_release -rd Description:Ubuntu 20.04.5 LTS Release:20.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.9-1ubuntu0.2 Candidate: 2:6.9-1ubuntu0.2 Version table: *** 2:6.9-1ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:6.9-1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages $ uname -a Linux desktop 5.4.0-132-generic #148-Ubuntu SMP Mon Oct 17 16:02:06 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs (rw,relatime,vers=3.0,cache=strict,username=nas_rw,uid=1000,forceuid,gid=1000,forcegid,addr=192.168.1.10,file_mode=0664,dir_mode=0775,soft,nounix,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1) laptop: $ lsb_release -rd Description:KDE neon 5.26 Release:22.04 $ apt-cache policy cifs-utils cifs-utils: Installed: 2:6.14-1ubuntu0.1 Candidate: 2:6.14-1ubuntu0.1 Version table: *** 2:6.14-1ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:6.14-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ uname -a Linux laptop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux $ mount -v //nas/backup on /media/scratch type cifs
[Kernel-packages] [Bug 2052332] [NEW] package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15.
Public bug reported: I reverted to 6.2.0-39 and purged headers and image for 6.5 since my computer cannot boot with 6.5+nvidia390 and when I use nouveau, my resolution is 640x320 and I can't proceed like this. Good luck with this one, thanks in advance. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 2 21:56:15 2024 DpkgHistoryLog: Start-Date: 2024-02-02 21:53:50 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-extra-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-hwe-6.5-headers-6.5.0-15:amd64 (6.5.0-15.15~22.04.1, automatic), linux-modules-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-image-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-headers-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic) Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-headers-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8) ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2023-02-25 (342 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2052332 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed building boot with linux kernel 6.5.0-15. Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I reverted to 6.2.0-39 and purged headers and image for 6.5 since my computer cannot boot with 6.5+nvidia390 and when I use nouveau, my resolution is 640x320 and I can't proceed like this. Good luck with this one, thanks in advance. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-390 390.157-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Feb 2 21:56:15 2024 DpkgHistoryLog: Start-Date: 2024-02-02 21:53:50 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-extra-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-hwe-6.5-headers-6.5.0-15:amd64 (6.5.0-15.15~22.04.1, automatic), linux-modules-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-image-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic), linux-headers-6.5.0-15-generic:amd64 (6.5.0-15.15~22.04.1, automatic) Upgrade: linux-image-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-headers-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8), linux-generic-hwe-22.04:amd64 (6.5.0.14.14~22.04.7, 6.5.0.15.15~22.04.8) ErrorMessage: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 InstallationDate: Installed on 2023-02-25 (342 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to install/upgrade: le sous-processus paquet nvidia-dkms-390 script post-installation installé a renvoyé un état de sortie d'erreur 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2052332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 2043811] Re: AWS: arm64: pauth: don't sign leaf functions
Patches sent to mailing list: Jammy: https://lists.ubuntu.com/archives/kernel- team/2024-February/148619.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2043811 Title: AWS: arm64: pauth: don't sign leaf functions Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Lunar: In Progress Bug description: SRU Justification [Impact] From our experiments, we found that not signing leaf functions on AWS Graviton instances helps improve application performance. We would like to have the patch https://github.com/torvalds/linux/commit/c68cf5285e1896a2b725ec01a1351f08610165b8 backported to Ubuntu 5.15, 5.19 and 6.2 kernels. We saw some of these performance improvements: NGINX 1%, MySQL 2%, PyTorch 2% [Test Plan] AWS tested. [Regression Potential] Arm64 binaries may not work correctly. [Other Info] SF: #00372369 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2043811/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7
I am attaching the other file version with the binary zero holes inside, as copied back from the server. ** Attachment added: "testdata-back-from-server.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+attachment/5744352/+files/testdata-back-from-server.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2049634 Title: SMB 1 broken in kernel 6.5.0.14.14~22.04.7 Status in linux package in Ubuntu: New Status in linux source package in Mantic: New Bug description: Hi all: I upgraded my Ubuntu yesterday and automatically got the newer Linux Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was running kernel version 6.2 . I still have a legacy system on the network using SMB protocol version 1.0. With the new kernel version, copying files does not work reliably anymore. Some random byte blocks in the destination files are overwritten with binary zeros. It happens quite often. This is not the first time the Linux guys temporarily break SMB protocol version 1.0, see for example this bug report of mine: https://bugs.launchpad.net/ubuntu/+bug/2033732 I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it lists just 2 versions: 6.5.0.14.14~22.04.7 (jammy-updates) 5.15.0.25.27 (jammy) Is there a way to go back to the latest 6.2 kernel version? How do I prevent Ubuntu from upgrading to 6.5 next time around? I have searched the Internet, but I haven't found yet a usable answer. I don't want to go back all the way to Kernel 5.15 if I can avoid it. Thanks in advance, rdiez To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049634] Re: SMB 1 broken in kernel 6.5.0.14.14~22.04.7
I have done some more tests on a different computer with the same OS,
this time with the following Kernel version as reported by "uname -a":
Linux 6.5.0-15-generic #15~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC
Fri Jan 12 18:54:30 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I generated a reproducible pseudo-random text file in this way:
( set -o pipefail && head --bytes=$(( 55 * 1000 )) /dev/zero | openssl
enc -aes-128-ctr -nosalt -pass "pass:my-seed" -iter 1 | hexdump --no-
squeezing --format '40/1 "%02x"' --format '"\n"' >"testdata.txt" )
The resulting text file is around 111 kbytes long.
I copied the file with 'cp' to the SMB 1.0 Windows server and back. I
have attached both file versions to this bug report.
Comparing the files with 'meld' yields 5 holes with binary zeros, each
one exactly 3900 bytes long. This is how I located the holes on the
command line:
grep --perl-regexp --text --byte-offset --only-matching
'\x00{3900}' testdata-back-from-server.txt | tr --delete '\000'
The resulting hole offsets are:
16580
37060
57540
78020
98500
That is, the holes repeat at a fixed offset interval of 20480 bytes,
that is, exactly 20 KiB.
The other PC with Kernel version 6.2.0-39-generic is working fine, as it
has in the past years.
It would be nice if someone else could reproduce this, as it might
actually be the server side, however unlikely that is.
** Attachment added: "testdata.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+attachment/5744351/+files/testdata.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
SMB 1 broken in kernel 6.5.0.14.14~22.04.7
Status in linux package in Ubuntu:
New
Status in linux source package in Mantic:
New
Bug description:
Hi all:
I upgraded my Ubuntu yesterday and automatically got the newer Linux
Kernel version 6.5.0-14-generic #14~22.04.1-Ubuntu. Previously, I was
running kernel version 6.2 .
I still have a legacy system on the network using SMB protocol version
1.0.
With the new kernel version, copying files does not work reliably
anymore. Some random byte blocks in the destination files are
overwritten with binary zeros. It happens quite often.
This is not the first time the Linux guys temporarily break SMB protocol
version 1.0, see for example this bug report of mine:
https://bugs.launchpad.net/ubuntu/+bug/2033732
I checked package linux-image-generic-hwe-22.04 with Synaptic, and now it
lists just 2 versions:
6.5.0.14.14~22.04.7 (jammy-updates)
5.15.0.25.27 (jammy)
Is there a way to go back to the latest 6.2 kernel version?
How do I prevent Ubuntu from upgrading to 6.5 next time around? I have
searched the Internet, but I haven't
found yet a usable answer. I don't want to go back all the way to Kernel 5.15
if I can avoid it.
Thanks in advance,
rdiez
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049634/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052013] Re: NVMe high power state after wake up from sleep
Set affected package ** Description changed: [ISSUE] I have a dual boot acer helios laptop (windows is on the nvme, ubuntu on an SSD). Once I boot into Ubuntu (SSD) my drive works as expected. But once I set my laptop to sleep and wake it back up again the nvme drive power state is set to max rather than the default low power state. This causes a lot of heat to be generated and the smartctl tool reports the tempSenor#2 as 80-90C when in low power mode it runs at 40-60C. I've observed this behaviour under Ubuntu 20.04.6 LTS and via live USB (22.04.3 LTS, 23.10) BEFORE SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value:0x04 Workload Hint (WH): 0 - No Workload Power State (PS): 4 AFTER SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value: Workload Hint (WH): 0 - No Workload Power State (PS): 0 [Fix] If i run the following command i can manually set the drive into a low power mode which dramatically effects both the onboard nvme temps and system temp (PCH chip) sudo nvme set-feature /dev/nvme0n1p1 -f 2 -v 4 [INFO] cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" VERSION_CODENAME=focal UBUNTU_CODENAME=focal sudo nvme get-feature /dev/nvme0n1p1 -f 0x0c -H get-feature:0xc (Autonomous Power State Transition), Current value:0x01 - Autonomous Power State Transition Enable (APSTE): Enabled + Autonomous Power State Transition Enable (APSTE): Enabled sudo smartctl /dev/nvme0n1p1 -a smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-92-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZVL2512HCJQ-00B07 - Serial Number: S63CNF0R202458 + Serial Number: <> Firmware Version: GXA7302Q PCI Vendor/Subsystem ID:0x144d IEEE OUI Identifier:0x002538 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 6 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization:200,490,106,880 [200 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:002538 b211b0a1d9 Local Time is: Thu Feb 1 22:18:19 2024 PST Firmware Updates (0x16):3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 81 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 8.37W --0 0 0 00 0 1 + 8.37W --1 1 1 10 200 2 + 8.37W --2 2 2 20 200 3 - 0.0500W --3 3 3 3 20001200 4 - 0.0050W --4 4 4 4 5009500 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:43 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:5,771,370 [2.95 TB] Data Units Written: 6,509,044 [3.33 TB] Host Read Commands: 96,282,996 Host Write Commands:92,199,213 Controller Busy Time: 56 Power Cycles: 1,245 Power On Hours: 2,632 Unsafe Shutdowns: 145 Media and Data Integrity Errors:3 Error Information Log Entries: 0 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Temperature Sensor 1: 43 Celsius Temperature Sensor 2: 42 Celsius Thermal Temp. 1 Transition Count: 3 Thermal Temp. 1 Total Time: 240 Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is
[Kernel-packages] [Bug 2052013] [NEW] NVMe high power state after wake up from sleep
You have been subscribed to a public bug: [ISSUE] I have a dual boot acer helios laptop (windows is on the nvme, ubuntu on an SSD). Once I boot into Ubuntu (SSD) my drive works as expected. But once I set my laptop to sleep and wake it back up again the nvme drive power state is set to max rather than the default low power state. This causes a lot of heat to be generated and the smartctl tool reports the tempSenor#2 as 80-90C when in low power mode it runs at 40-60C. I've observed this behaviour under Ubuntu 20.04.6 LTS and via live USB (22.04.3 LTS, 23.10) BEFORE SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value:0x04 Workload Hint (WH): 0 - No Workload Power State (PS): 4 AFTER SLEEP: sudo nvme get-feature /dev/nvme0n1p1 -f 2 -H get-feature:0x2 (Power Management), Current value: Workload Hint (WH): 0 - No Workload Power State (PS): 0 [Fix] If i run the following command i can manually set the drive into a low power mode which dramatically effects both the onboard nvme temps and system temp (PCH chip) sudo nvme set-feature /dev/nvme0n1p1 -f 2 -v 4 [INFO] cat /etc/os-release NAME="Ubuntu" VERSION="20.04.6 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.6 LTS" VERSION_ID="20.04" VERSION_CODENAME=focal UBUNTU_CODENAME=focal sudo nvme get-feature /dev/nvme0n1p1 -f 0x0c -H get-feature:0xc (Autonomous Power State Transition), Current value:0x01 Autonomous Power State Transition Enable (APSTE): Enabled sudo smartctl /dev/nvme0n1p1 -a smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.15.0-92-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZVL2512HCJQ-00B07 Serial Number: <> Firmware Version: GXA7302Q PCI Vendor/Subsystem ID:0x144d IEEE OUI Identifier:0x002538 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 6 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Utilization:200,490,106,880 [200 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64:002538 b211b0a1d9 Local Time is: Thu Feb 1 22:18:19 2024 PST Firmware Updates (0x16):3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x0057): Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 81 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 8.37W --0 0 0 00 0 1 + 8.37W --1 1 1 10 200 2 + 8.37W --2 2 2 20 200 3 - 0.0500W --3 3 3 3 20001200 4 - 0.0050W --4 4 4 4 5009500 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature:43 Celsius Available Spare:100% Available Spare Threshold: 10% Percentage Used:0% Data Units Read:5,771,370 [2.95 TB] Data Units Written: 6,509,044 [3.33 TB] Host Read Commands: 96,282,996 Host Write Commands:92,199,213 Controller Busy Time: 56 Power Cycles: 1,245 Power On Hours: 2,632 Unsafe Shutdowns: 145 Media and Data Integrity Errors:3 Error Information Log Entries: 0 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Temperature Sensor 1: 43 Celsius Temperature Sensor 2: 42 Celsius Thermal Temp. 1 Transition Count: 3 Thermal Temp. 1 Total Time: 240 Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- NVMe high power state after wake up from sleep https://bugs.launchpad.net/bugs/2052013 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1996609] Re: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1996609 Title: AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 intel IoTG kernel Status in HWE Next: Fix Released Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-iotg-5.15 source package in Focal: Fix Released Status in linux-intel-iotg source package in Jammy: Fix Released Status in linux-intel-iotg-5.15 source package in Jammy: Invalid Bug description: [Summary] AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel. [Steps to reproduce] install 5.15 Intel IoTG kernel. [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% The ucode version 66 would not be loaded successfully on this particular model with the folloing error messages: [ 13.231830] kernel: iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [ 13.232964] kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [ 13.233061] kernel: iwlwifi :02:00.0: Start IWL Error Log Dump: [ 13.233062] kernel: iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [ 13.233064] kernel: iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [ 13.233065] kernel: iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [ 13.233066] kernel: iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [ 13.233067] kernel: iwlwifi :02:00.0: 0x | trm_hw_status1 [ 13.233068] kernel: iwlwifi :02:00.0: 0x004DA722 | branchlink2 ... [ 14.094020] kernel: iwlwifi :02:00.0: Failed to run INIT ucode: -5 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040522] Re: gVNIC DQO-QPL feature
Verified by Google as part of SF#00366697. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2040522 Title: gVNIC DQO-QPL feature Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Focal: Won't Fix Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Lunar: Won't Fix Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Google requested inclusion of gVNIC DQO-QPL feature. [Fix] * Mantic: all clean cherry-picks from upstream * Jammy: 22 clean cherry-picks, 8 backports from upstream [Test Case] * Compile tested * Boot tested * Tested by Google [Where things could go wrong] * Low chance of regression. Almost all changes isolated to Google Ethernet drivers. * All changes upstream as of v6.6. [Other Info] * SF #00366697 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2040522/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039720] Re: Intel IDPF support
Verified by Google as part of SF#00368902 as well as internally on GCE instance. ** Tags removed: verification-needed-jammy-linux-gcp verification-needed-mantic-linux-gcp ** Tags added: verification-done-jammy-linux-gcp verification-done-mantic-linux-gcp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2039720 Title: Intel IDPF support Status in linux-gcp package in Ubuntu: New Status in linux-gcp source package in Jammy: Fix Committed Status in linux-gcp source package in Mantic: Fix Committed Bug description: [Impact] * Request from Google to include new Intel IDPF driver support [Fix] * Mantic - 24 clean cherry-picks, 1 backport from upstream * Jammy - 11 clean cherry-picks, 7 backports from upstream [Test Case] * Compile tested * Boot tested * Tested internally and by Google using neper (https://github.com/google/neper) * Networking is functional and throughput is as expected [Where things could go wrong] * Low chance of regression, changes have been upstream since 6.6 kernel * Bulk of changes in IDPF driver * Other changes to network drivers largely adding #include directives [Other Info] * SF #00368902 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2039720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
** Attachment added: "jammy: verification steps 4-6" https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5744328/+files/jammy.log ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Committed Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Committed Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
** Attachment added: "mantic: verification steps 4-6" https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5744327/+files/mantic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2043059 Title: Installation errors out when installing in a chroot Status in kdump-tools package in Ubuntu: Fix Released Status in linux-nvidia package in Ubuntu: Invalid Status in kdump-tools source package in Jammy: Fix Committed Status in linux-nvidia source package in Jammy: Invalid Status in kdump-tools source package in Mantic: Fix Committed Status in linux-nvidia source package in Mantic: Invalid Status in kdump-tools source package in Noble: Fix Released Status in linux-nvidia source package in Noble: Invalid Bug description: [Impact] When installing in a chroot environment, the kdump-tools kernel hook will fail. This breaks certain OS image creation tools, such as BCM (which I assume is NVIDIA Base Command Manager from context). While BCM's image generation tool requires some additional tweaks to consume this, the proposed fix is necessary, and should be sufficient for other tools that use chroots. [Test Plan] 1) debootstrap a chroot environment for the target Ubuntu release 2) Install kdump-tools within that environment 3) Install a kernel package and make sure it succeeds. 4) do the same steps in a virtual machine, but with `ischroot` symlinked to /dev/true at install time. This should simulate a system that was just installed with an image prepared as above. 5) Then restore ischroot, and reboot. 6) Confirm the systemd service does generate an initramfs at boot, and 7) that a crash dump can be triggered afterwords. [Where Problems Could Occur] The solution we implemented in noble was simply to detect a chroot environment with ischroot, and disable initramfs generation. The systemd service will detect that an initrd is missing, and generate one on first boot. A source of potential problems is if that does not happen for some reason, resulting in a kdump-tools service failure on first boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdump-tools/+bug/2043059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
So what's the current status with this bug? Is it now fixed in 6.8rc1 kernel and above? Any older kernel has to be patched? -- 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/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043059] Re: Installation errors out when installing in a chroot
# verification steps 1-3: installation in a chroot
I set up 2 chroots - one w/ the normal sources.list, the other w/
proposed enabled, and did a side by side install test.
$ for chroot in mantic mantic-proposed jammy jammy-proposed; do sudo chroot
$chroot apt list kdump-tools; done
Listing... Done
kdump-tools/mantic,now 1:1.8.1ubuntu1 amd64 [installed]
Listing... Done
kdump-tools/mantic-proposed,now 1:1.8.1ubuntu1.1 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
Listing... Done
kdump-tools/jammy-updates,now 1:1.6.10ubuntu2.1 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
Listing... Done
kdump-tools/jammy-proposed,now 1:1.6.10ubuntu2.2 amd64 [installed]
N: There are 2 additional versions. Please use the '-a' switch to see them.
## mantic
### first w/ only updates enabled
dannf@lakitu:~$ sudo chroot mantic-proposed apt install kdump-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kdump-tools is already the newest version (1:1.8.1ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 40 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
Setting up linux-image-6.5.0-15-generic (6.5.0-15.15) ...
Processing triggers for linux-image-6.5.0-15-generic (6.5.0-15.15) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic
/etc/kernel/postinst.d/kdump-tools:
kdump-tools: Generating /var/lib/kdump/initrd.img-6.5.0-15-generic
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /var/lib/kdump/initramfs-tools
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for /var/lib/kdump/initrd.img-6.5.0-15-generic with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
dpkg: error processing package linux-image-6.5.0-15-generic (--configure):
installed linux-image-6.5.0-15-generic package post-installation script
subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-6.5.0-15-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
### and now w/ proposed
$ sudo chroot mantic-proposed apt install kdump-tools -t mantic-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
kdump-tools
1 upgraded, 0 newly installed, 0 to remove and 50 not upgraded.
1 not fully installed or removed.
Need to get 30.8 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu mantic-proposed/main amd64
kdump-tools amd64 1:1.8.1ubuntu1.1 [30.8 kB]
Fetched 30.8 kB in 0s (1216 kB/s)
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LANG = "en_US.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Preconfiguring packages ...
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (19: No such device)
(Reading database ... 46941 files and directories currently installed.)
Preparing to unpack .../kdump-tools_1%3a1.8.1ubuntu1.1_amd64.deb ...
Unpacking kdump-tools (1:1.8.1ubuntu1.1) over (1:1.8.1ubuntu1) ...
Setting up linux-image-6.5.0-15-generic (6.5.0-15.15) ...
Setting up kdump-tools (1:1.8.1ubuntu1.1) ...
Installing new version of config file /etc/kernel/postinst.d/kdump-tools ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
Running in chroot, ignoring request.
Processing triggers for initramfs-tools (0.142ubuntu15.1) ...
update-initramfs: Generating /boot/initrd.img-6.5.0-15-generic
Processing triggers for linux-image-6.5.0-15-generic (6.5.0-15.15) ...
[Kernel-packages] [Bug 2051450] Re: Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106
I might not need to open a new bug report because I found a few links related to the nvidia module problem: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-510/+bug/1963805 https://answers.launchpad.net/ubuntu/+question/706349 I hope this can help others who have a similar problem with their nvidia modules. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051450 Title: Nouveau kernel errors prevent reaching the login screen on NVIDIA GA106 Status in linux-hwe-6.5 package in Ubuntu: New Bug description: n/a ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-15.15~22.04.1-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 28 09:29:28 2024 ExecutablePath: /usr/libexec/gnome-session-binary InstallationDate: Installed on 2023-12-27 (31 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2051450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 2049768] Re: my computer doesnt start
Please Ignore this report. I figured the kernel 6.5 has a bug thats making my computer crash. Another person is helping me out. Em 01/02/2024 20:58, Seth Arnold escreveu: > ** Changed in: linux (Ubuntu) > Status: Incomplete => New > -- J.P. 3D Studio www.jonathanpaul.com.br -- 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/2049768 Title: my computer doesnt start Status in linux package in Ubuntu: New Bug description: This shows up on the black screen: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-hwe-6.5-6.5.0/include/linux/ieee80211.h: 4304 : 28 index 15 is out of range for type 'u8 [1] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jonathan 1116 F pulseaudio /dev/snd/controlC1: jonathan 1116 F pulseaudio /dev/snd/pcmC0D0p: jonathan 1116 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-02-09 (709 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 RelatedPackageVersions: linux-restricted-modules-6.2.0-39-generic N/A linux-backports-modules-6.2.0-39-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 6.2.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2018 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: INTEL H55 dmi.board.vendor: INTEL dmi.board.version: INTEL dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
Also backported to 6.1.76 Can we get it into Mantic 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/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. Status in linux package in Ubuntu: Confirmed Bug description: My setup: Host: Ubuntu Linux 22.04.1, kernel 5.15, Ryzen 5900x Hypervisor: KVM Windows VM with VMware Workstation 16 Running nested VMs in VMware works ok. It fails if Linux host kernel is updated to 5.19 (22.04.2) with MONITOR PANIC: Invalid VMCB. VMware Workstation unrecoverable error: (vcpu-0) vcpu-0:Invalid VMCB. If I update to Workstation 17 it fails with 2023-02-24T15:21:35.112Z In(05) vmx The following features are required for SVM support in VMware Workstation; however, these features are not available on this host: 2023-02-24T15:21:35.112Z In(05) vmxFlush by ASID. This host supports AMD-V, but the AMD-V implementation is incompatible with VMware Workstation. VMware Workstation does not support the user level monitor on this host. Module 'MonitorMode' power on failed. The same VM works ok on 5.19 kernel on my Intel PC. So it has to do with updated Linux kernel and AMD virtualization and VMware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033416] Re: [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
The following are some basic tests to compare results on a system before and after this change. For existing kernels built with CONFIG_PERF_EVENTS_AMD_UNCORE=m, the following will fail unless the "amd_uncore" module is loaded. For new kernels built with CONFIG_PERF_EVENTS_AMD_UNCORE=y, the following should pass without having to load a module. 1. The following sysfs directories will be present. /sys/bus/event_source/devices/amd_l3 /sys/bus/event_source/devices/amd_df 2. Opening events on the L3 and DF PMUs should not return any errors. sudo perf stat -e amd_l3// -a true sudo perf stat -e amd_df// -a true 3. There are several named events and metrics in perf tool which use amd_l3 and amd_df events. To test if these are working after this change, one can run some tests from the built-in test suite. The tests of importance are 101: perf stat tests 102: perf all metricgroups test 103: perf all metrics test 104: perf all PMU test Please note that the test numbering can vary but can be found by running "perf test list". Once the test numbers are known, they can be run individually as shown below. It is preferable to run these tests in verbose mode in order to get more information in case of a failure. $ sudo perf test -v 101 I don't expect any side-effects since there are no functional changes in terms of how the uncore PMU events are handled. -- 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/2033416 Title: [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y Status in linux package in Ubuntu: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Bug description: [Impact] Ubuntu currently sets CONFIG_PERF_EVENTS_AMD_UNCORE=m for distro kernels. However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event. Also, a primary motivation to add module support in uncore driver was to ease development (https://git.kernel.org/torvalds/c/05485745ad482). Its not immediately apparent from perf tool output that the "amd- uncore" module is not loaded when opening "amd_df" or "amd_l3" events fail or when they do not show up in "perf list" despite using a compatible kernel. Since the primary motivation of the commit [1] that made it possible for this to be loaded as a module was to make development easier, CONFIG_PERF_EVENTS_AMD_UNCORE defaults to 'y' [2]. [1] https://git.kernel.org/torvalds/c/05485745ad482 [2] https://github.com/torvalds/linux/blob/master/arch/x86/events/Kconfig#L40 [Fix] Change kernel config to CONFIG_PERF_EVENTS_AMD_UNCORE=y [Test case] (How can this change be tested/verified?) [Where problems may occur] (What side effects or regressions could this change create?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051733] Re: Specifying nohz_full breaks CPU frequency reporting
I'm not familiar with Linux kernel internals, or how scaling_cur_freq is implemented internally, but that doesn't look like a valid logic to me. If it takes an IPI (or two, as the commit message suggests) to read the core frequency, then make those IPIs. It doesn't matter how expensive it is - if the user wants to read the current frequency then he is willing to pay for that information. This likely won't be a frequent operation anyway. Providing an interface to read this information and then feeding bogus data through it is not acceptable, IMO. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2051733 Title: Specifying nohz_full breaks CPU frequency reporting Status in linux-signed-lowlatency-hwe-6.5 package in Ubuntu: Confirmed Bug description: With the lowlatency kernel, if I specify "nohz_full=1-15" boot parameter then CPU frequency reporting doesn't work for the logical cores 1-15. That is, only logical core 0 shows varying CPU frequency in its /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq file, all other cores constantly show 80 in their scaling_cur_freq files (which is the lowest supported frequency) regardless of the CPU load. Steps to reproduce: 1. Add "nohz_full=1-15" (specify the core numbers to include all logical cores except 0) to kernel boot options in /etc/default/grub. 2. Run `sudo update-grub` and reboot. 3. Upon booting, run a multithreaded workload. For example, run `openssl speed -multi $(nproc --all)`. 4. In another console, monitor CPU frequencies by running `watch cat /sys/devices/system/cpu/cpu[0-9]*/cpufreq/scaling_cur_freq`. Actual results: All cores specified in "nohz_full" parameter always report their lowest frequency. Despite that, the actual performance seems to be as if frequency scaling actually works (i.e. according to benchmarks, the performance seems to be similar with and without the "nohz_full" parameter). Expected results: All cores must report their actual frequency depending on the load. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-15-lowlatency 6.5.0-15.15.1.1~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-15.15.1.1~22.04.1-lowlatency 6.5.3 Uname: Linux 6.5.0-15-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Jan 30 23:39:51 2024 InstallationDate: Installed on 2015-05-01 (3196 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: linux-signed-lowlatency-hwe-6.5 UpgradeStatus: Upgraded to jammy on 2022-05-14 (626 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency-hwe-6.5/+bug/2051733/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051871] Re: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/2051871 Title: mlxbf-tmfifo: Drop Tx network packet when Tx TmFIFO is full Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: New Bug description: SRU Justification: [Impact] This is a cherry-pick fix from upstream to drop Tx network packet when Tx TmFIFO is full. [Fix] Starting from Linux 5.16 kernel, Tx timeout mechanism was added in the virtio_net driver which prints the "Tx timeout" warning message when a packet stays in Tx queue for too long. Below is an example of the reported message: "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since last trans: 3079892256". This issue could happen when external host driver which drains the FIFO is restared, stopped or upgraded. To avoid such confusing "Tx timeout" messages, this commit adds logic to drop the outstanding Tx packet if it's not able to transmit in two seconds due to Tx FIFO full, which can be considered as congestion or out-of-resource drop. This commit also handles the special case that the packet is half- transmitted into the Tx FIFO. In such case, the packet is discarded with remaining length stored in vring->rem_padding. So paddings with zeros can be sent out when Tx space is available to maintain the integrity of the packet format. The padded packet will be dropped on the receiving side. [Test Case] Same functionality and testing as on BlueField-1/2/3. No functionality change. [Regression Potential] Same behavior from user perspective. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2051871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Hello Tobias, or anyone else affected,
Accepted zfs-linux into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.1.5-1ubuntu6~22.04.3 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: zfs-linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: zfs-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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2044657] Please test proposed package
Hello Tobias, or anyone else affected,
Accepted zfs-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.8.3-1ubuntu12.17 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
Fix Committed
Status in zfs-linux source package in Jammy:
Fix Committed
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032247] Comment bridged from LTC Bugzilla
--- Comment From s...@de.ibm.com 2024-02-02 04:24 EDT--- are there any news regarding missing rcrt1.o? -- 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/2032247 Title: [UBUNTU 23.04] S390: static-PIE programs segfaults if libc6-dev-s390x-cross package is installed Status in Ubuntu on IBM z Systems: New Status in gcc-12-cross package in Ubuntu: New Status in gcc-13-cross package in Ubuntu: New Status in glibc package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: == by Stefan == A simple helloworld program build and linked as static-PIE segfaults while startup in __libc_setup_tls: $ gcc -c -fPIE -static-pie -o hello.o hello.c $ gcc -o hello hello.o -static-pie Note: If only libc6-dev package is installed, all is fine. If both libc6-dev and libc6-dev-s390x-cross packages are installed, you will see the mentioned segfault. Linking with "-Wl,-v" dumps the used linker command and it shows the used startup-files: /usr/lib/s390x-linux-gnu/rcrt1.o => from libc6-dev /usr/s390x-linux-gnu/lib/crti.o => from libc6-dev-s390x-cross /usr/lib/gcc/s390x-linux-gnu/12/crtbeginS.o /usr/lib/gcc/s390x-linux-gnu/12/crtendS.o /usr/s390x-linux-gnu/lib/crtn.o => from libc6-dev-s390x-cross Linking as static-PIE requires the rcrt1.o file, which is not available in libc6-dev-s390x-cross package, but in libc6-dev. Due to this mixing of the startup-files, you get the segfault. This issue can be fixed by enabling static-PIE also in the libc6-dev-s390x-cross package, then all startup-files belong to the same package. For s390x static-PIE was introduced in glibc 2.36: commit "S390: Enable static PIE" (in glibc 2.36) https://sourceware.org/git/?p=glibc.git;a=commit;h=728894dba4a19578bd803906de184a8dd51ed13c There is a configure check which do a link-test to ensure that a suitable binutils(ld) version is used. Afterwards static-PIE is automatically enabled. The required binutils-patches are first included in binutils 2.39. According to the build log of package cross-toolchain-base (see https://launchpad.net/ubuntu/+source/cross-toolchain-base/66ubuntu3/+build/25689036), the libc6-dev-s390x-cross package is cross-build on x86_64 and the mentioned configure check fails: running configure fragment for sysdeps/s390/s390-64 checking for s390-specific static PIE requirements... no In this cross build, glibc is configured in order to first build the crt-startup-files, which are needed to complete the cross-gcc build. At this time, the sysroot does not contain the crt-files or libc.so itself. Thus the "linking" configure check is failing. After building the cross-gcc, glibc is build without re-configuring. Thus static-PIE is not enabled. In glibc-upstream, this configure check is now adjusted and it allows checking binutils by version number: commit "s390x: Fix static PIE condition for toolchain bootstrapping." (will be in glibc 2.39) https://sourceware.org/git/?p=glibc.git;a=commit;h=f5f96b784beb3480e0e8d10e250ca7e6063ab881 Perhaps you also have to pick the following commits by Sam James which adjusted the tests in between (both are in glibc 2.36): - commit "s390: use $READELF" https://sourceware.org/git/?p=glibc.git;a=commit;h=c376ff3287b9b0f78a4f8951313c6dae60cbdfea - commit "s390: use LC_ALL=C for readelf call" https://sourceware.org/git/?p=glibc.git;a=commit;h=2249ec60a987f9a7aa585890de2bd365b3656d28 In addition to the static-PIE configure-checks, there are those other s390-specific configure-checks to determine which IFUNC-optimizations can be build and used as default. Those also fail for libc6-dev-s390x-cross as linking is also involved: running configure fragment for sysdeps/s390 checking for __builtin_tbegin... yes checking for S390 vector instruction support... no configure: WARNING: Use binutils with vector-support in order to use optimized implementations. checking for S390 vector support in gcc... no checking for S390 arch13 zarch instruction support... no checking for S390 z10 zarch instruction support as default... no checking for S390 z196 zarch instruction support as default... no checking for S390 z13 zarch instruction support as default... no checking for S390 arch13 zarch instruction support as default... no Those checks were also adjusted in glibc-upstream. Please also pick this commits: commit "S390: Use compile-only instead of also link-tests in configure." (in glibc 2.38) https://sourceware.org/git/?p=glibc.git;a=commit;h=368b7c614b102122b86af3953daea2b30230d0a8 I've observed this issue on Ubuntu 23.04 with glibc 2.37 and binutils 2.40: binutils/lunar-updates,lunar-security,now 2.40-2ubuntu4.1 s390x [installed] libc6-dev-s390x-cross/lunar,now 2.37-0ubuntu2cross1 all [installed] libc6-dev/lunar,now 2.37-0ubuntu2 s390x
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen
Patches sent (to multiple places per get_maintainer.pl): https://lkml.org/lkml/2024/2/2/373 https://lkml.org/lkml/2024/2/2/375 -- 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/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2044657] Re: Multiple data corruption issues in zfs
Hello Tobias, 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.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
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.
** Changed in: zfs-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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2044657
Title:
Multiple data corruption issues in zfs
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Xenial:
Confirmed
Status in zfs-linux source package in Bionic:
Confirmed
Status in zfs-linux source package in Focal:
In Progress
Status in zfs-linux source package in Jammy:
In Progress
Status in zfs-linux source package in Lunar:
Won't Fix
Status in zfs-linux source package in Mantic:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
[ Impact ]
* Multiple data corruption issues have been identified and fixed in
ZFS. Some of them, at varying real-life reproducibility frequency have
been deterimed to affect very old zfs releases. Recommendation is to
upgrade to 2.2.2 or 2.1.14 or backport dnat patch alone. This is to
ensure users get other potentially related fixes and runtime tunables
to possibly mitigate other bugs that are related and are being fixed
upstream for future releases.
* For jammy the 2.1.14 upgrade will bring HWE kernel support and also
compatiblity/support for hardened kernel builds that mitigate SLS
(straight-line-speculation).
* In the absence of the upgrade a cherry-pick will address this
particular popular issue alone - without addressing other issues
w.r.t. Redbleed / SLS, bugfixes around trim support, and other related
improvements that were discovered and fixed around the same time as
this popular issue.
[ Test Plan ]
* !!! Danger !!! use reproducer from
https://zfsonlinux.topicbox.com/groups/zfs-discuss/T12876116b8607cdb
and confirm if that issue is resolved or not. Do not run on production
ZFS pools / systems.
* autopkgtest pass (from https://ubuntu-archive-
team.ubuntu.com/proposed-migration/ )
* adt-matrix pass (from https://kernel.ubuntu.com/adt-matrix/ )
* kernel regression zfs testsuite pass (from Kernel team RT test
results summary, private)
* zsys integration test pass (upgrade of zsys installed systems for
all releases)
* zsys install test pass (for daily images of LTS releases only that
have such installer support, as per iso tracker test case)
* LXD (ping LXD team to upgrade vendored in tooling to 2.2.2 and
2.1.14, and test LXD on these updated kernels)
[ Where problems could occur ]
* Upgrade to 2.1.14 on jammy with SLS mitigations compatiblity will
introduce slight slow down on amd64 (for hw accelerated assembly code-
paths only in the encryption primitives)
* Uncertain of the perfomance impact of the extra checks in dnat
patch fix itself. Possibly affecting speed of operation, at the
benefit of correctness.
* The cherry-picked patch ("dnat"? dnode) changes the dirty data check, but
only makes it stronger and not weaker, thus if it were incorrect, likely
only performance would be impacted (and it is unlikely to be incorrect
given upstream reviews and attention to data corruption issues; also,
there are no additional changes to that function upstream)
[ Other Info ]
* https://github.com/openzfs/zfs/pull/15571 is most current
consideration of affairs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help
[Kernel-packages] [Bug 2045562] Re: [Debian] autoreconstruct - Do not generate chmod -x for deleted files
This is a pure packaging change which I consider verified by the fact that correctly building source debs got uploaded. ** Tags removed: verification-needed-jammy-linux ** Tags added: verification-done-jammy-linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2045562 Title: [Debian] autoreconstruct - Do not generate chmod -x for deleted files Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Status in linux source package in Noble: Fix Committed Bug description: SRU Justification: [Impact] Debian source format 1.0 cannot remove files, create symlinks and change permission in the .diff.gz tarball. Therefore any changes in these 3 categories cannot be represented without any tricks. To solve this, the `reconstruct` script is used every time we build the source package. The script is generated by `gen-auto-reconstruct` script during `cranky close`. It checks if there has been any changes in the 3 categories mentioned above between the upstream version (i.e v6.5) and the current one. The problem with the script is that in case a file A was removed since the upstream version was released, the `reconstruct` script will contains these commands in this exact order: rm -f A chmod -x A The second command will fail because file A does not exist anymore. This is solved by generating the `chmod +/-x` commands before `rm`. Which results in: chmod -x A rm -f A But because the reconstruct script is used during `clean` rule which is triggered pretty much during every cranky step which is run in the source repo, the first command will always file because file A is not present anymore in the tree. To solved this, any `chmod` change is added only if the file has not been deleted. Therefore if file A has been deleted, the `reconstruct` script will contain only this: rm -f A [Fix] Generate chmod commands first. And when generating chmod -x command, first check if the file has been deleted. If yes, no need for a chmod command. [Test Plan] It was tested for cycle sru 2023.10.30 for mantic,lunar,jammy and focal and it reconstruct script looked correct. [Other Info] An example of this is #lp2038611 where `script/is_rust_module.sh` was removed, but we keep seeing "chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory" because `rm -f` and `chmod -x` command were generated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
