Hello Oleksandr Tyshchenko,
Thanks for your quick response. With Xen stable 4.13 branch, the mentioned
issue is solved.
Is there any document which I could refer to bring up Xen[DOM0] and have an
hands on ? because am currently seeing no output after this
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 324kB init memory.
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
Attaching the complete logs for reference.
Mit freundlichen Grüßen / Best regards
Chockalingam Manikandan
ES-CM Core fn,ADIT (RBEI/ECF3)
Robert Bosch GmbH | Postfach 10 60 50 | 70049 Stuttgart | GERMANY |
www.bosch.com
Tel. +91 80 6136-4452 | Fax +91 80 6617-0711 |
manikandan.chockalin...@in.bosch.com<mailto:manikandan.chockalin...@in.bosch.com>
Registered Office: Stuttgart, Registration Court: Amtsgericht Stuttgart, HRB
14000;
Chairman of the Supervisory Board: Franz Fehrenbach; Managing Directors: Dr.
Volkmar Denner,
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer,
Dr. Stefan Hartung,
Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke,
Peter Tyroller
From: Oleksandr Tyshchenko <olekst...@gmail.com>
Sent: Wednesday, July 15, 2020 1:00 AM
To: Manikandan Chockalingam (RBEI/ECF3) <manikandan.chockalin...@in.bosch.com>
Cc: Bertrand Marquis <bertrand.marq...@arm.com>; nd <n...@arm.com>;
xen-de...@lists.xen.org
Subject: Re: [BUG] Xen build for RCAR failing
Hello
[Sorry for the possible format issues]
On Tue, Jul 14, 2020 at 4:44 PM Manikandan Chockalingam (RBEI/ECF3)
<manikandan.chockalin...@in.bosch.com<mailto:manikandan.chockalin...@in.bosch.com>>
wrote:
Hello Bertrand,
I succeeded in building the core minimal image with dunfell and its compatible
branches [except xen-troops (modified some files to complete the build)].
But I face the following error while booting.
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) Timer: Unable to retrieve IRQ 0 from the device tree
(XEN) ****************************************
The reason for that problem *might* be in the arch timer node in your device
tree which contains "interrupts-extended" property instead of just
"interrupts". As far as I remember Xen v4.12 doesn't have required support to
handle "interrupts-extended".
It went in a bit later [1]. If this is the real reason, I think you should
either switch to the new Xen version or modify your arch timer node in a way to
use the "interrupts" property [2]. I would suggest using the new Xen version if
possible (at least v4.13).
[1]
https://lists.xenproject.org/archives/html/xen-devel/2019-05/msg01775.html<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.xenproject.org%2Farchives%2Fhtml%2Fxen-devel%2F2019-05%2Fmsg01775.html&data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%7Cf43735b682524701f9e008d8282c6400%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637303518829046287&sdata=8ZritGkF%2Bv29cQsagR2KJaW2NUTVBk0no7Rt7Ez37ek%3D&reserved=0>
[2]
https://github.com/otyshchenko1/linux/commit/c25044845f2c3678f5df789881e7a125556af6fc<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fotyshchenko1%2Flinux%2Fcommit%2Fc25044845f2c3678f5df789881e7a125556af6fc&data=02%7C01%7CManikandan.Chockalingam%40in.bosch.com%7Cf43735b682524701f9e008d8282c6400%7C0ae51e1907c84e4bbb6d648ee58410f4%7C0%7C0%7C637303518829046287&sdata=rLjx9VzjBfldUjg%2Fv6wTD8Z89TzSfN71RFpdxCO%2F%2F0A%3D&reserved=0>
--
Regards,
Oleksandr Tyshchenko
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'r8a7795-salvator-x-xen.dtb'.
Load address: 0x4a000000
Loading: ######
1.8 MiB/s
done
Bytes transferred = 80783 (13b8f hex)
=> tftp 0x48200000 Image
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'Image'.
Load address: 0x48200000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
############
2.2 MiB/s
done
Bytes transferred = 21156352 (142d200 hex)
=> tftp 0x48000000 xen
Using ethernet@e6800000 device
TFTP from server 192.168.2.11; our IP address is 192.168.2.51
Filename 'xen'.
Load address: 0x48000000
Loading: ###############################################################
1 MiB/s
done
Bytes transferred = 918864 (e0550 hex)
=> booti 0x48000000 - 0x4A000000
## Flattened Device Tree blob at 4a000000
Booting using the fdt blob at 0x4a000000
Using Device Tree in place at 000000004a000000, end 000000004a016b8e
Starting kernel ...
Xen 4.13.2-pre
(XEN) Xen version 4.13.2-pre (manikandan@) (aarch64-linux-gnu-gcc (Sourcery
CodeBench 2018.05-7) 7.3.1 20180612) d0
(XEN) Latest ChangeSet: Tue Jul 7 15:05:36 2020 +0200 git:378321b
(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) 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) Initialising XSM SILO mode
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) Allocated console ring of 16 KiB.
(XEN) Bringing up CPU1
(XEN) Bringing up CPU2
(XEN) Bringing up CPU3
(XEN) Bringing up CPU4
(XEN) CPU4 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU4 never came online
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Bringing up CPU5
(XEN) CPU5 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU5 never came online
(XEN) Failed to bring up CPU 5 (error -5)
(XEN) Bringing up CPU6
(XEN) CPU6 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU6 never came online
(XEN) Failed to bring up CPU 6 (error -5)
(XEN) Bringing up CPU7
(XEN) CPU7 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073),
(XEN) disable cpu (see big.LITTLE.txt under docs/).
(XEN) CPU7 never came online
(XEN) Failed to bring up CPU 7 (error -5)
(XEN) Brought up 4 CPUs
(XEN) I/O virtualisation disabled
(XEN) P2M: 44-bit IPA with 44-bit PA and 8-bit VMID
(XEN) P2M: 4 levels with order-0 root, VTCR 0x80043594
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading d0 kernel from boot module @ 0000000048200000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000600000000-0x00000640000000 (1024MB)
(XEN) Grant table range: 0x00000048000000-0x00000048040000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading zImage from 0000000048200000 to 0000000600080000-0000000600f80000
(XEN) Loading d0 DTB to 0x0000000608000000-0x0000000608012d37
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 324kB init memory.
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) *** Serial input to Xen (type 'CTRL-a' three times to switch input)
