Hi, Ian,
I *guess* that "bug" come from uefi. At least, I think "Synchronous Exception" come from uefi. But I have not the Juno board. So I have not chance to test it, although I want to test it in a real hardware.
For now, Xen can not work with the new linaro-edk2, because the new one will try to allocate the memory from the "high" bank(if we have two banks of memory).
Please try my repo: https://git.linaro.org/people/fu.wei/grub.git branch : multiboot_xen_support_upstream_dev
I agree with you for the multiple banks of memory. Will try to use the first bank, and report the result here. :-)
Great thanks!!
On 07/21/2014 08:45 PM, Ian Campbell wrote:
On Fri, 2014-06-27 at 22:02 +0800, Fu Wei wrote:
Hi Leif, I have make a new multiboot support patch V3.5, because Ian has fixed the bugs in his branch.
FYI I tried v3.4 of this patch (because -ENOPATCH here) on a Juno board and got: [...]Welcome to GRUB! [...]error: no such device: boot. [...]GNU GRUB version 2.02~beta2 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. grub> Synchronous Exception at 0x00000000FEB2B808 ([...] are ANSI escape codes which I've removed)
I didn't have a chance to press any keys, this happened without any input etc. The Synchronous Exception messages just keep repeating with the same address.
This was based on: commit 0901e7855f922e770cbfeb58262cb8fded518190 Author: Colin Watson cjwatson@ubuntu.com Date: Tue Jul 8 23:54:30 2014 +0100 Fix an infinite loop in grub-mkconfig
To Ian: Once Xen can support multiple blanks of RAM, please let me know, then I can test the latest linaro-edk2 with GRUB and Xen.
I've started having a look at this but it looks like it will be a while before I complete it. Can you remind me what the issue is? If Xen sees multiple banks of memory which represent an address map which is too sparse it should try and continue with just the first bank. Obviously not ideal, but should work, I think.
Ian.