[Kernel-packages] [Bug 2003588] Re: CVE 2022-4378 fix is in Kinetic, needed on Lunar
Because it is not production ready, We use the livecd uninstalled. Please make an exception for the kernel packages, Please just put the kinetic kernels on the lunar livecds, (And for all new) So we dont have to roll our own livecd just to smoke test a new version, So we dont get the avalanche of failures like our recent move to jammy. Without the kernel package I have not found it practical to try lunar (and all new) online at all. -- 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/2003588 Title: CVE 2022-4378 fix is in Kinetic, needed on Lunar Status in linux package in Ubuntu: Won't Fix Bug description: This and many other CVE's are still unfixed on Lunar. No sign of a tracking bug on Lunar Is there a reason the Kinetic kernel can't be pushed to lunar? Priority is high: https://ubuntu.com/security/CVE-2022-4378 Can the lunar livecd automatically get all linux package updates when they hit kinetic? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003640] [NEW] Integrate NVIDIA Grace kernel fixes for vGIC
Public bug reported: [Impact] To save the vgic LPI pending state with GICv4.1, the VPEs must all be unmapped from the ITSs so that the sGIC caches can be flushed. The opposite is done once the state is saved. This is all done by using the activate/deactivate irqdomain callbacks directly from the vgic code. Crutially, this is done without holding the irqdesc lock for the interrupts that represent the VPE. And these callbacks are changing the state of the irqdesc. What could possibly go wrong? If a doorbell fires while we are messing with the irqdesc state, it will acquire the lock and change the interrupt state concurrently. Since we don't hole the lock, curruption occurs in on the interrupt state. Oh well. While acquiring the lock would fix this (and this was Shanker's initial approach), this is still a layering violation we could do without. A better approach is actually to free the VPE interrupt, do what we have to do, and re-request it. It is more work, but this usually happens only once in the lifetime of the VM and we don't really care about this sort of overhead. The upstream maintainer acknowledged the bug, fixed the issue. and it will be available in v6.2. [Fixes] - single patch to address the race condition on VPE activation/deactivation ** Affects: linux-nvidia-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-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2003640 Title: Integrate NVIDIA Grace kernel fixes for vGIC Status in linux-nvidia-5.19 package in Ubuntu: New Bug description: [Impact] To save the vgic LPI pending state with GICv4.1, the VPEs must all be unmapped from the ITSs so that the sGIC caches can be flushed. The opposite is done once the state is saved. This is all done by using the activate/deactivate irqdomain callbacks directly from the vgic code. Crutially, this is done without holding the irqdesc lock for the interrupts that represent the VPE. And these callbacks are changing the state of the irqdesc. What could possibly go wrong? If a doorbell fires while we are messing with the irqdesc state, it will acquire the lock and change the interrupt state concurrently. Since we don't hole the lock, curruption occurs in on the interrupt state. Oh well. While acquiring the lock would fix this (and this was Shanker's initial approach), this is still a layering violation we could do without. A better approach is actually to free the VPE interrupt, do what we have to do, and re-request it. It is more work, but this usually happens only once in the lifetime of the VM and we don't really care about this sort of overhead. The upstream maintainer acknowledged the bug, fixed the issue. and it will be available in v6.2. [Fixes] - single patch to address the race condition on VPE activation/deactivation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-5.19/+bug/2003640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999406] Re: Update firmware for hwe/oem kernel migrations
This bug was fixed in the package linux-firmware - 20230120.gitbb2d42dc-0ubuntu1 --- linux-firmware (20230120.gitbb2d42dc-0ubuntu1) lunar; urgency=medium * Update firmware for hwe/oem kernel migrations (LP: #1999406) - [Packaging] scripts: add back list-lts-update-files * Miscellaneous Ubuntu changes - Rebase to upstream commit bb2d42dceff755623d6d59a32a743ccf87cbb6b9 Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - sr150 : Add NXP SR150 UWB firmware - amdgpu: updated aldebaran firmware for amd-5.4 - amdgpu: updated navi12 firmware for amd-5.4 - amdgpu: updated renoir firmware for amd-5.4 - amdgpu: updated navi14 firmware for amd-5.4 - amdgpu: updated arcture firmware for amd-5.4 - amdgpu: updated sienna cichlid firmware for amd-5.4 - amdgpu: updated green sardine firmware for amd-5.4 - amdgpu: updated navy flounder firmware for amd-5.4 - amdgpu: updated picasso firmware for amd-5.4 - amdgpu: updated vangogh firmware for amd-5.4 - amdgpu: updated dimgrey cavefish firmware for amd-5.4 - amdgpu: updated beige goby firmware for amd-5.4 - amdgpu: updated vega10 firmware for amd-5.4 - amdgpu: add DCN 3.2.0 firmware for amd-5.4 - amdgpu: add GC 11.0.0 firmware for amd-5.4 - amdgpu: add PSP 13.0.0 firmware for amd-5.4 - amdgpu: Add SDMA 6.0.0 firmware for amd-5.4 - amdgpu: add SMU 13.0.0 firmware for amd-5.4 - amdgpu: add VCN 4.0.0 firmware for amd-5.4 - amdgpu: updated PSP 13.0.5 firmware for amd-5.4 - amdgpu: updated vega20 firmware for amd-5.4 - amdgpu: updated GC 10.3.7 RLC firmware for amd-5.4 - amdgpu: updated PSP 13.0.8 firmware for amd-5.4 - amdgpu: updated raven firmware for amd-5.4 - amdgpu: updated raven2 firmware for amd-5.4 - amdgpu: updated yellow carp firmware for amd-5.4 - amdgpu: updated navi10 firmware for amd-5.4 - rtw89: 8852c: update fw to v0.27.56.8 - rtw89: 8852c: update fw to v0.27.56.9 - qca: Update firmware files for BT chip WCN6750 - cxgb4: Update firmware to revision 1.27.1.0 - linux-firmware: update firmware for mediatek bluetooth chip (MT7922) - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7922 WiFi device - linux-firmware: update firmware for MT7921 WiFi device - amdgpu: update copyright date for LICENSE.amdgpu - amdgpu: Update renoir PSP firmware - amdgpu: update renoir DMCUB firmware - iwlwifi: update 9000-family firmwares to core75-47 - iwlwifi: add new FWs from core75-47 release - iwlwifi: update cc/Qu/QuZ firmwares for core76-35 release - iwlwifi: add new FWs from core76-35 release - amdgpu: update GC11.0.0 firmware from amd-5.4 - amdgpu: update PSP13.0.0 firmware from amd-5.4 - amdgpu: update SDMA6.0.0 firmware from amd-5.4 - amdgpu: update SMU13.0.0 firmware from amd-5.4 - amdgpu: update VCN4.0.0 firmware from amd-5.4 - amdgpu: add DCN3.2.1 firmware from amd-5.4 - amdgpu: add GC11.0.2 firmware from amd-5.4 - amdgpu: add PSP13.0.7 firmware from amd-5.4 - amdgpu: add SDMA6.0.2 firmware from amd-5.4 - amdgpu: add SMU13.0.7 firmware from amd-5.4 - amdgpu: add VCN4.0.4 firmware from amd-5.4 - QCA: Add Bluetooth firmware for QCA2066 - rtw89: 8852c: update fw to v0.27.56.10 - qcom: add firmware files for Adreno A200 - brcm: add configuration files for CyberTan WC121 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - amdgpu: update vangogh firmware - linux-firmware: update firmware for mediatek bluetooth chip (MT7921) - linux-firmware: update firmware for MT7921 WiFi device -- Juerg Haefliger Fri, 20 Jan 2023 17:21:10 +0100 ** Changed in: linux-firmware (Ubuntu Lunar) Status: Fix Committed => Fix Released -- 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/1999406 Title: Update firmware for hwe/oem kernel migrations Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Ja
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
It works in 5.15.0-56-generic. It looks like you included https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/xen-netback?h=linux-5.15.y&id=0fe29bd92594a747a2561589bd452c259451929e to fix CVE-2022-3643. Unfortunately, that commit had issues and needed a fixup: https://lore.kernel.org/xen-devel/681773dd-6264-63ac-a3b5-a9182b9e0...@suse.com/T/#t The 5.15.y version of that patch is in stable here: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/xen-netback?h=linux-5.15.y&id=dec5abd91abc700dcb869f8056bc1f48d045ff97 Looking at http://launchpadlibrarian.net/644373416/linux_5.15.0-56.62_5.15.0-58.64.diff.gz , it looks like dec5abd91abc700dcb869f8056bc1f48d045ff97 is 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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Incomplete Bug description: With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988797] Re: pcieport 0000:00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
Hi, I am facing this problem on ubuntu 22.04, kernel version 5.15. I do not understand which kernel version should I install to get rid of this issue. On Wed, 18 Jan 2023, 3:57 pm Ubuntu Kernel Bot, <1988...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-aws/5.15.0-1029.33 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy' to 'verification-done-jammy'. If the > problem still exists, change the tag 'verification-needed-jammy' to > 'verification-failed-jammy'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-aws > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1988797 > > Title: > pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non- > Fatal), type=Transaction Layer, (Requester ID) > > Status in HWE Next: > Fix Committed > Status in OEM Priority Project: > New > Status in linux package in Ubuntu: > Confirmed > Status in linux-oem-5.14 package in Ubuntu: > Invalid > Status in linux-oem-5.17 package in Ubuntu: > Invalid > Status in linux-oem-6.0 package in Ubuntu: > Invalid > Status in linux source package in Jammy: > Fix Released > Status in linux-oem-5.14 source package in Jammy: > Invalid > Status in linux-oem-5.17 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-5.14 source package in Kinetic: > Invalid > Status in linux-oem-5.17 source package in Kinetic: > Invalid > Status in linux-oem-6.0 source package in Kinetic: > Invalid > > Bug description: > My kernel log periodically bursts with: > > [10405.588287] pcieport :00:1b.0: PCIe Bus Error: > severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) > [10405.593393] pcieport :00:1b.0: device [8086:7ac4] error > status/mask=0010/4000 > [10405.598564] pcieport :00:1b.0:[20] UnsupReq > (First) > [10405.603829] pcieport :00:1b.0: AER: TLP Header: 3400 > 0152 > [10405.609563] pcieport :00:1b.0: PCIe Bus Error: > severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) > [10405.614959] pcieport :00:1b.0: device [8086:7ac4] error > status/mask=0010/4000 > [10405.620296] pcieport :00:1b.0:[20] UnsupReq > (First) > [10405.625554] pcieport :00:1b.0: AER: TLP Header: 3400 > 0152 > [10405.631180] pcieport :00:1b.0: PCIe Bus Error: > severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) > [10405.636495] pcieport :00:1b.0: device [8086:7ac4] error > status/mask=0010/4000 > [10405.641867] pcieport :00:1b.0:[20] UnsupReq > (First) > [10405.647169] pcieport :00:1b.0: AER: TLP Header: 3400 > 0152 > [10405.652919] pcieport :00:1b.0: PCIe Bus Error: > severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) > [10405.658369] pcieport :00:1b.0: device [8086:7ac4] error > status/mask=0010/4000 > [10405.663803] pcieport :00:1b.0:[20] UnsupReq > (First) > [10405.669263] pcieport :00:1b.0: AER: TLP Header: 3400 > 0152 > [10405.675130] pcieport :00:1b.0: PCIe Bus Error: > severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) > [10405.680699] pcieport :00:1b.0: device [8086:7ac4] error > status/mask=0010/4000 > [10405.686267] pcieport :00:1b.0:[20] UnsupReq > (First) > [10405.691759] pcieport :00:1b.0: AER: TLP Header: 3400 > 0152 > > This has happened even since I got the machine. It also happened with > 5.15. > > ProblemType: Bug > DistroRelease: Ubuntu 22.10 > Package: linux-image-5.19.0-15-generic 5.19.0-15.15 > ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 > Uname: Linux 5.19.0-15-generic x86_64 > ApportVersion: 2.23.0-0ubuntu1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: dan2477 F wireplumber >/dev/snd/seq:dan2474 F pipewire > CRDA: N/A > CasperMD5CheckResult: pass > Date: Tue Sep 6 13:52:35 2022 > InstallationDate: Installed on 2022-07-20 (47 days ago) > InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220718) > MachineType: Intel(R) Client Systems NUC12DCMi7 > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-gener
[Kernel-packages] [Bug 2002537] Re: kernel 5.19.0-xx-generic fails to install
** Summary changed: - kernel 5.19.0-xx-generic fails to install due to inexisting dependency version zlib1g(>=1:1.2.3.3) + kernel 5.19.0-xx-generic fails to install -- 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/2002537 Title: kernel 5.19.0-xx-generic fails to install Status in linux package in Ubuntu: Confirmed Bug description: Want to install that kernel from kinetic-proposed onto an amd64 Lunar mate flavor; but got a faulty installation about it: Préparation du dépaquetage de .../0-linux-modules-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-modules-5.19.0-30-generic (5.19.0-30.31) ... Sélection du paquet linux-image-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../1-linux-image-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-image-5.19.0-30-generic (5.19.0-30.31) ... Sélection du paquet linux-modules-extra-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../2-linux-modules-extra-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-modules-extra-5.19.0-30-generic (5.19.0-30.31) ... Préparation du dépaquetage de .../3-linux-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Préparation du dépaquetage de .../4-linux-image-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-image-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Sélection du paquet linux-headers-5.19.0-30 précédemment désélectionné. Préparation du dépaquetage de .../5-linux-headers-5.19.0-30_5.19.0-30.31_all.deb ... Dépaquetage de linux-headers-5.19.0-30 (5.19.0-30.31) ... Sélection du paquet linux-headers-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../6-linux-headers-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-headers-5.19.0-30-generic (5.19.0-30.31) ... Préparation du dépaquetage de .../7-linux-headers-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-headers-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Paramétrage de linux-modules-5.19.0-30-generic (5.19.0-30.31) ... Paramétrage de linux-headers-5.19.0-30 (5.19.0-30.31) ... Paramétrage de linux-modules-extra-5.19.0-30-generic (5.19.0-30.31) ... Paramétrage de linux-image-5.19.0-30-generic (5.19.0-30.31) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.19.0-30-generic I: /boot/initrd.img is now a symlink to initrd.img-5.19.0-30-generic Paramétrage de linux-headers-5.19.0-30-generic (5.19.0-30.31) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.19.0-30-generic efi_runtime.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 4.8.0. We will avoid installing for future kernels above 4.8.0. You may override by specifying --force. Error! Installation aborted. 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: erreur de traitement du paquet linux-headers-5.19.0-30-generic (--configure) : installed linux-headers-5.19.0-30-generic package post-installation script subprocess returned error exit status 1 Paramétrage de linux-image-generic (5.19.0.30.27) ... dpkg: des problèmes de dépendances empêchent la configuration de linux-headers-generic : linux-headers-generic dépend de linux-headers-5.19.0-30-generic; cependant : Le paquet linux-headers-5.19.0-30-generic n'est pas encore configuré. dpkg: erreur de traitement du paquet linux-headers-generic (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. dpkg: des problèmes de dépendances empêchent la configuration de linux-generic : linux-generic dépend de linux-headers-generic (= 5.19.0.30.27); cependant : Le paquet linux-headers-generic n'est pas encore configuré. dpkg: erreur de traitement du paquet linux-generic (--configure) : problèmes de dépendances - laissé non configuré Traitement des actions différées (« triggers ») pour linux-image-5.19.0-30-generic (5.19.0-30.31) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.19.0-30-generic efi_runtime.ko: Running module version sanity check. Module has been obsoleted due
[Kernel-packages] [Bug 2002537] Re: kernel 5.19.0-xx-generic fails to install due to inexisting dependency version zlib1g(>=1:1.2.3.3)
The latest Lunar zlib1g version is 1.2.11 (main) and 1.2.13 (proposed) ** Summary changed: - kernel 5.19.0-30-generic fails to install due to efi_runtime.ko + kernel 5.19.0-xx-generic fails to install due to inexisting dependency version zlib1g(>=1:1.2.3.3) ** Description changed: Want to install that kernel from kinetic-proposed onto an amd64 Lunar mate flavor; but got a faulty installation about it: - Préparation du dépaquetage de .../0-linux-modules-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... + Préparation du dépaquetage de .../0-linux-modules-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-modules-5.19.0-30-generic (5.19.0-30.31) ... Sélection du paquet linux-image-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../1-linux-image-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-image-5.19.0-30-generic (5.19.0-30.31) ... Sélection du paquet linux-modules-extra-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../2-linux-modules-extra-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-modules-extra-5.19.0-30-generic (5.19.0-30.31) ... Préparation du dépaquetage de .../3-linux-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Préparation du dépaquetage de .../4-linux-image-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-image-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Sélection du paquet linux-headers-5.19.0-30 précédemment désélectionné. Préparation du dépaquetage de .../5-linux-headers-5.19.0-30_5.19.0-30.31_all.deb ... Dépaquetage de linux-headers-5.19.0-30 (5.19.0-30.31) ... Sélection du paquet linux-headers-5.19.0-30-generic précédemment désélectionné. Préparation du dépaquetage de .../6-linux-headers-5.19.0-30-generic_5.19.0-30.31_amd64.deb ... Dépaquetage de linux-headers-5.19.0-30-generic (5.19.0-30.31) ... Préparation du dépaquetage de .../7-linux-headers-generic_5.19.0.30.27_amd64.deb ... Dépaquetage de linux-headers-generic (5.19.0.30.27) sur (5.19.0.28.25) ... Paramétrage de linux-modules-5.19.0-30-generic (5.19.0-30.31) ... Paramétrage de linux-headers-5.19.0-30 (5.19.0-30.31) ... Paramétrage de linux-modules-extra-5.19.0-30-generic (5.19.0-30.31) ... Paramétrage de linux-image-5.19.0-30-generic (5.19.0-30.31) ... I: /boot/vmlinuz is now a symlink to vmlinuz-5.19.0-30-generic I: /boot/initrd.img is now a symlink to initrd.img-5.19.0-30-generic Paramétrage de linux-headers-5.19.0-30-generic (5.19.0-30.31) ... /etc/kernel/header_postinst.d/dkms: - * dkms: running auto installation service for kernel 5.19.0-30-generic + * dkms: running auto installation service for kernel 5.19.0-30-generic efi_runtime.ko: Running module version sanity check. Module has been obsoleted due to being included in kernel 4.8.0. We will avoid installing for future kernels above 4.8.0. You may override by specifying --force. Error! Installation aborted. Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. -...fail! + ...fail! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 dpkg: erreur de traitement du paquet linux-headers-5.19.0-30-generic (--configure) : - installed linux-headers-5.19.0-30-generic package post-installation script subprocess returned error exit status 1 + installed linux-headers-5.19.0-30-generic package post-installation script subprocess returned error exit status 1 Paramétrage de linux-image-generic (5.19.0.30.27) ... dpkg: des problèmes de dépendances empêchent la configuration de linux-headers-generic : - linux-headers-generic dépend de linux-headers-5.19.0-30-generic; cependant : - Le paquet linux-headers-5.19.0-30-generic n'est pas encore configuré. + linux-headers-generic dépend de linux-headers-5.19.0-30-generic; cependant : + Le paquet linux-headers-5.19.0-30-generic n'est pas encore configuré. dpkg: erreur de traitement du paquet linux-headers-generic (--configure) : - problèmes de dépendances - laissé non configuré + problèmes de dépendances - laissé non configuré Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. - Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. - dpkg: des problèmes de dépendances empêchent la configuration de linux-generic : - linux-generic dépend de linux-headers-generic (= 5.19.0.30.27); cependant : - Le paquet linux-headers-generic n'est pas encore configuré. +
