[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
** Description changed: [Impact] - on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. + on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. The reason is that the EFI firmware image switched to ACPI mode by default in bionic. We knew that was happening, and backported some minimal ACPI support to keep xenial guests booting (bug 1744754). But, now we're seeing guests panic when trying to initialize PCI. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. - [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. The reason is that the EFI firmware image switched to ACPI mode by default in bionic. We knew that was happening, and backported some minimal ACPI support to keep xenial guests booting (bug 1744754). But, now we're seeing guests panic when trying to initialize PCI. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." >
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
I'm not aware of any armhf hardware that has PCI and was supported by the 4.4 kernel. Calxeda gear maybe - but that was never officially released and I don't have access to it anyway. I did regression test using the virt model in QEMU. System still boots, lspci smoke tests OK: ubuntu@ubuntu:~$ lspci 00:00.0 Host bridge: Red Hat, Inc. QEMU PCIe Host bridge Kernel messages during PCI probe look identical, except we now see ECAM messages (which makes sense, that support is new): 4.4.0+arm64acpipci.dmesg:[1.269192] PCI: CLS 0 bytes, default 64 4.4.0+arm64acpipci.dmesg:[6.708312] PCI host bridge /pcie@1000 ranges: 4.4.0+arm64acpipci.dmesg:[6.747553] pci-host-generic 3f00.pcie: PCI host bridge to bus :00 4.4.0+arm64acpipci.dmesg:[6.792745] PCI: bus0: Fast back to back transfers disabled 4.4.0+arm64acpipci.dmesg:[7.012429] ehci-pci: EHCI PCI platform driver 4.4.0+arm64acpipci.dmesg:[7.037416] ohci-pci: OHCI PCI platform driver 4.4.0.dmesg:[1.309199] PCI: CLS 0 bytes, default 64 4.4.0.dmesg:[6.733705] PCI host bridge /pcie@1000 ranges: 4.4.0.dmesg:[6.760085] pci-host-generic 3f00.pcie: PCI host bridge to bus :00 4.4.0.dmesg:[6.802961] PCI: bus0: Fast back to back transfers disabled 4.4.0.dmesg:[7.016247] ehci-pci: EHCI PCI platform driver 4.4.0.dmesg:[7.040325] ohci-pci: OHCI PCI platform driver -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
Regression tested on ThunderX/X-Gene, which I believe were the only 2 arm64 servers supported by the 4.4 kernel. -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch Only adds new code w/ no callers yet > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch As noted in the commit message: "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch As noted, no functional change. > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch As noted, no functional change. > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch Only adds new code, w/ no callers yet > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch Enables code that will be added in the next patch. > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch As noted, no functional change intended. > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch Again, no functional change. > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
@ppisati: Would you be able to regression test this on armhf? ** Description changed: - on openstack rocky-bionic (with patch, see 1771662), xenial guests will - fail to launch as they drop to the busybox prompt after booting. - However, bionic guests will build and launch successfully. + [Impact] + on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. - Dann F believes this may be related to the xenial image not containing - appropriate acpi modifications. + [Test Case] + Deploy rocky-bionic OpenStack and try to launch a xenial guest. - xenial guest console log: - https://pastebin.canonical.com/p/ntRxFJTvjV/ + [Fix] + Backport ACPI/PCIe support for arm64 from upstream. - xenial virshxml: + [ Regression Risk ] + TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: - https://pastebin.canonical.com/p/cCY4ZVynP7/ + > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch + Enables code that will be added in the next patch. - bionic virshxml for comparison: + > 0002-PCI-Provide-common-functions-for-ECAM-mapping.patch + Only adds new code w/ no callers yet - https://pastebin.canonical.com/p/MSV3xG7t7g/ + > 0003-PCI-generic-thunder-Use-generic-ECAM-API.patch + As noted in the commit message: + "The patch does not introduce any functional changes other than a very minor one: with the new code, on 64-bit platforms, we do just a single ioremap for the whole config space." - validation: + > 0004-PCI-of-Move-PCI-I-O-space-management-to-PCI-core-cod.patch + As noted, no functional change. - https://pastebin.canonical.com/p/nC9pfSkXVs/ + > 0005-PCI-Move-ecam.h-to-linux-include-pci-ecam.h.patch + As noted, no functional change. + + > 0006-PCI-Add-parent-device-field-to-ECAM-struct-pci_confi.patch + This makes changes to the ecam code, but that was added in this series, so no regression risk there. The pci-thunder-pem changes will be regression tested on the hardware that uses that driver (Cavium ThunderX). + + > 0007-PCI-Add-pci_unmap_iospace-to-unmap-I-O-resources.patch + Only adds new code, w/ no callers yet + + > 0008-PCI-ACPI-Support-I-O-resources-when-parsing-host-bri.patch + Adds and calls a new function that is a no-op on !ARM (PCI_IOBASE is only defined on ARM). Also adds a call to pci_unmap_iospace(), which was added in a previous patch and is also a no-op on !ARM. + + > 0009-UBUNTU-Config-CONFIG_ACPI_MCFG-y.patch + Enables code that will be added in the next patch. + + > 0010-PCI-ACPI-Add-generic-MCFG-table-handling.patch + Adds parsing of a new ACPI table. A possible regression risk to platforms an MCFG table that were working fine w/ 4.4 and there's a latent bug in this parsing code. + + > 0011-PCI-Refactor-pci_bus_assign_domain_nr-for-CONFIG_PCI.patch + As noted, no functional change intended. + + > 0012-PCI-Factor-DT-specific-pci_bus_find_domain_nr-code-o.patch + Again, no functional change. + + > 0013-ARM64-PCI-Add-acpi_pci_bus_find_domain_nr.patch + Only impacts ARM due to CONFIG_PCI_DOMAINS_GENERIC guard + + > 0014-ARM64-PCI-ACPI-support-for-legacy-IRQs-parsing-and-c.patch + arm64-specific PCI initialization code - mitigate risk by regression testing on supported platforms (X-Gene, ThunderX). + + > 0015-ARM64-PCI-Support-ACPI-based-PCI-host-controller.patch + Adds new code for arm64-ACPI support. We didn't previously support these devices, so regression risk is negligible. ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Xenial) 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Fix Released Bug description: [Impact] on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. [Test Case] Deploy rocky-bionic OpenStack and try to launch a xenial guest. [Fix] Backport ACPI/PCIe support for arm64 from upstream. [ Regression Risk ] TLDR: Definitely warrants some regression testing on armhf/arm64, but regression risk seems low for other architectures. Here's a patch-by-patch risk analysis: > 0001-UBUNTU-Config-CONFIG_PCI_ECAM-y.patch Enables code that will be added in the next patch. >
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
** Tags removed: performing-bisect -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
I've backported the necessary fixes and verified that the result does solve the problem: https://git.launchpad.net/~dannf/ubuntu/+source/linux/+git/linux?h=xenial-arm64-acpi-pci That being said, the changes are not particularly isolated, so it will require careful review and testing for regression risk. Particularly on any armhf platforms that support PCI (I don't have any). Test builds are available in ppa:dannf/test. -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
There was no v4.6-yakkety build for arm64, but v4.8 booted fine. I further bisected this down to: 0cb0786bac159 ARM64: PCI: Support ACPI-based PCI host controller Presumably nova in newer OpenStack releases has made changes to the libvirt xml it generates that requires additional kernel support. I'll attempt a backport of the necessary changes to get an idea of feasibility of repairing this w/ a kernel change. Can someone provide a copy of a guest XML generated by an earlier OpenStack that does successfully boot xenial guests? An alternative approach we could investigate if the kernel backport proves infeasible would be to see if we could go back to the older XML format until xenial guest support EOLs. -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
I'd like to perform a "Reverse" bisect to figure out what commit fixes this bug. We need to identify the last kernel version that had the bug, and the first kernel version that fixed the bug. Can you test the following kernels and report back: v4.6 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ v4.8 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8/ V4.10 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10/ You don't have to test every kernel, just up until the first kernel that does not have the bug. Thanks in advance! -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
@Joseph I think I have bandwidth, please provide specific links and instructions:) -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
Would it be possible for you to test out some test kernels? That would allow us to reverse bisect and identify any missing commits from the 4.4 kernel. ** Tags added: performing-bisect -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: kernel-da-key -- 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/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+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