[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
same worked perfectly 18.04 gone 19.10 this week and now i have to keep manually importing then restarting mysql service because it could not access its data ,, -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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 1850130] Re: zpools fail to import after reboot on fresh install of eoan
from what I can see is that its trying to do importing before the disks have been mapped because /etc/multipath.conf is being read just after zfs failed Dec 11 23:04:57 aio systemd[1]: Started Mount ZFS filesystems. Dec 11 23:04:57 aio systemd[1]: Starting Mount ZFS filesystems... Dec 11 23:04:57 aio systemd[1]: Reached target ZFS pool import target. Dec 11 23:04:57 aio systemd[1]: Failed to start Import ZFS pools by cache file. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Failed with result 'exit-code'. Dec 11 23:04:57 aio systemd[1]: zfs-import-cache.service: Main process exited, code=exited, status=1/FAILURE Dec 11 23:04:57 aio zpool[3622]: a backup source. Dec 11 23:04:57 aio zpool[3622]: Destroy and re-create the pool from Dec 11 23:04:57 aio zpool[3622]: cannot import 'ZFS3WAY': no such pool or dataset Dec 11 23:04:57 aio multipathd[3627]: path checkers start up Dec 11 23:04:57 aio multipathd[3627]: read /etc/multipath.conf Dec 11 23:04:57 aio multipathd[3627]: start up Dec 11 23:04:57 aio kernel: rdac: device handler registered Dec 11 23:04:57 aio kernel: emc: device handler registered Dec 11 23:04:57 aio kernel: alua: device handler registered Dec 11 23:04:57 aio systemd[1]: Starting Import ZFS pools by cache file... Dec 11 23:04:57 aio systemd[1]: Started Install ZFS kernel module. Dec 11 23:04:57 aio systemd[1]: Starting Device-Mapper Multipath Device Controller... Dec 11 23:04:57 aio systemd[1]: Starting Install ZFS kernel module... Dec 11 23:04:57 aio systemd[1]: Started udev Wait for Complete Device Initialization. Dec 11 23:04:57 aio kernel: ZFS: Loaded module v0.8.2-1, ZFS pool version 5000, ZFS filesystem version 5 Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Dec 11 23:04:57 aio systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Dec 11 23:04:57 aio systemd[1]: Starting LVM event activation on device 9:0... Dec 11 23:04:57 aio systemd[1]: Created slice system-lvm2\x2dpvscan.slice. -- 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/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in zfs-linux package in Ubuntu: Confirmed Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1850130/+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 1823037] Re: amd_iommu possible data corruption
Running Ubuntu 19.10 5.4.3-050403-generic Ryzen 3900x GA x570 UD mainboard DDR 3200 , I have been getting data corruption on my 4x SSD on Sata ports ( btrfs/ext4) disks running from my LSI / Avago SAS Raid 9302-16e 12Gb/s PCIe 3.0 controller (btrfs/EXT4) and all my disks running from my HBA (zfs) I started off with PCI-e gen 4 dropped it to gen 3 as that is what my raid controller is as not using a NVMe yet all 64 gig Memory test's good and HDD's test good if tested individually anymore than 8 being accessed at a time they fail being 3 separate controllers and multiple disks I am leading towards a software issue and I remember having data issues before when I had my a10-5800k and that was solved by disabling iommu , I had no issues with this setup while running my intel 4790k -- 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/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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 1823037] Re: amd_iommu possible data corruption
seems I finally found the real issue in the bios of my Gigabyte x570 UD , when I have 4G encode option enabled I have silent data corruption ( or at least if its enabled along side with IOMMU ) I need to make another array that I can kill to keep testing with , but I can literally go into the bios enable 4G reboot then start a zfs scrub and instantly have crc errors pop up everywhere , reboot disable do a scrub and it's all good , seems to only kick in when multiple disks are in use In the past ~2012 with my Gigabyte F2A85x-UP4 AMD A10 5800k I also had data issues with IOMMU enabled ... never had issues with my intel i7 4790k build , so it could very well just be AMD IOMMU that is causing it for me -- 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/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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 1626731]
[366338.166585] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41 [366338.166652] usbcore: registered new interface driver uvcvideo [366338.166652] USB Video Class driver (1.1.1) [366357.978516] usbcore: deregistering interface driver uvcvideo [366377.298295] usb 5-4: USB disconnect, device number 16 [366382.517118] usb 5-4: new high-speed USB device number 17 using xhci_hcd [366382.539011] usb 5-4: config 1 interface 1 altsetting 0 endpoint 0x82 has wMaxPacketSize 0, skipping [366382.539015] usb 5-4: New USB device found, idVendor=eb1a, idProduct=299f, bcdDevice= 6.09 [366382.539017] usb 5-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [366382.596668] uvcvideo: Found UVC 1.00 device (eb1a:299f) [366382.601384] uvcvideo: No streaming interface found for terminal 2. [366382.601390] uvcvideo 5-4:1.0: Entity type for entity Extension 4 was not initialized! [366382.601395] uvcvideo 5-4:1.0: Entity type for entity Processing 3 was not initialized! [366382.601397] uvcvideo 5-4:1.0: Entity type for entity Camera 1 was not initialized! [366382.601536] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input42 [366382.601624] usbcore: registered new interface driver uvcvideo [366382.601625] USB Video Class driver (1.1.1) 5.4.11-050411-generic camera worked pre kernel 4's and before going from Ubuntu 18 - 19 -- 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/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1626731/+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 1628238]
[366338.166585] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input41 [366338.166652] usbcore: registered new interface driver uvcvideo [366338.166652] USB Video Class driver (1.1.1) [366357.978516] usbcore: deregistering interface driver uvcvideo [366377.298295] usb 5-4: USB disconnect, device number 16 [366382.517118] usb 5-4: new high-speed USB device number 17 using xhci_hcd [366382.539011] usb 5-4: config 1 interface 1 altsetting 0 endpoint 0x82 has wMaxPacketSize 0, skipping [366382.539015] usb 5-4: New USB device found, idVendor=eb1a, idProduct=299f, bcdDevice= 6.09 [366382.539017] usb 5-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [366382.596668] uvcvideo: Found UVC 1.00 device (eb1a:299f) [366382.601384] uvcvideo: No streaming interface found for terminal 2. [366382.601390] uvcvideo 5-4:1.0: Entity type for entity Extension 4 was not initialized! [366382.601395] uvcvideo 5-4:1.0: Entity type for entity Processing 3 was not initialized! [366382.601397] uvcvideo 5-4:1.0: Entity type for entity Camera 1 was not initialized! [366382.601536] input: UVC Camera (eb1a:299f) as /devices/pci:00/:00:08.1/:0d:00.3/usb5/5-4/5-4:1.0/input/input42 [366382.601624] usbcore: registered new interface driver uvcvideo [366382.601625] USB Video Class driver (1.1.1) 5.4.11-050411-generic camera worked pre kernel 4's and before going from Ubuntu 18 - 19 -- 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/1628238 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: [5.525445] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [5.525452] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [5.525456] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-17-lowlatency 4.8.0-17.19 ProcVersionSignature: Ubuntu 4.8.0-17.19-lowlatency 4.8.0-rc7 Uname: Linux 4.8.0-17-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2084 F...m pulseaudio /dev/snd/controlC0: caravena 2084 F pulseaudio CurrentDesktop: GNOME Date: Tue Sep 27 15:21:42 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (429 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-lowlatency root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-lowlatency N/A linux-backports-modules-4.8.0-17-lowlatency N/A linux-firmware 1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1628238/+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 1689390] Re: Kernel 4.11 update
DKMS make.log for spl-0.6.5.9 for kernel 4.11.0-041100-generic (x86_64) Sun 14 May 03:28:51 AEST 2017 make: *** No targets specified and no makefile found. Stop. -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: New Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb Seleccionando el paquete linux-headers-4.11.0-041100-generic previamente no seleccionado. (Leyendo la base de datos ... 407178 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Desempaquetando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/nvidia-304/304.135/build/make.log for more information. I have attached the make.log file. How could I make the update? Thank you very much in advance Kind regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1689390/+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 1689390] Re: Kernel 4.11 update
Distribution: Ubuntu 17.04 System architecture: amd64 Running kernel: 4.10.12-041012-generic Kernel version: 4.10.12-041012-generic Using cache directory: /home/aio/.cache/ukuu Found installed: 4.6.7-040607.201608160432 Found installed: 4.9.0-040900.201612111631 Found installed: 4.8.17-040817.201701090438 Found installed: 1.0.amdgpu Found installed: 4.10.6-041006.201703260832 Found installed: 4.8.7-040807.201611101131 Found installed: 4.7.3-040703.201609070334 Found installed: 4.2.8-040208.201512150620 Found installed: 4.10.0.21.23 Found installed: 4.10.0-20.22 Found installed: 4.10.12-041012.201704210512 Found installed: 4.10.0-21.23 Found installed: 4.7.2-040702.201608201334 Found installed: 4.10.8-041008.201703310531 Downloading: 'linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb'... aria2c version: 1.30.0 OK Downloading: 'linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb'... 48.6 MB / 50.1 MB, 850.9 KB/s (1s) (ukuu:8557): GLib-GIO-CRITICAL **: g_output_stream_close: assertion 'G_IS_OUTPUT_STREAM (stream)' failed (ukuu:8557): GLib-GIO-CRITICAL **: g_output_stream_clear_pending: assertion 'G_IS_OUTPUT_STREAM (stream)' failed OK Downloading: 'linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb'... E: Error removing file /tmp/ukuu/r0Bjkbx6/vYRr1oZC/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb: No such file or directory E: Failed to move file: '/tmp/ukuu/r0Bjkbx6/vYRr1oZC/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb' → '/home/aio/.cache/ukuu/v4.11/amd64/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb' OK Preparing to install 'v4.11' Selecting previously unselected package linux-headers-4.11.0-041100-generic. (Reading database ... 800276 files and directories currently installed.) Preparing to unpack linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Unpacking linux-headers-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Selecting previously unselected package linux-image-4.11.0-041100-generic. Preparing to unpack linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb ... Examining /etc/kernel/preinst.d/ Done. Unpacking linux-image-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Selecting previously unselected package linux-headers-4.11.0-041100. Preparing to unpack linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Unpacking linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Setting up linux-image-4.11.0-041100-generic (4.11.0-041100.201705041534) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.11.0-041100-generic /boot/vmlinuz-4.11.0-041100-generic configure: error: unknown ERROR (dkms apport): kernel package linux-headers-4.11.0-041100-generic is not supported Error! Bad return status for module build on kernel: 4.11.0-041100-generic (x86_64) Consult /var/lib/dkms/spl/0.6.5.9/build/make.log for more information. -- 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/1689390 Title: Kernel 4.11 update Status in dkms package in Ubuntu: New Bug description: I was trying to update my Ubuntu 16.04 with the last kernel version. My current version is uname -r 4.8.8-040808-generic And I would like to update the kernel to the new 4.11. I downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/ the files linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb linux-headers-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb to a folder, there I executed the first one without errors, but on the second one I have a problem. This is the log generated on the installation... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dpkg -i linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb Seleccionando el paquete linux-headers-4.11.0-041100 previamente no seleccionado. (Leyendo la base de datos ... 389575 ficheros o directorios instalados actualmente.) Preparando para desempaquetar linux-headers-4.11.0-041100_4.11.0-041100.201705041534_all.deb ... Desempaquetando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... Configurando linux-headers-4.11.0-041100 (4.11.0-041100.201705041534) ... root@Ratrichus-HP-ENVY-17:/home/alucasr/Descargas/SW/Kernels# dp
