[Bug 1675522] Re: arm64: Synchronous Exception at 0x00000000BBC129BC
ChristianEhrhardt
1675522 at bugs.launchpad.net
Fri Mar 24 08:01:32 UTC 2017
Hi Dann, thanks for your checks already!
Are you intending to break this down if e.g. Yakkety qemu is fixed as well as zesty seems?
And then once we know if Y is good maybe even down to a bisect of qemu in that regard?
Given your checks already the test seems to be as "easy" as "boot zesty
+ reboot = crash".
Do you happen to know:
- if it makes a difference what exact arm HW (more diverse than x86 at least) the host has?
- if it could be reproduced on qemu on x86 doing arm emulation?
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1675522
Title:
arm64: Synchronous Exception at 0x00000000BBC129BC
Status in edk2 package in Ubuntu:
Invalid
Status in grub2 package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in qemu package in Ubuntu:
New
Bug description:
I installed a KVM VM with the zesty beta server ISO. The install went
well but, upon reboot, GRUB entered a Synchronous Exception loop after
selecting the Ubuntu boot option.
After killing qemu-system-aarch64 and restarting the VM, the system
booted to a prompt w/o issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1675522/+subscriptions
More information about the foundations-bugs
mailing list