[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
** Changed in: maas Assignee: (unassigned) => Björn Tillenius (bjornt) -- 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/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: New Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+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 1954692] Re: Reconsider compressed kernels on arm64
** Changed in: maas-images Status: In Progress => Fix Committed ** Changed in: maas-images Importance: Undecided => High -- 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/1954692 Title: Reconsider compressed kernels on arm64 Status in maas-images: Fix Committed Status in flash-kernel package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Bug description: Compressed kernel images were introduced in bug 1384955 to work around some limits on old u-boot systems. This in turn broke grub-check- signatures, meaning that while cloud images booted in secure boot, you could not upgrade grub or install new kernels on secure systems as that would trigger a "you have unsigned kernels" message. grub 2.06 also fails to boot the images, as it verifies before decompressing. Work to fix grub to handle such images on arm64 for backward compatibility is tracked in bug 1954683. This bug is to reconsider whether the change is still necessary or could be removed in 22.04 such that we can have proper UEFI executables again. To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1954692/+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 1898808] Re: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5
** Changed in: maas-images Assignee: (unassigned) => Lee Trager (ltrager) ** Changed in: maas-images 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/1898808 Title: [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after images update on Oct 5 Status in MAAS: New Status in maas-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Note: Per comment #29, this was working up until Oct 5. It looks to me like the last update to the focal boot images are also dated Oct 5 coinciding with the appearance of this issue. 1. maas:2.4.2 (7034-g2f5deb8b8-0ubuntu1) 2. 18.04(bionic) is good to deploy on the same sut/env. 3. deployment failed on SUT pxe boot stage w/ error below, "Booting under MAAS direction... error: timeout reading 'ubuntu/amd64/ga-20.04/focal/daily/boot-initrd'. press any key to continue..." 4.cross check for 'boot-initrd' file had been found on MAAS sever(ref attachment) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0b:bd11/15/2019:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnH12SSW-NT/iN:rvr0123456789:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. eno1np0 no wireless extensions. eno2np1 no wireless extensions. MachineType: Supermicro Super Server 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-118-generic root=UUID=3a412367-9f1c-419b-8d53-39c529aefb9f ro ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-118-generic N/A linux-backports-modules-4.15.0-118-generic N/A linux-firmware 1.173.19 RfKill: Tags: bionic uec-images Uname: Linux 4.15.0-118-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H12SSW-NT/iN dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789
[Kernel-packages] [Bug 1881821] Re: MAAS does not properly detect max interface speed for interfaces which use multiple phyiscal ports(Cisco UCS B200 M5 blade)
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Changed in: maas/2.7
Status: New => Fix Committed
** Changed in: maas/2.7
Importance: Undecided => Critical
** Changed in: maas/2.7
Assignee: (unassigned) => Lee Trager (ltrager)
** Changed in: maas/2.7
Milestone: None => 2.7.2
--
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/1881821
Title:
MAAS does not properly detect max interface speed for interfaces which
use multiple phyiscal ports(Cisco UCS B200 M5 blade)
Status in MAAS:
Fix Committed
Status in MAAS 2.7 series:
Fix Committed
Status in MAAS 2.8 series:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Bug description:
MAAS 2.7.1
Ubuntu 18.04.4
When attempting to commission a Cisco UCS B200 M5 blade, the
commissioning finishes (if smartctl-validate is disabled), however on
the machine in question in the Networking tab, it only shows 2 nics,
eth0 and eth1. and shows no storage.
Going to SSH in the middle of commissioning, running lshw shows all 10
NICs, and the disk of the proper size.
This is causing the buckets.yaml for FCE to be inaccurate, and thus
cannot write a bucketsconfig.yaml since the actual devices don't show
up.
This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
commissioning, all have the same behavior.
I was previously hitting this bug
https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
comment #10, and am no longer getting any commissioning errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+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 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
Thanks for the background info, in 2.7 MAAS started modelling the speeds
of interfaces and links, so I expect that 2.6 will not have the same
problem.
--
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/1881821
Title:
Kernel does not report interface speed correctly for Cisco UCS B200 M5
blade
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
Triaged
Status in MAAS 2.8 series:
Triaged
Status in linux package in Ubuntu:
Confirmed
Bug description:
MAAS 2.7.1
Ubuntu 18.04.4
When attempting to commission a Cisco UCS B200 M5 blade, the
commissioning finishes (if smartctl-validate is disabled), however on
the machine in question in the Networking tab, it only shows 2 nics,
eth0 and eth1. and shows no storage.
Going to SSH in the middle of commissioning, running lshw shows all 10
NICs, and the disk of the proper size.
This is causing the buckets.yaml for FCE to be inaccurate, and thus
cannot write a bucketsconfig.yaml since the actual devices don't show
up.
This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
commissioning, all have the same behavior.
I was previously hitting this bug
https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
comment #10, and am no longer getting any commissioning errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+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 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
** Also affects: maas/2.7
Importance: Undecided
Status: New
** Also affects: maas/2.8
Importance: Critical
Assignee: Lee Trager (ltrager)
Status: Triaged
** Changed in: maas/2.8
Milestone: None => 2.8.0rc1
** Changed in: maas/2.7
Milestone: None => 2.7.2
** Changed in: maas/2.7
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
Kernel does not report interface speed correctly for Cisco UCS B200 M5
blade
Status in MAAS:
Triaged
Status in MAAS 2.7 series:
Triaged
Status in MAAS 2.8 series:
Triaged
Status in linux package in Ubuntu:
Confirmed
Bug description:
MAAS 2.7.1
Ubuntu 18.04.4
When attempting to commission a Cisco UCS B200 M5 blade, the
commissioning finishes (if smartctl-validate is disabled), however on
the machine in question in the Networking tab, it only shows 2 nics,
eth0 and eth1. and shows no storage.
Going to SSH in the middle of commissioning, running lshw shows all 10
NICs, and the disk of the proper size.
This is causing the buckets.yaml for FCE to be inaccurate, and thus
cannot write a bucketsconfig.yaml since the actual devices don't show
up.
This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
commissioning, all have the same behavior.
I was previously hitting this bug
https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
comment #10, and am no longer getting any commissioning errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+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 1881821] Re: Kernel does not report interface speed correctly for Cisco UCS B200 M5 blade
** Changed in: maas
Importance: Undecided => Critical
** Changed in: maas
Assignee: (unassigned) => Lee Trager (ltrager)
--
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/1881821
Title:
Kernel does not report interface speed correctly for Cisco UCS B200 M5
blade
Status in MAAS:
Triaged
Status in linux package in Ubuntu:
Confirmed
Bug description:
MAAS 2.7.1
Ubuntu 18.04.4
When attempting to commission a Cisco UCS B200 M5 blade, the
commissioning finishes (if smartctl-validate is disabled), however on
the machine in question in the Networking tab, it only shows 2 nics,
eth0 and eth1. and shows no storage.
Going to SSH in the middle of commissioning, running lshw shows all 10
NICs, and the disk of the proper size.
This is causing the buckets.yaml for FCE to be inaccurate, and thus
cannot write a bucketsconfig.yaml since the actual devices don't show
up.
This was tried with bionic {ga,hwe,hwe-edge} and focal ga kernels for
commissioning, all have the same behavior.
I was previously hitting this bug
https://bugs.launchpad.net/maas/+bug/1878643 but applied the fix from
comment #10, and am no longer getting any commissioning errors.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1881821/+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 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption
*** This bug is a duplicate of bug 1864360 *** https://bugs.launchpad.net/bugs/1864360 ** This bug is no longer a duplicate of bug 1862215 dm-crypt missing from initramfs ** This bug has been marked a duplicate of bug 1864360 cryptsetup-run is transitional package, but removing it also removes cryptsetup-initramfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1864293 Title: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption Status in linux-5.4 package in Ubuntu: New Bug description: Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion had been set up from the 19.10 installer and had been working perfectly. Today, when I try to boot, the splash screen stalls at the throbber and doesn't open a prompt for my encryption key. After a minute or so it drops to the initramfs shell. Rebooting without "silent splash" on the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be found, and running `ls /dev/mapper` outputs only `control`. Rebooting with the 5.4.0-12 kernel works without any problems. I've added `mitigations=off` to my default boot flags some time ago, if that's relevant? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neil 3193 F pulseaudio CurrentDesktop: MATE Date: Sat Feb 22 12:29:27 2020 InstallationDate: Installed on 2019-10-11 (133 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2) MachineType: LENOVO 2325A39 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.186 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-5.4 UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago) dmi.bios.date: 06/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB3WW (2.73 ) dmi.board.asset.tag: Not Available dmi.board.name: 2325A39 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2325A39 dmi.product.sku: LENOVO_MT_2325 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1864293/+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 1862215] Re: dm-crypt missing from initiramfs
*** This bug is a duplicate of bug 1864360 *** https://bugs.launchpad.net/bugs/1864360 Ah, suspect this is actually an incident of bug 1864360, confirmed I do not have cryptsetup-initramfs installed, and purged all transitional packages ** Summary changed: - dm-crypt missing from initiramfs + dm-crypt missing from initramfs ** This bug has been marked a duplicate of bug 1864360 cryptsetup-run is transitional package, but removing it also removes cryptsetup-initramfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: dm-crypt missing from initramfs Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Attempting to boot linux-image-5.4.0-12-generic and it failed to find my LVM VG. -9 worked without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.12.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 17:20:45 2020 InstallationDate: Installed on 2016-11-01 (1192 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-5.4 UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+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 1862215] Re: dm-crypt missing from initiramfs
** Summary changed: - Failure to boot with LVM + encrypted root disk + dm-crypt missing from initiramfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: dm-crypt missing from initiramfs Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Attempting to boot linux-image-5.4.0-12-generic and it failed to find my LVM VG. -9 worked without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.12.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 17:20:45 2020 InstallationDate: Installed on 2016-11-01 (1192 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-5.4 UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+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 1862215] Re: Failure to boot with LVM + encrypted root disk
$ lsinitramfs /boot/initrd.img-5.4.0-9-generic | grep dm-crypt usr/lib/modules/5.4.0-9-generic/kernel/drivers/md/dm-crypt.ko Confirmed it is there for -9 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: Failure to boot with LVM + encrypted root disk Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Attempting to boot linux-image-5.4.0-12-generic and it failed to find my LVM VG. -9 worked without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.12.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 17:20:45 2020 InstallationDate: Installed on 2016-11-01 (1192 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-5.4 UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+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 1862215] Re: Failure to boot with LVM + encrypted root disk
$ lsinitramfs /boot/initrd.img-5.4.0-14-generic | grep dm-crypt 1 $ https://paste.ubuntu.com/p/bDq66dMjYM/ for the full list -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862215 Title: Failure to boot with LVM + encrypted root disk Status in linux-5.4 package in Ubuntu: Confirmed Bug description: Attempting to boot linux-image-5.4.0-12-generic and it failed to find my LVM VG. -9 worked without issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.12.15 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 17:20:45 2020 InstallationDate: Installed on 2016-11-01 (1192 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-5.4 UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1862215/+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 1689853] [NEW] Kernel bug after probable OOM?
Public bug reported: Symptoms were a hung tab in Firefox (nightly) which then left a zombie process lingering around after introducing the processes to Mr Kill -KILL. I don't have swap configured because I like to be different. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed May 10 17:28:21 2017 HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754 InstallationDate: Installed on 2015-07-04 (676 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7917 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1689853 Title: Kernel bug after probable OOM? Status in linux package in Ubuntu: New Bug description: Symptoms were a hung tab in Firefox (nightly) which then left a zombie process lingering around after introducing the processes to Mr Kill -KILL. I don't have swap configured because I like to be different. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed May 10 17:28:21 2017 HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754 InstallationDate: Installed on 2015-07-04 (676 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7917 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-24 (16 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689853/+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 1553676] [NEW] package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Upgrade from Wily to Xenial from byobu launched in desktop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: acollard 6051 F pulseaudio /dev/snd/controlC1: acollard 6051 F pulseaudio /dev/snd/controlC2: acollard 6051 F pulseaudio /dev/snd/controlC0: acollard 6051 F pulseaudio Date: Sun Mar 6 09:10:40 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754 InstallationDate: Installed on 2015-07-04 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7917 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- 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/1553676 Title: package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Upgrade from Wily to Xenial from byobu launched in desktop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: acollard 6051 F pulseaudio /dev/snd/controlC1: acollard 6051 F pulseaudio /dev/snd/controlC2: acollard 6051 F pulseaudio /dev/snd/controlC0: acollard 6051 F pulseaudio Date: Sun Mar 6 09:10:40 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 HibernationDevice: RESUME=UUID=fda86ae0-6316-4551-a064-a782b5d2a754 InstallationDate: Installed on 2015-07-04 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: MSI MS-7917 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic root=UUID=c992784f-51c3-441c-b9ae-e4e9278f2a4b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 12/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 GAMING 5 (MS-7917) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7917 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications
