thr3ads.net - Xen devel - Re: Xen arm working branch [Sep 2013]

If this information is useful, please help other people find it:
Share via:

Julien Grall

2013-Sep-24 09:56 UTC

Re: Xen arm working branch

(Add xen-devel)

On 09/24/2013 10:19 AM, Анастасия Коробицына wrote:> 
> Hello Julien,
Hello,
> Sorry for stupid questions below :)
> Which Xen and dom0 git branch do you use for your experiments? And which
> of them is working for you?
> I was trying to boot Xen and dom0 on Arndale board. I used Xen master
> branch and linux 3.9-rc4 for dom0, as mentioned on wiki, but I failed.
> I've seen mailing list archives, where you mentioned that linux 3.9-rc4
> does not work at all. Is it true?
The both branch on the wiki page should work. Can you send the serial
output log?

Cheers,

-- 
Julien Grall

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

Анастасия Коробицына

2013-Sep-24 10:02 UTC

head link

Re: Xen arm working branch

Hi,

Here is my log, I used SD card boot.

## Booting kernel from Legacy Image at 50000000 ...
Image Name:
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 900104 Bytes = 879 KiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

__ __ _ _ _ _ _ _ _
\ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___
\ // _ \ ''_ \ | || |_| || |_ __| | | | ''_ \/ __| __/ _` |
''_ \| |/ _ \
/ \ __/ | | | |__ _|__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
/_/\_\___|_| |_| |_|(_) |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|

