| 2018-01-22 16:20:40 |
dann frazier |
bug |
|
|
added bug |
| 2018-01-22 16:20:56 |
dann frazier |
bug task added |
|
cloud-images |
|
| 2018-01-22 16:21:10 |
dann frazier |
bug task added |
|
linux (Ubuntu) |
|
| 2018-01-22 16:21:33 |
dann frazier |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-01-22 16:21:33 |
dann frazier |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2018-01-22 16:21:33 |
dann frazier |
bug task added |
|
edk2 (Ubuntu Xenial) |
|
| 2018-01-22 16:30:06 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2018-01-22 16:30:09 |
Ubuntu Kernel Bot |
linux (Ubuntu Xenial): status |
New |
Incomplete |
|
| 2018-01-22 16:30:11 |
Ubuntu Kernel Bot |
tags |
|
xenial |
|
| 2018-02-01 01:06:44 |
dann frazier |
linux (Ubuntu Xenial): status |
Incomplete |
In Progress |
|
| 2018-02-01 01:06:51 |
dann frazier |
linux (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2018-02-01 01:07:02 |
dann frazier |
edk2 (Ubuntu Xenial): status |
New |
Invalid |
|
| 2018-02-01 22:41:47 |
dann frazier |
description |
[Impact]
After upgrading your KVM hypervisor past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
TBD |
[Impact]
After upgrading your KVM hypervisor past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems.
Patch 6 only adds new macro definitions.
Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel-parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference.
Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86.
Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code).
Patch 10 only touches arm64-specific code, adding the call to parse_spcr().
Patch 11 adds a new match method to the ARM-specific pl011 console driver. |
|
| 2018-02-01 22:42:00 |
dann frazier |
linux (Ubuntu Xenial): assignee |
|
dann frazier (dannf) |
|
| 2018-02-01 22:42:47 |
dann frazier |
description |
[Impact]
After upgrading your KVM hypervisor past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems.
Patch 6 only adds new macro definitions.
Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel-parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference.
Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86.
Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code).
Patch 10 only touches arm64-specific code, adding the call to parse_spcr().
Patch 11 adds a new match method to the ARM-specific pl011 console driver. |
[Impact]
After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems.
Patch 6 only adds new macro definitions.
Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel-parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference.
Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86.
Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code).
Patch 10 only touches arm64-specific code, adding the call to parse_spcr().
Patch 11 adds a new match method to the ARM-specific pl011 console driver. |
|
| 2018-02-02 15:58:54 |
dann frazier |
description |
[Impact]
After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems.
Patch 6 only adds new macro definitions.
Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel-parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference.
Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86.
Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code).
Patch 10 only touches arm64-specific code, adding the call to parse_spcr().
Patch 11 adds a new match method to the ARM-specific pl011 console driver. |
[Impact]
After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based guests will fail to boot.
[Test Case]
Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
[Regression Risk]
I've tested booting a xenial cloud image in bionic (ACPI mode), and regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel only supported 2 GICv3 systems - the 1 socket and 2 socket variants of the Cavium ThunderX CRB - and I've regression tested on those systems.
Patch 6 only adds new macro definitions.
Patch 7 is restricted to devicetree code, except for a change to earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed on the cmdline (vs. earlycon=something), this function used to return 0 - but now it will return -ENODEV on non-devicetree systems, which is a subtle API change. However, according to kernel-parameters.txt (and the code itself), 'earlycon' by itself is only valid on devicetree systems. Just to be sure, I booted an x86 system up w/ 'earlycon' with and without this series, and observed no difference.
Patch 8 adds the SPCR table parser, but no caller to it yet. It also modifies the same earlycon code as Patch 7 - here it avoids earlycon init in the case that the devicetree-specific 'earlycon' was passed. As mentioned in my analysis Patch 7, this codepath is only supported for devicetree systems, and has been regression tested on x86.
Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to build this for other archs - but I checked the logs, and there's no spcr.o built on other archs. (Not that that should be a problem - they would just grow a bit of unused code).
Patch 10 only touches arm64-specific code, adding the call to parse_spcr(), so risk is limited to arm64.
Patch 11 adds a new match method to the ARM-specific pl011 console driver, so regression risk to other architectures is negligible. |
|
| 2018-02-15 19:45:53 |
Francis Ginther |
tags |
xenial |
id-5a674ab10c375ca04060ea9a xenial |
|
| 2018-02-27 02:38:19 |
Launchpad Janitor |
edk2 (Ubuntu): status |
New |
Confirmed |
|
| 2018-02-27 02:45:53 |
Po-Hsu Lin |
bug |
|
|
added subscriber Po-Hsu Lin |
| 2018-03-02 13:18:20 |
Kleber Sacilotto de Souza |
linux (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2018-03-09 14:22:41 |
dann frazier |
cloud-images: status |
New |
Invalid |
|
| 2018-03-09 14:22:46 |
dann frazier |
edk2 (Ubuntu): status |
Confirmed |
Invalid |
|
| 2018-03-19 10:55:14 |
Stefan Bader |
tags |
id-5a674ab10c375ca04060ea9a xenial |
id-5a674ab10c375ca04060ea9a verification-needed-xenial xenial |
|
| 2018-03-19 20:25:57 |
dann frazier |
attachment added |
|
dmesg-xenial-host.txt https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084478/+files/dmesg-xenial-host.txt |
|
| 2018-03-19 20:26:16 |
dann frazier |
attachment added |
|
dmesg-bionic-host.txt https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5084479/+files/dmesg-bionic-host.txt |
|
| 2018-03-19 20:26:36 |
dann frazier |
tags |
id-5a674ab10c375ca04060ea9a verification-needed-xenial xenial |
id-5a674ab10c375ca04060ea9a verification-done-xenial xenial |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-15129 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-16995 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-17448 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-17450 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-17741 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-17862 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2017-5753 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2018-1000026 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2018-5333 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2018-5344 |
|
| 2018-04-04 09:27:25 |
Launchpad Janitor |
cve linked |
|
2018-8043 |
|
| 2018-04-20 15:29:57 |
dann frazier |
attachment added |
|
xenial-guest-in-bionic.log https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1744754/+attachment/5123982/+files/xenial-guest-in-bionic.log |
|
