* Error in Xen while booting for salvator-X (M3 Board)
@ 2017-02-21 12:03 George John
2017-02-24 14:53 ` Julien Grall
0 siblings, 1 reply; 8+ messages in thread
From: George John @ 2017-02-21 12:03 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1.1: Type: text/plain, Size: 2102 bytes --]
Hi,
I was trying out xen in salvator-X(M3 Board as described in
https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
I ran in to following error:
U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
CPU: Renesas Electronics R8A7796 rev 1.0
Board: Salvator-X
I2C: ready
DRAM: 3.9 GiB
MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
In: serial
Out: serial
Err: serial
Net: Board Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot: 0
819584 bytes read in 89 ms (8.8 MiB/s)
64927 bytes read in 23 ms (2.7 MiB/s)
14038016 bytes read in 1188 ms (11.3 MiB/s)
10319 bytes read in 19 ms (530.3 KiB/s)
## Booting kernel from Legacy Image at 48080000 ...
Image Name: XEN
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 819520 Bytes = 800.3 KiB
Load Address: 78080000
Entry Point: 78080000
Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
Booting using the fdt blob at 0x48000000
Loading Kernel Image ... OK
Using Device Tree in place at 0000000048000000, end 0000000048012d9e
Starting kernel ...
- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000048000000 - 000000007fffffff
(XEN) RAM: 0000000500000000 - 000000053fffffff
(XEN) RAM: 0000000600000000 - 000000063fffffff
(XEN) RAM: 0000000700000000 - 000000073fffffff
(XEN)
(XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
(XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
(XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
(XEN) RESVD[0]: 0000000048000000 - 0000000048010000
(XEN)
(XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
(XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
(XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
000000007fe00000-000000007ff16e01
After this, it hangs. What could be the possible reason?
Regards,
George
[-- Attachment #1.2: Type: text/html, Size: 3055 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-21 12:03 Error in Xen while booting for salvator-X (M3 Board) George John
@ 2017-02-24 14:53 ` Julien Grall
2017-02-24 15:13 ` Oleksandr Tyshchenko
0 siblings, 1 reply; 8+ messages in thread
From: Julien Grall @ 2017-02-24 14:53 UTC (permalink / raw)
To: George John, xen-devel; +Cc: nd
On 21/02/17 12:03, George John wrote:
> Hi,
Hello,
> I was trying out xen in salvator-X(M3 Board as described
> in https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
>
> I ran in to following error:
>
>
> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>
> CPU: Renesas Electronics R8A7796 rev 1.0
> Board: Salvator-X
> I2C: ready
> DRAM: 3.9 GiB
> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
> In: serial
> Out: serial
> Err: serial
> Net: Board Net Initialization Failed
> No ethernet found.
> Hit any key to stop autoboot: 0
> 819584 bytes read in 89 ms (8.8 MiB/s)
> 64927 bytes read in 23 ms (2.7 MiB/s)
> 14038016 bytes read in 1188 ms (11.3 MiB/s)
> 10319 bytes read in 19 ms (530.3 KiB/s)
> ## Booting kernel from Legacy Image at 48080000 ...
> Image Name: XEN
> Image Type: AArch64 Linux Kernel Image (uncompressed)
> Data Size: 819520 Bytes = 800.3 KiB
> Load Address: 78080000
> Entry Point: 78080000
> Verifying Checksum ... OK
> ## Flattened Device Tree blob at 48000000
> Booting using the fdt blob at 0x48000000
> Loading Kernel Image ... OK
> Using Device Tree in place at 0000000048000000, end 0000000048012d9e
>
> Starting kernel ...
>
> - UART enabled -
> - CPU 00000000 booting -
> - Current EL 00000008 -
> - Xen starting at EL2 -
> - Zero BSS -
> - Setting up control registers -
> - Turning on paging -
> - Ready -
> (XEN) Checking for initrd in /chosen
> (XEN) RAM: 0000000048000000 - 000000007fffffff
> (XEN) RAM: 0000000500000000 - 000000053fffffff
> (XEN) RAM: 0000000600000000 - 000000063fffffff
> (XEN) RAM: 0000000700000000 - 000000073fffffff
> (XEN)
> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
> (XEN)
> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
> 000000007fe00000-000000007ff16e01
Which kernel version is it?
>
>
>
>
>
>
> After this, it hangs. What could be the possible reason?
Xen will initialize the heap and then continue into the boot. I would
add more debug around setup_mm to see where it failed.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-24 14:53 ` Julien Grall
@ 2017-02-24 15:13 ` Oleksandr Tyshchenko
2017-02-27 10:29 ` George John
0 siblings, 1 reply; 8+ messages in thread
From: Oleksandr Tyshchenko @ 2017-02-24 15:13 UTC (permalink / raw)
To: George John; +Cc: xen-devel, Julien Grall, nd
Hi,
Not 100% sure, but anyway...
Can you recheck after squashing all memory nodes to a single one.
---
I guess, you have following in your device tree:
memory@48000000 {
device_type = "memory";
/* first 128MB is reserved for secure area. */
reg = <0x0 0x48000000 0x0 0x38000000>;
};
memory@500000000 {
device_type = "memory";
reg = <0x5 0x00000000 0x0 0x40000000>;
};
memory@600000000 {
device_type = "memory";
reg = <0x6 0x00000000 0x0 0x40000000>;
};
memory@700000000 {
device_type = "memory";
reg = <0x7 0x00000000 0x0 0x40000000>;
};
---
Try to make next:
memory@48000000 {
device_type = "memory";
/* first 128MB is reserved for secure area. */
reg = <0x0 0x48000000 0x0 0x38000000>,
<0x5 0x00000000 0x0 0x40000000>,
<0x6 0x00000000 0x0 0x40000000>,
<0x7 0x00000000 0x0 0x40000000>;
};
On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall <julien.grall@arm.com> wrote:
>
>
> On 21/02/17 12:03, George John wrote:
>>
>> Hi,
>
>
> Hello,
>
>
>> I was trying out xen in salvator-X(M3 Board as described
>> in
>> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
>>
>> I ran in to following error:
>>
>>
>> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>>
>> CPU: Renesas Electronics R8A7796 rev 1.0
>> Board: Salvator-X
>> I2C: ready
>> DRAM: 3.9 GiB
>> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
>> In: serial
>> Out: serial
>> Err: serial
>> Net: Board Net Initialization Failed
>> No ethernet found.
>> Hit any key to stop autoboot: 0
>> 819584 bytes read in 89 ms (8.8 MiB/s)
>> 64927 bytes read in 23 ms (2.7 MiB/s)
>> 14038016 bytes read in 1188 ms (11.3 MiB/s)
>> 10319 bytes read in 19 ms (530.3 KiB/s)
>> ## Booting kernel from Legacy Image at 48080000 ...
>> Image Name: XEN
>> Image Type: AArch64 Linux Kernel Image (uncompressed)
>> Data Size: 819520 Bytes = 800.3 KiB
>> Load Address: 78080000
>> Entry Point: 78080000
>> Verifying Checksum ... OK
>> ## Flattened Device Tree blob at 48000000
>> Booting using the fdt blob at 0x48000000
>> Loading Kernel Image ... OK
>> Using Device Tree in place at 0000000048000000, end 0000000048012d9e
>>
>> Starting kernel ...
>>
>> - UART enabled -
>> - CPU 00000000 booting -
>> - Current EL 00000008 -
>> - Xen starting at EL2 -
>> - Zero BSS -
>> - Setting up control registers -
>> - Turning on paging -
>> - Ready -
>> (XEN) Checking for initrd in /chosen
>> (XEN) RAM: 0000000048000000 - 000000007fffffff
>> (XEN) RAM: 0000000500000000 - 000000053fffffff
>> (XEN) RAM: 0000000600000000 - 000000063fffffff
>> (XEN) RAM: 0000000700000000 - 000000073fffffff
>> (XEN)
>> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
>> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
>> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
>> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
>> (XEN)
>> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
>> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
>> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
>> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
>> 000000007fe00000-000000007ff16e01
>
>
> Which kernel version is it?
>
>>
>>
>>
>>
>>
>>
>> After this, it hangs. What could be the possible reason?
>
>
> Xen will initialize the heap and then continue into the boot. I would add
> more debug around setup_mm to see where it failed.
>
> Regards,
>
> --
> Julien Grall
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
--
Regards,
Oleksandr Tyshchenko
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-24 15:13 ` Oleksandr Tyshchenko
@ 2017-02-27 10:29 ` George John
2017-02-27 10:48 ` Oleksandr Tyshchenko
2017-02-27 10:52 ` Andrii Anisov
0 siblings, 2 replies; 8+ messages in thread
From: George John @ 2017-02-27 10:29 UTC (permalink / raw)
To: Oleksandr Tyshchenko; +Cc: xen-devel, Julien Grall, nd
[-- Attachment #1.1: Type: text/plain, Size: 4340 bytes --]
Hi,
Thanks for the reply,
I am using Linux version 4.6.
The memory nodes were already squashed. When I have used a different
version of Xen, it booted to dom0. but still the crash occurs as shown in
the log below.
I have also noticed that for salvator x M3 board(r8a7796) the dtb file used
was r8a7795-salvator-x-dom0.dtb
Is it ok?
regards,
George
On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko <olekstysh@gmail.com>
wrote:
> Hi,
>
> Not 100% sure, but anyway...
>
> Can you recheck after squashing all memory nodes to a single one.
>
> ---
> I guess, you have following in your device tree:
>
> memory@48000000 {
> device_type = "memory";
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>;
> };
>
> memory@500000000 {
> device_type = "memory";
> reg = <0x5 0x00000000 0x0 0x40000000>;
> };
>
> memory@600000000 {
> device_type = "memory";
> reg = <0x6 0x00000000 0x0 0x40000000>;
> };
>
> memory@700000000 {
> device_type = "memory";
> reg = <0x7 0x00000000 0x0 0x40000000>;
> };
>
> ---
> Try to make next:
>
> memory@48000000 {
> device_type = "memory";
> /* first 128MB is reserved for secure area. */
> reg = <0x0 0x48000000 0x0 0x38000000>,
> <0x5 0x00000000 0x0 0x40000000>,
> <0x6 0x00000000 0x0 0x40000000>,
> <0x7 0x00000000 0x0 0x40000000>;
> };
>
>
>
> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall <julien.grall@arm.com>
> wrote:
> >
> >
> > On 21/02/17 12:03, George John wrote:
> >>
> >> Hi,
> >
> >
> > Hello,
> >
> >
> >> I was trying out xen in salvator-X(M3 Board as described
> >> in
> >> https://wiki.xenproject.org/wiki/Xen_ARM_with_
> Virtualization_Extensions/Salvator-X
> >>
> >> I ran in to following error:
> >>
> >>
> >> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
> >>
> >> CPU: Renesas Electronics R8A7796 rev 1.0
> >> Board: Salvator-X
> >> I2C: ready
> >> DRAM: 3.9 GiB
> >> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
> >> In: serial
> >> Out: serial
> >> Err: serial
> >> Net: Board Net Initialization Failed
> >> No ethernet found.
> >> Hit any key to stop autoboot: 0
> >> 819584 bytes read in 89 ms (8.8 MiB/s)
> >> 64927 bytes read in 23 ms (2.7 MiB/s)
> >> 14038016 bytes read in 1188 ms (11.3 MiB/s)
> >> 10319 bytes read in 19 ms (530.3 KiB/s)
> >> ## Booting kernel from Legacy Image at 48080000 ...
> >> Image Name: XEN
> >> Image Type: AArch64 Linux Kernel Image (uncompressed)
> >> Data Size: 819520 Bytes = 800.3 KiB
> >> Load Address: 78080000
> >> Entry Point: 78080000
> >> Verifying Checksum ... OK
> >> ## Flattened Device Tree blob at 48000000
> >> Booting using the fdt blob at 0x48000000
> >> Loading Kernel Image ... OK
> >> Using Device Tree in place at 0000000048000000, end 0000000048012d9e
> >>
> >> Starting kernel ...
> >>
> >> - UART enabled -
> >> - CPU 00000000 booting -
> >> - Current EL 00000008 -
> >> - Xen starting at EL2 -
> >> - Zero BSS -
> >> - Setting up control registers -
> >> - Turning on paging -
> >> - Ready -
> >> (XEN) Checking for initrd in /chosen
> >> (XEN) RAM: 0000000048000000 - 000000007fffffff
> >> (XEN) RAM: 0000000500000000 - 000000053fffffff
> >> (XEN) RAM: 0000000600000000 - 000000063fffffff
> >> (XEN) RAM: 0000000700000000 - 000000073fffffff
> >> (XEN)
> >> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
> >> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
> >> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
> >> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
> >> (XEN)
> >> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
> >> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
> >> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
> >> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
> >> 000000007fe00000-000000007ff16e01
> >
> >
> > Which kernel version is it?
> >
> >>
> >>
> >>
> >>
> >>
> >>
> >> After this, it hangs. What could be the possible reason?
> >
> >
> > Xen will initialize the heap and then continue into the boot. I would add
> > more debug around setup_mm to see where it failed.
> >
> > Regards,
> >
> > --
> > Julien Grall
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > https://lists.xen.org/xen-devel
>
>
>
> --
> Regards,
>
> Oleksandr Tyshchenko
>
[-- Attachment #1.2: Type: text/html, Size: 6267 bytes --]
[-- Attachment #2: log_27_feb2017 --]
[-- Type: application/octet-stream, Size: 20878 bytes --]
U-Boot 2015.04 (Feb 22 2017 - 12:42:36)
CPU: Renesas Electronics R8A7796 rev 1.0
Board: Salvator-X
I2C: ready
DRAM: 3.9 GiB
MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
In: serial
Out: serial
Err: serial
Net: Board Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot: 0
819584 bytes read in 89 ms (8.8 MiB/s)
65696 bytes read in 26 ms (2.4 MiB/s)
14935040 bytes read in 1276 ms (11.2 MiB/s)
10319 bytes read in 16 ms (628.9 KiB/s)
## Booting kernel from Legacy Image at 48080000 ...
Image Name: XEN
Image Type: AArch64 Linux Kernel Image (uncompressed)
Data Size: 819520 Bytes = 800.3 KiB
Load Address: 78080000
Entry Point: 78080000
Verifying Checksum ... OK
## Flattened Device Tree blob at 48000000
Booting using the fdt blob at 0x48000000
Loading Kernel Image ... OK
Using Device Tree in place at 0000000048000000, end 000000004801309f
Starting kernel ...
Xen 4.8.0
(XEN) Xen version 4.8.0 (aarch64-poky-linux-gcc (Linaro GCC 5.2-2015.11-2) 5.2.1 20151005) debug=n Wed Feb 22 12:42:00 IST 2017
(XEN) Latest ChangeSet: Wed Jun 22 17:28:18 2016 +0300 git:3fa5d2a-dirty
(XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
(XEN) 64-bit Execution:
(XEN) Processor Features: 0000000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001124 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00000131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10201105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Using PSCI-1.0 for SMP bringup
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 8333 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f1010000
(XEN) gic_cpu_addr=00000000f1020000
(XEN) gic_hyp_addr=00000000f1040000
(XEN) gic_vcpu_addr=00000000f1060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf102f000
(XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
(XEN) XSM Framework v1.0.0 initialized
(XEN) xsm: Policy len = 0x0000000000010000 start at 0x000000007c000000
(XEN) Flask: 128 avtab hash slots, 280 rules.
(XEN) Flask: 128 avtab hash slots, 280 rules.
(XEN) Flask: 4 users, 3 roles, 38 types, 2 bools
(XEN) Flask: 12 classes, 280 rules
(XEN) Flask: Starting in enforcing mode.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
(XEN) Failed to bring up CPU2
(XEN) Failed to bring up CPU 2 (error -2)
(XEN) Bringing up CPU3
(XEN) Failed to bring up CPU3
(XEN) Failed to bring up CPU 3 (error -2)
(XEN) Bringing up CPU4
(XEN) Failed to bring up CPU4
(XEN) Failed to bring up CPU 4 (error -6)
(XEN) Bringing up CPU5
(XEN) Failed to bring up CPU5
(XEN) Failed to bring up CPU 5 (error -6)
(XEN) Bringing up CPU6
(XEN) Failed to bring up CPU6
(XEN) Failed to bring up CPU 6 (error -6)
(XEN) Bringing up CPU7
(XEN) Failed to bring up CPU7
(XEN) Failed to bring up CPU 7 (error -6)
(XEN) Brought up 2 CPUs
(XEN) P2M: 44-bit IPA with 44-bit PA
(XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
(XEN) I/O virtualisation disabled
(XEN) build-id: 8b6f49c2fa705f5c305695bdb790a9d71c568498
(XEN) alternatives: Patching with alt table 00000000400d5218 -> 00000000400d56a4
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 000000007a000000
(XEN) Allocating 1:1 mappings totalling 752MB for dom0:
(XEN) BANK[0] 0x00000080000000-0x000000a0000000 (512MB)
(XEN) BANK[1] 0x000000b0000000-0x000000bf000000 (240MB)
(XEN) Grant table range: 0x000000bfe00000-0x000000bfe65000
(XEN) Loading zImage from 000000007a000000 to 0000000080080000-0000000082080000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000088000000-0x000000008800f776
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 288kB init memory.
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER4
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER8
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER12
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER16
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER20
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER24
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER28
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER32
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER36
(XEN) d0v0: vGICD: unhandled word write 0xffffffff to ICACTIVER40
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.6.0-yocto-standard (gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2) ) #1 SMP PREEMPT Wed Feb 22 12:19:29 IST 2017
[ 0.000000] Boot CPU: AArch64 Processor [411fd073]
[ 0.000000] debug: ignoring loglevel setting.
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
[ 0.000000] cma: Reserved 128 MiB at 0x00000000b7000000
[ 0.000000] On node 0 totalpages: 192512
[ 0.000000] DMA zone: 3008 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 192512 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv0.2 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: Trusted OS migration not required
[ 0.000000] Xen 4.8 support found
[ 0.000000] percpu: Embedded 20 pages/cpu @ffff800036f46000 s43776 r8192 d29952 u81920
[ 0.000000] pcpu-alloc: s43776 r8192 d29952 u81920 alloc=20*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Detected PIPT I-cache on CPU0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 189504
[ 0.000000] Kernel command line: console=hvc0 root=/dev/mmcblk1p1 rw rootwait rootfstype=ext4 ignore_loglevel cma=128M
[ 0.000000] log_buf_len individual max cpu contribution: 4096 bytes
[ 0.000000] log_buf_len total cpu_extra contributions: 12288 bytes
[ 0.000000] log_buf_len min size: 16384 bytes
[ 0.000000] log_buf_len: 32768 bytes
[ 0.000000] early log buf free: 14756(90%)
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.000000] software IO TLB [mem 0xb1c00000-0xb5c00000] (64MB) mapped at [ffff800031c00000-ffff800035bfffff]
[ 0.000000] Memory: 539304K/770048K available (8936K kernel code, 761K rwdata, 3924K rodata, 960K init, 324K bss, 99672K reserved, 131072K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] modules : 0xffff000000000000 - 0xffff000008000000 ( 128 MB)
[ 0.000000] vmalloc : 0xffff000008000000 - 0xffff7dffbfff0000 (129022 GB)
[ 0.000000] .text : 0xffff000008080000 - 0xffff000008930000 ( 8896 KB)
[ 0.000000] .rodata : 0xffff000008930000 - 0xffff000008d10000 ( 3968 KB)
[ 0.000000] .init : 0xffff000008d10000 - 0xffff000008e00000 ( 960 KB)
[ 0.000000] .data : 0xffff000008e00000 - 0xffff000008ebe400 ( 761 KB)
[ 0.000000] .bss : 0xffff000008ebe400 - 0xffff000008f0f6f0 ( 325 KB)
[ 0.000000] fixed : 0xffff7dfffe7fd000 - 0xffff7dfffec00000 ( 4108 KB)
[ 0.000000] PCI I/O : 0xffff7dfffee00000 - 0xffff7dffffe00000 ( 16 MB)
[ 0.000000] vmemmap : 0xffff7e0000000000 - 0xffff800000000000 ( 2048 GB maximum)
[ 0.000000] 0xffff7e0000000000 - 0xffff7e0000fc0000 ( 15 MB actual)
[ 0.000000] memory : 0xffff800000000000 - 0xffff80003f000000 ( 1008 MB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 64.
[ 0.000000] RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4
[ 0.000000] NR_IRQS:64 nr_irqs:64 0
[ 0.000000] Architected cp15 timer(s) running at 8.33MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1ec02923e, max_idle_ns: 440795202125 ns
[ 0.000004] sched_clock: 56 bits at 8MHz, resolution 120ns, wraps every 2199023255496ns
[ 0.000320] Console: colour dummy device 80x25
[ 0.349885] console [hvc0] enabled
[ 0.353360] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.66 BogoMIPS (lpj=33333)
[ 0.363623] pid_max: default: 32768 minimum: 301
[ 0.368341] Security Framework initialized
[ 0.372467] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.379176] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.387184] ASID allocator initialised with 65536 entries
[ 0.392716] xen:grant_table: Grant tables using version 1 layout
[ 0.398654] Grant table initialized
[ 0.402193] xen:events: Using FIFO-based ABI
[ 0.406500] Xen: initializing cpu0
[ 0.428049] EFI services will not be available.
[ 0.456732] Detected PIPT I-cache on CPU1
[ 0.456829] Xen: initializing cpu1
[ 0.456852] CPU1: Booted secondary processor [411fd073]
[ 0.472850] Detected PIPT I-cache on CPU2
[ 0.472916] Xen: initializing cpu2
[ 0.472933] CPU2: Booted secondary processor [411fd073]
[ 0.488809] Detected PIPT I-cache on CPU3
[ 0.488864] Xen: initializing cpu3
[ 0.488879] CPU3: Booted secondary processor [411fd073]
[ 0.488942] Brought up 4 CPUs
[ 0.530189] SMP: Total of 4 processors activated.
[ 0.534946] CPU features: detected feature: 32-bit EL0 Support
[ 0.540821] CPU: All CPU(s) started at EL1
[ 0.700955] devtmpfs: initialized
[ 0.710630] DMI not present or invalid.
[ 0.714732] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.727265] pinctrl core: initialized pinctrl subsystem
[ 0.735025] NET: Registered protocol family 16
[ 0.741938] vdso: 2 pages (1 code @ ffff000008936000, 1 data @ ffff000008e04000)
[ 0.749316] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.756830] DMA: preallocated 256 KiB pool for atomic allocations
[ 0.762941] xen:swiotlb_xen: Warning: only able to allocate 4 MB for software IO TLB
[ 0.771465] software IO TLB [mem 0xb0c00000-0xb1000000] (4MB) mapped at [ffff800030c00000-ffff800030ffffff]
[ 0.781366] Serial: AMBA PL011 UART driver
[ 0.790583] sh-pfc e6060000.pfc: r8a77950_pfc support registered
[ 0.796847] renesas_irqc e61c0000.interrupt-controller: failed to add to PM domain always-on: -517
[ 0.815528] rcar_hwspinlock e62600c0.mfis-lock: failed to add to PM domain always-on: -517
[ 0.854356] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.863002] ACPI: Interpreter disabled.
[ 0.867361] rcar-cpufreq: use avs value: 0
[ 0.871956] xen:balloon: Initialising balloon driver
[ 0.877394] xen_balloon: Initialising balloon driver
[ 0.884664] vgaarb: loaded
[ 0.887610] SCSI subsystem initialized
[ 0.891715] libata version 3.00 loaded.
[ 0.896065] usbcore: registered new interface driver usbfs
[ 0.901551] usbcore: registered new interface driver hub
[ 0.906947] usbcore: registered new device driver usb
[ 0.912893] media: Linux media interface: v0.10
[ 0.917399] Linux video capture interface: v2.00
[ 0.922050] pps_core: LinuxPPS API ver. 1 registered
[ 0.927020] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.936200] PTP clock support registered
[ 0.940272] dmi: Firmware registration failed.
[ 0.946499] Advanced Linux Sound Architecture Driver Initialized.
[ 0.953654] i2c-sh_mobile e60b0000.i2c: I2C adapter 7, bus speed 100000 Hz
[ 1.171521] clocksource: Switched to clocksource arch_sys_counter
[ 1.177756] VFS: Disk quotas dquot_6.6.0
[ 1.181655] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 1.188807] pnp: PnP ACPI: disabled
[ 1.211014] /soc/thermal-zones/sensor-thermal3/cooling-maps/map0: could not find phandle
[ 1.219162] missing cooling_device property
[ 1.223264] failed to build thermal zone sensor-thermal3: -22
[ 1.229215] NET: Registered protocol family 2
[ 1.233961] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 1.240956] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[ 1.247612] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.253983] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 1.259859] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 1.266390] NET: Registered protocol family 1
[ 1.271093] RPC: Registered named UNIX socket transport module.
[ 1.276938] RPC: Registered udp transport module.
[ 1.281681] RPC: Registered tcp transport module.
[ 1.286422] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.292927] PCI: CLS 0 bytes, default 128
[ 1.297728] /soc/pmu_a57: could not find phandle
[ 1.302392] hw perfevents: enabled with armv8_cortex_a57 PMU driver, 1 counters available
[ 1.310573] /soc/pmu_a53: could not find phandle
[ 1.315192] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 1 counters available
[ 1.323835] kvm [1]: HYP mode not available
[ 1.333849] futex hash table entries: 1024 (order: 5, 131072 bytes)
[ 1.340187] audit: initializing netlink subsys (disabled)
[ 1.345586] audit: type=2000 audit(0.907:1): initialized
[ 1.352070] workingset: timestamp_bits=44 max_order=18 bucket_order=0
[ 1.364773] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 1.371361] NFS: Registering the id_resolver key type
[ 1.376381] Key type id_resolver registered
[ 1.380578] Key type id_legacy registered
[ 1.384909] fuse init (API version 7.24)
[ 1.389949] 9p: Installing v9fs 9p2000 file system support
[ 1.401264] io scheduler noop registered
[ 1.405286] io scheduler cfq registered (default)
[ 1.415535] gpio_rcar e6050000.gpio: driving 16 GPIOs
[ 1.420976] gpio_rcar e6051000.gpio: driving 28 GPIOs
[ 1.426343] gpio_rcar e6052000.gpio: driving 15 GPIOs
[ 1.431673] gpio_rcar e6053000.gpio: driving 16 GPIOs
[ 1.436988] gpio_rcar e6054000.gpio: driving 18 GPIOs
[ 1.442291] gpio_rcar e6055000.gpio: driving 26 GPIOs
[ 1.447617] gpio_rcar e6055400.gpio: driving 32 GPIOs
[ 1.452884] gpio_rcar e6055800.gpio: driving 4 GPIOs
[ 1.459773] PCI host bridge /soc/pcie@fe000000 ranges:
[ 1.464856] IO 0xfe100000..0xfe1fffff -> 0x00000000
[ 1.470030] MEM 0xfe200000..0xfe3fffff -> 0xfe200000
[ 1.475198] MEM 0x30000000..0x37ffffff -> 0x30000000
[ 1.480394] MEM 0x38000000..0x3fffffff -> 0x38000000
[ 1.535691] rcar-pcie fe000000.pcie: PCIe link down
[ 1.540603] PCI host bridge /soc/pcie@ee800000 ranges:
[ 1.545670] IO 0xee900000..0xee9fffff -> 0x00000000
[ 1.550849] MEM 0xeea00000..0xeebfffff -> 0xeea00000
[ 1.556031] MEM 0xc0000000..0xc7ffffff -> 0xc0000000
[ 1.561213] MEM 0xc8000000..0xcfffffff -> 0xc8000000
[ 1.616471] rcar-pcie ee800000.pcie: PCIe link down
[ 1.704108] xen:xen_evtchn: Event-channel device installed
[ 1.712615] bd9571mwv 7-0030: bd9571mwv probed
[ 1.726029] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.734268] SuperH (H)SCI(F) driver initialized
[ 1.739288] e6e68000.serial: ttySC1 at MMIO 0xe6e68000 (irq = 139, base_baud = 0) is a scif
[ 1.748313] msm_serial: driver initialized
[ 1.752664] [drm] Initialized drm 1.1.0 20060810
[ 1.758411] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 1.764979] [drm] No driver support for vblank timestamp query.
[ 1.771149] rcar-du feb00000.display: failed to initialize DRM/KMS (-517)
[ 1.779455] Unable to detect cache hierarchy from DT for CPU 0
[ 1.792073] loop: module loaded
(XEN) domain_crash_sync called from traps.c:2756
(XEN) Domain 0 (vcpu#3) crashed on cpu#1:
(XEN) ----[ Xen-4.8.0 arm64 debug=n Not tainted ]----
(XEN) CPU: 1
(XEN) PC: ffff00000856f530
(XEN) LR: ffff00000856f780
(XEN) SP_EL0: ffff800031870000
(XEN) SP_EL1: ffff800031873c00
(XEN) CPSR: 80000045 MODE:64-bit EL1h (Guest Kernel, handler)
(XEN) X0: ffff00000806570c X1: 0000000000002303 X2: 0000000000000001
(XEN) X3: ffff000008065104 X4: ffff000008065100 X5: ffff000008065118
(XEN) X6: ffff000008065114 X7: ffff000008065110 X8: ffff00000806510c
(XEN) X9: ffff000008065108 X10: 0000000000001400 X11: ffff000008066000
(XEN) X12: ffff000008e09000 X13: ffff000008e09450 X14: ffff000008065fff
(XEN) X15: ffff000008e23000 X16: 0000000000000012 X17: 0000000000000007
(XEN) X18: ffff000008065fff X19: ffff000008064000 X20: ffff80003096df18
(XEN) X21: ffff80003111d810 X22: ffff000008e68000 X23: ffff80003111d800
(XEN) X24: 00000000000000a1 X25: ffff000008d62b48 X26: ffff000008d10470
(XEN) X27: ffff000008dcd3a8 X28: 0000000000000000 FP: ffff800031873c00
(XEN)
(XEN) ELR_EL1: ffff0000080fa5b0
(XEN) ESR_EL1: 00000000
(XEN) FAR_EL1: 0000000000000000
(XEN)
(XEN) SCTLR_EL1: 34d5d91d
(XEN) TCR_EL1: 34b5103510
(XEN) TTBR0_EL1: 0000000080ec2000
(XEN) TTBR1_EL1: 0000000080f13000
(XEN)
(XEN) VTCR_EL2: 80043594
(XEN) VTTBR_EL2: 000100067ff20000
(XEN)
(XEN) SCTLR_EL2: 30cd183d
(XEN) HCR_EL2: 000000008038663f
(XEN) TTBR0_EL2: 00000000bff00000
(XEN)
(XEN) ESR_EL2: bf000000
(XEN) HPFAR_EL2: 0000000000000000
(XEN) FAR_EL2: 0000000000000000
(XEN)
(XEN) Guest stack trace from sp=ffff800031873c00:
(XEN) ffff800031873c20 ffff00000856f780 ffff800030a08318 ffff000008e68000
(XEN) ffff800031873c60 ffff000008508e50 ffff000008e68e50 ffff80003111d810
(XEN) ffff000008e68e28 ffff000008e68e50 0000000000000000 ffff000008d01428
(XEN) ffff800031873c90 ffff00000850732c ffff80003111d810 ffff000008eed000
(XEN) 0000000000000000 ffff000008eed000 ffff800031873cd0 ffff000008507484
(XEN) ffff80003111d810 ffff000008e68e50 ffff80003111d870 ffff000008e62e98
(XEN) ffff000008e62000 ffff0000085052e4 ffff800031873d00 ffff0000085052d8
(XEN) 0000000000000000 ffff000008e68e50 ffff0000085073d8 ffff800031873d50
(XEN) ffff800031873d40 ffff000008506ab8 ffff000008e68e50 ffff80003096de00
(XEN) 0000000000000000 00000000ffffffe0 ffff800031805ea8 ffff8000310af968
(XEN) ffff800031873d50 ffff0000085066a8 ffff800031873d90 ffff000008507c48
(XEN) ffff000008e68e50 ffff000008e11920 ffff800030a08080 ffff000008d3bd10
(XEN) 0000000000000000 ffff0000080819c4 ffff800031873db0 ffff000008508d90
(XEN) ffff000008e11920 ffff000008e11920 ffff800031873dc0 ffff000008d3bd28
(XEN) ffff800031873dd0 ffff0000080819d4 ffff800031873e50 ffff000008d10cbc
(XEN) 0000000000000128 ffff000008d62be0 ffff000008ec3000 0000000000000006
(XEN) ffff000008ec3000 ffff000008d10470 ffff000008dccd00 0000000000000000
(XEN) ffff000008ec3000 ffff000008bc46f0 0000000600000006 0000000000000000
(XEN) 0000000000000000 ffff000008d01428 ffff800031873eb0 ffff000008911890
(XEN) ffff000008911880 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffff000008084e10
(XEN) ffff000008911880 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000005
(XEN) 0000000000000000 0000000000000000 ffffffffffffffff ffffffffbffeffff
(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
[-- Attachment #3: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-27 10:29 ` George John
@ 2017-02-27 10:48 ` Oleksandr Tyshchenko
2017-02-27 10:55 ` Oleksandr Andrushchenko
2017-02-27 10:52 ` Andrii Anisov
1 sibling, 1 reply; 8+ messages in thread
From: Oleksandr Tyshchenko @ 2017-02-27 10:48 UTC (permalink / raw)
To: George John; +Cc: Oleksandr Andrushchenko, xen-devel, Julien Grall, nd
Hi.
On Mon, Feb 27, 2017 at 12:29 PM, George John <georgeeldhojohn@gmail.com> wrote:
> Hi,
> Thanks for the reply,
> I am using Linux version 4.6.
> The memory nodes were already squashed. When I have used a different version
> of Xen, it booted to dom0. but still the crash occurs as shown in the log
> below.
>
> I have also noticed that for salvator x M3 board(r8a7796) the dtb file used
> was r8a7795-salvator-x-dom0.dtb
> Is it ok?
I don't know about M3 board.
CC my colleague who plays with M3 board. Hope, that he can shed some lights.
>
> regards,
> George
>
> On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko <olekstysh@gmail.com>
> wrote:
>>
>> Hi,
>>
>> Not 100% sure, but anyway...
>>
>> Can you recheck after squashing all memory nodes to a single one.
>>
>> ---
>> I guess, you have following in your device tree:
>>
>> memory@48000000 {
>> device_type = "memory";
>> /* first 128MB is reserved for secure area. */
>> reg = <0x0 0x48000000 0x0 0x38000000>;
>> };
>>
>> memory@500000000 {
>> device_type = "memory";
>> reg = <0x5 0x00000000 0x0 0x40000000>;
>> };
>>
>> memory@600000000 {
>> device_type = "memory";
>> reg = <0x6 0x00000000 0x0 0x40000000>;
>> };
>>
>> memory@700000000 {
>> device_type = "memory";
>> reg = <0x7 0x00000000 0x0 0x40000000>;
>> };
>>
>> ---
>> Try to make next:
>>
>> memory@48000000 {
>> device_type = "memory";
>> /* first 128MB is reserved for secure area. */
>> reg = <0x0 0x48000000 0x0 0x38000000>,
>> <0x5 0x00000000 0x0 0x40000000>,
>> <0x6 0x00000000 0x0 0x40000000>,
>> <0x7 0x00000000 0x0 0x40000000>;
>> };
>>
>>
>>
>> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall <julien.grall@arm.com>
>> wrote:
>> >
>> >
>> > On 21/02/17 12:03, George John wrote:
>> >>
>> >> Hi,
>> >
>> >
>> > Hello,
>> >
>> >
>> >> I was trying out xen in salvator-X(M3 Board as described
>> >> in
>> >>
>> >> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
>> >>
>> >> I ran in to following error:
>> >>
>> >>
>> >> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>> >>
>> >> CPU: Renesas Electronics R8A7796 rev 1.0
>> >> Board: Salvator-X
>> >> I2C: ready
>> >> DRAM: 3.9 GiB
>> >> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
>> >> In: serial
>> >> Out: serial
>> >> Err: serial
>> >> Net: Board Net Initialization Failed
>> >> No ethernet found.
>> >> Hit any key to stop autoboot: 0
>> >> 819584 bytes read in 89 ms (8.8 MiB/s)
>> >> 64927 bytes read in 23 ms (2.7 MiB/s)
>> >> 14038016 bytes read in 1188 ms (11.3 MiB/s)
>> >> 10319 bytes read in 19 ms (530.3 KiB/s)
>> >> ## Booting kernel from Legacy Image at 48080000 ...
>> >> Image Name: XEN
>> >> Image Type: AArch64 Linux Kernel Image (uncompressed)
>> >> Data Size: 819520 Bytes = 800.3 KiB
>> >> Load Address: 78080000
>> >> Entry Point: 78080000
>> >> Verifying Checksum ... OK
>> >> ## Flattened Device Tree blob at 48000000
>> >> Booting using the fdt blob at 0x48000000
>> >> Loading Kernel Image ... OK
>> >> Using Device Tree in place at 0000000048000000, end 0000000048012d9e
>> >>
>> >> Starting kernel ...
>> >>
>> >> - UART enabled -
>> >> - CPU 00000000 booting -
>> >> - Current EL 00000008 -
>> >> - Xen starting at EL2 -
>> >> - Zero BSS -
>> >> - Setting up control registers -
>> >> - Turning on paging -
>> >> - Ready -
>> >> (XEN) Checking for initrd in /chosen
>> >> (XEN) RAM: 0000000048000000 - 000000007fffffff
>> >> (XEN) RAM: 0000000500000000 - 000000053fffffff
>> >> (XEN) RAM: 0000000600000000 - 000000063fffffff
>> >> (XEN) RAM: 0000000700000000 - 000000073fffffff
>> >> (XEN)
>> >> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
>> >> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
>> >> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
>> >> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
>> >> (XEN)
>> >> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
>> >> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
>> >> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
>> >> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
>> >> 000000007fe00000-000000007ff16e01
>> >
>> >
>> > Which kernel version is it?
>> >
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> After this, it hangs. What could be the possible reason?
>> >
>> >
>> > Xen will initialize the heap and then continue into the boot. I would
>> > add
>> > more debug around setup_mm to see where it failed.
>> >
>> > Regards,
>> >
>> > --
>> > Julien Grall
>> >
>> > _______________________________________________
>> > Xen-devel mailing list
>> > Xen-devel@lists.xen.org
>> > https://lists.xen.org/xen-devel
>>
>>
>>
>> --
>> Regards,
>>
>> Oleksandr Tyshchenko
>
>
--
Regards,
Oleksandr Tyshchenko
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-27 10:29 ` George John
2017-02-27 10:48 ` Oleksandr Tyshchenko
@ 2017-02-27 10:52 ` Andrii Anisov
1 sibling, 0 replies; 8+ messages in thread
From: Andrii Anisov @ 2017-02-27 10:52 UTC (permalink / raw)
To: George John, Oleksandr Tyshchenko; +Cc: xen-devel, Julien Grall, nd
[-- Attachment #1.1: Type: text/plain, Size: 1510 bytes --]
Dear George,
Actually r8a7796 and r8a7795 are different chips with different
peripherals, so you should adjust your r8a7796-xxx.dtb.
I'm not really sure what the problem is with XEN 4.6, but the crash
point you are stepped in with 4.8 is commented as following
/*
* Currently, to ensure hypervisor safety, when we received a
* guest-generated vSerror/vAbort, we just crash the guest to protect
* the hypervisor. In future we can better handle this by injecting
* a vSerror/vAbort to the guest.
*/
So I guess you see the abort on access to a peripheral missing on
r8a7796 but described in a device tree for r8a7795.
--
*Andrii Anisov*
*Lead Systems Engineer*
*Office: *+380 44 390 5457 <tel:+380%2044%20390%205457> *x* 66766
<tel:66766>*Cell: *+380 50 5738852 <tel:+380%2050%205738852>*Email:
*andrii_anisov@epam.com <mailto:andrii_anisov@epam.com>
*Kyiv**,* *Ukraine *(GMT+3)*epam.com <http://www.epam.com>*
CONFIDENTIALITY CAUTION AND DISCLAIMER
This message is intended only for the use of the individual(s) or
entity(ies) to which it is addressed and contains information that is
legally privileged and confidential. If you are not the intended
recipient, or the person responsible for delivering the message to the
intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
All unintended recipients are obliged to delete this message and destroy
any printed copies.
[-- Attachment #1.2: Type: text/html, Size: 5359 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-27 10:48 ` Oleksandr Tyshchenko
@ 2017-02-27 10:55 ` Oleksandr Andrushchenko
2017-02-28 15:01 ` George John
0 siblings, 1 reply; 8+ messages in thread
From: Oleksandr Andrushchenko @ 2017-02-27 10:55 UTC (permalink / raw)
To: Oleksandr Tyshchenko, George John; +Cc: xen-devel, Julien Grall, nd
[-- Attachment #1: Type: text/plain, Size: 4871 bytes --]
Hi,
PFA the DTS I use for M3ULCB board
On 02/27/2017 12:48 PM, Oleksandr Tyshchenko wrote:
> Hi.
>
> On Mon, Feb 27, 2017 at 12:29 PM, George John <georgeeldhojohn@gmail.com> wrote:
>> Hi,
>> Thanks for the reply,
>> I am using Linux version 4.6.
>> The memory nodes were already squashed. When I have used a different version
>> of Xen, it booted to dom0. but still the crash occurs as shown in the log
>> below.
>>
>> I have also noticed that for salvator x M3 board(r8a7796) the dtb file used
>> was r8a7795-salvator-x-dom0.dtb
>> Is it ok?
> I don't know about M3 board.
> CC my colleague who plays with M3 board. Hope, that he can shed some lights.
>
>> regards,
>> George
>>
>> On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko <olekstysh@gmail.com>
>> wrote:
>>> Hi,
>>>
>>> Not 100% sure, but anyway...
>>>
>>> Can you recheck after squashing all memory nodes to a single one.
>>>
>>> ---
>>> I guess, you have following in your device tree:
>>>
>>> memory@48000000 {
>>> device_type = "memory";
>>> /* first 128MB is reserved for secure area. */
>>> reg = <0x0 0x48000000 0x0 0x38000000>;
>>> };
>>>
>>> memory@500000000 {
>>> device_type = "memory";
>>> reg = <0x5 0x00000000 0x0 0x40000000>;
>>> };
>>>
>>> memory@600000000 {
>>> device_type = "memory";
>>> reg = <0x6 0x00000000 0x0 0x40000000>;
>>> };
>>>
>>> memory@700000000 {
>>> device_type = "memory";
>>> reg = <0x7 0x00000000 0x0 0x40000000>;
>>> };
>>>
>>> ---
>>> Try to make next:
>>>
>>> memory@48000000 {
>>> device_type = "memory";
>>> /* first 128MB is reserved for secure area. */
>>> reg = <0x0 0x48000000 0x0 0x38000000>,
>>> <0x5 0x00000000 0x0 0x40000000>,
>>> <0x6 0x00000000 0x0 0x40000000>,
>>> <0x7 0x00000000 0x0 0x40000000>;
>>> };
>>>
>>>
>>>
>>> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall <julien.grall@arm.com>
>>> wrote:
>>>>
>>>> On 21/02/17 12:03, George John wrote:
>>>>> Hi,
>>>>
>>>> Hello,
>>>>
>>>>
>>>>> I was trying out xen in salvator-X(M3 Board as described
>>>>> in
>>>>>
>>>>> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Salvator-X
>>>>>
>>>>> I ran in to following error:
>>>>>
>>>>>
>>>>> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>>>>>
>>>>> CPU: Renesas Electronics R8A7796 rev 1.0
>>>>> Board: Salvator-X
>>>>> I2C: ready
>>>>> DRAM: 3.9 GiB
>>>>> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
>>>>> In: serial
>>>>> Out: serial
>>>>> Err: serial
>>>>> Net: Board Net Initialization Failed
>>>>> No ethernet found.
>>>>> Hit any key to stop autoboot: 0
>>>>> 819584 bytes read in 89 ms (8.8 MiB/s)
>>>>> 64927 bytes read in 23 ms (2.7 MiB/s)
>>>>> 14038016 bytes read in 1188 ms (11.3 MiB/s)
>>>>> 10319 bytes read in 19 ms (530.3 KiB/s)
>>>>> ## Booting kernel from Legacy Image at 48080000 ...
>>>>> Image Name: XEN
>>>>> Image Type: AArch64 Linux Kernel Image (uncompressed)
>>>>> Data Size: 819520 Bytes = 800.3 KiB
>>>>> Load Address: 78080000
>>>>> Entry Point: 78080000
>>>>> Verifying Checksum ... OK
>>>>> ## Flattened Device Tree blob at 48000000
>>>>> Booting using the fdt blob at 0x48000000
>>>>> Loading Kernel Image ... OK
>>>>> Using Device Tree in place at 0000000048000000, end 0000000048012d9e
>>>>>
>>>>> Starting kernel ...
>>>>>
>>>>> - UART enabled -
>>>>> - CPU 00000000 booting -
>>>>> - Current EL 00000008 -
>>>>> - Xen starting at EL2 -
>>>>> - Zero BSS -
>>>>> - Setting up control registers -
>>>>> - Turning on paging -
>>>>> - Ready -
>>>>> (XEN) Checking for initrd in /chosen
>>>>> (XEN) RAM: 0000000048000000 - 000000007fffffff
>>>>> (XEN) RAM: 0000000500000000 - 000000053fffffff
>>>>> (XEN) RAM: 0000000600000000 - 000000063fffffff
>>>>> (XEN) RAM: 0000000700000000 - 000000073fffffff
>>>>> (XEN)
>>>>> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
>>>>> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
>>>>> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
>>>>> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
>>>>> (XEN)
>>>>> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
>>>>> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
>>>>> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
>>>>> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
>>>>> 000000007fe00000-000000007ff16e01
>>>>
>>>> Which kernel version is it?
>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> After this, it hangs. What could be the possible reason?
>>>>
>>>> Xen will initialize the heap and then continue into the boot. I would
>>>> add
>>>> more debug around setup_mm to see where it failed.
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Julien Grall
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xen.org
>>>> https://lists.xen.org/xen-devel
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Oleksandr Tyshchenko
>>
>
>
[-- Attachment #2: r8a7796-m3ulcb-dom0.dts --]
[-- Type: text/plain, Size: 10146 bytes --]
/*
* Device Tree Source for the M3ULCB (R-Car Starter Kit Pro) board
*
* Copyright (C) 2016-2017 Renesas Electronics Corp.
* Copyright (C) 2016 Cogent Embedded, Inc.
*
* This file is licensed under the terms of the GNU General Public License
* version 2. This program is licensed "as is" without any warranty of any
* kind, whether express or implied.
*/
/dts-v1/;
#include "r8a7796.dtsi"
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/input/input.h>
/ {
model = "Renesas M3ULCB board based on r8a7796";
compatible = "renesas,m3ulcb", "renesas,r8a7796";
aliases {
serial0 = &scif2;
ethernet0 = &avb;
};
chosen {
bootargs = "dom0_mem=752M console=dtuart dtuart=serial0 dom0_max_vcpus=4 bootscrub=0 flask_enforcing=1 loglvl=all";
xen,dom0-bootargs = "console=hvc0 root=/dev/mmcblk1p1 rw rootwait rootfstype=ext4 ignore_loglevel cma=128M";
//xen,dom0-bootargs = "console=hvc0 root=/dev/nfs nfsroot=192.168.1.1:/tftpboot/dom0-rootfs ip=192.168.1.21 rw rootwait rootfstype=ext4 ignore_loglevel cma=128M";
modules {
#address-cells = <2>;
#size-cells = <2>;
module@1 {
compatible = "xen,linux-zimage", "xen,multiboot-module";
reg = <0x0 0x7a000000 0x0 0x02000000>;
};
module@2 {
compatible = "xen,xsm-policy", "xen,multiboot-module";
reg = <0x0 0x7c000000 0x0 0x10000>;
};
};
};
memory@48000000 {
device_type = "memory";
/* first 128MB is reserved for secure area. */
reg = <0x0 0x48000000 0x0 0x38000000>,
<0x6 0x00000000 0x0 0x40000000>;
};
soc {
pll: pll@fff00000 {
reg = <0 0xfff00000 0 0x1000>;
};
avs: avs@e60a0000 {
reg = <0 0xe60a0000 0 0x1000>;
};
lossy: lossy@47fd7000 {
reg = <0 0x47fd7000 0 0x1000>;
};
};
leds {
compatible = "gpio-leds";
led5 {
gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
};
led6 {
gpios = <&gpio6 13 GPIO_ACTIVE_HIGH>;
};
};
keyboard {
compatible = "gpio-keys";
key-1 {
linux,code = <KEY_1>;
label = "SW3";
wakeup-source;
debounce-interval = <20>;
gpios = <&gpio6 11 GPIO_ACTIVE_LOW>;
};
};
reg_1p8v: regulator0 {
compatible = "regulator-fixed";
regulator-name = "fixed-1.8V";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
regulator-boot-on;
regulator-always-on;
};
reg_3p3v: regulator1 {
compatible = "regulator-fixed";
regulator-name = "fixed-3.3V";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
vcc_sdhi0: regulator-vcc-sdhi0 {
compatible = "regulator-fixed";
regulator-name = "SDHI0 Vcc";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
gpio = <&gpio5 2 GPIO_ACTIVE_HIGH>;
enable-active-high;
};
vccq_sdhi0: regulator-vccq-sdhi0 {
compatible = "regulator-gpio";
regulator-name = "SDHI0 VccQ";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
gpios = <&gpio5 1 GPIO_ACTIVE_HIGH>;
gpios-states = <1>;
states = <3300000 1
1800000 0>;
};
x12_clk: x12 {
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <24576000>;
};
audio_clkout: audio-clkout {
/*
* This is same as <&rcar_sound 0>
* but needed to avoid cs2000/rcar_sound probe dead-lock
*/
compatible = "fixed-clock";
#clock-cells = <0>;
clock-frequency = <11289600>;
};
rsnd_ak4613: sound {
compatible = "simple-audio-card";
simple-audio-card,format = "left_j";
simple-audio-card,bitclock-master = <&sndcpu>;
simple-audio-card,frame-master = <&sndcpu>;
sndcpu: simple-audio-card,cpu {
sound-dai = <&rcar_sound>;
};
sndcodec: simple-audio-card,codec {
sound-dai = <&ak4613>;
};
};
vspm_if {
compatible = "renesas,vspm_if";
};
hdmi-out {
compatible = "hdmi-connector";
type = "a";
port {
hdmi0_con: endpoint {
remote-endpoint = <&rcar_dw_hdmi0_out>;
};
};
};
};
&extal_clk {
clock-frequency = <16666666>;
};
&extalr_clk {
clock-frequency = <32768>;
};
&a57_0 {
cpu-supply = <&vdd_dvfs>;
};
&pfc {
pinctrl-0 = <&scif_clk_pins>;
pinctrl-names = "default";
scif2_pins: scif2 {
groups = "scif2_data_a";
function = "scif2";
};
scif_clk_pins: scif_clk {
groups = "scif_clk_a";
function = "scif_clk";
};
i2c2_pins: i2c2 {
groups = "i2c2_a";
function = "i2c2";
};
avb_pins: avb {
groups = "avb_mdc";
function = "avb";
};
sdhi0_pins: sd0 {
groups = "sdhi0_data4", "sdhi0_ctrl";
function = "sdhi0";
power-source = <3300>;
};
sdhi0_pins_uhs: sd0_uhs {
groups = "sdhi0_data4", "sdhi0_ctrl";
function = "sdhi0";
power-source = <1800>;
};
sdhi2_pins: sd2 {
groups = "sdhi2_data8", "sdhi2_ctrl";
function = "sdhi2";
power-source = <3300>;
};
sdhi2_pins_uhs: sd2_uhs {
groups = "sdhi2_data8", "sdhi2_ctrl";
function = "sdhi2";
power-source = <1800>;
};
msiof1_pins: spi2 {
groups = "msiof1_clk_a", "msiof1_sync_a",
"msiof1_rxd_a", "msiof1_txd_a";
function = "msiof1";
};
sound_pins: sound {
groups = "ssi0129_ctrl", "ssi0_data", "ssi1_data_a";
function = "ssi";
};
sound_clk_pins: sound-clk {
groups = "audio_clk_a_a", "audio_clk_b_a", "audio_clk_c_a",
"audio_clkout_a", "audio_clkout3_a";
function = "audio_clk";
};
usb1_pins: usb1 {
groups = "usb1";
function = "usb1";
};
};
&avb {
pinctrl-0 = <&avb_pins>;
pinctrl-names = "default";
renesas,no-ether-link;
phy-handle = <&phy0>;
status = "okay";
phy-gpios = <&gpio2 11 GPIO_ACTIVE_LOW>;
phy0: ethernet-phy@0 {
rxc-skew-ps = <1500>;
rxdv-skew-ps = <420>; /* default */
rxd0-skew-ps = <420>; /* default */
rxd1-skew-ps = <420>; /* default */
rxd2-skew-ps = <420>; /* default */
rxd3-skew-ps = <420>; /* default */
txc-skew-ps = <900>; /* default */
txen-skew-ps = <420>; /* default */
txd0-skew-ps = <420>; /* default */
txd1-skew-ps = <420>; /* default */
txd2-skew-ps = <420>; /* default */
txd3-skew-ps = <420>; /* default */
reg = <0>;
interrupt-parent = <&gpio2>;
interrupts = <11 IRQ_TYPE_LEVEL_LOW>;
};
};
&du_dotclkin0 {
clock-frequency = <148500000>;
};
&du_dotclkin1 {
clock-frequency = <33000000>;
};
&du_dotclkin2 {
clock-frequency = <108000000>;
};
&du {
status = "okay";
ports {
port@1 {
endpoint {
remote-endpoint = <&rcar_dw_hdmi0_in>;
};
};
};
};
&hdmi0 {
status = "okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
rcar_dw_hdmi0_in: endpoint {
remote-endpoint = <&du_out_hdmi0>;
};
};
port@1 {
reg = <1>;
rcar_dw_hdmi0_out: endpoint {
remote-endpoint = <&hdmi0_con>;
};
};
};
};
&sdhi0 {
pinctrl-0 = <&sdhi0_pins>;
pinctrl-1 = <&sdhi0_pins_uhs>;
pinctrl-names = "default", "state_uhs";
vmmc-supply = <&vcc_sdhi0>;
vqmmc-supply = <&vccq_sdhi0>;
cd-gpios = <&gpio3 12 GPIO_ACTIVE_LOW>;
bus-width = <4>;
sd-uhs-sdr50;
status = "okay";
};
&sdhi2 {
/* used for on-board 8bit eMMC */
pinctrl-0 = <&sdhi2_pins>;
pinctrl-1 = <&sdhi2_pins_uhs>;
pinctrl-names = "default", "state_uhs";
vmmc-supply = <®_3p3v>;
vqmmc-supply = <®_1p8v>;
mmc-hs200-1_8v;
mmc-hs400-1_8v;
bus-width = <8>;
non-removable;
status = "okay";
};
&scif2 {
pinctrl-0 = <&scif2_pins>;
pinctrl-names = "default";
status = "okay";
};
&scif_clk {
clock-frequency = <14745600>;
status = "okay";
};
&i2c2 {
pinctrl-0 = <&i2c2_pins>;
pinctrl-names = "default";
status = "okay";
clock-frequency = <100000>;
ak4613: codec@10 {
compatible = "asahi-kasei,ak4613";
#sound-dai-cells = <0>;
reg = <0x10>;
clocks = <&rcar_sound 3>;
asahi-kasei,in1-single-end;
asahi-kasei,in2-single-end;
asahi-kasei,out1-single-end;
asahi-kasei,out2-single-end;
asahi-kasei,out3-single-end;
asahi-kasei,out4-single-end;
asahi-kasei,out5-single-end;
asahi-kasei,out6-single-end;
};
cs2000: clk-multiplier@4f {
#clock-cells = <0>;
compatible = "cirrus,cs2000-cp";
reg = <0x4f>;
clocks = <&audio_clkout>, <&x12_clk>;
clock-names = "clk_in", "ref_clk";
assigned-clocks = <&cs2000>;
assigned-clock-rates = <24576000>; /* 1/1 divide */
};
};
&i2c4 {
status = "okay";
clock-frequency = <400000>;
};
&rcar_sound {
pinctrl-0 = <&sound_pins &sound_clk_pins>;
pinctrl-names = "default";
/* Single DAI */
#sound-dai-cells = <0>;
/* audio_clkout0/1/2/3 */
#clock-cells = <1>;
clock-frequency = <11289600>;
clkout-lr-synchronous;
status = "okay";
/* update <audio_clk_b> to <cs2000> */
clocks = <&cpg CPG_MOD 1005>,
<&cpg CPG_MOD 1006>, <&cpg CPG_MOD 1007>,
<&cpg CPG_MOD 1008>, <&cpg CPG_MOD 1009>,
<&cpg CPG_MOD 1010>, <&cpg CPG_MOD 1011>,
<&cpg CPG_MOD 1012>, <&cpg CPG_MOD 1013>,
<&cpg CPG_MOD 1014>, <&cpg CPG_MOD 1015>,
<&cpg CPG_MOD 1022>, <&cpg CPG_MOD 1023>,
<&cpg CPG_MOD 1024>, <&cpg CPG_MOD 1025>,
<&cpg CPG_MOD 1026>, <&cpg CPG_MOD 1027>,
<&cpg CPG_MOD 1028>, <&cpg CPG_MOD 1029>,
<&cpg CPG_MOD 1030>, <&cpg CPG_MOD 1031>,
<&cpg CPG_MOD 1020>, <&cpg CPG_MOD 1021>,
<&cpg CPG_MOD 1020>, <&cpg CPG_MOD 1021>,
<&cpg CPG_MOD 1019>, <&cpg CPG_MOD 1018>,
<&audio_clk_a>, <&cs2000>,
<&audio_clk_c>,
<&cpg CPG_CORE R8A7796_CLK_S0D4>;
rcar_sound,dai {
dai0 {
playback = <&ssi0 &src0 &dvc0>;
capture = <&ssi1 &src1 &dvc1>;
};
};
};
&ssi1 {
shared-pin;
};
&audio_clk_a {
clock-frequency = <22579200>;
};
&i2c_dvfs {
status = "okay";
clock-frequency = <400000>;
vdd_dvfs: regulator@30 {
compatible = "rohm,bd9571mwv";
reg = <0x30>;
regulator-min-microvolt = <750000>;
regulator-max-microvolt = <1030000>;
regulator-boot-on;
regulator-always-on;
};
};
&wdt0 {
timeout-sec = <60>;
status = "okay";
};
&usb2_phy1 {
pinctrl-0 = <&usb1_pins>;
pinctrl-names = "default";
status = "okay";
};
&ehci1 {
status = "okay";
};
&ohci1 {
status = "okay";
};
&msiof_ref_clk {
clock-frequency = <66666666>;
};
&msiof1 {
pinctrl-0 = <&msiof1_pins>;
pinctrl-names = "default";
status = "okay";
spidev@0 {
compatible = "renesas,sh-msiof";
reg = <0>;
spi-max-frequency = <66666666>;
spi-cpha;
spi-cpol;
};
};
&vspb {
status = "okay";
};
&vspi0 {
status = "okay";
};
[-- Attachment #3: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Error in Xen while booting for salvator-X (M3 Board)
2017-02-27 10:55 ` Oleksandr Andrushchenko
@ 2017-02-28 15:01 ` George John
0 siblings, 0 replies; 8+ messages in thread
From: George John @ 2017-02-28 15:01 UTC (permalink / raw)
To: Oleksandr Andrushchenko; +Cc: Oleksandr Tyshchenko, xen-devel, Julien Grall, nd
[-- Attachment #1.1: Type: text/plain, Size: 5867 bytes --]
Hi,
Thanks for the support. I think I solved the problem partially.
@Andrii
> So I guess you see the abort on access to a peripheral missing on r8a7796
> but described in a device tree for r8a7795.
>
You were right. I commented out &sata and &rcarsound nodes from the device
tree created for xen and made some other modifications. The Dom0 now boots
without crash.
@Oleksandr
> PFA the DTS I use for M3ULCB board
Thank you very much. I used it for reference. I got a bit lucky because of
the fact that H3 and M3 are similar.
Still the framebuffer is not coming up. I will try to update with the logs
Thanks and regards,
George
On Mon, Feb 27, 2017 at 4:25 PM, Oleksandr Andrushchenko <andr2000@gmail.com
> wrote:
> Hi,
>
> PFA the DTS I use for M3ULCB board
>
>
>
> On 02/27/2017 12:48 PM, Oleksandr Tyshchenko wrote:
>
>> Hi.
>>
>> On Mon, Feb 27, 2017 at 12:29 PM, George John <georgeeldhojohn@gmail.com>
>> wrote:
>>
>>> Hi,
>>> Thanks for the reply,
>>> I am using Linux version 4.6.
>>> The memory nodes were already squashed. When I have used a different
>>> version
>>> of Xen, it booted to dom0. but still the crash occurs as shown in the log
>>> below.
>>>
>>> I have also noticed that for salvator x M3 board(r8a7796) the dtb file
>>> used
>>> was r8a7795-salvator-x-dom0.dtb
>>> Is it ok?
>>>
>> I don't know about M3 board.
>> CC my colleague who plays with M3 board. Hope, that he can shed some
>> lights.
>>
>> regards,
>>> George
>>>
>>> On Fri, Feb 24, 2017 at 8:43 PM, Oleksandr Tyshchenko <
>>> olekstysh@gmail.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Not 100% sure, but anyway...
>>>>
>>>> Can you recheck after squashing all memory nodes to a single one.
>>>>
>>>> ---
>>>> I guess, you have following in your device tree:
>>>>
>>>> memory@48000000 {
>>>> device_type = "memory";
>>>> /* first 128MB is reserved for secure area. */
>>>> reg = <0x0 0x48000000 0x0 0x38000000>;
>>>> };
>>>>
>>>> memory@500000000 {
>>>> device_type = "memory";
>>>> reg = <0x5 0x00000000 0x0 0x40000000>;
>>>> };
>>>>
>>>> memory@600000000 {
>>>> device_type = "memory";
>>>> reg = <0x6 0x00000000 0x0 0x40000000>;
>>>> };
>>>>
>>>> memory@700000000 {
>>>> device_type = "memory";
>>>> reg = <0x7 0x00000000 0x0 0x40000000>;
>>>> };
>>>>
>>>> ---
>>>> Try to make next:
>>>>
>>>> memory@48000000 {
>>>> device_type = "memory";
>>>> /* first 128MB is reserved for secure area. */
>>>> reg = <0x0 0x48000000 0x0 0x38000000>,
>>>> <0x5 0x00000000 0x0 0x40000000>,
>>>> <0x6 0x00000000 0x0 0x40000000>,
>>>> <0x7 0x00000000 0x0 0x40000000>;
>>>> };
>>>>
>>>>
>>>>
>>>> On Fri, Feb 24, 2017 at 4:53 PM, Julien Grall <julien.grall@arm.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On 21/02/17 12:03, George John wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>>
>>>>> I was trying out xen in salvator-X(M3 Board as described
>>>>>> in
>>>>>>
>>>>>> https://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization
>>>>>> _Extensions/Salvator-X
>>>>>>
>>>>>> I ran in to following error:
>>>>>>
>>>>>>
>>>>>> U-Boot 2015.04 (Feb 21 2017 - 14:24:48)
>>>>>>
>>>>>> CPU: Renesas Electronics R8A7796 rev 1.0
>>>>>> Board: Salvator-X
>>>>>> I2C: ready
>>>>>> DRAM: 3.9 GiB
>>>>>> MMC: sh-sdhi: 0, sh-sdhi: 1, sh-sdhi: 2
>>>>>> In: serial
>>>>>> Out: serial
>>>>>> Err: serial
>>>>>> Net: Board Net Initialization Failed
>>>>>> No ethernet found.
>>>>>> Hit any key to stop autoboot: 0
>>>>>> 819584 bytes read in 89 ms (8.8 MiB/s)
>>>>>> 64927 bytes read in 23 ms (2.7 MiB/s)
>>>>>> 14038016 bytes read in 1188 ms (11.3 MiB/s)
>>>>>> 10319 bytes read in 19 ms (530.3 KiB/s)
>>>>>> ## Booting kernel from Legacy Image at 48080000 ...
>>>>>> Image Name: XEN
>>>>>> Image Type: AArch64 Linux Kernel Image (uncompressed)
>>>>>> Data Size: 819520 Bytes = 800.3 KiB
>>>>>> Load Address: 78080000
>>>>>> Entry Point: 78080000
>>>>>> Verifying Checksum ... OK
>>>>>> ## Flattened Device Tree blob at 48000000
>>>>>> Booting using the fdt blob at 0x48000000
>>>>>> Loading Kernel Image ... OK
>>>>>> Using Device Tree in place at 0000000048000000, end
>>>>>> 0000000048012d9e
>>>>>>
>>>>>> Starting kernel ...
>>>>>>
>>>>>> - UART enabled -
>>>>>> - CPU 00000000 booting -
>>>>>> - Current EL 00000008 -
>>>>>> - Xen starting at EL2 -
>>>>>> - Zero BSS -
>>>>>> - Setting up control registers -
>>>>>> - Turning on paging -
>>>>>> - Ready -
>>>>>> (XEN) Checking for initrd in /chosen
>>>>>> (XEN) RAM: 0000000048000000 - 000000007fffffff
>>>>>> (XEN) RAM: 0000000500000000 - 000000053fffffff
>>>>>> (XEN) RAM: 0000000600000000 - 000000063fffffff
>>>>>> (XEN) RAM: 0000000700000000 - 000000073fffffff
>>>>>> (XEN)
>>>>>> (XEN) MODULE[0]: 0000000048000000 - 0000000048010000 Device Tree
>>>>>> (XEN) MODULE[1]: 000000007a000000 - 000000007c000000 Kernel
>>>>>> (XEN) MODULE[2]: 000000007c000000 - 000000007c010000 XSM
>>>>>> (XEN) RESVD[0]: 0000000048000000 - 0000000048010000
>>>>>> (XEN)
>>>>>> (XEN) Command line: dom0_mem=512M console=dtuart dtuart=serial0
>>>>>> dom0_max_vcpus=1 bootscrub=0 flask_enforcing=1
>>>>>> (XEN) Placing Xen at 0x000000007fe00000-0x0000000080000000
>>>>>> (XEN) Update BOOTMOD_XEN from 0000000078080000-0000000078196e01 =>
>>>>>> 000000007fe00000-000000007ff16e01
>>>>>>
>>>>>
>>>>> Which kernel version is it?
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> After this, it hangs. What could be the possible reason?
>>>>>>
>>>>>
>>>>> Xen will initialize the heap and then continue into the boot. I would
>>>>> add
>>>>> more debug around setup_mm to see where it failed.
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Julien Grall
>>>>>
>>>>> _______________________________________________
>>>>> Xen-devel mailing list
>>>>> Xen-devel@lists.xen.org
>>>>> https://lists.xen.org/xen-devel
>>>>>
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Oleksandr Tyshchenko
>>>>
>>>
>>>
>>
>>
>
[-- Attachment #1.2: Type: text/html, Size: 8280 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-02-28 15:01 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-02-21 12:03 Error in Xen while booting for salvator-X (M3 Board) George John
2017-02-24 14:53 ` Julien Grall
2017-02-24 15:13 ` Oleksandr Tyshchenko
2017-02-27 10:29 ` George John
2017-02-27 10:48 ` Oleksandr Tyshchenko
2017-02-27 10:55 ` Oleksandr Andrushchenko
2017-02-28 15:01 ` George John
2017-02-27 10:52 ` Andrii Anisov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).