Re: [Kernel-packages] [Bug 1967858] Re: Make arch specific linux-firmware
On Thu, 4 May 2023, 22:35 Mantas Kriaučiūnas, <1967...@bugs.launchpad.net> wrote: > @juergh maybe it would be better simply reuse debian packaging practice > for linux-firmware? Please also look at LP bug #1958518 - this issue is > solved in Debian a long time ago: > > metapackage https://packages.debian.org/sid/firmware-linux depends on > small firmware-linux-free package and firmware-linux-nonfree metapackage > Ubuntu and Debian have different licensing and distribution requirements of what goes into free/nonfree/any. metapackage https://packages.debian.org/sid/firmware-linux-nonfree > depends on most useful "nonfree" firmware, including this pretty > firmware-misc-nonfree package (takes only ~40 MB after installation, > instead of ~900MB sized of Ubuntu's linux-firmware): > https://packages.debian.org/sid/firmware-misc-nonfree > > For example netronome network adapters firmware is packaged separately > in Debian, see https://packages.debian.org/sid/firmware-netronome For many reasons in Debian firmwares are split into multiple source packages which in Ubuntu we do not want for operational reasons. Also in Ubuntu, unlike in Debian, we have support for additional hardware detection and package installation via ubuntu-drivers. > Someone from Ubuntu developers decided simply put all useful and almost > not used firmware into huge package, which is updated very often and > this causes a lot of problems for users, especially who uses SSD storage > or slow internet connection :( > > For example see bug #1972806 - simple change of some device firmware > (few kilobytes size) requires to download ~250MB linux-firmware package > for *every* Ubuntu user. This is a nonsense and waste of bandwidth and > other resources. > There are many optimisations we can do on that front that are orthogonal to this. Adopting Debian packaging split is not enough for us, and thus if we are doing work to split things we need it to be done the most optimal way that will serve all our current needs and the future ones. Just adopting Debian splits will improve things a little for us, but also regress many of our usecases which will break our users. No silver bullet so far. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1967858 Title: Make arch specific linux-firmware Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Mantic: In Progress Bug description: There are many kernel modules that only exist on some architectures. Yet linux-firmware is an arch:all package that ships firmware for all drivers, for all architectures. For example, it is pointless to ship many Intel firmware on non-x86 machines. At the same time it is pointless to ship many Qualcomm firmware on non-arm machines. Or shipping nvidia firmware on architectures that have no Nvidia drivers. Or shipping wifi firmware on IBM Z / PowerPC. It seems like we should build-depend on linux / linux-oem kernels and only install relevant firmware files on relevant architectures only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1967858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685291] Re: RFC: virtio and virtio-scsi should be built in
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685291 Title: RFC: virtio and virtio-scsi should be built in Status in linux package in Ubuntu: Fix Committed Bug description: Hi, I was trying to verify bug 1677376 yesterday, and came to find out that our kernel does not have virtio or virtio-scsi builtin drivers. This generally has not been a problem as initramfs has been used. However, as there is recently an interest in booting without initramfs it would seem to make sense to have popular drivers builtin to -generic to allow that. Also, from a priority perspective, if we're going to have any block devices builtin to the -generic kernel, then i'd think that virtio and virtio-scsi would make more sense than an IDE driver. I understand there are tradeoffs involved. Related bugs: * bug 1677376: growing partitions does not work when booted without initramfs ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: User Name 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 20:07 seq crw-rw 1 root audio 116, 33 Apr 19 20:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Apr 20 19:37:23 2017 Ec2AMI: ami-0019 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017571] Re: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package
** Description changed: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. - * Extend package.config inside azure cvm builds + * Extend package.config inside linux-signed-azure* to add cvm builds + * Add linux-meta changes for the above * Drop linux-azure-fde* source kernels -- 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/2017571 Title: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package Status in linux package in Ubuntu: Triaged Bug description: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. * Extend package.config inside linux-signed-azure* to add cvm builds * Add linux-meta changes for the above * Drop linux-azure-fde* source kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017571] Re: Combine azure & azure-fde packages
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Description changed: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. + + == Plan of action == + * Extend linux-signed & linux-generate to produce CVM specific package builds. + * Apply that everywhere. + * Extend package.config inside azure cvm builds + * Drop linux-azure-fde* source kernels ** Summary changed: - Combine azure & azure-fde packages + SIGNEDv4: add Azure CVM support to the linux-generate ancillary package -- 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/2017571 Title: SIGNEDv4: add Azure CVM support to the linux-generate ancillary package Status in linux package in Ubuntu: Triaged Bug description: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. == Plan of action == * Extend linux-signed & linux-generate to produce CVM specific package builds. * Apply that everywhere. * Extend package.config inside azure cvm builds * Drop linux-azure-fde* source kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
I'm not too sure if updates from sed1991s above are correct -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: Fix Released Status in systemd source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in systemd source package in Jammy: Fix Released Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970077] Re: efivars file system missing in Ubuntu 22.04 real-time kernel
** Description changed: In Ubuntu 22.04 generic kernel like 5.15.0-23, efivars file system is mounted and is visible in the output of mount command, however in Ubuntu 22.04 real-time kernel like 5.15.0-1005-realtime or 5.15.0-1007-realtime, efivars file system is missing. Intel SGX feature relies on efivars file system to function, could u please investigate this issue? Thanks. + + --- + + In ubuntu, multiple things rely on reliable access to efivars (read- + only) and to have ability to manipulate them too (read-write). Thus imho + we should revert the v5.15 patch that turns efivars by default; and in + later series update annotation to keep it on, even under realtime. + + Things sort of work on boot, as shim fallback app (fb*.efi) parsses, + loads and sets initial boot variables. However subsequent updates to our + bootloaders (shim, grub, nullboot, snapd) do not know if they are set, + if they are correct, or if they can be used. Functionality that is + missing on such systems is then thus inability to install fw updates + with fwupd, inatibility to boot into firmware setup (systemctl reboot + --firmware-setup), and inability to predict measurements to predict + sealing policies with new updates in case of TPM based sealed secrets + (i.e. UC based FDE, systemd based secrets, SGX, etc). + + I will use this bug report to address this by default. Users that are + concerned about userspace/OS accessing and using efivars during + maintainance operations (package upgrades) or during runtime otherwise + (arbitrary calls to bootctl for example), should consider getting + hardware that has realtime aware EFI implementation, or modify their + classic or core systems to disable efi runtime services by opting-out of + efivars. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970077 Title: efivars file system missing in Ubuntu 22.04 real-time kernel Status in ubuntu-realtime: Triaged Status in linux package in Ubuntu: New Bug description: In Ubuntu 22.04 generic kernel like 5.15.0-23, efivars file system is mounted and is visible in the output of mount command, however in Ubuntu 22.04 real-time kernel like 5.15.0-1005-realtime or 5.15.0-1007-realtime, efivars file system is missing. Intel SGX feature relies on efivars file system to function, could u please investigate this issue? Thanks. --- In ubuntu, multiple things rely on reliable access to efivars (read- only) and to have ability to manipulate them too (read-write). Thus imho we should revert the v5.15 patch that turns efivars by default; and in later series update annotation to keep it on, even under realtime. Things sort of work on boot, as shim fallback app (fb*.efi) parsses, loads and sets initial boot variables. However subsequent updates to our bootloaders (shim, grub, nullboot, snapd) do not know if they are set, if they are correct, or if they can be used. Functionality that is missing on such systems is then thus inability to install fw updates with fwupd, inatibility to boot into firmware setup (systemctl reboot --firmware-setup), and inability to predict measurements to predict sealing policies with new updates in case of TPM based sealed secrets (i.e. UC based FDE, systemd based secrets, SGX, etc). I will use this bug report to address this by default. Users that are concerned about userspace/OS accessing and using efivars during maintainance operations (package upgrades) or during runtime otherwise (arbitrary calls to bootctl for example), should consider getting hardware that has realtime aware EFI implementation, or modify their classic or core systems to disable efi runtime services by opting-out of efivars. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-realtime/+bug/1970077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017658] [NEW] FDE v5.19 edge variant meta packages are incorrectly named
Public bug reported: FDE v5.19 edge variant meta packages are incorrectly named they should just be named `linux-azure-fde-edge`, not `linux-azure- fde-5.19-edge`. ** Affects: linux-meta-azure-fde-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-azure-fde-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017658 Title: FDE v5.19 edge variant meta packages are incorrectly named Status in linux-meta-azure-fde-5.19 package in Ubuntu: New Bug description: FDE v5.19 edge variant meta packages are incorrectly named they should just be named `linux-azure-fde-edge`, not `linux-azure- fde-5.19-edge`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-azure-fde-5.19/+bug/2017658/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994516] Re: Kernels after 5.16 cannot execute x32-ABI binaries
Hi Sven & doko, Nice to hear from you Sven again, you always pop-up on x32 kernel mailing lists threads, great to hear you use Ubuntu. Debian also has ports that provide x32 binaries, whereas Ubuntu doesn't. We did do preliminary work to enable x32 over sixteen years ago in gutsy, but since then no demand has materialised to actually ever support this. It is probably a mistake and oversight that we have kept this config option on for so long; and continue to have portions of toolchain available too (triarch). From the investigations I did, it appears this config was dropped as part of the kernel config review, when a few other obsolete execution formats were dropped. Note that no ubuntu certification, tooling, or assertions enforce or test x32 binaries on ubuntu kernels, and imho shouldn't gonig forward. I spoke to a few people about this, and consenus infofar is this opens an attack vector even when simply complied in and not enabled at runtime. Other distributions also do not have this on (fedora, suse). I will use this bug report, to document that x32 should be off and not turned back on. If you use 22.04 LTS you can use linux-generic (v5.15) based kernel, which will continue to have existing config as is. Or alternatively you can build your own kernel, or use Debian one. ** Tags removed: rls-kk-incoming rls-ll-incoming ** Tags added: rls-kk-notfixing rls-ll-notfixing ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/1994516 Title: Kernels after 5.16 cannot execute x32-ABI binaries Status in linux package in Ubuntu: Won't Fix Bug description: The kernel configuration option CONFIG_X86_X32_ABI is outcommented for kernel 5.17 and higher (amd64). x32 binaries are now reporting: cannot execute binary file: Exec format error The x32-ABI has its proven merits in some HPC tasks (e.g. link and GC intensive tasks) because it saves CPU time and critical resources like energy. So, the following approach (e.g. Debian) looks more appropriate: 1. Include the x32-relevant code, but disable its use on standard boots: CONFIG_X86_X32=y CONFIG_X86_X32_DISABLED=y 2. Users that must run x32 binaries can easily add the GRUB cmdline option syscall.x32=y to enable x32 binaries. This could be a good compromise between kernel complexity and resource efficiency. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-10-24 (1 days ago) InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=b71ed1bd-e82f-41cb-b6dd-a7805136105f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 RfKill: Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: False dmi.bios.date: 10/13/2022 dmi.bios.release: 8.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: Default string dmi.board.name: PRIME B650-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd10/13/2022:br8.5:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB650-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 2017571] [NEW] Combine azure & azure-fde packages
Public bug reported: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2017571 Title: Combine azure & azure-fde packages Status in linux package in Ubuntu: Incomplete Bug description: Combine azure & azure-fde packages We can generate signed vmlinuz and kernel.efi from the same build. Thus use the same build for both. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Note despite the hwe-5.15 obviously picking up all the code changes in the kernel, this feature will not work in hwe-5.15 in focal, due to lack of toolchain support. Thus this is a no-op in focal. ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Released Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
vmlinuz-6.2.0-18-generic is good, so regression introduced in 6.2.0-19
abi, suspecting new apparmor stack
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012136
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in AppArmor:
New
Status in MAAS:
Triaged
Status in maas-images:
Invalid
Status in apparmor package in Ubuntu:
New
Status in linux package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/2016908/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
alexsander-souza - if you can make this on per-distro basis that would
be great. Indeed empty (thus apparmor=1) should work on jammy and up,
but yes we can never know. And having it for lunar onwards would be
super nice, because yes overlayfs apparmor things got fixed a while back
and are expected to work from now on. And there are more and more things
that rely on apparmor to be there.
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in MAAS:
Triaged
Status in maas-images:
Invalid
Status in linux package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/2016908/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
Lunar kernel will need SRU to be fixed up.
And separately, we could check if we can get rid of apparmor=0 for all
supported releases or not, in next mass release.
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in MAAS:
Triaged
Status in maas-images:
Invalid
Status in linux package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/2016908/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: udev fails to make prctl() syscall with apparmor=0 (as used by maas by default)
Now about those bugs, it is true that apparmor and overlayfs used to not
play along.
Depending on support matrix we can attempt to turn apparmor back on.
Equally it is buggy that Ubuntu kernel does not work with apparmor
turned off.
It would be nice to investigate if we can at least enable apparmor for
some target series.
--
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/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
Status in MAAS:
Triaged
Status in maas-images:
Invalid
Status in linux package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Invalid
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) udevadm info --export-db
Failed to set death signal: Invalid argument
Observe that udevadm fails to setup death signal, with in systemd code
is this
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
util.c#L1252
if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
log_full_errno(prio, errno, "Failed to set death
signal: %m");
_exit(EXIT_FAILURE);
}
workaround set kernel commandline to `apparmor=1`
MAAS bug
Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/2016908/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016908] Re: Unable to deploy hosts with lunar images after 20230319 - fails to connect and download squashfs
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
+ Still gathering logs and info and will update as I go.
- Still gathering logs and info and will update as I go.
+
+
+ Kernel Bug / Apparmor
+ reproducer
+
+ $ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
+ $ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
+ $ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
+
+
+ #start the VM
+
+ Starting systemd-udevd version 252.5-2ubuntu3
+ Spawning shell within the initramfs
+
+
+ BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1) built-in shell (ash)
+ Enter 'help' for a list of built-in commands.
+
+ (initramfs) udevadm info --export-db
+ Failed to set death signal: Invalid argument
+
+ Observe that udevadm fails to setup death signal, with in systemd code
+ is this
+
+
https://github.com/systemd/systemd/blob/08c2f9c626e0f0052d505b1b7e52f335c0fbfa1d/src/basic/process-
+ util.c#L1252
+
+ if (flags & (FORK_DEATHSIG|FORK_DEATHSIG_SIGINT))
+ if (prctl(PR_SET_PDEATHSIG, (flags & FORK_DEATHSIG_SIGINT) ?
SIGINT : SIGTERM) < 0) {
+ log_full_errno(prio, errno, "Failed to set death
signal: %m");
+ _exit(EXIT_FAILURE);
+ }
+
+
+
+ MAAS bug
+ Why is maas setting `apparmor=0` ? Ubuntu shouldn't be used without apparmor.
Even for deployment and commisioning.
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: maas-images
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Also affects: maas
Importance: Undecided
Status: New
** Summary changed:
- Unable to deploy hosts with lunar images after 20230319 - fails to connect
and download squashfs
+ udev fails to make prctl() syscall with apparmor=0 (as used by maas by
default)
** Description changed:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which I
don't believe was part of the 20230319 serial. I don't have access to
the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
-
Kernel Bug / Apparmor
reproducer
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-kernel
$ wget
https://images.maas.io/ephemeral-v3/candidate/lunar/amd64/20230419/ga-23.04/generic/boot-initrd
$ qemu-system-x86_64 -nographic -m 2G -kernel ./boot-kernel -initrd
./boot-initrd -append 'console=ttyS0 break=modules apparmor=0'
-
#start the VM
Starting systemd-udevd version 252.5-2ubuntu3
Spawning shell within the initramfs
-
BusyBox v1.35.0 (Ubuntu 1:1.35.0-4ubuntu1)
[Kernel-packages] [Bug 2016908] Re: Unable to deploy hosts with lunar images after 20230319 - fails to connect and download squashfs
horay i managed to reproduce it locally. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016908 Title: Unable to deploy hosts with lunar images after 20230319 - fails to connect and download squashfs Status in maas-images: Incomplete Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I'm assuming the image being used for these deploys is 20230417 or 20230417.1 based on the fact that I saw a 6.2 kernel being used which I don't believe was part of the 20230319 serial. I don't have access to the maas server, so I can't directly check any log files. MAAS Version: 3.3.2 Here's where the serial log indicates it can't download the squashfs. The full log is attached as scobee-lunar-no-squashfs.log (there are some other console message intermixed): no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf /run/net6 -*.conf :: root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity =yes shfs :: mount_squash downloading http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0 4/lunar/candidate/squashfs to /root.tmp.img Connecting to 10.229.32.21:5248 (10.229.32.21:5248) wget: can't connect to remote host (10.229.32.21): Network is unreachable :: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp' mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory done. Still gathering logs and info and will update as I go. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/2016908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016888] [NEW] Split firmware into separate package
Public bug reported: Split firmware into separate package * Currently gsp.bin is shipped by nvidia-kernel-common that pulls in userspace dependencies and is required to match a particular driver * This prevents co-installing LRM of different nvidia upstream releases from different kernels, entangles them together for migration, and makes it difficult to vendor LRM/drivers alone in the kernel snaps without any userspace components. * To address some or all of the above things we need to split gsp.bin firmware into version specific package names, whilst keeping the dependency on the new nvidia-firmware-#FLAVOUR#-#VERSION#. Then once all dkms & lrms gain direct dependency on the nvidia- firmware-#FLAVOUR#-#VERSION# we will be able to consider relaxing or dropping dkms/lrm dependency on nvidia-kernel-common * Even if we don't relax/drop the nvidia-kernel-common dependency down the line these changes will enable easier packaging of kernel snaps, and may allow in the future an easier reuse of gsp.bin by the open source driver. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2016888 Title: Split firmware into separate package Status in linux-restricted-modules package in Ubuntu: New Bug description: Split firmware into separate package * Currently gsp.bin is shipped by nvidia-kernel-common that pulls in userspace dependencies and is required to match a particular driver * This prevents co-installing LRM of different nvidia upstream releases from different kernels, entangles them together for migration, and makes it difficult to vendor LRM/drivers alone in the kernel snaps without any userspace components. * To address some or all of the above things we need to split gsp.bin firmware into version specific package names, whilst keeping the dependency on the new nvidia-firmware-#FLAVOUR#-#VERSION#. Then once all dkms & lrms gain direct dependency on the nvidia- firmware-#FLAVOUR#-#VERSION# we will be able to consider relaxing or dropping dkms/lrm dependency on nvidia-kernel-common * Even if we don't relax/drop the nvidia-kernel-common dependency down the line these changes will enable easier packaging of kernel snaps, and may allow in the future an easier reuse of gsp.bin by the open source driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2016888/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Note livepatches can only start with the next abi specifically https://bugs.launchpad.net/kernel-sru-workflow/+bug/2016820 jammy/linux: 5.15.0-71.78 it started building already, and will undergo testing soon. -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Released Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Released Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Tags added: regression-release
--
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/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in Release Notes for Ubuntu:
New
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Triaged
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Yes, it is expected for you / Nvidia to update this patch if there is no
other solution.
Please provide patch for v6.2 for lunar & vanilla kernel latest RC.
Ideally also submit it upstream, such that a solution acceptable
upstream is eventually found.
This patch will need to go through acks, and integrated into an SRU
cycles once available. Initial lunar kernel for GA has frozen weeks ago.
So this will land in SRU cycle when next possible (April/may). Thus for
a while 23.04 will have this regression.
I will separately check which rebase dropped this patch and how come
notification about it did not get communicate prior to being identified
and escalated to me just today. I do apologise about it.
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Lunar)
Milestone: None => lunar-updates
--
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/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in linux package in Ubuntu:
Triaged
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Triaged
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
@Tarun Gupta
Is
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=e605d68b8accf43430144999e8206dd8511d135f
still needed in v6.2 kernel. It no longer applies, and there has been a lot of
work by @nvidia.com people on the driver in question (nicolinc kwankhede jgg)
--
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/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Incomplete
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Lunar)
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Kinetic)
** No longer affects: linux-meta-hwe-5.19 (Ubuntu Jammy)
** No longer affects: linux-meta-hwe-5.19 (Ubuntu)
** Changed in: linux-hwe-5.19 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-hwe-5.19 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-hwe-5.19 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Incomplete
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988806] Re: Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
it's incorrect to file bugs againt `linux-meta` bugs like these should
be filed against `linux` itself.
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Kinetic)
Status: New => Fix Released
** Also affects: linux-meta-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-meta-hwe-5.19 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-meta-hwe-5.19 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-meta-hwe-5.19 (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1988806
Title:
Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Incomplete
Status in linux-hwe-5.19 source package in Lunar:
Invalid
Bug description:
With below commit in 5.16 upstream kernel, support for
mdev_set_iommu_device() kABI was removed from kernel as there were no
in-tree drivers making use of the kABI.
fda49d97f2c4 ("vfio: remove the unused mdev iommu hook")
This kABI is used by SRIOV based Nvidia vGPU on Ubuntu 22.04. Ampere+
(SRIOV based) Nvidia vGPU use kernel's mdev framework and use this
kABI to pin all guest memory during VM boot.
As HWE kernel (for Ubuntu 22.04) will switch to 5.19 upstream kernel,
it will not include this kABI and as a result will break SRIOV based
Nvidia vGPU. So, filing this bug to request to have a custom patch in
HWE kernel which doesn't remove the support for
mdev_set_iommu_device() kABI.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
are you sure the dkms module is still needed with the v6.2 kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015361] [NEW] FTBFS with different dkms or when makeflags are set
Public bug reported: build_dkms fails 1) if updated dkms is used that changes return code for skip from 9 to 77 2) if MAKEFLAGS are exported that remove implicit variables, which dkms module submake invocations may require fix those things for lunar release. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Milestone: None => ubuntu-23.04 -- 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/2015361 Title: FTBFS with different dkms or when makeflags are set Status in linux package in Ubuntu: New Bug description: build_dkms fails 1) if updated dkms is used that changes return code for skip from 9 to 77 2) if MAKEFLAGS are exported that remove implicit variables, which dkms module submake invocations may require fix those things for lunar release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015361/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015279] Re: ftbfs during kernel build due to dkms changes in lunar
** Tags removed: block-proposed-lunar ** Changed in: v4l2loopback (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: Fix Committed Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015279] Re: ftbfs during kernel build due to dkms changes in lunar
** Description changed: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS + + + -- + + dkms in jammy and lunar are incompatible with each other, prevent kernel + from using dkms during its buildtime to prebuild certain dkms modules. + Workaround it by including a fixed copy of dkms script in the kernel, as + used at build-time only to produce certain pre-built modules. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015279 Title: ftbfs during kernel build due to dkms changes in lunar Status in linux package in Ubuntu: Incomplete Status in v4l2loopback package in Ubuntu: New Bug description: ftbfs during kernel build due to dkms changes in lunar need to revert explicit use of CC= variable, which is now no longer guaranteed to be exported once again. causes src:linux to FTBFS -- dkms in jammy and lunar are incompatible with each other, prevent kernel from using dkms during its buildtime to prebuild certain dkms modules. Workaround it by including a fixed copy of dkms script in the kernel, as used at build-time only to produce certain pre-built modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008084] Re: Linux image 5.19 cuts off the build date
ah, but that will not fix -a output either, so i guess sort of moot. -- 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/2008084 Title: Linux image 5.19 cuts off the build date Status in linux package in Ubuntu: Confirmed Bug description: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008084] Re: Linux image 5.19 cuts off the build date
imho i find it weird that PREEMPT_DYNAMIC got added and printed by default in that place on all kernels. imho PREEMPT_DYNAMIC shouldn't be in the -v output. is this something we can raise upstream? -- 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/2008084 Title: Linux image 5.19 cuts off the build date Status in linux package in Ubuntu: Confirmed Bug description: Hi, The output of uname -a is failing to show the full build date on Jammy 22.04.2 with kernel 5.19 as the string is too long. I believe there is some size limit that is being overrun when building the kernel. lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy uname -v #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 uname -a Linux kianp 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux cat /proc/version Linux version 5.19.0-32-generic (buildd@lcy02-amd64-026) (x86_64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan 30 17:03:34 UTC 2 cat /proc/version_signature Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 See above, the build date is missing the year (2023). On an older kernel the output of uname -v is much shorter which leads me to believe some buffer size limit is being hit. (Older Kernel): uname -v #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2015019] Re: 23.04 Beta: Realtek 8852be WiFi driver DKMS module fails to build
Hi, 8852be/1.0.5 is not a dkms module that Ubuntu ships in the Ubuntu archive. Note that Lunar ships v6.2 kernel that contains the following module: # modinfo /lib/modules/6.2.0-19-generic/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852be.ko filename: /lib/modules/6.2.0-19-generic/kernel/drivers/net/wireless/realtek/rtw89/rtw89_8852be.ko license:Dual BSD/GPL description:Realtek 802.11ax wireless 8852BE driver author: Realtek Corporation srcversion: 87FC3D1B28540DD0400027C alias: pci:v10ECdB85Bsv*sd*bc*sc*i* alias: pci:v10ECdB852sv*sd*bc*sc*i* depends:rtw89_pci,rtw89_8852b retpoline: Y intree: Y name: rtw89_8852be are you sure you still need this dkms module? If you do, please try to find where you downloaded it from and get an updated version. As upstream Linux releases new versions, changes to dkms modules are required from time to time. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2015019 Title: 23.04 Beta: Realtek 8852be WiFi driver DKMS module fails to build Status in linux package in Ubuntu: Incomplete Bug description: I installed the 23.04 Beta but the WiFi dkms module failed to build: Setting up linux-headers-6.2.0-18-generic (6.2.0-18.18) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-18-generic Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area...(bad exit status: 2) make -j16 KERNELRELEASE=6.2.0-18-generic ENTRY=yes all...(bad exit status: 2) ERROR (dkms apport): binary package for 8852be: 1.0.5 not found Error! Bad return status for module build on kernel: 6.2.0-18-generic (x86_64) Consult /var/lib/dkms/8852be/1.0.5/build/make.log for more information. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: error processing package linux-headers-6.2.0-18-generic (--configure): installed linux-headers-6.2.0-18-generic package post-installation script subprocess returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-headers-generic: linux-headers-generic depends on linux-headers-6.2.0-18-generic; however: Package linux-headers-6.2.0-18-generic is not configured yet. dpkg: error processing package linux-headers-generic (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-headers-6.2.0-18-generic linux-headers-generic E: Sub-process /usr/bin/dpkg returned an error code (1) The make log reads as follows (/var/lib/dkms/8852be/1.0.5/build/make.log): DKMS make.log for 8852be-1.0.5 for kernel 6.2.0-18-generic (x86_64) Mon 03 Apr 2023 06:32:07 +07 make -j7 -C /lib/modules/6.2.0-18-generic/build M=/var/lib/dkms/8852be/1.0.5/build KERNELRELEASE=6.2.0-18-generic ENTRY= modules make[1]: warning: -j7 forced in submake: resetting jobserver mode. make[1]: Entering directory '/usr/src/linux-headers-6.2.0-18-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 You are using: gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0 CC [M] /var/lib/dkms/8852be/1.0.5/build/platform/platform_linux_pc_pci.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/osdep_service.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/osdep_service_linux.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/rtw_cfg.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/os_intfs.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/ioctl_linux.o CC [M] /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/xmit_linux.o /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/os_intfs.c: In function ‘rtw_ndev_init’: /var/lib/dkms/8852be/1.0.5/build/os_dep/linux/os_intfs.c:294:9: error: too many arguments to function ‘netif_napi_add’ 294 | netif_napi_add(dev, >napi, rtw_recv_napi_poll, RTL_NAPI_WEIGHT); | ^~ In file included from /var/lib/dkms/8852be/1.0.5/build/include/osdep_service_linux.h:31, from /var/lib/dkms/8852be/1.0.5/build/include/osdep_service.h:42, from /var/lib/dkms/8852be/1.0.5/build/include/drv_types.h:31,
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
@ahasenack in lunar wireguard dropped depends on neither. Because it is expected to be built in, and the wireguard-dkms module is out of date, like a lot. Please discuss this further with the SRU team on https://bugs.launchpad.net/ubuntu/kinetic/+source/wireguard/+bug/2008086 as kernel's team position is that nobody should be using wireguard-dkms in jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013209] Re: expoline.o is packaged unconditionally for s390x
In an ideal world, this would be actually done by upstream Linux makefiles, i.e. they would have conditional hook to install that file, and add it as a dep on an appropriate install target (i.e. install- headers or whatnot). As all distributions so far manually create snippets like we did as well, to install this file in their packages. Similarly other bits like these installed manually. -- 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/2013209 Title: expoline.o is packaged unconditionally for s390x Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress Bug description: https://bugs.launchpad.net/bugs/1639924 enabled CONFIG_EXPOLINE_EXTERN for s390x in Jammy. While this works as expected on Jammy, it won't work on some derivatives of it: for example focal:hwe-5.15. On Focal, this config can't be enabled due to the GCC version it comes with. CONFIG_EXPOLINE_EXTERN requires >= 110200 while Focal comes with 90400. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685291] Re: RFC: virtio and virtio-scsi should be built in
Marking CONFIG_SCSI_VIRTIO=y enables initrd-less boot on generic kernel, enabling any Ubuntu installation to be lifted from any hardware and converted into a VM which will, even with corrupted initrd and missing modules, be able to boot by default. This is an extremly useful property to have on all ubuntu kernels. Separately, this also removes the need for linux-kvm kernel flavour, as all the changes it has are now incorporated into generic flavour & cloud-images. -- 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/1685291 Title: RFC: virtio and virtio-scsi should be built in Status in linux package in Ubuntu: Triaged Bug description: Hi, I was trying to verify bug 1677376 yesterday, and came to find out that our kernel does not have virtio or virtio-scsi builtin drivers. This generally has not been a problem as initramfs has been used. However, as there is recently an interest in booting without initramfs it would seem to make sense to have popular drivers builtin to -generic to allow that. Also, from a priority perspective, if we're going to have any block devices builtin to the -generic kernel, then i'd think that virtio and virtio-scsi would make more sense than an IDE driver. I understand there are tradeoffs involved. Related bugs: * bug 1677376: growing partitions does not work when booted without initramfs ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: User Name 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 20:07 seq crw-rw 1 root audio 116, 33 Apr 19 20:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Thu Apr 20 19:37:23 2017 Ec2AMI: ami-0019 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.1-1ubuntu1~cloud0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-zesty dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.1-1ubuntu1~cloud0:bd04/01/2014:svnOpenStackFoundation:pnOpenStackNova:pvr15.0.2:cvnQEMU:ct1:cvrpc-i440fx-zesty: dmi.product.name: OpenStack Nova dmi.product.version: 15.0.2 dmi.sys.vendor: OpenStack Foundation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
@Steve These packages only exist in focal. components-missmatches report is for devel only. in devel, there is a binary package pattern to automatically seed all kernels, as in practice we don't have almost any non-main kernels. I can add these package to focal seeds, but it will not actually make this package appear in the components missmatches. But also nothing will cause it to be downgraded. Please promote these focal-only packages, to main, in focal only. ** Changed in: linux-meta-xilinx-zynqmp (Ubuntu) Status: Incomplete => Triaged ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Triaged Status in linux-xilinx-zynqmp package in Ubuntu: Triaged Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1964992] Re: ZFS ignores ARC sizes below allmem/32
Editing 0.8.3-1ubuntu12.14 changelog seems inappropriate. Whoever is sponsoring this debdiff, should drop that hung, as long as it doesn't have any other mistakes. -- 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/1964992 Title: ZFS ignores ARC sizes below allmem/32 Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: In Progress Bug description: [Impact] ZFS ignores tunable "zfs_arc_max" due to it being below allmem/32 threshold. This prevents users from properly restraining ARC sizes, and can cause increased memory contention in some systems. [Test Plan] 1. Deploy test system with ZFS storage and 32GB RAM 2. Add ARC tunables to /etc/modprobe.d/99-zfs-arc.conf # cat /etc/modprobe.d/99-zfs-arc.conf options zfs zfs_arc_min=536870912 options zfs zfs_arc_max=966367641 3. Reboot system 4. Verify ARC sizes through "arc_summary" # arc_summary | grep -A3 "ARC size" ARC size (current): < 0.1 %1.3 MiB Target size (adaptive): 100.0 % 15.7 GiB Min size (hard limit): 3.2 % 512.0 MiB Max size (high water): 31:1 15.7 GiB For a 32GB test system, we should be able to set max ARC sizes below 1GB. [Fix] This has been fixed by upstream commit: - 36a6e2335c45 "Don't ignore zfs_arc_max below allmem/32" - e945e8d7f4fc "Restore FreeBSD sysctl processing for arc.min and arc.max" The commit has been introduced in upstream zfs-2.0.0, so it's needed for Bionic and Focal. Releases starting with Impish already have this commit by default: $ git describe --contains 36a6e2335c45 zfs-2.0.0-rc1~332 $ rmadison zfs-linux zfs-linux | 0.7.5-1ubuntu15| bionic | source zfs-linux | 0.7.5-1ubuntu16.12 | bionic-updates | source zfs-linux | 0.8.3-1ubuntu12| focal | source zfs-linux | 0.8.3-1ubuntu12.9 | focal-security | source zfs-linux | 0.8.3-1ubuntu12.13 | focal-updates | source zfs-linux | 0.8.3-1ubuntu12.14 | focal-proposed | source zfs-linux | 2.0.6-1ubuntu2 | impish | source zfs-linux | 2.0.6-1ubuntu2.1 | impish-updates | source zfs-linux | 2.1.2-1ubuntu3 | jammy | source [Regression Potential] The introduced commit essentially removes the limitation of setting ARC tunables below allmem/32, and re-arranges the order of how some of the tunables are parsed. Regressions would possibly show up as other tunables being ignored or not being set correctly due to parsing errors. We should validate whether other ARC related tunables are still being set correctly, and whether ZFS is using the set values for the ARC memory thresholds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009283] Re: linux: CONFIG_SERIAL_8250_MID=y
I understand that having it in the root filesystem is too late. However, I would have thought it would be good enough to have it early in the initrd, or do you also require output prior to initrd starting? having it built-in trades wasting RAM for all billions of Ubuntu instances, and the module in question is large. -- 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/2009283 Title: linux: CONFIG_SERIAL_8250_MID=y Status in linux package in Ubuntu: Incomplete Bug description: Starting from 5.19 HWE kernel, this option became as dedicated module instead of being compiled into the kernel. 5.19 hwe-next also has CONFIG_SERIAL_8250_MID=m On 5.15 it was OK ~$ uname -r 5.19.0-32-generic $ cat /boot/config-5.19.0-32-generic | grep 8250_MID CONFIG_SERIAL_8250_MID=m Please make it CONFIG_SERIAL_8250_MID=y for all the future kernels. Previous ticket: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967338 Some discussion: https://lists.ubuntu.com/archives/kernel-team/2022-March/128690.html Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009283/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008142] Re: bcmwl driver not installed
With secureboot, the live session install of that module should trigger installer questions w.r.t. MOK key enrollment. Post installer reboot, should trigger MOK interface to complete the mok key enrollment prior to OS loading. Once OS is loaded, the driver should work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: New Status in broadcom-sta package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in broadcom-sta source package in Lunar: New Status in subiquity source package in Lunar: New Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
** Tags removed: verification-needed-bionic verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-bionic verification-done-focal verification-done-jammy verification-done-kinetic ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008672] Re: focal linux-xilinx-zynqmp promote from universe to main
Status needs to be set to triaged, and ~ubuntu-archive team needs to be subscribed. These two things will get this bug into a queue for them to process. Also related packages need to be marked as affected too. I.e. meta ** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: New => Triaged ** Also affects: linux-meta-xilinx-zynqmp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-xilinx-zynqmp (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2008672 Title: focal linux-xilinx-zynqmp promote from universe to main Status in linux-meta-xilinx-zynqmp package in Ubuntu: Triaged Status in linux-xilinx-zynqmp package in Ubuntu: Triaged Bug description: focal linux-xilinx-zynqmp promote from universe to main new kernel published in the wrong component. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-xilinx-zynqmp/+bug/2008672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008523] [NEW] Make kexec work by default on secureboot systems
Public bug reported: Make kexec work by default on secureboot systems Lots of people are confused by kexec failing on secureboot systems, without realising that on Ubuntu one needs to use the option to use a modern syscall that works on secureboot systems since like forever. Let's make the mode that works the default one. ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: Fix Committed ** Changed in: kexec-tools (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2008523 Title: Make kexec work by default on secureboot systems Status in kexec-tools package in Ubuntu: Fix Committed Bug description: Make kexec work by default on secureboot systems Lots of people are confused by kexec failing on secureboot systems, without realising that on Ubuntu one needs to use the option to use a modern syscall that works on secureboot systems since like forever. Let's make the mode that works the default one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/2008523/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008434] Re: NBS cleanup required in lunar-proposed
Specifically version 390.157-0ubuntu2 needs to be removed on i386 and armhf -- 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/2008434 Title: NBS cleanup required in lunar-proposed Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2008434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008434] [NEW] NBS cleanup required in lunar-proposed
Public bug reported: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: Triaged ** Tags: update-excuse -- 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/2008434 Title: NBS cleanup required in lunar-proposed Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: NBS cleanup in lunar-proposed on i386 and armhf old binaries left on i386: libcuda1-384, libnvidia-cfg1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) missing build on armhf: libcuda1-384, libnvidia-cfg1-390, libnvidia-compute-390, libnvidia-fbc1-390, libnvidia-gl-390, libnvidia-ifr1-390, nvidia-384, nvidia-384-dev, nvidia-compute-utils-390, nvidia-dkms-390, nvidia-driver-390, nvidia-headless-390, nvidia-headless-no-dkms-390, nvidia-kernel-common-390, nvidia-kernel-source-390, nvidia-utils-390, xserver-xorg-video-nvidia-390 (from 390.157-0ubuntu2) arch:armhf not built yet, autopkgtest delayed there please remove these binaries, as they will no longer be built on 32bit arches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2008434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008269] Re: dkms prevents installing vendored-in dkms packages
** Tags added: lunar regression-release ** Changed in: dkms (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2008269 Title: dkms prevents installing vendored-in dkms packages Status in dkms package in Ubuntu: Fix Committed Bug description: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008269] [NEW] dkms prevents installing vendored-in dkms packages
Public bug reported: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. ** Affects: dkms (Ubuntu) Importance: Critical Status: Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2008269 Title: dkms prevents installing vendored-in dkms packages Status in dkms package in Ubuntu: Triaged Bug description: [ Impact ] * In kinetic, installing kernel which vendors a dkms module from the archive allows to still install the same dkms module from the archive, in an inactive package: $ sudo apt install linux-virtual zfs-dkms ... zstd.ko: Running module version sanity check. Error! Module version 1.4.5a-2.1.5-1ubuntu6 for zzstd.ko is not newer than what is already found in kernel 5.19.0-35-generic (1.4.5a-2.1.5-1ubuntu6). You may override by specifying --force. depmod... Processing triggers for libc-bin (2.36-0ubuntu2) ... $ echo $? 0 $ sudo dkms status zfs/2.1.5, 5.19.0-35-generic, x86_64: installed (WARNING! Diff between built and installed module!) If the user wishes to use dkms built module for whatever reason, one can then call dkms install --force after apt completes. Whereas in lunar, such apt installation fails, resulting in broken apt packages, and inability to specify `dkms install --force` zzstd.ko: Running module version sanity check. Module version 1.4.5a-2.1.7-1ubuntu1 for zzstd.ko exactly matches what is already found in kernel 6.1.0-14-generic. DKMS will not replace this module. You may override by specifying --force. Error! Installation aborted. dpkg: error processing package zfs-dkms (--configure): installed zfs-dkms package post-installation script subprocess returned error exit status 6 Processing triggers for libc-bin (2.36-0ubuntu4) ... Errors were encountered while processing: zfs-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) This breaks existing Ubuntu workflows that allow keeping dkms module installed, and get it upgraded on older kernel abis, if and when desired. [ Test Plan ] * Install zfs-dkms and linux-virtual that vendors the identical version zfs-dkms [ Where problems could occur ] * This looks like upstream regression [ Other Info ] * this is making kernels unmigratable in lunar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2008269/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008268] [NEW] Check abi compatiblity between Lunar and Jammy
Public bug reported: Check abi compatiblity between Lunar and Jammy ** Affects: zfs-linux (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Changed in: zfs-linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: zfs-linux (Ubuntu) Milestone: None => ubuntu-23.04-beta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2008268 Title: Check abi compatiblity between Lunar and Jammy Status in zfs-linux package in Ubuntu: New Bug description: Check abi compatiblity between Lunar and Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992513] Re: apt will not install nvidia-driver-470-server if nvidia-driver-450-server is installed and out of date
One should use ubuntu-drivers CLI or Additional Drivers GUI to install or switch nvidia graphics stacks from one major series to another. It ensures that correct matching pre-signed kernel drivers are installed together with the right userspace (with and without gui stacks, as needed). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1992513 Title: apt will not install nvidia-driver-470-server if nvidia- driver-450-server is installed and out of date Status in apt package in Ubuntu: Triaged Status in nvidia-graphics-drivers-450-server package in Ubuntu: New Status in nvidia-graphics-drivers-470-server package in Ubuntu: New Bug description: apt/jammy apt will refuse to install nvidia-driver-470-server if nvidia-driver-450-server is installed *and* out of date. I can reproduce this by disabling all but the jammy release pocket, installing the old n-d-450-s from there, and then enabling updates and trying to install n-v-470-s (where a new n-d-450-s is available): # libnvidia-gl-450-server has an update available root@dannf-apt-jammy:/var/cache# apt install --dry-run libnvidia-gl-470-server -o Debug::pkgProblemResolver=yes Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libnvidia-common-450-server : Conflicts: libnvidia-common libnvidia-common-470-server : Conflicts: libnvidia-common E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1992513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006762] Re: Please let 6.1 kernel migrate
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Description changed: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta - 1) dm-writeboost broken and abandoned, scheduled for removal in debian. - Ubuntu RM bug + DONE 1) dm-writeboost broken and abandoned, scheduled for removal in + debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) thus there no respins/changes to the kernel itself needed to get it out. and all outstanding issues are patched, and are available in proposed. ** Description changed: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta DONE 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) + 5) new LRM landed + new signing key, respin all LRMs? + thus there no respins/changes to the kernel itself needed to get it out. and all outstanding issues are patched, and are available in proposed. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- 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/2006762 Title: Please let 6.1 kernel migrate Status in linux package in Ubuntu: Triaged Bug description: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta DONE 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) 5) new LRM landed + new signing key, respin all LRMs? thus there no respins/changes to the kernel itself needed to get it out. and all outstanding issues are patched, and are available in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983297] Re: Additional fix for TGL + AUO panel flickering
Kai, open opening this bug report the devel series task at the time (kinetic) it was marked as fix-released => meaning it's not needed on v5.19+ kernels. But it seems, now, we do need this fix (or equivalent) on v5.19+ kernels right? Opening kinetic & lunar tasks to investigate. ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Fix Released ** Also affects: linux-oem-5.14 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Changed in: linux (Ubuntu Lunar) Status: Fix Released => New ** No longer affects: linux-oem-5.14 (Ubuntu Kinetic) ** No longer affects: linux-oem-5.14 (Ubuntu Lunar) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux source package in Kinetic: New Status in linux source package in Lunar: New Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007399] [NEW] RM linux-bluefield from jammy-proposed, shipped in a PPA instead
Public bug reported: RM linux-bluefield from jammy-proposed, shipped in PPA instead Please RM linux-bluefield kernel from jammy-proposed shipped in the ppa instead for now. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-meta-bluefield (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-bluefield (Ubuntu) Importance: Undecided Status: Triaged ** Also affects: linux-meta-bluefield (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-bluefield (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu) Status: New => Triaged ** Changed in: linux-meta-bluefield (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-bluefield (Ubuntu) Status: New => Triaged ** Summary changed: - RM linux-bluefield from jammy-proposed, shipped in PPA instead + RM linux-bluefield from jammy-proposed, shipped in a PPA instead -- 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/2007399 Title: RM linux-bluefield from jammy-proposed, shipped in a PPA instead Status in linux-bluefield package in Ubuntu: Triaged Status in linux-meta-bluefield package in Ubuntu: Triaged Status in linux-signed-bluefield package in Ubuntu: Triaged Bug description: RM linux-bluefield from jammy-proposed, shipped in PPA instead Please RM linux-bluefield kernel from jammy-proposed shipped in the ppa instead for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2007399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
1) changed -1ubuntu1~22.04.0 to -1~ubuntu22.04.0 because -1ubuntu1~22.04.0 is higher version that is in lunar: $ dpkg --compare-versions 2.13.8-1ubuntu1~22.04.0 lt 2.13.8-1 && echo "sru version is lower than devel" || echo "sru version is HIGHER than devel" sru version is HIGHER than devel $ dpkg --compare-versions 2.13.8-1~ubuntu22.04.0 lt 2.13.8-1 && echo "sru version is lower than devel" || echo "sru version is HIGHER than devel" sru version is lower than devel we want to ensure that lunar version remains higher than the sru backport versions 2) run update-maintainer as the -1 version was synced from debian without ubuntu maintainer set 3) generated jammy changes with $ debuild -S -d -nc -v2.13.1-1 similar done for kinetic too. both sponsored. ** Changed in: lttng-modules (Ubuntu Jammy) Status: New => In Progress ** Changed in: lttng-modules (Ubuntu Kinetic) Status: New => In Progress ** No longer affects: linux (Ubuntu Bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: In Progress Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 |
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
the liveapatch service builders are ephemeral and private - as unique one is setup for every kernel abi build, with matching build- dependencies, and potentially contains embargoed security updates code. livepatches are consumed via livepatch clients, with an optional onprem server. More information on https://ubuntu.com/security/livepatch -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec'
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
The next issue that is still to resolve is around UBSAN - https://bugs.launchpad.net/ubuntu-z-systems/+bug/2003374 it appears that kpatch is currently incompatible with our kernel configuration that enables UBSAN. -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in symbol conversion 3f8e1062cc create-diff-object: support
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
kpatch was updated in lunar, and canonical-livepatch-service has a backport of that in their PPAs to build livepatches on jammy. ** Changed in: kpatch (Ubuntu Jammy) Status: Confirmed => Invalid ** Changed in: kpatch (Ubuntu Kinetic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: In Progress Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Confirmed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' bf212f7750 create-diff-object: error on unsupported rela in
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
@roxana for the new upstream version backports, the debdiff is normally provided against the version that is being backported e.g. relative 2.13.8-1 Also when doing backport / any ubuntu change, the version string must include ubuntu in it, so something like ~ubuntu22.10.0 is best. -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
$ dput ubuntu lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes D: Setting host argument. Checking signature on .changes gpg: /tmp/lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes: Valid signature from 9B8EC849D5EF70ED Checking signature on .dsc gpg: /tmp/lttng-modules_2.10.8-1ubuntu2~18.04.5.dsc: Valid signature from 9B8EC849D5EF70ED Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5.dsc: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5.debian.tar.xz: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5_source.buildinfo: done. Uploading lttng-modules_2.10.8-1ubuntu2~18.04.5_source.changes: done. Successfully uploaded packages. ** Changed in: lttng-modules (Ubuntu Bionic) Status: New => In Progress -- 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/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from
[Kernel-packages] [Bug 2004644] Re: Incompatible jbd2 format between kernel and lttng-modules
** Changed in: lttng-modules (Ubuntu) Status: Invalid => Fix Committed ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Incomplete ** Also affects: lttng-modules (Ubuntu Lunar) Importance: Undecided Status: Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2004644 Title: Incompatible jbd2 format between kernel and lttng-modules Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in lttng-modules package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in lttng-modules source package in Bionic: New Status in linux source package in Focal: Incomplete Status in lttng-modules source package in Focal: Fix Committed Status in linux source package in Jammy: Incomplete Status in lttng-modules source package in Jammy: New Status in linux source package in Kinetic: Incomplete Status in lttng-modules source package in Kinetic: New Status in linux source package in Lunar: Incomplete Status in lttng-modules source package in Lunar: Fix Committed Bug description: [SRU Justification] Impact: Upstream stable added a change in the format of jbd2 in 5.4.229, 5.15.87, 6.1.3. This is incompatible with the current changes in the lttng-module for bionic-5.4 backports, focal, jammy, and kinetic. Focal and bionic updates are needed for the current sru kernel release (2023.01.30). Both adt and rt fail during compilation of the module. Jammy and kinetic updates are not needed for this cycle because patches from upstream stable are not applied yet but it will be needed for the next release(s). Correct changes are already in lttng-modules:master and in 2.13.8-1 version. Fix(es): 1. focal and bionic: Picking 4 patches from upstream lttng-modules which handle the changed interface as well as add the required code to enable that change for other versions as well: LTTNG_KERNEL_RANGE(5,4,229, 5,5,0) LTTNG_KERNEL_RANGE(5,10,163, 5,11,0) LTTNG_KERNEL_RANGE(5,15,87, 5,16,0) LTTNG_KERNEL_RANGE(6,0,18, 6,1,0) LTTNG_KERNEL_RANGE(6,1,4, 6,2,0) 2. Jammy and kinetic: backport 2.13.8-1 Tescase(s) for focal: 1. lttng-smoke-test fail to compile with the error from below. 2. adt lttng-module fail to compile with same error Regression potential: We may notice new failures in ubuntu_lttng_smoke_test once this will compile and run. But it was tested locally and results were good, so probablity is very very low. 760 21:14:39 DEBUG| [stdout] In file included from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/define_trace.h:87, 761 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:177, 762 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:29: 763 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:131:6: error: conflicting types for ‘trace_jbd2_run_stats’ 764 21:14:39 DEBUG| [stdout] 131 | void trace_##_name(_proto); 765 21:14:39 DEBUG| [stdout] | ^~ 766 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:43:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP’ 767 21:14:39 DEBUG| [stdout] 43 | LTTNG_TRACEPOINT_EVENT_INSTANCE_MAP(map, name, map, PARAMS(proto), PARAMS(args)) 768 21:14:39 DEBUG| [stdout] | ^~~ 769 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../probes/lttng-tracepoint-event-impl.h:85:2: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT_MAP’ 770 21:14:39 DEBUG| [stdout] 85 | LTTNG_TRACEPOINT_EVENT_MAP(name, name, \ 771 21:14:39 DEBUG| [stdout] | ^~ 772 21:14:39 DEBUG| [stdout] /var/lib/dkms/lttng-modules/2.12.5/build/probes/../instrumentation/events/lttng-module/jbd2.h:104:1: note: in expansion of macro ‘LTTNG_TRACEPOINT_EVENT’ 773 21:14:39 DEBUG| [stdout] 104 | LTTNG_TRACEPOINT_EVENT(jbd2_run_stats, 774 21:14:39 DEBUG| [stdout] | ^~ 775 21:14:39 DEBUG| [stdout] In file included from ./include/trace/events/jbd2.h:9, 776 21:14:39 DEBUG| [stdout] from /var/lib/dkms/lttng-modules/2.12.5/build/probes/lttng-probe-jbd2.c:18: 777 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:243:21: note: previous definition of ‘trace_jbd2_run_stats’ was here 778 21:14:39 DEBUG| [stdout] 243 | static inline void trace_##name(proto) \ 779 21:14:39 DEBUG| [stdout] | ^~ 780 21:14:39 DEBUG| [stdout] ./include/linux/tracepoint.h:406:2: note: in expansion of macro
[Kernel-packages] [Bug 1980484] Re: temporarily disable CONFIG_X86_KERNEL_IBT
** Tags removed: verification-needed ** Tags added: verification-done -- 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/1980484 Title: temporarily disable CONFIG_X86_KERNEL_IBT Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in v4l2loopback source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in v4l2loopback source package in Kinetic: Fix Released Bug description: Enabling IBT in the kernel is going to be problematic at the moment, because dkms' that have a precompiled binary need to be linked against non-IBT kernels and IBT kernels (see nvidia drivers for example). For this reason it's safer to keep IBT disabled at the moment, until all the kernels will have IBT enabled and the kernel modules / binaries will use the proper flags to generate IBT-compliant binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1980484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
v4l2loopback tested 0.12.7-2ubuntu2~22.04.1 to build on ga & hwe kernels in jammy. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: New Bug description: tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. * Some DKMS modules need further fixes to preserve and not loose the compiler setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1991664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy ** Description changed: + + tl; dr + + this has proven to be a bit futile, and instead we went ahead with + changing the default kernel makefiles to default to the correct + toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy + for now. + + So the things described here are not strictly even needed in jammy for + now. + + [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross- toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for example zfs-linux dkms. It should pass. * Attempt to build dkms modules against v5.15 kernel and v5.19 kernel from proposed. dkms module should be built with gcc and gcc-12 respectively. [ Where problems could occur ] * New gcc-12 dependency on the dkms package may result in two compilers being installed in the Ubuntu Desktop Live image * New gcc-12 dependency may prevent automatic upgrade/installation of the dkms package update via unattended upgrades. [ Other Info ] * It is questionable for dkms to depend on any c-compiler, given that a module for a given kernel can really be built with the same toolchain and the same compiler features. * In debian, linux kernel packages ship and extra configuration file in the kernel headers, dkms uses said configuration file to use a matching compiler, and linux-headers packages depend on the toolchain used to build a given kernel. Maybe in the future Ubuntu could consider using the same packaging. - * Some DKMS modules need further fixes to preserve and not loose the + * Some DKMS modules need further fixes to preserve and not loose the compiler setting -- 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/1991664 Title: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Released Status in ipu6-drivers package in Ubuntu: New Status in ivsc-driver package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in v4l2loopback package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: New Status in dkms source package in Jammy: Fix Released Status in ipu6-drivers source package in Jammy: New Status in ivsc-driver source package in Jammy: New Status in linux source package in Jammy: Incomplete Status in v4l2loopback source package in Jammy: Fix Committed Status in zfs-linux source package in Jammy: New Bug description: tl; dr this has proven to be a bit futile, and instead we went ahead with changing the default kernel makefiles to default to the correct toolchain and we have reverted hwe-5.19 kernel to use stock gcc on jammy for now. So the things described here are not strictly even needed in jammy for now. [ Impact ] * hwe-5.19 kernel has to be compiled with gcc-12+ for the new security kernel config options that have been enabled in that kernel (init zero structs). * dkms needs to be patched to attempt to use the same compiler as was used to build the kernel, specifically use gcc for v5.15 but gcc-12 for v5.19+ in jammy * dkms autopkgtests also need to be improved to ensure there are no false negatives when kernel has module under test already built-in at the same version. * because linux-headers packages in Ubuntu do not depend on a toolchain, and it is very hard to correctly depend on a native or cross-toolchain, add gcc-12 dependency in the dkms package. [ Test Plan ] * Retrigger dkms module test for a built-in package of the same version as already built into the kernel, for
[Kernel-packages] [Bug 2006762] Re: Please let 6.1 kernel migrate
** Description changed: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) - - https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#linux-signed + https://people.canonical.com/~ubuntu-archive/proposed- + migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) + + thus there no respins/changes to the kernel itself needed to get it out. + and all outstanding issues are patched, and are available in proposed. -- 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/2006762 Title: Please let 6.1 kernel migrate Status in linux package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) thus there no respins/changes to the kernel itself needed to get it out. and all outstanding issues are patched, and are available in proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006762] [NEW] Please let 6.1 kernel migrate
Public bug reported: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006762 Title: Please let 6.1 kernel migrate Status in linux package in Ubuntu: New Bug description: https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#linux-meta 1) dm-writeboost broken and abandoned, scheduled for removal in debian. Ubuntu RM bug https://bugs.launchpad.net/ubuntu/+source/writeboost/+bug/2006605 2) evdi fixed in https://launchpad.net/ubuntu/+source/evdi/1.12.0+dfsg-0.3ubuntu1 stuck in autopkgtests might migrate in a couple days 3) zfs-linux false negative fixed with new dkms, which is stuck in the huge autopkgtest queue. see https://people.canonical.com/~ubuntu- archive/proposed-migration/update_excuses.html#dkms please mark linux-meta as skiptest hint for the version 6.1.0.14.14) https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#linux-signed 4) s390x is dropped, please RM binary on the s390x missing build on s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
** Tags removed: verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006488] Re: Kill linux-kvm flavour
** Description changed: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable - -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability - wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); - setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); + -> in practice recent changes do disable the watchdog already, but do keep the sync And then we should change config to move virtio & ext4 filesystems as built in. -- 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/2006488 Title: Kill linux-kvm flavour Status in linux package in Ubuntu: Triaged Bug description: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable -> in practice recent changes do disable the watchdog already, but do keep the sync And then we should change config to move virtio & ext4 filesystems as built in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006488] Re: Kill linux-kvm flavour
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Description changed: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration - -> do this by default on paravirt machines, or potentially kvm only machines + -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age - -> do this by default on paravirt machines, or potentially kvm only machines + -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 - -> do this by default on paravirt machines, or potentially kvm only machines - + -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable - -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability - wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); - setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); + -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability + wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); + setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); And then we should change config to move virtio & ext4 filesystems as built in. -- 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/2006488 Title: Kill linux-kvm flavour Status in linux package in Ubuntu: Triaged Bug description: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); And then we should change config to move virtio & ext4 filesystems as built in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006488] [NEW] Kill linux-kvm flavour
Public bug reported: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> do this by default on paravirt machines, or potentially kvm only machines 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> do this by default on paravirt machines, or potentially kvm only machines 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> do this by default on paravirt machines, or potentially kvm only machines bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); And then we should change config to move virtio & ext4 filesystems as built in. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2006488 Title: Kill linux-kvm flavour Status in linux package in Ubuntu: New Bug description: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> do this by default on paravirt machines, or potentially kvm only machines 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> do this by default on paravirt machines, or potentially kvm only machines 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> do this by default on paravirt machines, or potentially kvm only machines bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); And then we should change config to move virtio & ext4 filesystems as built in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982776] Re: linux-modules for -kvm does not include dm-crypt
** Changed in: linux-kvm (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1982776 Title: linux-modules for -kvm does not include dm-crypt Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: New Status in linux-kvm source package in Jammy: New Bug description: I was playing with an lxc virtual machine today and attempted some use of luks. a cryptseutp open fails with strange error message: $ printf %s foobar | cryptsetup open --type=luks --key-file=- /dev/atom0/smtest_enc smtest device-mapper: reload ioctl on failed: Invalid argument $ echo $? 1 The reason is that the '-kvm' variant does not include dm-crypt.ko kernel module. That by itself doens't seem like all that crazy of a thing, but if you notice the following 4 all do have dm-crypt, -kvm seems like it should not be an outlier. linux-modules-5.15.0-1013-aws: /lib/modules/5.15.0-1013-aws/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-azure: /lib/modules/5.15.0-1013-azure/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-gcp: /lib/modules/5.15.0-1013-gcp/kernel/drivers/md/dm-crypt.ko linux-modules-5.15.0-1013-oracle: /lib/modules/5.15.0-1013-oracle/kernel/drivers/md/dm-crypt.ko ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-5.15.0-1010-kvm 5.15.0-1010.11 ProcVersionSignature: Ubuntu 5.15.0-1010.11-kvm 5.15.35 Uname: Linux 5.15.0-1010-kvm x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Jul 25 16:01:09 2022 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1982776/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004567] Re: Jammy kernel crashes on SiFive HiFive Unmatched
hm, i wonder if this is a u-boot only issue, or lack of running update- grub. the preinstalled images / installer media may boot with rootfs referenced by label; but then they should update to be bootable by-UUID upon kernel or grub updates; or call to update-grub. Not sure if we do something like that on riscv64 already / yet, and or explicitely on u-boot-menu images. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2004567 Title: Jammy kernel crashes on SiFive HiFive Unmatched Status in linux-riscv-5.19 package in Ubuntu: Invalid Bug description: I am testing the daily preinstalled Ubuntu image on the SiFive HiFive Unmatched board. After resetting I see the following: Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... y^done. [ 27.626148] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling... run-init[ 32.748312] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now [ 32.763928] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 32.782575] CPU: 0 PID: 1 Comm: run-init Not tainted 5.19.0-1012-generic #13~22.04.1-Ubuntu [ 32.790908] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 32.796463] Call Trace: [ 32.798895] [] dump_backtrace+0x30/0x42 [ 32.804279] [] show_stack+0x40/0x52 [ 32.809317] [] dump_stack_lvl+0x44/0x62 [ 32.814702] [] dump_stack+0x18/0x22 [ 32.819740] [] panic+0x11c/0x30a [ 32.824517] [] do_exit+0x462/0x468 [ 32.829468] [] do_group_exit+0x38/0x94 [ 32.834766] [] __wake_up_parent+0x0/0x3c [ 32.840239] [] ret_from_syscall+0x0/0x2 [ 32.845627] SMP: stopping secondary CPUs [ 32.849549] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 ]--- : can't execute '/sbin/init': Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1012-generic 5.19.0-1012.13~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: riscv64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Feb 2 14:15:58 2023 SourcePackage: linux-riscv-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.19/+bug/2004567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004567] Re: Jammy kernel crashes on SiFive HiFive Unmatched
We have a specification for this - https://wiki.ubuntu.com/FSTAB but I don't know if it needs updating or has regressed somewhere. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2004567 Title: Jammy kernel crashes on SiFive HiFive Unmatched Status in linux-riscv-5.19 package in Ubuntu: Invalid Bug description: I am testing the daily preinstalled Ubuntu image on the SiFive HiFive Unmatched board. After resetting I see the following: Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... y^done. [ 27.626148] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-464c, throttling... run-init[ 32.748312] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now [ 32.763928] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 32.782575] CPU: 0 PID: 1 Comm: run-init Not tainted 5.19.0-1012-generic #13~22.04.1-Ubuntu [ 32.790908] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 32.796463] Call Trace: [ 32.798895] [] dump_backtrace+0x30/0x42 [ 32.804279] [] show_stack+0x40/0x52 [ 32.809317] [] dump_stack_lvl+0x44/0x62 [ 32.814702] [] dump_stack+0x18/0x22 [ 32.819740] [] panic+0x11c/0x30a [ 32.824517] [] do_exit+0x462/0x468 [ 32.829468] [] do_group_exit+0x38/0x94 [ 32.834766] [] __wake_up_parent+0x0/0x3c [ 32.840239] [] ret_from_syscall+0x0/0x2 [ 32.845627] SMP: stopping secondary CPUs [ 32.849549] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 ]--- : can't execute '/sbin/init': Exec format error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1012-generic 5.19.0-1012.13~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic riscv64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: riscv64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Feb 2 14:15:58 2023 SourcePackage: linux-riscv-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv-5.19/+bug/2004567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997944] Re: Soundwire support for the Intel RPL Gen platforms
$ dput ubuntu firmware-sof_2.0-1ubuntu4.1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1.dsc: Valid signature from 9B8EC849D5EF70ED
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading firmware-sof_2.0-1ubuntu4.1.dsc: done.
Uploading firmware-sof_2.0-1ubuntu4.1.debian.tar.xz: done.
Uploading firmware-sof_2.0-1ubuntu4.1_source.buildinfo: done.
Uploading firmware-sof_2.0-1ubuntu4.1_source.changes: done.
Successfully uploaded packages.
In unapproved queue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1997944
Title:
Soundwire support for the Intel RPL Gen platforms
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
In Progress
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in firmware-sof source package in Lunar:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justfication]
[Impact]
Need soundwire support for the Intel RPL Gen platforms, specifically
0C10/0C4F/0C11. 0C40 added due to dependency.
[Fix]
Fixes from linux-next for v6.2, as well as those for firmware-sof and
alsa-ucm-conf.
[Test Case]
All the fixes are currently packaged in experimental kernel/firmware
PPAs. Install the latest ones and check audio functions.
[Where problems could occur]
Most of the patches add model information only, and they'd only take
effect on platforms with the corresponding hardware pieces.
[Other Info]
Nominated for Unstable/Lunar and OEM-6.0.
== original bug report ==
Include the support for Soundwire of RPL Gen platforms
Related components/fixes:
* kernel:
* b07908ab26ce ALSA: hda: intel-dsp-config: Add RaptorLake PCI IDs
* d608bc44181c ASoC: Intel: sof_sdw: Add support for SKU 0C10 product
* 55fc03445e2c ASoC: Intel: soc-acpi: add SKU 0C10 SoundWire configuration
* 880bf4b47fc1 ASoC: Intel: sof_sdw: Add support for SKU 0C40 product
* 97b5fbf44c00 ASoC: Intel: soc-acpi: add SKU 0C40 SoundWire configuration
* a9248c868c39 ASoC: Intel: sof_sdw: Add support for SKU 0C4F product
* 6ad73a2b42ea ASoC: rt1318: Add RT1318 SDCA vendor-specific driver
* 8c4b3a8ea2c0 ASoC: intel: sof_sdw: add rt1318 codec support.
* d84e10da17e7 ASoC: Intel: sof_sdw: Add support for SKU 0C11 product
* 0050e3d3d43d ASoC: Intel: soc-acpi: add SKU 0C11 SoundWire configuration
* SOF Audio firmware and topology support for Intel RPL Mobiles
* https://github.com/thesofproject/sof/releases/tag/v2.2.3
* https://github.com/thesofproject/sof-bin/pull/108
* https://github.com/alsa-project/alsa-ucm-conf
* c82c400fb653 ucm2: sof-soundwire: add basic settings for RT1318 SDCA
device
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 1337 F pulseaudio
/dev/snd/pcmC0D4c: ubuntu 1337 F...m pulseaudio
/dev/snd/pcmC0D2p: ubuntu 1337 F...m pulseaudio
CasperMD5json:
{
"result": "skip"
}
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-torchic+X72
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-25 (25 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220504-33
MachineType: Dell Inc. Precision 5480
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-9009-oem
root=UUID=58df5e81-0c25-471c-ace5-4decd3bcf449 ro automatic-oem-config quiet
splash
ProcVersionSignature: Ubuntu 6.0.0-9009.9+exp.25-oem 6.0.10
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.0.0-9009-oem N/A
linux-backports-modules-6.0.0-9009-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy apport-hook-error
Uname: Linux 6.0.0-9009-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
[Kernel-packages] [Bug 2000030] Re: Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
$ dput ubuntu firmware-sof_2.0-1ubuntu4.1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1_source.changes: Valid signature from
9B8EC849D5EF70ED
Checking signature on .dsc
gpg: /tmp/firmware-sof_2.0-1ubuntu4.1.dsc: Valid signature from 9B8EC849D5EF70ED
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading firmware-sof_2.0-1ubuntu4.1.dsc: done.
Uploading firmware-sof_2.0-1ubuntu4.1.debian.tar.xz: done.
Uploading firmware-sof_2.0-1ubuntu4.1_source.buildinfo: done.
Uploading firmware-sof_2.0-1ubuntu4.1_source.changes: done.
Successfully uploaded packages.
In unapproved queue.
** Changed in: firmware-sof (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/230
Title:
Soundwire support for the Intel RPL Gen 0C40/0C11 platforms
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
In Progress
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux-oem-6.1 source package in Jammy:
Fix Released
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing support for two additional product model of Intel RPL Gen
Soundwire.
[Fix]
Two additional commits merged in upstream sof development repository
on GitHub.
[Test Case]
Apply the two changes along with an alsa ucm conf fix, then perform audio
automatic/manual checkbox tests.
[Where problems could occur]
New hardware. No known issue so far, but might have minor issues in
the future.
[Other Info]
Nominated for U/L/OEM-6.0/OEM-6.1. Depending on fixes from bug
1997944.
== original bug report ==
This is a follow-up to bug 1997944 that supports more RPL gen
platforms.
Staging fixes:
*
https://github.com/thesofproject/linux/commit/9aacc6f5c422b98ef8ea98d190a8f6db9aa447c4
("ASoC: Intel: soc-acpi: add configuration for variant of 0C40 product")
*
https://github.com/thesofproject/linux/commit/e3707e4dd275bc731f6ed4067a2694534675ca52
("ASoC: Intel: soc-acpi: add configuration for variant of 0C11 product")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/230/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004262] Re: Intel E810 NICs driver in causinghangs when booting and bonds configured
Which driver is used by untainted generic kernels for the device in question? Can you attach sosreport, dmesg, etc? -- 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/2004262 Title: Intel E810 NICs driver in causinghangs when booting and bonds configured Status in linux package in Ubuntu: Incomplete Bug description: jammy 22.04.1 linux-image-generic 5.15.0-58-generic Intel E810-XXV Dual Port NICs in Dell PowerEdge 650 After beonding is enabled on switch and server side, the system will hang at initialing ubuntu. The kernel loads but around starting the Network Services the system can hang for sometimes 5 minutes, and in other cases, indefinitely. The message of: echo 0 > /proc/sys/kernel/hung_task_timeout_sec” systemd-resolve blocked for more than 120 seconds appears, and eventually the Network services just attempts to start and never does. This is with or without DHCP enabled. Tried this same setup with the hwe-22.04, hwe-20.04, hwe-22.04-ege and linux-oem kernels and all exhibit the same failure. To work around this. installing the Intel 'ice' driver of version 1.10.1.2.2 works. The system doesn't even remotely hang at startup and all networking functions remain working (ping, DNS, general accessibility). The driver can be found at https://downloadmirror.intel.com/763930/ice-1.10.1.2.2.tar.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004171] [NEW] 2022.08.12 new upstream release
*** This bug is a security vulnerability *** Public security bug reported: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Jammy) Importance: Undecided Status: New ** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/2004171 Title: 2022.08.12 new upstream release Status in wireless-regdb package in Ubuntu: New Status in wireless-regdb source package in Trusty: New Status in wireless-regdb source package in Xenial: New Status in wireless-regdb source package in Bionic: New Status in wireless-regdb source package in Focal: New Status in wireless-regdb source package in Jammy: New Status in wireless-regdb source package in Kinetic: New Status in wireless-regdb source package in Lunar: New Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2004171/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
** Also affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New ** Changed in: crda (Ubuntu) Status: New => Fix Released ** Changed in: crda (Ubuntu Jammy) Status: New => Fix Released ** Description changed: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: - https://bugs.debian.org/1003903 + https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. + + wireless-regdb should stop shipping /lib/crda files which only removed + crda package used to use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: New Status in crda source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in wireless-regdb source package in Jammy: New Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. wireless-regdb should stop shipping /lib/crda files which only removed crda package used to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004010] [NEW] Missing sbsigntool build-dependency
Public bug reported: [ Impact ] * On UEFI platforms, sbverify is used by linux-signed packaging to check correctness of signing (to ensure that kernel was not signed with a revoked key by accident). * Some signed packages are missing such build dependency on arm64 platforms. [ Test Plan ] * Check linux-signed package build-log and ensure that sbverify calls do not result in command not found, but instead correctly check and reject verification against revoked certs. [ Where problems could occur ] * sbverify is available on all uefi platforms [ Other Info ] * All other packages have correct dependency. ** Affects: linux-signed-gcp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2004010 Title: Missing sbsigntool build-dependency Status in linux-signed-gcp package in Ubuntu: New Bug description: [ Impact ] * On UEFI platforms, sbverify is used by linux-signed packaging to check correctness of signing (to ensure that kernel was not signed with a revoked key by accident). * Some signed packages are missing such build dependency on arm64 platforms. [ Test Plan ] * Check linux-signed package build-log and ensure that sbverify calls do not result in command not found, but instead correctly check and reject verification against revoked certs. [ Where problems could occur ] * sbverify is available on all uefi platforms [ Other Info ] * All other packages have correct dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-gcp/+bug/2004010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993718] Re: Promote to restricted: broadcom-sta & bcmwl are duplicates
** Summary changed: - broadcom-sta & bcmwl are duplicates + Promote to restricted: broadcom-sta & bcmwl are duplicates ** Changed in: broadcom-sta (Ubuntu) Status: New => Triaged ** Description changed: + Ubuntu archive please promote broadcom-sta from multiverse to + restricted. + + After that's done and migrates, we will be able to remove bcmwl from the + archive. + + --- + broadcom-sta & bcmwl are duplicates of each other. One is packaged and maintained by archlinux/debian the other one was our self packaged one. We should merge the two. On the surface the source code is the same, there is slightly better dkms packaging on the broadcom-sta package. However it is missing modaliases stanzas. I think we should port the modaliases to the new package, and remove the old one. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1993718 Title: Promote to restricted: broadcom-sta & bcmwl are duplicates Status in bcmwl package in Ubuntu: New Status in broadcom-sta package in Ubuntu: Triaged Bug description: Ubuntu archive please promote broadcom-sta from multiverse to restricted. After that's done and migrates, we will be able to remove bcmwl from the archive. --- broadcom-sta & bcmwl are duplicates of each other. One is packaged and maintained by archlinux/debian the other one was our self packaged one. We should merge the two. On the surface the source code is the same, there is slightly better dkms packaging on the broadcom-sta package. However it is missing modaliases stanzas. I think we should port the modaliases to the new package, and remove the old one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1993718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
@sil2100 marked out test case in the bug report more clearly. ** Description changed: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. + + [Testcase] + + tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not + unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) - E: Problem opening + E: Problem opening E: The package lists or status file could not be parsed or opened. + Notes: Switching to a TTY will print a crash error message related to + the same missing /var/lib/dpkg/status file. Running "sudo touch + /var/lib/dpkg/status" will allow "sudo apt update" to function and fix + the crashed process in the TTY. - Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. + [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update- manager in my experience, and another one was from "check-new-release- gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Triaged Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text=ubiquity ** Also affects: ubiquity (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: zsys (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: snapd (Ubuntu Jammy) ** No longer affects: systemd (Ubuntu Jammy) ** Changed in: ubiquity (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu Jammy) Status: New => Triaged ** Changed in: ubiquity (Ubuntu Jammy) Milestone: None => ubuntu-22.04.2 ** No longer affects: zfs-linux (Ubuntu Jammy) ** No longer affects: zsys (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Triaged Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003174] Re: zfs-dkms fails to build on jammy with linux 5.19
zfs-linux SRUs, should follow the regular SRU testing process which covers all bases. In the past we have used these: [Test Plan] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass The first two cover unit, functional, and integration tests. Whilst the last one covers full-end-to-end zfs-on-root systems with snapshotting. More details guidelines are available internally in a google doc shared with kernel team, on how to execute them. -- 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/2003174 Title: zfs-dkms fails to build on jammy with linux 5.19 Status in zfs-linux package in Ubuntu: Invalid Status in zfs-linux source package in Jammy: In Progress Bug description: [Impact] zfs-dkms fails to build on jammy with the latest linux hwe 5.19: *** ZFS Version: zfs-2.1.4-0ubuntu0.1 *** Compatible Kernels: 3.10 - 5.17 [Test case] $ sudo apt install zfs-dkms [Fix] The most reliable fix is probably to move to the same version that is available in kinetic, since there's no significant ABI change in this way we should be able to support both 5.15 and 5.19 kernels. [Regression potential] We may experience zfs regressions if there's a format/ABI incompatibility with volumes created with the previous version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2003174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19
We should SRU these changes to Kinetic too, as they do fixup an issue which can be hit on kinetic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2002636 Title: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19 Status in broadcom-sta package in Ubuntu: Invalid Status in broadcom-sta source package in Jammy: Fix Committed Bug description: [Impact] broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install broadcom-sta-dkms [Fix] The attached debdiff sync Jammy version to Lunar, minus the dh-dkms build-dep. [Regression potential] None, it's the same version we are already using in Lunar and it contains only fixes to the base version (that is the same among Jammy, Kinetic and Lunar). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996198] Re: Fix rfkill causing soft blocked wifi
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1996198 Title: Fix rfkill causing soft blocked wifi Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.0 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Need this patch in so a BIOS upgrade won't cause issues on HP laptops. commit 1598bfa8e1faa932de42e1ee7628a1c4c4263f0a Author: Jorge Lopez Date: Fri Oct 28 10:55:27 2022 -0500 platform/x86: hp_wmi: Fix rfkill causing soft blocked wifi After upgrading BIOS to U82 01.02.01 Rev.A, the console is flooded strange char "^@" which printed out every second and makes login nearly impossible. Also the below messages were shown both in console and journal/dmesg every second: usb 1-3: Device not responding to setup address. usb 1-3: device not accepting address 4, error -71 usb 1-3: device descriptor read/all, error -71 usb usb1-port3: unable to enumerate USB device Wifi is soft blocked by checking rfkill. When unblocked manually, after few seconds it would be soft blocked again. So I was suspecting something triggered rfkill to soft block wifi. At the end it was fixed by removing hp_wmi module. The root cause is the way hp-wmi driver handles command 1B on post-2009 BIOS. In pre-2009 BIOS, command 1Bh return 0x4 to indicate that BIOS no longer controls the power for the wireless devices. Signed-off-by: Jorge Lopez Link: https://bugzilla.kernel.org/show_bug.cgi?id=216468 Reviewed-by: Mario Limonciello Link: https://lore.kernel.org/r/20221028155527.7724-1-jorge.lop...@hp.com Cc: sta...@vger.kernel.org Reviewed-by: Hans de Goede Signed-off-by: Hans de Goede [Test case] test on a HP laptop with the new BIOS [Where problems could occur] from the commit: * In pre-2009 BIOS, command 1Bh return 0x4 to indicate that * BIOS no longer controls the power for the wireless * devices. All features supported by this command will no * longer be supported. anyone running a laptop with obsolete pre-2009 BIOS probably won't notice the missing feature at this point. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996198/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992266] Re: input/keyboard: the keyboard on some Asus laptops can't work
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992266 Title: input/keyboard: the keyboard on some Asus laptops can't work Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: This is upstream tracking bug: https://bugzilla.kernel.org/show_bug.cgi?id=216158 The bug originates from an upstream bug, and the ubuntu users request me to do a SRU to make the ubuntu linux work on their Asus laptops, so once the pathces are merge to mainline kernel, I start to prepare this SRU. [Impact] Some Asus laptops config the IRQ of keyboard in the BIOS, but kernel will override to a new configuration for that IRQ, this will make the keyboard not work anymore under linux. [Fix] Backport 2 patches from mainlie kernel to fix this problem. [Test] boot the patched kernel on the machine, test the keyboard, all regular keys could work. [Where problems could occur] The patches use the dmi table to match the machines, so only the matched Asus laptops will be impacted by the patches, if there is any regression, the regression only affects those matched Asus laptops, and the regression possibility is very low since ubuntu users already tested the patches on their own Asus laptops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Tags removed: verification-needed-focal verification-needed-jammy verification-needed-kinetic ** Tags added: verification-done-focal verification-done-jammy verification-done-kinetic ** Tags added: kernel-stable-tracking-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999009] Re: bcmwl: properly support linux 6.1
Uploaded to unapproved queue of jammy and kinetic, proposed of lunar. ** Also affects: bcmwl (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: bcmwl (Ubuntu Lunar) Status: New => Fix Committed ** Changed in: bcmwl (Ubuntu Kinetic) Status: New => In Progress ** Changed in: bcmwl (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1999009 Title: bcmwl: properly support linux 6.1 Status in bcmwl package in Ubuntu: Fix Committed Status in bcmwl source package in Jammy: In Progress Status in bcmwl source package in Kinetic: In Progress Status in bcmwl source package in Lunar: Fix Committed Bug description: [Impact] bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar. Moreover, with kernels >= 5.17 there's an incorrect access to struct netdev (see LP: #1998039). [Test case] $ sudo apt install bcmwl-kernel-source [Fix] The following upstream commits have change the cfg80211 ABI in linux >= 6.1: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=efbabc11650040c64884ff3019b88c7bcc0ceb1d https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7a7b84e33178db4a839c5e1773247be17597c1f Change bcmwl to properly support the new ABI changes. Moreover, to fix the incorrect netdev access with kernels >= 5.17 we can apply this patch https://raw.githubusercontent.com/archlinux/svntogit- community/master/broadcom-wl-dkms/trunk/012-linux517.patch (see LP: #1998039 - thanks to Brett Holman for the backport and for reporting the problem). [Regression potential] We may experience regressions with kernels >= 6.1 using the bcmwl- kernel-source dkms. The code for the previous kernels remains unchanged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Changed in: snapd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] [NEW] Revoke & rotate to new signing key
Public bug reported: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key ** Affects: linux (Ubuntu) Importance: Undecided Status: Triaged ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2002812 Title: Revoke & rotate to new signing key Status in linux package in Ubuntu: Triaged Bug description: [ Impact ] * Revoke & rotate to new signing key * Update revocations, which match the next Ubuntu shim 15.7 revocations. Specifically - revoke certs that were previously protected with by-hash revocations, revoke lost/unused certificates. * Start using advantage2021v1 and ubuntu2022v1 signing keys. * This is a routine key rotation. [ Test Plan ] * Check that old shim/grub boot this kernel * Check that the upcomming future shim/grub can boot this kernel * Check that these kernels can do signed kexec into itself [ Where problems could occur ] * Kernels with this patch applied should be signed using ubuntu/4 pro/3 core/2 signing streams. [ Other Info ] * TPM PCR values and measurements will change when changing the signing key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002664] [NEW] RM obsolete unsupported v5.17 kernel
Public bug reported: RM obsolete unsupported and no longer used v5.17 kernels ** Affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-meta-oem-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-restricted-signatures-oem-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-signed-oem-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: Triaged ** Also affects: linux-meta-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-allwinner-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-meta-starfive-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-restricted-signatures-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - RM obsolete unsupported kernel + RM obsolete unsupported v5.17 kernel ** Description changed: - RM obsolete unsupported kernels - - * linux-oem-5.17 + RM obsolete unsupported and no longer used v5.17 kernels ** No longer affects: linux-meta-allwinner-5.17 (Ubuntu) ** No longer affects: linux-meta-starfive-5.17 (Ubuntu) ** Changed in: linux-allwinner-5.17 (Ubuntu) Status: New => Triaged ** Changed in: linux-meta-oem-5.17 (Ubuntu) Status: New => Triaged ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Triaged ** Changed in: linux-restricted-signatures-oem-5.17 (Ubuntu) Status: New => Triaged ** Changed in: linux-signed-oem-5.17 (Ubuntu) Status: New => Triaged ** Changed in: linux-starfive-5.17 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2002664 Title: RM obsolete unsupported v5.17 kernel Status in linux-allwinner-5.17 package in Ubuntu: Triaged Status in linux-meta-oem-5.17 package in Ubuntu: Triaged Status in linux-oem-5.17 package in Ubuntu: Triaged Status in linux-restricted-signatures-oem-5.17 package in Ubuntu: Triaged Status in linux-signed-oem-5.17 package in Ubuntu: Triaged Status in linux-starfive-5.17 package in Ubuntu: Triaged Bug description: RM obsolete unsupported and no longer used v5.17 kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-allwinner-5.17/+bug/2002664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999750] [NEW] Set explicit CC in the headers package
Public bug reported: [ Impact ] * Currently Ubuntu Linux kernel header packages use stock Makefile as shipped by upstream kernel. During linux kernel package build however HOSTCC and CC are typically overridden to use explicit complier version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module build failures as despite all efforts to reuse matching gcc version out of .config, various shell scripts / build systems / makefiles do not pass the CC variable as a make variable to the end make call that is used to build dkms modules. To avoid this, hardcode the correct compiler in the linux headers package shipped Makefile. This is similar to the Makefile includes that debian ships, albeit with less indirections. [ Test Plan ] * adt-matrix for dkms modules should start to pass correctly [ Where problems could occur ] * headers package for hwe kernels may demand a newer compiler, for which runtime dependency does not exist. dkms package in jammy-updates already has explicit dependency on gcc-12 for that reason. Installing build-deps of the kernel package will install correct/required compilers. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999750 Title: Set explicit CC in the headers package Status in linux package in Ubuntu: New Bug description: [ Impact ] * Currently Ubuntu Linux kernel header packages use stock Makefile as shipped by upstream kernel. During linux kernel package build however HOSTCC and CC are typically overridden to use explicit complier version $(DEB_HOST_GNU_TYPE)-gcc-12. This can lead to dkms module build failures as despite all efforts to reuse matching gcc version out of .config, various shell scripts / build systems / makefiles do not pass the CC variable as a make variable to the end make call that is used to build dkms modules. To avoid this, hardcode the correct compiler in the linux headers package shipped Makefile. This is similar to the Makefile includes that debian ships, albeit with less indirections. [ Test Plan ] * adt-matrix for dkms modules should start to pass correctly [ Where problems could occur ] * headers package for hwe kernels may demand a newer compiler, for which runtime dependency does not exist. dkms package in jammy-updates already has explicit dependency on gcc-12 for that reason. Installing build-deps of the kernel package will install correct/required compilers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999396] [NEW] pnvm firmware files undeclared
Public bug reported: At the moment fallback pnvm firmware files exists, but are undeclared. Ensure that if ucode for such devices is copied, that pnvm files are copied too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1999396 Title: pnvm firmware files undeclared Status in linux package in Ubuntu: New Bug description: At the moment fallback pnvm firmware files exists, but are undeclared. Ensure that if ucode for such devices is copied, that pnvm files are copied too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998841] Re: firmware blob in missing pc-kernel 22/stable of Ubuntu Core22
2022-12-12 13:37:30.762 :: 2022-12-12 13:36:02.048 :: + /root/parts/kernel/src/trim-firmware /root/parts/kernel/install/lib 2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.710 :: Overriding iwlwifi-so-a0-gf-a0-66.ucode with iwlwifi-so-a0-gf-a0-64.ucode 2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.716 :: Overriding iwlwifi-so-a0-hr-b0-66.ucode with iwlwifi-so-a0-hr-b0-64.ucode 2022-12-12 13:37:30.762 :: 2022-12-12 13:36:13.723 :: Overriding iwlwifi-so-a0-jf-b0-66.ucode with iwlwifi-so-a0-jf-b0-64.ucode Having some progress to fix this. ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1998841 Title: firmware blob in missing pc-kernel 22/stable of Ubuntu Core22 Status in linux package in Ubuntu: In Progress Bug description: We are building an application in our private brand store. While trying to use the pc-kernel 22/stable our wifi networking does not work. The same hardware (a Dell 5570) works well on Desktop 22.04. Thee issue seems to be a missing firmware blob to enable the wifi networking. Ubuntu desktop 22.04 loads the following firmware blob. lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode Please add this firmware blob to pc-kernel 22/stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998841] Re: firmware blob in missing pc-kernel 22/stable of Ubuntu Core22
Our kernel driver supports loading UCODE API versions 39 to 66 inclusive. Our linux-firmware package, for this SKU variant ships: ./lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode ./lib/firmware/iwlwifi-so-a0-gf-a0-67.ucode ./lib/firmware/iwlwifi-so-a0-gf-a0-68.ucode I don't quite know why 65 & 66 are missing, lets assume they have been discovered to be buggy. The module declares to only support 66.ucode, when actually that's the max version $ modinfo iwlwifi | grep so-a0-gf-a0 firmware: iwlwifi-so-a0-gf-a0-66.ucode And our trim-firmware scripts do not realise that we should include v64 of the ucode, if desired v66 & v65 are missing. -- 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/1998841 Title: firmware blob in missing pc-kernel 22/stable of Ubuntu Core22 Status in linux package in Ubuntu: Confirmed Bug description: We are building an application in our private brand store. While trying to use the pc-kernel 22/stable our wifi networking does not work. The same hardware (a Dell 5570) works well on Desktop 22.04. Thee issue seems to be a missing firmware blob to enable the wifi networking. Ubuntu desktop 22.04 loads the following firmware blob. lib/firmware/iwlwifi-so-a0-gf-a0-64.ucode Please add this firmware blob to pc-kernel 22/stable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998841/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Currently libunwind-dev is not used on s390x by the kernel build, thus the runtime dep for libunwind-dev can probably be dropped, will test. Also not sure why it is at all specified. ** Description changed: [ Impact ] - * kpatch upstream has gained support for more architectures which we + * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. - * This SRU is to enable s390x builds of kpatch on kinetic & jammy. - - * Separately linux kernel patches for s390x will also be backported to + * This SRU is to enable s390x builds of kpatch on kinetic & jammy. + + * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] - * Attempt to run and load sample integration livepatches from the + * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - - amd64 jammy v5.15 - - amd64 & s390x jammy v5.19 - - amd64 & s390x kinetic v5.19 + - amd64 jammy v5.15 + - amd64 & s390x jammy v5.19 + - amd64 & s390x kinetic v5.19 [ Where problems could occur ] - * The newly generated livepatches produced by this kpatch may have + * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. - * This is a fairly large upstream update to the tooling. - - * One command line option to kpatch-build is no longer supported '-e', + * This is a fairly large upstream update to the tooling. + + * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot-module'. And ' --ott-module-src' becomes mandatory in such cases, previously '-- sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. - * Majority of non-test/non-doc changes are to do with: -- add support for s390x and 32bit powerpc -- add support for newer kernels and compilers (support & bugfixes to various sections and symbols) -- more strict checking and bugfixes w.r.t. livepatch generation -- refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. + * Majority of non-test/non-doc changes are to do with: + - add support for s390x and 32bit powerpc + - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) + - more strict checking and bugfixes w.r.t. livepatch generation + - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
** Description changed: - Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). - But the kpatch-build tool does only support amd64 as of today. + [ Impact ] + + * kpatch upstream has gained support for more architectures which we + would like to enable on LTS release. Since building livepatches using + the kpatch tooling makes the most sense on LTS kernels. + + * This SRU is to enable s390x builds of kpatch on kinetic & jammy. + + * Separately linux kernel patches for s390x will also be backported to + the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to + support livepatches. + + [ Test Plan ] + + * Attempt to run and load sample integration livepatches from the + kpatch integration source code, against v5.15 & v5.19 kernels. These + should succeed on: + + - amd64 jammy v5.15 + - amd64 & s390x jammy v5.19 + - amd64 & s390x kinetic v5.19 + + [ Where problems could occur ] + + * The newly generated livepatches produced by this kpatch may have + different content (more or less sections/sybmols/relocations/etc), but + remain compatible with all prior kernels and tool-chains. + + * This is a fairly large upstream update to the tooling. + + * One command line option to kpatch-build is no longer supported '-e', + instead long form command line option must be used '--oot-module'. And ' + --ott-module-src' becomes mandatory in such cases, previously '-- + sourcedire' was required. + + Additional command line options added '--oot-module-src, -R|--non- + replace'. + + '--skip-gcc-check' is still supported but prints warnings, it is + deprecated in favour of '--skip-compiler-check'. + + kpatch-cc utility is added, which is a toolchain wrapper. + + Thus adjustments might be needed to scripts used to invoke and create + kpatch modules. + + * Majority of non-test/non-doc changes are to do with: +- add support for s390x and 32bit powerpc +- add support for newer kernels and compilers (support & bugfixes to various sections and symbols) +- more strict checking and bugfixes w.r.t. livepatch generation +- refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. + + * Some of the fixes from these new upstream releases have already been + cherry-picked in the kpatch, but others might soon be needed on x84, + i.e. to support gcc-12 built kernels. + + $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch-build/ + > shortlog.txt + + d46fea98ef kpatch-build: strengthen conditions for changed sections + 9fac261ed0 kpatch-build: rela section could disappear after patched + fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules + 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support + 07433e98c0 kpatch-cc: fix stripping of source tree prefix + 33368a88cd create-diff-object: add support for .return_sites section (x86) + e921c557f9 macros: tweak syscall patching macros + a1171b112e create-diff-object: Create missing section symbol + 0308d52bcd kpatch/s390: Enable kpatch build support + b0330ab18e kpatch/s390: Add additional bundled symbols. + eb4a85f778 kpatch/s390: Add exclusion lists + f0d00a9290 kpatch/s390: Add initial support for kpatch + 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch + c6d0b5450b lookup: fix symtab parsing + 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() + 017015a725 create-diff-object: make kpatch_check_relocations() more precise + f0e3da336c create-diff-object: fix string extraction + 86d5208b46 create-diff-object: error on symbol conversion failure + 325bccd89d create-diff-object: skip conversion for sections which never have symbols + 8508abd3b1 create-diff-object: allow converstion of empty symbols + 8d5a628bde create-diff-object: add extra check for symbol conversion edge case + 01427d50a1 create-diff-object: move addend math to a new function + bec6488af6 create-diff-object: add rela_insn() error check + 6b1895a6b7 create-diff-object: convert rela_insn() to take normal 'sec' + bf212f7750 create-diff-object: error on unsupported rela in symbol conversion + 3f8e1062cc create-diff-object: support R_X86_64_NONE in kpatch_replace_sections_syms() + 79f45d1b0a create-diff-object: fix kpatch_replace_sections_syms() for non-text + 61e46094b5 create-diff-object: convert function return types to 'bool' + c24d135f40 create-diff-object: rename "sec" -> "relasec" for rela sections + 3b63456817 kpatch-elf: convert functions to static + 0c5a1e7753 kpatch-build: make xtrace output less verbose + 2784f5056b kpatch-build: add support for openEuler + 3392049665 kpatch-build: remove duplicated use_klp_arch + e9c0b67862 macros: add syscall patching macros + c2e73c2cbc create-diff-object: ensure debug sections don't use dynrelas + 305ff8a5d8 create-diff-object: include .LCx string literal symbols + b700732f5d create-diff-object: add "_printk" to the __LINE__ detection +
[Kernel-packages] [Bug 1997914] [NEW] intel/sof firmware is undeclared
Public bug reported: intel/sof firmware is undeclared by the modules that load it ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997914 Title: intel/sof firmware is undeclared Status in linux package in Ubuntu: New Bug description: intel/sof firmware is undeclared by the modules that load it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997914/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997910] [NEW] Undeclared btqca and btusb firmware
Public bug reported: Undeclared btusb firmware btusb.ko can request snprintf(fwname, sizeof(fwname), "qca/rampatch_usb_%08x.bin", ver_rom); but doesn't declare it as MODULES_FIRMWARE. btqca can request lots of qca/ things ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Summary changed: - Undeclared btusb firmware + Undeclared btqca and btusb firmware ** Description changed: Undeclared btusb firmware btusb.ko can request snprintf(fwname, sizeof(fwname), "qca/rampatch_usb_%08x.bin", ver_rom); but doesn't declare it as MODULES_FIRMWARE. + + btqca can request lots of qca/ things -- 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/1997910 Title: Undeclared btqca and btusb firmware Status in linux package in Ubuntu: Incomplete Bug description: Undeclared btusb firmware btusb.ko can request snprintf(fwname, sizeof(fwname), "qca/rampatch_usb_%08x.bin", ver_rom); but doesn't declare it as MODULES_FIRMWARE. btqca can request lots of qca/ things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996730] Re: Missing firmware in kernel snap
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996730 Title: Missing firmware in kernel snap Status in linux package in Ubuntu: Fix Released Bug description: alsa-topology-conf is part of the desktop image. It installs /lib/firmware/skl_hda_dsp_generic-tplg.bin this firmware file is missing from kernel snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1997841] [NEW] More dkms fixes for exact cc compiler
Public bug reported: [ Impact ] * Previously https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991664 has fixed up some dkms modules that use makefiles without setting a CC= variable inside them. However, there is a class of dkms modules that set a CC= variable inside the makefile, and then the environment variable is ignored, thus resulting in hwe-5.19 dkms modules to FTBFS. * Fix those by setting MAKEFLAGS="--environment-overrides" to really ensure that environmental variable compiler is really being used. Observe the following: $ cat Makefile.just-cc all: echo $(CC) $ cat Makefile.cc-set CC=cc-set-in-makefile all: echo $(CC) # cmdline override works in both cases $ make -f Makefile.just-cc CC=make-var-cmdline echo make-var-cmdline make-var-cmdline $ make -f Makefile.cc-set CC=make-var-cmdline echo make-var-cmdline make-var-cmdline # environment/shell variable override only works in one of them $ CC=env-cc make -f Makefile.just-cc echo env-cc env-cc $ CC=env-cc make -f Makefile.cc-set echo cc-set-in-makefile cc-set-in-makefile # unless environment-overrides is set $ MAKEFLAGS=--environment-overrides CC=env-cc make -f Makefile.cc-set echo env-cc env-cc [ Test Plan ] * Divert /usr/bin/gcc to /bin/false $ sudo ln -sf /bin/false /usr/bin/gcc * Install a v5.19 kernel that must be built with gcc-12 and a dkms module that uses a CC variable set inside its makefile $ sudo apt install linux-virtual-hwe-22.04-edge gost-crypto-dkms * Check that dkms status has the module successfully installed for v5.19 kernel $ dkms status [ Where problems could occur ] * dkms cleans environment of all tool-chain related variables already, but MAKEFLAGS=--environment-overrides may result in additional/new/unexpected variables leaking into the dkms module build, which were previously ignored. * A better solution might be for our kernel builds to emit a makefile snippet that is included by the Kbuild makefiles, but that too will only cover a subset of dkms modules, not all of them. * It might be nice if environment-overrides command line option of make accepted a list of allowed variables that are desired to be honored from the environment. [ Other Info ] * Any better suggestions of how to handle toolchain export would be welcome here, as this is starting to be silly. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1997841 Title: More dkms fixes for exact cc compiler Status in dkms package in Ubuntu: New Status in dkms source package in Jammy: New Status in dkms source package in Kinetic: New Status in dkms source package in Lunar: New Bug description: [ Impact ] * Previously https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1991664 has fixed up some dkms modules that use makefiles without setting a CC= variable inside them. However, there is a class of dkms modules that set a CC= variable inside the makefile, and then the environment variable is ignored, thus resulting in hwe-5.19 dkms modules to FTBFS. * Fix those by setting MAKEFLAGS="--environment-overrides" to really ensure that environmental variable compiler is really being used. Observe the following: $ cat Makefile.just-cc all: echo $(CC) $ cat Makefile.cc-set CC=cc-set-in-makefile all: echo $(CC) # cmdline override works in both cases $ make -f Makefile.just-cc CC=make-var-cmdline echo make-var-cmdline make-var-cmdline $ make -f Makefile.cc-set CC=make-var-cmdline echo make-var-cmdline make-var-cmdline # environment/shell variable override only works in one of them $ CC=env-cc make -f Makefile.just-cc echo env-cc env-cc $ CC=env-cc make -f Makefile.cc-set echo cc-set-in-makefile cc-set-in-makefile # unless environment-overrides is set $ MAKEFLAGS=--environment-overrides CC=env-cc make -f Makefile.cc-set echo env-cc env-cc [ Test Plan ] * Divert /usr/bin/gcc to /bin/false $ sudo ln -sf /bin/false /usr/bin/gcc * Install a v5.19 kernel that must be built with gcc-12 and a dkms module that uses a CC variable set inside its makefile $ sudo apt install linux-virtual-hwe-22.04-edge gost-crypto-dkms * Check that dkms status has the module successfully installed for v5.19 kernel $ dkms status
[Kernel-packages] [Bug 1991664] Re: backport dkms fixes to build modules correctly for hwe-5.19+ kernels with custom compiler
# Setup apt install software-properties-common ubuntu-dev-tools add-apt-repository ppa:canonical-kernel-team/ubuntu/ppa apt install linux-generic linux-generic-wip dkms=2.8.7-2ubuntu2 pull-lp-debs v4l2loopback kinetic This installs v5.15 and preliminary v5.19 kernels in a jammy chroot, together with dkms from jammy release pocket. It also fetches a sample dkms module from kinetic, that supports both kernels. # apt install ./v4l2loopback-dkms_0.12.7-2ubuntu2_all.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'v4l2loopback-dkms' instead of './v4l2loopback-dkms_0.12.7-2ubuntu2_all.deb' Suggested packages: v4l2loopback-utils The following NEW packages will be installed: v4l2loopback-dkms 0 upgraded, 1 newly installed, 0 to remove and 2 not upgraded. Need to get 0 B/29.3 kB of archives. After this operation, 113 kB of additional disk space will be used. Get:1 /root/v4l2loopback-dkms_0.12.7-2ubuntu2_all.deb v4l2loopback-dkms all 0.12.7-2ubuntu2 [29.3 kB] Selecting previously unselected package v4l2loopback-dkms. (Reading database ... 93941 files and directories currently installed.) Preparing to unpack .../v4l2loopback-dkms_0.12.7-2ubuntu2_all.deb ... Unpacking v4l2loopback-dkms (0.12.7-2ubuntu2) ... Setting up v4l2loopback-dkms (0.12.7-2ubuntu2) ... Loading new v4l2loopback-0.12.7 DKMS files... It is likely that 5.15.0-52-generic belongs to a chroot's host Building for 5.15.0-54-generic and 5.19.0-18-generic Building initial module for 5.15.0-54-generic Done. v4l2loopback.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/5.15.0-54-generic/updates/dkms/ depmod... Building initial module for 5.19.0-18-generic Error! Bad return status for module build on kernel: 5.19.0-18-generic (x86_64) Consult /var/lib/dkms/v4l2loopback/0.12.7/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/local/libexec/mk-sbuild/dpkg returned an error code (1) # dkms status v4l2loopback/0.12.7, 5.15.0-54-generic, x86_64: installed With current dkms, the module is built correctly for v5.15 kernel bug fails for v5.19 kernel. In the build log we can see that gcc-11 is used to build the module instead of gcc-12. warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0 You are using: cc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0 Upgrade dkms package to the proposed version # apt install dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: cpp-12 gcc-12 libasan8 libgcc-12-dev libtsan2 Suggested packages: gcc-12-locales menu gcc-12-multilib gcc-12-doc The following NEW packages will be installed: cpp-12 gcc-12 libasan8 libgcc-12-dev libtsan2 The following packages will be upgraded: dkms ... Setting up gcc-12 (12.1.0-2ubuntu1~22.04) ... Setting up dkms (2.8.7-2ubuntu2.1) ... Setting up v4l2loopback-dkms (0.12.7-2ubuntu2) ... Removing old v4l2loopback-0.12.7 DKMS files... Module v4l2loopback-0.12.7 for kernel 5.15.0-54-generic (x86_64). Before uninstall, this module version was ACTIVE on this kernel. v4l2loopback.ko: - Uninstallation - Deleting from: /lib/modules/5.15.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... Deleting module v4l2loopback-0.12.7 completely from the DKMS tree. Loading new v4l2loopback-0.12.7 DKMS files... It is likely that 5.15.0-52-generic belongs to a chroot's host Building for 5.15.0-54-generic and 5.19.0-18-generic Building initial module for 5.15.0-54-generic Done. v4l2loopback.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/5.15.0-54-generic/updates/dkms/ depmod... Building initial module for 5.19.0-18-generic Done. v4l2loopback.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.19.0-18-generic/updates/dkms/ depmod... Processing triggers for libc-bin (2.35-0ubuntu3) ... # dkms status v4l2loopback/0.12.7, 5.15.0-54-generic, x86_64: installed v4l2loopback/0.12.7, 5.19.0-18-generic, x86_64: installed We observe that the dkms module is built correctly for both v5.15 and v5.19 kernels. Also we can see that matching toolchain was used for each kernel: # readelf -p .comment /lib/modules/*/updates/dkms/v4l2loopback.ko File: /lib/modules/5.15.0-54-generic/updates/dkms/v4l2loopback.ko String dump of section
[Kernel-packages] [Bug 1996955] [NEW] Check if EFI signatures are revoked at build time
Public bug reported: [ Impact ] * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] * Add test-build PPA certificate as revoked * Perform a test-build crank of linux & linux-signed, in test-build PPA * linux-signed should FTBFS in test-build PPA * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches * The verification is done on EFI signed binaries only for now. OPAL & SIPL signing checks might be implemented in the future ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed ** Description changed: [ Impact ] - * Recent kernels expose built-in trusted and revoked certificates. See + * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 - * When kernels expose such information, it is prudent to check if the + * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. - * This ensures that a given signed kernel, can perform verified kexec + * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. - * This also helps with key rotations, in case kernel is routed to be + * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] - * Add test-build PPA certificate as revoked - * Perform a test-build crank of linux & linux-signed, in test-build PPA - * linux-signed should FTBFS in test-build PPA - * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly + * Add test-build PPA certificate as revoked + * Perform a test-build crank of linux & linux-signed, in test-build PPA + * linux-signed should FTBFS in test-build PPA + * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] - * Each individual linux-signed package needs to add a build-dep on all + * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches + + * The verification is done on EFI signed binaries only for now. OPAL & + SIPL signing checks might be implemented in the future ** Summary changed: - Fail the build if EFI binaries are signed with revoked keys + Check if EFI signatures are revoked at build ** Summary changed: - Check if EFI signatures are revoked at build + Check if EFI signatures are revoked at build time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1996955 Title: Check if EFI signatures are revoked at build time Status in linux-signed package in Ubuntu: Confirmed Bug description: [ Impact ] * Recent kernels expose built-in trusted and revoked certificates. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892 * When kernels expose such information, it is prudent to check if the freshly signed EFI binaries are actually revoked. And fail the build in such cases. * This ensures that a given signed kernel, can perform verified kexec for quick-reboot or for kdump purposes. * This also helps with key rotations, in case kernel is routed to be signed with the wrong key due to miss-configuration of the build. [ Test Plan ] * Add test-build PPA certificate as revoked * Perform a test-build crank of linux & linux-signed, in test-build PPA * linux-signed should FTBFS in test-build PPA * Copy linux and linux-signed with binaries to a personal PPA, linux-signed should complete the build correctly [ Where problems could occur ] * Each individual linux-signed package needs to add a build-dep on all buildinfo packages of all EFI signed flavours on EFI signed arches * The verification is done on EFI signed binaries only for now. OPAL & SIPL signing checks might be implemented in the future To manage notifications about this bug go to:
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Focal) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996892] Re: Expose built-in trusted and revoked certificates
** Description changed: [ Impact ] - * Kernels have a set of builtin trusted and revoked certificates as a bundle - * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally - * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information + * Kernels have a set of builtin trusted and revoked certificates as a bundle + * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally + * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] - * sudo apt install linux-buildinfo-$(uname -r) - * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert - * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert + * sudo apt install linux-buildinfo-$(uname -r) + * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert + * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert + + Example output: + $ grep Subject: -r usr/lib/linux + usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing + usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing + usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing + [ Where problems could occur ] - * buildinfo is an auxiliary package not installed by default, but used + * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: Incomplete Status in linux source package in Lunar: Incomplete Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
