[Kernel-packages] [Bug 1754584] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1754584/+attachment/5074099/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev samba
[Kernel-packages] [Bug 1754584] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1754584/+attachment/5074102/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambash
[Kernel-packages] [Bug 1754584] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1754584/+attachment/5074091/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _M
[Kernel-packages] [Bug 1754584] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1754584/+attachment/5074094/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev s
[Kernel-packages] [Bug 1754584] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1754584/+attachment/5074093/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj1878 F pulseaudio /dev/snd/controlC0: powersj1878 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 RelatedPackageVersions: linux-restricted-modules-4.15.0-12-generic N/A linux-backports-modules-4.15.0-12-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare
[Kernel-packages] [Bug 1754584] Re: system process hung on container stop/delete
apport information ** Tags added: apport-collected ** Description changed: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: powersj1878 F pulseaudio + /dev/snd/controlC0: powersj1878 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb + InstallationDate: Installed on 2018-02-19 (17 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) + Lsusb: + Bus 001 Device 002: ID 8087:8001 Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 20BSCTO1WW + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic root=/dev/mapper/ubuntu--vg-root ro + ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-12-generic N/A + linux-backports-modules-4.15.0-12-generic N/A + linux-firmware 1.172 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: bionic + Uname: Linux 4.15.0-12-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 09/13/2017 + dmi.bios.vendor: LENOVO + dmi.bios.version: N14ET42W (1.20 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20BSCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0E50512 STD + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvn
[Kernel-packages] [Bug 1754584] Re: system process hung on container stop/delete
Since I need zfs I did mark as kernel-fixed-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/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754584/+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 1754584] Re: system process hung on container stop/delete
> Did this issue start happening after an update/upgrade? > Was there a prior kernel version where you were not having this particular > problem? This was the first time I have attempted this so I do not know about previous kernels. After installing 4.16-rc4 I could not re-attempt to reproduce because the zfs modules are not present: modprobe: FATAL: Module zfs not found in directory /lib/modules/4.16.0-041600rc4-generic I changed lxd to use btrfs instead of zfs and attempted to reproduce and was not able to. ** Tags added: kernel-fixed-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/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754584/+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 1754584] [NEW] system process hung on container stop/delete
Public bug reported: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic ** Summary changed: - stack trace on system process hung + system process hung on container stop/delete -- 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/1754584 Title: system process hung on container stop/delete Status in linux package in Ubuntu: Confirmed Bug description: Summary: On a Bionic system running 4.15.0-10-generic, after attempting to build libaio in a Bionic daily container I cannot stop or delete the container. dmesg shows a variety of hung tasks Steps to Reproduce: Use the following script and watch for the the hang. At that point attempt to stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/ Originally filed against LXD: https://github.com/lxc/lxd/issues/4314 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2414 F pulseaudio /dev/snd/controlC0: powersj2414 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 9 09:19:11 2018 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic root=/dev/ma
[Kernel-packages] [Bug 1736770] Re: debian-installer/main-menu changes priority
** Changed in: debconf (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Re: debian-installer/main-menu changes priority
I take this back, it is still an issue with the amd64 ISO: https://paste.ubuntu.com/26178135/ -- 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/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Re: debian-installer/main-menu changes priority
It looks like the installer is getting further now, however, failing on kernel package install: https://paste.ubuntu.com/26166359/ Shall we close this bug and open a new one for that issue? -- 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/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Re: debian-installer/main-menu changes priority
Here is syslog from booting using the commands in the bug description: https://paste.ubuntu.com/26127285/ This is another boot with DEBCONF_DEBUG=developer enabled: https://paste.ubuntu.com/26127333/ -- 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/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: New Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Re: debian-installer/main-menu changes priority
@cyphermox, thanks for looking. I added Linux to get their look at it as it does look like the kernel rev changed between the last successful ISO and the current failing ISO: Last Successful ISO had: /pool/main/l/linux/linux-image-4.13.0-16-generic_4.13.0-16.19_amd64.deb Currently failing ISO has: /pool/main/l/linux/linux-image-4.13.0-17-generic_4.13.0-17.20_amd64.deb ** 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/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: New Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1551747] Re: ubuntu-fan causes issues during network configuration
** Changed in: cloud-init Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1551747 Title: ubuntu-fan causes issues during network configuration Status in cloud-init: Invalid Status in Snappy: Confirmed Status in ubuntu-fan package in Ubuntu: Fix Released Status in ubuntu-fan source package in Xenial: Fix Released Status in ubuntu-fan source package in Yakkety: Fix Released Bug description: it seems that ubuntu-fan is causing issues with network configuration. On 16.04 daily image: root@localhost:~# snappy list NameDate Version Developer canonical-pi2 2016-02-02 3.0 canonical canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical ubuntu-core 2016-02-22 16.04.0-10.armhf canonical I see this when I'm activating a wifi card on a raspberry pi 2. root@localhost:~# ifdown wlan0 ifdown: interface wlan0 not configured root@localhost:~# ifup wlan0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/wlan0/c4:e9:84:17:31:9b Sending on LPF/wlan0/c4:e9:84:17:31:9b Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e) DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e) DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 (xid=0x5ec9c081) DHCPOFFER of 192.168.0.170 from 192.168.0.251 DHCPACK of 192.168.0.170 from 192.168.0.251 RTNETLINK answers: File exists bound to 192.168.0.170 -- renewal in 17145 seconds. run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1 Failed to bring up wlan0. === [Impact] Installing ubuntu-fan can trigger error messages when initialising with no fan configuration. [Test Case] As above. [Regression Potential] Low, suppresses errorneous error messages. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1551747/+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 1694531] Re: 17.10 Install Fails to Start
Confirmed that with the amd64 ISO dated June 2nd this is no longer an issue. The i386 and ppc64el ISOs passed testing this morning, amd64 did not, but it appears to have ran with the June 1 ISO still. I have kicked off a run to download the ISO again (June 2) and try again. -- 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/1694531 Title: 17.10 Install Fails to Start Status in linux package in Ubuntu: Triaged Status in ubiquity package in Ubuntu: New Status in linux source package in Artful: Triaged Status in ubiquity source package in Artful: New Bug description: As of May 25, 2017 it appears the Ubuntu 17.10 server ISOs have failed to start an install. Trying other options like 'rescue a broken system' or 'Install MAAS [Region|Rack] Controller' have the same issue. Expected results: The Ubuntu Server installer menu system should have started asking for a language or keyboard mapping. Steps to reproduce: 1. Download an ISO dated after May 24 (server or desktop) [1] 2. Boot system to ISO 3. Choose language 4. Select 'Install Ubuntu Server' 5. Black screen will flicker with blinking cursor in bottom left Investigation: Running 'Check the disk for defects' finds nothing wrong. The last few syslog entries do not give any glaring issues: acpiphp: Slot [30] registered acpiphp: Slot [31] registered PCI host brdige to bus :00 random: crng init done: 0x max_cycles: 0x39c5 [1] http://cdimage.ubuntu.com/ubuntu-server/daily/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694531/+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 1694531] Re: 17.10 Install Fails to Start
@brad-figg, Can you give the md5sum of the file you used sucessfully? This is what I am using: 46eb85873d18b45badf86c3e8618c2ff dated May 30, 2017 from http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ Note I originally thought this was desktop and server due to Dean's comment's, but like him I verified Desktop is working as expected and I am only seeing this on Server. -- 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/1694531 Title: 17.10 Install Fails to Start Status in linux package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: New Bug description: As of May 25, 2017 it appears the Ubuntu 17.10 server ISOs have failed to start an install. Trying other options like 'rescue a broken system' or 'Install MAAS [Region|Rack] Controller' have the same issue. Expected results: The Ubuntu Server installer menu system should have started asking for a language or keyboard mapping. Steps to reproduce: 1. Download an ISO dated after May 24 (server or desktop) [1] 2. Boot system to ISO 3. Choose language 4. Select 'Install Ubuntu Server' 5. Black screen will flicker with blinking cursor in bottom left Investigation: Running 'Check the disk for defects' finds nothing wrong. The last few syslog entries do not give any glaring issues: acpiphp: Slot [30] registered acpiphp: Slot [31] registered PCI host brdige to bus :00 random: crng init done: 0x max_cycles: 0x39c5 [1] http://cdimage.ubuntu.com/ubuntu-server/daily/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694531/+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 1694531] Re: 17.10 Install Fails to Start
This is during an install and unable to run apport-collect. ** Description changed: - As of May 25, 2017 it appears the Ubuntu 17.10 server and desktop ISOs - have failed to start an install. Trying other options like 'rescue a - broken system' or 'Install MAAS [Region|Rack] Controller' have the same - issue. + As of May 25, 2017 it appears the Ubuntu 17.10 server ISOs have failed + to start an install. Trying other options like 'rescue a broken system' + or 'Install MAAS [Region|Rack] Controller' have the same issue. Expected results: The Ubuntu Server installer menu system should have started asking for a language or keyboard mapping. Steps to reproduce: 1. Download an ISO dated after May 24 (server or desktop) [1] 2. Boot system to ISO 3. Choose language 4. Select 'Install Ubuntu Server' 5. Black screen will flicker with blinking cursor in bottom left Investigation: Running 'Check the disk for defects' finds nothing wrong. The last few syslog entries do not give any glaring issues: acpiphp: Slot [30] registered acpiphp: Slot [31] registered PCI host brdige to bus :00 random: crng init done: 0x max_cycles: 0x39c5 [1] http://cdimage.ubuntu.com/ubuntu-server/daily/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: artful -- 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/1694531 Title: 17.10 Install Fails to Start Status in linux package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: New Bug description: As of May 25, 2017 it appears the Ubuntu 17.10 server ISOs have failed to start an install. Trying other options like 'rescue a broken system' or 'Install MAAS [Region|Rack] Controller' have the same issue. Expected results: The Ubuntu Server installer menu system should have started asking for a language or keyboard mapping. Steps to reproduce: 1. Download an ISO dated after May 24 (server or desktop) [1] 2. Boot system to ISO 3. Choose language 4. Select 'Install Ubuntu Server' 5. Black screen will flicker with blinking cursor in bottom left Investigation: Running 'Check the disk for defects' finds nothing wrong. The last few syslog entries do not give any glaring issues: acpiphp: Slot [30] registered acpiphp: Slot [31] registered PCI host brdige to bus :00 random: crng init done: 0x max_cycles: 0x39c5 [1] http://cdimage.ubuntu.com/ubuntu-server/daily/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694531/+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 1694531] Re: 17.10 Install Fails to Start
Here is a list of udeb differences between the versions: https://paste.ubuntu.com/24718580/ Because this is occurring before the install, the udeb and kernel on the system are what I suspect to be the root cause. I'll add the kernel to this defect. ** 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/1694531 Title: 17.10 Install Fails to Start Status in linux package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: As of May 25, 2017 it appears the Ubuntu 17.10 server and desktop ISOs have failed to start an install. Trying other options like 'rescue a broken system' or 'Install MAAS [Region|Rack] Controller' have the same issue. Expected results: The Ubuntu Server installer menu system should have started asking for a language or keyboard mapping. Steps to reproduce: 1. Download an ISO dated after May 24 (server or desktop) [1] 2. Boot system to ISO 3. Choose language 4. Select 'Install Ubuntu Server' 5. Black screen will flicker with blinking cursor in bottom left Investigation: Running 'Check the disk for defects' finds nothing wrong. The last few syslog entries do not give any glaring issues: acpiphp: Slot [30] registered acpiphp: Slot [31] registered PCI host brdige to bus :00 random: crng init done: 0x max_cycles: 0x39c5 [1] http://cdimage.ubuntu.com/ubuntu-server/daily/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694531/+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 1499869] Re: maas wily deployment to HP Proliant m400 arm64 server cartridge fails
** Changed in: cloud-init Status: Confirmed => 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/1499869 Title: maas wily deployment to HP Proliant m400 arm64 server cartridge fails Status in cloud-init: Fix Released Status in curtin: Invalid Status in cloud-init package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Vivid: Fix Released Status in cloud-init source package in Wily: Fix Released Status in linux source package in Wily: Fix Released Bug description: This is the error seen on the console: [ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin [ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))] [ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds [ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404] This times out eventually and the node is left at the login prompt. I can install wily via netboot without issue and some time back, wily was deployable to this node from MAAS. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1499869/+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 1627875] Re: Yakkety server Beta install fails in a virtual client with UEFI bios
** Changed in: linux (Ubuntu Yakkety) Importance: Undecided => Critical -- 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/1627875 Title: Yakkety server Beta install fails in a virtual client with UEFI bios Status in Ubuntu Manual Tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: Using Virt-manager the Beta2 ISO fails to boot when a UEFI BIOS is selected. 4GB RAM, 8 CPUs. Nothing appears on the console after the Tiancore splash screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1627875/+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 1625675] Re: Trusty 'linux-virtual' kernel missing
This is during an install so I do not believe I am able to run that command. ** Changed in: linux (Ubuntu) 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/1625675 Title: Trusty 'linux-virtual' kernel missing Status in linux package in Ubuntu: Confirmed Bug description: The Ubuntu Server team runs a series of tests against the LTS and current development ISOs. On Trusty, one of the tests is to install a minimal VM kernel by using the "linux-virtual" kernel via a preseed entry as follows: d-i base-installer/kernel/override-image string linux-virtual On Trusty, the follow error is received: Sep 14 22:40:43 base-installer: warning: Kernel override 'linux- virtual' not present And the only useable kernels are as follows: Sep 14 22:40:43 base-installer: info: kernel linux-signed-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-extra-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-4.4.0-31-generic usable on em64t-p4 Which leads to the following kernels selected: Sep 14 22:40:43 debconf: Adding [KERNELS] -> [linux-signed-generic- lts-xenial,linux-generic-lts-xenial,linux-virtual-lts-xenial,linux- signed-image-generic-lts-xenial,linux-image-extra-4.4.0-31-generic ,linux-image-generic-lts-xenial,linux-image-virtual-lts-xenial,linux- signed-image-4.4.0-31-generic,linux-image-4.4.0-31-generic] I would have expected the 'linux-virtual' meta package to exist and in this case possibly point to 'linux-virtual-lts-xenial'. This way my existing preseed would not need to be updated. Forgive me in advance if this is due to my lack of understanding of the LTS/HWE kernels, however as I stated I expected the linux-virtual package to continue to exist. This does work as expected on Yakkety and Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625675/+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 1625675] Re: Trusty 'linux-virtual' kernel missing
** Attachment added: "utah-20978-trusty-server-amd64-preseed.cfg" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1625675/+attachment/4744425/+files/utah-20978-trusty-server-amd64-preseed.cfg -- 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/1625675 Title: Trusty 'linux-virtual' kernel missing Status in linux-meta package in Ubuntu: New Bug description: The Ubuntu Server team runs a series of tests against the LTS and current development ISOs. On Trusty, one of the tests is to install a minimal VM kernel by using the "linux-virtual" kernel via a preseed entry as follows: d-i base-installer/kernel/override-image string linux-virtual On Trusty, the follow error is received: Sep 14 22:40:43 base-installer: warning: Kernel override 'linux- virtual' not present And the only useable kernels are as follows: Sep 14 22:40:43 base-installer: info: kernel linux-signed-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-extra-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-4.4.0-31-generic usable on em64t-p4 Which leads to the following kernels selected: Sep 14 22:40:43 debconf: Adding [KERNELS] -> [linux-signed-generic- lts-xenial,linux-generic-lts-xenial,linux-virtual-lts-xenial,linux- signed-image-generic-lts-xenial,linux-image-extra-4.4.0-31-generic ,linux-image-generic-lts-xenial,linux-image-virtual-lts-xenial,linux- signed-image-4.4.0-31-generic,linux-image-4.4.0-31-generic] I would have expected the 'linux-virtual' meta package to exist and in this case possibly point to 'linux-virtual-lts-xenial'. This way my existing preseed would not need to be updated. Forgive me in advance if this is due to my lack of understanding of the LTS/HWE kernels, however as I stated I expected the linux-virtual package to continue to exist. This does work as expected on Yakkety and Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1625675/+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 1625675] [NEW] Trusty 'linux-virtual' kernel missing
Public bug reported: The Ubuntu Server team runs a series of tests against the LTS and current development ISOs. On Trusty, one of the tests is to install a minimal VM kernel by using the "linux-virtual" kernel via a preseed entry as follows: d-i base-installer/kernel/override-image string linux-virtual On Trusty, the follow error is received: Sep 14 22:40:43 base-installer: warning: Kernel override 'linux-virtual' not present And the only useable kernels are as follows: Sep 14 22:40:43 base-installer: info: kernel linux-signed-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-extra-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-4.4.0-31-generic usable on em64t-p4 Which leads to the following kernels selected: Sep 14 22:40:43 debconf: Adding [KERNELS] -> [linux-signed-generic-lts- xenial,linux-generic-lts-xenial,linux-virtual-lts-xenial,linux-signed- image-generic-lts-xenial,linux-image-extra-4.4.0-31-generic,linux-image- generic-lts-xenial,linux-image-virtual-lts-xenial,linux-signed- image-4.4.0-31-generic,linux-image-4.4.0-31-generic] I would have expected the 'linux-virtual' meta package to exist and in this case possibly point to 'linux-virtual-lts-xenial'. This way my existing preseed would not need to be updated. Forgive me in advance if this is due to my lack of understanding of the LTS/HWE kernels, however as I stated I expected the linux-virtual package to continue to exist. This does work as expected on Yakkety and Xenial. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1625675/+attachment/4744424/+files/syslog -- 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/1625675 Title: Trusty 'linux-virtual' kernel missing Status in linux-meta package in Ubuntu: New Bug description: The Ubuntu Server team runs a series of tests against the LTS and current development ISOs. On Trusty, one of the tests is to install a minimal VM kernel by using the "linux-virtual" kernel via a preseed entry as follows: d-i base-installer/kernel/override-image string linux-virtual On Trusty, the follow error is received: Sep 14 22:40:43 base-installer: warning: Kernel override 'linux- virtual' not present And the only useable kernels are as follows: Sep 14 22:40:43 base-installer: info: kernel linux-signed-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-extra-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-generic-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-virtual-lts-xenial usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-signed-image-4.4.0-31-generic usable on em64t-p4 Sep 14 22:40:43 base-installer: info: kernel linux-image-4.4.0-31-generic usable on em64t-p4 Which leads to the following kernels selected: Sep 14 22:40:43 debconf: Adding [KERNELS] -> [linux-signed-generic- lts-xenial,linux-generic-lts-xenial,linux-virtual-lts-xenial,linux- signed-image-generic-lts-xenial,linux-image-extra-4.4.0-31-generic ,linux-image-generic-lts-xenial,linux-image-virtual-lts-xenial,linux- signed-image-4.4.0-31-generic,linux-image-4.4.0-31-generic] I would have expected the 'linux-virtual' meta package to exist and in this case possibly point to 'linux-virtual-lts-xenial'. This way my existing preseed would not need to be updated. Forgive me in advance if this is due to my lack of understanding of the LTS/HWE kernels, however as I stated I expected the linux-virtual package to continue to exist. This does work as expected on Yakkety and Xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1625675/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kern