(XEN) Xen version 4.4-unstable (builder@) (arm-none-eabi-gcc (Sourcery
CodeBench Lite 2011.09-69) 4.6.1) debug=y Tue Sep 3 12:06:45 EDT 2013
(XEN) Latest ChangeSet: Mon Aug 26 12:40:44 2013 +0200 git:8a7769b-dirty
(XEN) Console output is synchronous.
(XEN) Processor: "ARM Limited", variant: 0x0, part 0xc0f, rev 0x4
(XEN) 32-bit Execution:
(XEN) Processor Features: 00001031:00011011
(XEN) Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 02010555
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10201105 20000000 01240000 02102211
(XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Platform: SAMSUNG EXYNOS5
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
(Xeneric timer at 24000 KHz
(XEN) GIC initializatio gic_dist_ad0000010481000
(XEN) gic_cpu_addr=0000000010482000
(XEN) gic_hyp_addr=0000000010484000
(XEN) gic_vcpu_addr=0000000010486000
(XEN) gic_maintenance_irq=25
(XEN) GIC: 160 lines, 2 cpus, secure (IID 0200043b).
(XEN) Waiting for 1 other CPUs to be ready
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 16 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) CPU 1 booted.
(XEN) Brought up 2 CPUs
(XEN) OADING DOMAIN 0 ***
(XEN) Device-tree contains "xenIgnoring.
(XEN) Populate P2M 0x90000000->0xa0000000 (1:1 mapping for dom0)
(XEN) Loading kernel from boot module 1
(XEN) Loading zImage from 0000000060000000 to
0000000090008000-00000000900df700
(XEN) Loading dom0 DTB to 0x000000009fe00000-0x000000009fe0445a0:
Unexpected Trata Abort
(XEN) ----[ Xen-4.4-unstable arm32 debug=y Tainted: C ]----
(XEN) CPU: 0
(XEN) PC: 00214248 free_heap_pages+0x22c/0x414
(XEN) CPSR: 8000005a MODE:Hypervisor
(XEN) R0: 002d200c R1: 00261d9c R2: 00000000 R3: 01800000
(XEN) R4: 00000012 R5: 02000000 R6: 00000012 R7: 00100100
(XEN) R8: 00000001 R9: 02600000 R10:000c0000 R11:0028fa24 R12:00200200
(XEN) HYP: SP: 0028f9fc LR: 00000000
(XEN)
(XEN) VTCR_EL2: 80002558
(XEN) VTTBR_EL2: 00010000bfdfc000
(XEN)
HCR_EL2: 0000000000282835
(XEN) TTBR0_EL2: 00000000000
(XEN)
(XENESR_EL2: 94000006
(XEN) HPFAR_EL2: 0000000000000000
(XEN) HDFAR: 01800008
(XEN) HIFAR: 00000000
(XEN)
(XEN) Xen stack trace from sp=0028f9fc:
(XEN) 002140ac 0029a3a0 000003ff 02407fe0 00299118 00000000 00000400
00000000
(XEN) 0029a3a0 0028fa4c 00214eec 00000000 00000fff 00000000 00270010
00000000
(XEN) 60000000 00000000 00004160 0028fa5c 002151e0 002704b0 00000001
0028fa7c
(XEN) 0026b3b8 00000040 9fe00000 00000000 9fe00000 00000002 00000000
0028fedc
(XEN) 002439dc 9fe0445a 00000000 00020000 00000000 00000000 4003ff58
90000000
(XEN) 00000000 00000000 00000000 4ffe1000 0025e734 00000000 00000000
00000000
(XEN) 00000008 00000001 0000000025e718 00000000 00000000 4ffeb000 00000008
(XEN) 000057cf8 00000002 001 0025e674 00000000 00004118 00000001
(XEN) 00000001 00000001 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000001
(XEN) 00000001 00000001 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
2c6e6578
(XEN) 2d6e6578 00342e34 2c6e6578 006e6578 000000b0 00000200 00000000
00000000
(XEN) 01000000 0f000000 080f0000 00000000 00000000 00000000 00000000
00000000
(XEN) 4fffb62c 4ffe2f80 0028fb94 40030000 00000000 10000000 00000000
00000001
(XEN) 00000000 90000000 00000000 10000000 00000000000 00000000 00000000
(XEN) 00000000 00000000 000 00000000 000000000000 00000000 00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000
(XEN) 00000000 9fe00000 00000000 90008000 00000000 00000000 00000000
60000000
(XEN) Xen call trace:
(XEN) [<00214248>] free_heap_pages+0x22c/0x414 (PC)
(XEN) [<00000000>] ??? (LR)
(XEN) [<00214eec>] init_heap_pages+0x108/0x120
(XEN) [<002151e0>] init_domheap_pages+0xa8/0xac
(XEN) [<0026b3b8>] discard_initial_modules+0x6c/0x98
(XEN) [<002439dc>] construct_dom0+0xc84/0xe30
(XEN) [<0026be48>] start_xen+0xa28/0xae0
(XEN) [<6000016c>] ???
(XEN)


2013/9/24 Julien Grall <julien.grall@citrix.com>
> (Add xen-devel)
>
> On 09/24/2013 10:19 AM, Анастасия Коробицына wrote:
> >
> > Hello Julien,
>
> Hello,
>
> > Sorry for stupid questions below :)
> > Which Xen and dom0 git branch do you use for your experiments? And
which
> > of them is working for you?
> > I was trying to boot Xen and dom0 on Arndale board. I used Xen master
> > branch and linux 3.9-rc4 for dom0, as mentioned on wiki, but I failed.
> > I''ve seen mailing list archives, where you mentioned that
linux 3.9-rc4
> > does not work at all. Is it true?
>
> The both branch on the wiki page should work. Can you send the serial
> output log?
>
> Cheers,
>
> --
> Julien Grall
>

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

Julien Grall

2013-Sep-24 10:15 UTC

head link

Re: Xen arm working branch

On 09/24/2013 11:02 AM, Анастасия Коробицына wrote:> Hi,
> 
> Here is my log, I used SD card boot.
> 
> ## Booting kernel from Legacy Image at 50000000 ...
> Image Name:
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 900104 Bytes = 879 KiB
> Load Address: 60000000
> Entry Point: 60000000
> Verifying Checksum ... OK
> Loading Kernel Image ... OK
> OK
> 
> Starting kernel ...
> 
> __ __ _ _ _ _ _ _ _
> \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___
> \ // _ \ '_ \ | || |_| || |_ __| | | | '_ \/ __| __/ _` | '_ \|
|/ _ \
> / \ __/ | | | |__ _|__ _|__| |_| | | | \__ \ || (_| | |_) | | __/
> /_/\_\___|_| |_| |_|(_) |_| \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
> 
> (XEN) Xen version 4.4-unstable (builder@) (arm-none-eabi-gcc (Sourcery
> CodeBench Lite 2011.09-69) 4.6.1) debug=y Tue Sep 3 12:06:45 EDT 2013
> (XEN) Latest ChangeSet: Mon Aug 26 12:40:44 2013 +0200 git:8a7769b-dirty
Are you sure to use the latest Xen master branch? It seems, your HEAD
commit date is "Monday 26 August" 8a7769b.
> (XEN) Console output is synchronous.
> (XEN) Processor: "ARM Limited", variant: 0x0, part 0xc0f, rev 0x4
> (XEN) 32-bit Execution:
> (XEN) Processor Features: 00001031:00011011
> (XEN) Instruction Sets: AArch32 Thumb Thumb-2 ThumbEE Jazelle
> (XEN) Extensions: GenericTimer Security
> (XEN) Debug Features: 02010555
> (XEN) Auxiliary Features: 00000000
> (XEN) Memory Model Features: 10201105 20000000 01240000 02102211
> (XEN) ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
> (XEN) Platform: SAMSUNG EXYNOS5
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27
> (Xeneric timer at 24000 KHz
> (XEN) GIC initializatio gic_dist_ad0000010481000
> (XEN) gic_cpu_addr=0000000010482000
> (XEN) gic_hyp_addr=0000000010484000
> (XEN) gic_vcpu_addr=0000000010486000
> (XEN) gic_maintenance_irq=25
> (XEN) GIC: 160 lines, 2 cpus, secure (IID 0200043b).
> (XEN) Waiting for 1 other CPUs to be ready
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (XEN) Allocated console ring of 16 KiB.
> (XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
> (XEN) CPU 1 booted.
> (XEN) Brought up 2 CPUs
> (XEN) OADING DOMAIN 0 ***
> (XEN) Device-tree contains "xenIgnoring.
> (XEN) Populate P2M 0x90000000->0xa0000000 (1:1 mapping for dom0)
> (XEN) Loading kernel from boot module 1
> (XEN) Loading zImage from 0000000060000000 to
> 0000000090008000-00000000900df700
> (XEN) Loading dom0 DTB to 0x000000009fe00000-0x000000009fe0445a0:
> Unexpected Trata Abort
> (XEN) ----[ Xen-4.4-unstable arm32 debug=y Tainted: C ]----
> (XEN) CPU: 0
> (XEN) PC: 00214248 free_heap_pages+0x22c/0x414
> (XEN) CPSR: 8000005a MODE:Hypervisor
> (XEN) R0: 002d200c R1: 00261d9c R2: 00000000 R3: 01800000
> (XEN) R4: 00000012 R5: 02000000 R6: 00000012 R7: 00100100
> (XEN) R8: 00000001 R9: 02600000 R10:000c0000 R11:0028fa24 R12:00200200
> (XEN) HYP: SP: 0028f9fc LR: 00000000
> (XEN)
> (XEN) VTCR_EL2: 80002558
> (XEN) VTTBR_EL2: 00010000bfdfc000
> (XEN)
> HCR_EL2: 0000000000282835
> (XEN) TTBR0_EL2: 00000000000
> (XEN)
> (XENESR_EL2: 94000006
> (XEN) HPFAR_EL2: 0000000000000000
> (XEN) HDFAR: 01800008
> (XEN) HIFAR: 00000000
> (XEN)
> (XEN) Xen stack trace from sp=0028f9fc:
> (XEN) 002140ac 0029a3a0 000003ff 02407fe0 00299118 00000000 00000400
> 00000000
> (XEN) 0029a3a0 0028fa4c 00214eec 00000000 00000fff 00000000 00270010
> 00000000
> (XEN) 60000000 00000000 00004160 0028fa5c 002151e0 002704b0 00000001
> 0028fa7c
> (XEN) 0026b3b8 00000040 9fe00000 00000000 9fe00000 00000002 00000000
> 0028fedc
> (XEN) 002439dc 9fe0445a 00000000 00020000 00000000 00000000 4003ff58
> 90000000
> (XEN) 00000000 00000000 00000000 4ffe1000 0025e734 00000000 00000000
> 00000000
> (XEN) 00000008 00000001 0000000025e718 00000000 00000000 4ffeb000 00000008
> (XEN) 000057cf8 00000002 001 0025e674 00000000 00004118 00000001
> (XEN) 00000001 00000001 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000001
> (XEN) 00000001 00000001 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 2c6e6578
> (XEN) 2d6e6578 00342e34 2c6e6578 006e6578 000000b0 00000200 00000000
> 00000000
> (XEN) 01000000 0f000000 080f0000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 4fffb62c 4ffe2f80 0028fb94 40030000 00000000 10000000 00000000
> 00000001
> (XEN) 00000000 90000000 00000000 10000000 00000000000 00000000 00000000
> (XEN) 00000000 00000000 000 00000000 000000000000 00000000 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> 00000000
> (XEN) 00000000 9fe00000 00000000 90008000 00000000 00000000 00000000
> 60000000
> (XEN) Xen call trace:
> (XEN) [<00214248>] free_heap_pages+0x22c/0x414 (PC)
> (XEN) [<00000000>] ??? (LR)
> (XEN) [<00214eec>] init_heap_pages+0x108/0x120
> (XEN) [<002151e0>] init_domheap_pages+0xa8/0xac
> (XEN) [<0026b3b8>] discard_initial_modules+0x6c/0x98
> (XEN) [<002439dc>] construct_dom0+0xc84/0xe30
> (XEN) [<0026be48>] start_xen+0xa28/0xae0
> (XEN) [<6000016c>] ???
> (XEN)
I believe this is fixed in the latest master.

-- 
Julien Grall

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

Xen devel - Sep 2013 - Re: Xen arm working branch

Re: Xen arm working branch

Re: Xen arm working branch

Re: Xen arm working branch