Re: [Xen-devel] Data Abort while in booting when using Julien's new patches on Arndale Board

[Julien Grall <julien.grall@xxxxxxxxxx>]

On 05/02/2013 03:46 AM, Gihun Jung wrote:

> 2013/5/1 Julien Grall <julien.grall@xxxxxxxxxx>:
> 
>> This is not related, but this branch doesn't work. If you want to try
>> Linux 3.9 I advise you use to "dev-arndale-dom0-3.9-rc4". I use this
>> branch for my test.
>>
>> - DTS: arch/arm/boot/exynos5250-arndale.dts
>> - config: arch/arm/configs/xen_dom0_arndale_defconfig
> 
> I have tried "dev-arndale-dom0-3.9-rc4" and followed what you suggest.
> FYI, I am using the latest u-boot version from linaro-stable
> (git://git.linaro.org/git-ro/boot/u-boot-linaro-stable.git)
> 
>> I have noticed this issue yesterday. The lines between
>> p2m_populate_ram... and unmap_domain_page... should be removed.
> 
> I have removed it; available to go next step without data abort.
> 
>> But there is another issue with linux 3.7. If you want to use
>> this version you need to checkout "arndale" branch in my xen git.
>> Otherwise you can use the branch "arm" with linux 3.9.
>>
>> Let me know if you have any issue with this patch series.
> 
> But, I am still facing a problem to booting :(
> According to log, it seems to success to load the zImage to newly
> mapping area for dom0.
> It was not working; It was hang on Guest ABT
> 
> In here, I have questions. When I used "1:1 mapping for dom0" from
> Anthony's patch (i.e. that is removed and improved by your new patch
> series),
> Xen told me that it populated P2M for dom0 (i.e. mem size = 256M) from
> 0x40000000 - 0x50000000.
> It is exactly same start address of physical RAM of Arndale Board.
> Buy, in your patch series, it is in 0x50000000 - 0x60000000.
> Is it possible to be a cause of Data Abort?

I don't think so. I don't see usefull things in the log, you need to
enable more debug for linux. Could you apply this hacky patch on linux?

diff --git a/kernel/printk.c b/kernel/printk.c
index abbdd9e..6975215 100644
--- a/kernel/printk.c
+++ b/kernel/printk.c
@@ -1652,6 +1652,8 @@ asmlinkage int printk_emit(int facility, int level,
 }
 EXPORT_SYMBOL(printk_emit);

+void xen_raw_console_write(const char *buf);
+
 /**
  * printk - print a kernel message
  * @fmt: format string
@@ -1677,6 +1679,7 @@ asmlinkage int printk(const char *fmt, ...)
 {
        va_list args;
        int r;
+       static char buf[512];

 #ifdef CONFIG_KGDB_KDB
        if (unlikely(kdb_trap_printk)) {
@@ -1687,9 +1690,12 @@ asmlinkage int printk(const char *fmt, ...)
        }
 #endif
        va_start(args, fmt);
-       r = vprintk_emit(0, -1, NULL, 0, fmt, args);
+//     r = vprintk_emit(0, -1, NULL, 0, fmt, args);
+       r = vsnprintf(buf, sizeof(buf), fmt, args);
        va_end(args);

+       xen_raw_console_write(buf);
+
        return r;
 }
 EXPORT_SYMBOL(printk);

-- 
Julien

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel