[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
** Tags added: cscc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-raspi2 source package in Xenial: Fix Released Status in linux-snapdragon source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: Fix Released Status in linux-snapdragon source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-raspi2 source package in Cosmic: Fix Released Status in linux-snapdragon source package in Cosmic: 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." > 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 busybox under openstack bionic-rocky
This bug was fixed in the package linux-raspi2 - 4.4.0-1101.109 --- linux-raspi2 (4.4.0-1101.109) xenial; urgency=medium * linux-raspi2: 4.4.0-1101.109 -proposed tracker (LP: #1802780) * rpi3bp+: ethernet leds don't blink (LP: #1802320) - Revert "lan78xx: Ignore DT MAC address if already valid" - Revert "lan78xx: Read MAC address from DT if present" - lan78xx: Read MAC address from DT if present - Revert "UBUNTU: SAUCE: Revert "lan78xx: Correctly indicate invalid OTP"" [ Ubuntu: 4.4.0-140.166 ] * linux: 4.4.0-140.166 -proposed tracker (LP: #1802776) * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * xenial guest on arm64 drops to busybox under openstack bionic-rocky (LP: #1797092) - [Config] CONFIG_PCI_ECAM=y - PCI: Provide common functions for ECAM mapping - PCI: generic, thunder: Use generic ECAM API - PCI, of: Move PCI I/O space management to PCI core code - PCI: Move ecam.h to linux/include/pci-ecam.h - PCI: Add parent device field to ECAM struct pci_config_window - PCI: Add pci_unmap_iospace() to unmap I/O resources - PCI/ACPI: Support I/O resources when parsing host bridge resources - [Config] CONFIG_ACPI_MCFG=y - PCI/ACPI: Add generic MCFG table handling - PCI: Refactor pci_bus_assign_domain_nr() for CONFIG_PCI_DOMAINS_GENERIC - PCI: Factor DT-specific pci_bus_find_domain_nr() code out - ARM64: PCI: Add acpi_pci_bus_find_domain_nr() - ARM64: PCI: ACPI support for legacy IRQs parsing and consolidation with DT code - ARM64: PCI: Support ACPI-based PCI host controller * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Update ENA driver to version 2.0.1K (LP: #1798182) - net: ena: remove ndo_poll_controller - net: ena: fix warning in rmmod caused by double iounmap - net: ena: fix rare bug when failed restart/resume is followed by driver removal - net: ena: fix NULL dereference due to untimely napi initialization - net: ena: fix auto casting to boolean - net: ena: minor performance improvement - net: ena: complete host info to match latest ENA spec - net: ena: introduce Low Latency Queues data structures according to ENA spec - net: ena: add functions for handling Low Latency Queues in ena_com - net: ena: add functions for handling Low Latency Queues in ena_netdev - net: ena: use CSUM_CHECKED device indication to report skb's checksum status - net: ena: explicit casting and initialization, and clearer error handling - net: ena: limit refill Rx threshold to 256 to avoid latency issues - net: ena: change rx copybreak default to reduce kernel memory pressure - net: ena: remove redundant parameter in ena_com_admin_init() - net: ena: update driver version to 2.0.1 - net: ena: fix indentations in ena_defs for better readability - net: ena: Fix Kconfig dependency on X86 - net: ena: enable Low Latency Queues - net: ena: fix compilation error in xtensa architecture * Xenial update: 4.4.162 upstream stable release (LP: #1801900) - ASoC: wm8804: Add ACPI support - ASoC: sigmadsp: safeload should not have lower byte limit - selftests/efivarfs: add required kernel configs - mfd: omap-usb-host: Fix dts probe of children - sound: enable interrupt after dma buffer initialization - stmmac: fix valid numbers of unicast filter entries - net: macb: disable scatter-gather for macb on sama5d3 - ARM: dts: at91: add new compatibility string for macb on sama5d3 - drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7 - ext4: add corruption check in ext4_xattr_set_entry() - mm/vmstat.c: fix outdated vmstat_text - mach64: detect the dot clock divider correctly on sparc - perf script python: Fix export-to-postgresql.py occasional failure - i2c: i2c-scmi: fix for i2c_smbus_write_block_data - xhci: Don't print a warning when setting link state for disabled ports - jffs2: return -ERANGE when xattr buffer is too small - bnxt_en: Fix TX timeout during netpoll. - bonding: avoid possible dead-lock - ip6_tunnel: be careful when accessing the inner header - ip_tunnel: be careful when accessing the inner header - ipv4: fix use-after-free in ip_cmsg_recv_dstaddr() - net: ipv4: update fnhe_pmtu when first hop's MTU changes -
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
This bug was fixed in the package linux - 4.4.0-140.166 --- linux (4.4.0-140.166) xenial; urgency=medium * linux: 4.4.0-140.166 -proposed tracker (LP: #1802776) * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * xenial guest on arm64 drops to busybox under openstack bionic-rocky (LP: #1797092) - [Config] CONFIG_PCI_ECAM=y - PCI: Provide common functions for ECAM mapping - PCI: generic, thunder: Use generic ECAM API - PCI, of: Move PCI I/O space management to PCI core code - PCI: Move ecam.h to linux/include/pci-ecam.h - PCI: Add parent device field to ECAM struct pci_config_window - PCI: Add pci_unmap_iospace() to unmap I/O resources - PCI/ACPI: Support I/O resources when parsing host bridge resources - [Config] CONFIG_ACPI_MCFG=y - PCI/ACPI: Add generic MCFG table handling - PCI: Refactor pci_bus_assign_domain_nr() for CONFIG_PCI_DOMAINS_GENERIC - PCI: Factor DT-specific pci_bus_find_domain_nr() code out - ARM64: PCI: Add acpi_pci_bus_find_domain_nr() - ARM64: PCI: ACPI support for legacy IRQs parsing and consolidation with DT code - ARM64: PCI: Support ACPI-based PCI host controller * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Update ENA driver to version 2.0.1K (LP: #1798182) - net: ena: remove ndo_poll_controller - net: ena: fix warning in rmmod caused by double iounmap - net: ena: fix rare bug when failed restart/resume is followed by driver removal - net: ena: fix NULL dereference due to untimely napi initialization - net: ena: fix auto casting to boolean - net: ena: minor performance improvement - net: ena: complete host info to match latest ENA spec - net: ena: introduce Low Latency Queues data structures according to ENA spec - net: ena: add functions for handling Low Latency Queues in ena_com - net: ena: add functions for handling Low Latency Queues in ena_netdev - net: ena: use CSUM_CHECKED device indication to report skb's checksum status - net: ena: explicit casting and initialization, and clearer error handling - net: ena: limit refill Rx threshold to 256 to avoid latency issues - net: ena: change rx copybreak default to reduce kernel memory pressure - net: ena: remove redundant parameter in ena_com_admin_init() - net: ena: update driver version to 2.0.1 - net: ena: fix indentations in ena_defs for better readability - net: ena: Fix Kconfig dependency on X86 - net: ena: enable Low Latency Queues - net: ena: fix compilation error in xtensa architecture * Xenial update: 4.4.162 upstream stable release (LP: #1801900) - ASoC: wm8804: Add ACPI support - ASoC: sigmadsp: safeload should not have lower byte limit - selftests/efivarfs: add required kernel configs - mfd: omap-usb-host: Fix dts probe of children - sound: enable interrupt after dma buffer initialization - stmmac: fix valid numbers of unicast filter entries - net: macb: disable scatter-gather for macb on sama5d3 - ARM: dts: at91: add new compatibility string for macb on sama5d3 - drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7 - ext4: add corruption check in ext4_xattr_set_entry() - mm/vmstat.c: fix outdated vmstat_text - mach64: detect the dot clock divider correctly on sparc - perf script python: Fix export-to-postgresql.py occasional failure - i2c: i2c-scmi: fix for i2c_smbus_write_block_data - xhci: Don't print a warning when setting link state for disabled ports - jffs2: return -ERANGE when xattr buffer is too small - bnxt_en: Fix TX timeout during netpoll. - bonding: avoid possible dead-lock - ip6_tunnel: be careful when accessing the inner header - ip_tunnel: be careful when accessing the inner header - ipv4: fix use-after-free in ip_cmsg_recv_dstaddr() - net: ipv4: update fnhe_pmtu when first hop's MTU changes - net/ipv6: Display all addresses in output of /proc/net/if_inet6 - netlabel: check for IPV4MASK in addrinfo_get - net/usb: cancel pending work when unbinding smsc75xx - qlcnic: fix Tx descriptor corruption on 82xx devices - team: Forbid enslaving team device to itself - net: mvpp2: Extract the correct ethtype from the skb for tx csum offload - net: systemport: Fix wake-up interrupt race during
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
This bug was fixed in the package linux-snapdragon - 4.4.0-1105.110 --- linux-snapdragon (4.4.0-1105.110) xenial; urgency=medium * linux-snapdragon: 4.4.0-1105.110 -proposed tracker (LP: #1802781) * xenial guest on arm64 drops to busybox under openstack bionic-rocky (LP: #1797092) - [Config] CONFIG_PCI_ECAM=y - [Config] CONFIG_ACPI_MCFG=y [ Ubuntu: 4.4.0-140.166 ] * linux: 4.4.0-140.166 -proposed tracker (LP: #1802776) * Bypass of mount visibility through userns + mount propagation (LP: #1789161) - mount: Retest MNT_LOCKED in do_umount - mount: Don't allow copying MNT_UNBINDABLE|MNT_LOCKED mounts * kdump fail due to an IRQ storm (LP: #1797990) - SAUCE: x86/PCI: Export find_cap() to be used in early PCI code - SAUCE: x86/quirks: Add parameter to clear MSIs early on boot - SAUCE: x86/quirks: Scan all busses for early PCI quirks * crash in ENA driver on removing an interface (LP: #1802341) - SAUCE: net: ena: fix crash during ena_remove() * xenial guest on arm64 drops to busybox under openstack bionic-rocky (LP: #1797092) - [Config] CONFIG_PCI_ECAM=y - PCI: Provide common functions for ECAM mapping - PCI: generic, thunder: Use generic ECAM API - PCI, of: Move PCI I/O space management to PCI core code - PCI: Move ecam.h to linux/include/pci-ecam.h - PCI: Add parent device field to ECAM struct pci_config_window - PCI: Add pci_unmap_iospace() to unmap I/O resources - PCI/ACPI: Support I/O resources when parsing host bridge resources - [Config] CONFIG_ACPI_MCFG=y - PCI/ACPI: Add generic MCFG table handling - PCI: Refactor pci_bus_assign_domain_nr() for CONFIG_PCI_DOMAINS_GENERIC - PCI: Factor DT-specific pci_bus_find_domain_nr() code out - ARM64: PCI: Add acpi_pci_bus_find_domain_nr() - ARM64: PCI: ACPI support for legacy IRQs parsing and consolidation with DT code - ARM64: PCI: Support ACPI-based PCI host controller * [GLK/CLX] Enhanced IBRS (LP: #1786139) - x86/speculation: Remove SPECTRE_V2_IBRS in enum spectre_v2_mitigation - x86/speculation: Support Enhanced IBRS on future CPUs * Update ENA driver to version 2.0.1K (LP: #1798182) - net: ena: remove ndo_poll_controller - net: ena: fix warning in rmmod caused by double iounmap - net: ena: fix rare bug when failed restart/resume is followed by driver removal - net: ena: fix NULL dereference due to untimely napi initialization - net: ena: fix auto casting to boolean - net: ena: minor performance improvement - net: ena: complete host info to match latest ENA spec - net: ena: introduce Low Latency Queues data structures according to ENA spec - net: ena: add functions for handling Low Latency Queues in ena_com - net: ena: add functions for handling Low Latency Queues in ena_netdev - net: ena: use CSUM_CHECKED device indication to report skb's checksum status - net: ena: explicit casting and initialization, and clearer error handling - net: ena: limit refill Rx threshold to 256 to avoid latency issues - net: ena: change rx copybreak default to reduce kernel memory pressure - net: ena: remove redundant parameter in ena_com_admin_init() - net: ena: update driver version to 2.0.1 - net: ena: fix indentations in ena_defs for better readability - net: ena: Fix Kconfig dependency on X86 - net: ena: enable Low Latency Queues - net: ena: fix compilation error in xtensa architecture * Xenial update: 4.4.162 upstream stable release (LP: #1801900) - ASoC: wm8804: Add ACPI support - ASoC: sigmadsp: safeload should not have lower byte limit - selftests/efivarfs: add required kernel configs - mfd: omap-usb-host: Fix dts probe of children - sound: enable interrupt after dma buffer initialization - stmmac: fix valid numbers of unicast filter entries - net: macb: disable scatter-gather for macb on sama5d3 - ARM: dts: at91: add new compatibility string for macb on sama5d3 - drm/amdgpu: Fix SDMA HQD destroy error on gfx_v7 - ext4: add corruption check in ext4_xattr_set_entry() - mm/vmstat.c: fix outdated vmstat_text - mach64: detect the dot clock divider correctly on sparc - perf script python: Fix export-to-postgresql.py occasional failure - i2c: i2c-scmi: fix for i2c_smbus_write_block_data - xhci: Don't print a warning when setting link state for disabled ports - jffs2: return -ERANGE when xattr buffer is too small - bnxt_en: Fix TX timeout during netpoll. - bonding: avoid possible dead-lock - ip6_tunnel: be careful when accessing the inner header - ip_tunnel: be careful when accessing the inner header - ipv4: fix use-after-free in ip_cmsg_recv_dstaddr() - net: ipv4: update fnhe_pmtu when first hop's MTU changes - net/ipv6: Display all addresses in output of /proc/net/if_inet6 - netlabel: check for IPV4MASK in addrinfo_get - net/usb: cancel pending
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
Verified - see attached dmesg. ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/bionic/+source/linux-snapdragon/+bug/1797092/+attachment/5214304/+files/dmesg ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1797092 Title: xenial guest on arm64 drops to busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: Fix Released Status in linux-snapdragon source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-raspi2 source package in Cosmic: Fix Released Status in linux-snapdragon source package in Cosmic: 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." > 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 busybox under openstack bionic-rocky
** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux-raspi2 (Ubuntu) Status: New => Fix Released ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-raspi2 (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux-snapdragon (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: linux-snapdragon (Ubuntu) Status: New => Fix Released ** Changed in: linux-snapdragon (Ubuntu Bionic) Status: New => 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/1797092 Title: xenial guest on arm64 drops to busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: Fix Released Status in linux-snapdragon source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-raspi2 source package in Cosmic: Fix Released Status in linux-snapdragon source package in Cosmic: 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." > 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 :
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1797092 Title: xenial guest on arm64 drops to busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: New Status in linux-snapdragon source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-raspi2 source package in Cosmic: New Status in linux-snapdragon source package in Cosmic: New 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." > 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 :
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybox under openstack bionic-rocky
** Also affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-snapdragon (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: linux-snapdragon (Ubuntu Xenial) Status: New => Fix Committed -- 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 busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Status in linux-raspi2 source package in Xenial: Fix Committed Status in linux-snapdragon source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux-raspi2 source package in Bionic: New Status in linux-snapdragon source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-raspi2 source package in Cosmic: New Status in linux-snapdragon source package in Cosmic: New 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." > 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 busybox under openstack bionic-rocky
** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Committed -- 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 busybox under openstack bionic-rocky Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed 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." > 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 busybox under openstack bionic-rocky
** Summary changed: - xenial guest on arm64 drops to busybux under openstack bionic-rocky + xenial guest on arm64 drops to busybox under openstack bionic-rocky -- 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 busybox 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." > 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