subject:"Re\: Loading kernel on Non\-root cell in jetson\-TX2."

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-17 Thread Jan Kiszka

On 2018-01-15 12:05, Ashok Kumar wrote:
> Hi,
> 
> Thank you all, earlier i was facing issue with unpacking initramfs, As
> Jan suggested to tweak with memory layout i have resolved that issue
> unfortunately stuck with another one.  
> 
>  As i am trying to boot 4.14 upstream kernel(maintained by Jan) into
> non-root cell on TX2, i am facing issues related to loading of images
> and rootfs.
> 
> I have referred non-root cell configs of other platform and created one
> for TX2, i want  to understand the role of virt_start and how to
> calculate these addresses?
> 
> I have attached Tx2 non-root cell config file and dtb file, with this
> configuration i am getting following logs. 
> 
> 
> Started cell "jetson-tx2-linux-demo"
> [    0.00] Booting Linux on physical CPU 0x102
> [    0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version
> 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
> [    0.00] Boot CPU: AArch64 Processor [411fd073]
> [    0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
> [    0.00] efi: Getting EFI parameters from FDT:
> [    0.00] efi: UEFI not found.
> [    0.00] cma: Reserved 16 MiB at 0xff00
> [    0.00] psci: probing for conduit method from DT.
> [    0.00] psci: PSCIv0.2 detected in firmware.
> [    0.00] psci: Using standard PSCI v0.2 function IDs
> [    0.00] psci: MIGRATE_INFO_TYPE not supported.
> [    0.00] percpu: Embedded 21 pages/cpu @800042cb5000 s47128
> r8192 d30696 u86016
> [    0.00] Detected PIPT I-cache on CPU0
> [    0.00] Built 1 zonelists, mobility grouping on.  Total pages: 108092
> [    0.00] Kernel command line: console=ttyS0,115200
> [    0.00] PID hash table entries: 2048 (order: 2, 16384 bytes)
> [    0.00] Dentry cache hash table entries: 65536 (order: 7, 524288
> bytes)
> [    0.00] Inode-cache hash table entries: 32768 (order: 6, 262144
> bytes)
> [    0.00] software IO TLB [mem 0xfafff000-0xfefff000] (64MB) mapped
> at [80003afff000-80003effefff]
> [    0.00] Memory: 295476K/439232K available (8956K kernel code,
> 1084K rwdata, 4052K rodata, 1088K init, 282K bss, 127372K reserved, 16384)
> [    0.00] Virtual kernel memory layout:
> [    0.00]     modules : 0x - 0x0800 
>  (   128 MB)
> [    0.00]     vmalloc : 0x0800 - 0x7dffbfff 
>  (129022 GB)
> [    0.00]       .text : 0x0808 - 0x0894 
>  (  8960 KB)
> [    0.00]     .rodata : 0x0894 - 0x08d4 
>  (  4096 KB)
> [    0.00]       .init : 0x08d4 - 0x08e5 
>  (  1088 KB)
> [    0.00]       .data : 0x08e5 - 0x08f5f200 
>  (  1085 KB)
> [    0.00]        .bss : 0x08f5f200 - 0x08fa5be0 
>  (   283 KB)
> [    0.00]     fixed   : 0x7dfffe7fd000 - 0x7dfffec0 
>  (  4108 KB)
> [    0.00]     PCI I/O : 0x7dfffee0 - 0x7de0 
>  (    16 MB)
> [    0.00]     vmemmap : 0x7e00 - 0x8000 
>  (  2048 GB maximum)
> [    0.00]               0x7ea0 - 0x7e00010b3c00 
>  (     6 MB actual)
> [    0.00]     memory  : 0x80002800 - 0x800042cf 
>  (   428 MB)
> [    0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
> [    0.00] Preemptible hierarchical RCU implementation.
> [    0.00]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
> [    0.00]  Tasks RCU enabled.
> [    0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
> [    0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
> [    0.00] arch_timer: cp15 timer(s) running at 31.25MHz (virt).
> [    0.00] clocksource: arch_sys_counter: mask: 0xff
> max_cycles: 0xe6a171046, max_idle_ns: 881590405314 ns
> [    0.02] sched_clock: 56 bits at 31MHz, resolution 32ns, wraps
> every 4398046511088ns
> [    0.53] Console: colour dummy device 80x25
> [    0.68] Calibrating delay loop (skipped), value calculated using
> timer frequency.. 62.50 BogoMIPS (lpj=125000)
> [    0.76] pid_max: default: 32768 minimum: 301
> [    0.000118] Security Framework initialized
> [    0.000139] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
> [    0.000145] Mountpoint-cache hash table entries: 1024 (order: 1, 8192
> bytes)
> [    0.016037] ASID allocator initialised with 65536 entries
> [    0.024034] Hierarchical SRCU implementation.
> [    0.032146] EFI services will not be available.
> [    0.040058] smp: Bringing up secondary CPUs ...
> [    0.068122] Detected PIPT I-cache on CPU1
> [    0.068158] CPU1: Booted secondary processor [411fd073]
> [    0.068206] smp: Brought up 1 node, 2 CPUs
> [    0.068214] SMP: Total of 2 processors activated.
> [    0.068220] CPU features: detected feature: 32-bit EL0 Support
> [    0.068351] CPU: All CPU(s) started at EL1
> [

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-15 Thread Ashok Kumar

Hi,

Thank you all, earlier i was facing issue with unpacking initramfs, As Jan
suggested to tweak with memory layout i have resolved that issue
unfortunately stuck with another one.

 As i am trying to boot 4.14 upstream kernel(maintained by Jan) into
non-root cell on TX2, i am facing issues related to loading of images and
rootfs.

I have referred non-root cell configs of other platform and created one for
TX2, i want  to understand the role of virt_start and how to calculate
these addresses?

I have attached Tx2 non-root cell config file and dtb file, with this
configuration i am getting following logs.


Started cell "jetson-tx2-linux-demo"
[0.00] Booting Linux on physical CPU 0x102
[0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version
5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
[0.00] Boot CPU: AArch64 Processor [411fd073]
[0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0xff00
[0.00] psci: probing for conduit method from DT.
[0.00] psci: PSCIv0.2 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] psci: MIGRATE_INFO_TYPE not supported.
[0.00] percpu: Embedded 21 pages/cpu @800042cb5000 s47128 r8192
d30696 u86016
[0.00] Detected PIPT I-cache on CPU0
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 108092
[0.00] Kernel command line: console=ttyS0,115200
[0.00] PID hash table entries: 2048 (order: 2, 16384 bytes)
[0.00] Dentry cache hash table entries: 65536 (order: 7, 524288
bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 6, 262144
bytes)
[0.00] software IO TLB [mem 0xfafff000-0xfefff000] (64MB) mapped at
[80003afff000-80003effefff]
[0.00] Memory: 295476K/439232K available (8956K kernel code, 1084K
rwdata, 4052K rodata, 1088K init, 282K bss, 127372K reserved, 16384)
[0.00] Virtual kernel memory layout:
[0.00] modules : 0x - 0x0800   (
 128 MB)
[0.00] vmalloc : 0x0800 - 0x7dffbfff
 (129022 GB)
[0.00]   .text : 0x0808 - 0x0894   (
8960 KB)
[0.00] .rodata : 0x0894 - 0x08d4   (
4096 KB)
[0.00]   .init : 0x08d4 - 0x08e5   (
1088 KB)
[0.00]   .data : 0x08e5 - 0x08f5f200   (
1085 KB)
[0.00].bss : 0x08f5f200 - 0x08fa5be0   (
 283 KB)
[0.00] fixed   : 0x7dfffe7fd000 - 0x7dfffec0   (
4108 KB)
[0.00] PCI I/O : 0x7dfffee0 - 0x7de0   (
16 MB)
[0.00] vmemmap : 0x7e00 - 0x8000   (
2048 GB maximum)
[0.00]   0x7ea0 - 0x7e00010b3c00   (
 6 MB actual)
[0.00] memory  : 0x80002800 - 0x800042cf   (
 428 MB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=2.
[0.00]  Tasks RCU enabled.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[0.00] arch_timer: cp15 timer(s) running at 31.25MHz (virt).
[0.00] clocksource: arch_sys_counter: mask: 0xff
max_cycles: 0xe6a171046, max_idle_ns: 881590405314 ns
[0.02] sched_clock: 56 bits at 31MHz, resolution 32ns, wraps every
4398046511088ns
[0.53] Console: colour dummy device 80x25
[0.68] Calibrating delay loop (skipped), value calculated using
timer frequency.. 62.50 BogoMIPS (lpj=125000)
[0.76] pid_max: default: 32768 minimum: 301
[0.000118] Security Framework initialized
[0.000139] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes)
[0.000145] Mountpoint-cache hash table entries: 1024 (order: 1, 8192
bytes)
[0.016037] ASID allocator initialised with 65536 entries
[0.024034] Hierarchical SRCU implementation.
[0.032146] EFI services will not be available.
[0.040058] smp: Bringing up secondary CPUs ...
[0.068122] Detected PIPT I-cache on CPU1
[0.068158] CPU1: Booted secondary processor [411fd073]
[0.068206] smp: Brought up 1 node, 2 CPUs
[0.068214] SMP: Total of 2 processors activated.
[0.068220] CPU features: detected feature: 32-bit EL0 Support
[0.068351] CPU: All CPU(s) started at EL1
[0.068696] devtmpfs: initialized
[0.068965] random: get_random_u32 called from
bucket_table_alloc+0x108/0x288 with crng_init=0
[0.069155] clocksource: jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 764504178510 ns
[0.069164]

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-15 Thread Ashok Kumar

Hi,

Thank you all, earlier i was facing issue with unpacking initramfs, As Jan
suggested to tweak with memory layout i have resolved that issue
unfortunately stuck with another one.

 As i am trying to boot 4.14 upstream kernel(maintained by Jan) into
non-root cell on TX2, i am facing issues related to loading of images and
rootfs.

I have referred non-root cell configs of other platform and created one for
TX2, i want  to understand the role of virt_start and how to calculate
these addresses?

I have attached Tx2 non-root cell config file and dtb file, with this
configuration i am getting following logs.



Cell "jetson-tx2-linux-demo" can be loaded
Started cell "jetson-tx2-linux-demo"
[0.00] Booting Linux on physical CPU 0x102
[0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version
5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
[0.00] Boot CPU: AArch64 Processor [411fd073]
[0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
[0.00] efi: Getting EFI parameters from FDT:
[0.00] efi: UEFI not found.
[0.00] cma: Reserved 16 MiB at 0xff00
[0.00] psci: probing for conduit method from DT.
[0.00] psci: PSCIv0.2 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] psci: MIGRATE_INFO_TYPE not supported.
[0.00] missing boot CPU MPIDR, not enabling secondaries
[0.00] percpu: Embedded 21 pages/cpu @80005bcca000 s47128 r8192
d30696 u86016
[0.00] Detected PIPT I-cache on CPU0
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 208892
[0.00] Kernel command line: console=ttyS0,115200
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576
bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 7, 524288
bytes)
[0.00] software IO TLB [mem 0xfafff000-0xfefff000] (64MB) mapped at
[80003afff000-80003effefff]
[0.00] Memory: 711292K/848832K available (8956K kernel code, 1084K
rwdata, 4052K rodata, 1088K init, 282K bss, 121156K reserved, 16384)
[0.00] Virtual kernel memory layout:
[0.00] modules : 0x - 0x0800   (
 128 MB)
[0.00] vmalloc : 0x0800 - 0x7dffbfff
 (129022 GB)
[0.00]   .text : 0x0808 - 0x0894   (
8960 KB)
[0.00] .rodata : 0x0894 - 0x08d4   (
4096 KB)
[0.00]   .init : 0x08d4 - 0x08e5   (
1088 KB)
[0.00]   .data : 0x08e5 - 0x08f5f200   (
1085 KB)
[0.00].bss : 0x08f5f200 - 0x08fa5be0   (
 283 KB)
[0.00] fixed   : 0x7dfffe7fd000 - 0x7dfffec0   (
4108 KB)
[0.00] PCI I/O : 0x7dfffee0 - 0x7de0   (
16 MB)
[0.00] vmemmap : 0x7e00 - 0x8000   (
2048 GB maximum)
[0.00]   0x7ea0 - 0x7e00016f3c00   (
12 MB actual)
[0.00] memory  : 0x80002800 - 0x80005bcf   (
 828 MB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=1.
[0.00]  Tasks RCU enabled.
[0.00] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[0.00] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[0.00] arch_timer: cp15 timer(s) running at 31.25MHz (virt).
[0.00] clocksource: arch_sys_counter: mask: 0xff
max_cycles: 0xe6a171046, max_idle_ns: 881590405314 ns
[0.02] sched_clock: 56 bits at 31MHz, resolution 32ns, wraps every
4398046511088ns
[0.52] Console: colour dummy device 80x25
[0.67] Calibrating delay loop (skipped), value calculated using
timer frequency.. 62.50 BogoMIPS (lpj=125000)
[0.75] pid_max: default: 32768 minimum: 301
[0.000119] Security Framework initialized
[0.000140] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[0.000148] Mountpoint-cache hash table entries: 2048 (order: 2, 16384
bytes)
[0.016032] ASID allocator initialised with 65536 entries
[0.024031] Hierarchical SRCU implementation.
[0.032139] EFI services will not be available.
[0.040053] smp: Bringing up secondary CPUs ...
[0.040059] smp: Brought up 1 node, 1 CPU
[0.040063] SMP: Total of 1 processors activated.
[0.040069] CPU features: detected feature: 32-bit EL0 Support
[0.040128] CPU: All CPU(s) started at EL1
[0.040472] devtmpfs: initialized
[0.040743] random: get_random_u32 called from
bucket_table_alloc+0x108/0x288 with crng_init=0
[0.044148] clocksource: jiffies: mask: 0x max_cycles:
0x, max_idle_ns: 764504178510 ns
[

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-09 Thread Gustavo Lima Chaves

* Jan Kiszka  [2018-01-09 07:21:00 +0100]:

> > 
> > I have also started to see these inmate boot stalls. They are random,
> > though, if you try again you may see the boot pass. BTW, why the
> > change "tools: Leave more space between kernel and initrd on x86"? I'm
> > running with it reverted for a while, since it now takes too much
> > space on inmates for typical 8MB kernels.
> 
> Look into next, and you will find both answers and (hopefully) some
> solution.

Awesome, thanks!

> 
> Jan
> 
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

-- 
Gustavo Lima Chaves
Intel - Open Source Technology Center

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-09 Thread a . kumar

Hi Jan,

> jailhouse cell linux --help
> [...]
>   --write-params FILE, -w FILE
> only parse cell configuration, write out parameters
> into the specified file and print required jailhouse
> cell commands to boot Linux to the console
> 
> It also reports the commands you need to issue on the target. Those
> reveal which addresses the images should be loaded to.
> 
> Note that I pushed some updates to the next branch that make the gap
> between kernel and initrd configurable, and they also shrink it for
> ARM64 (because that arch does not do any kernel compression). Maybe
> worth a try.

We tried with new updated jailhouse, but still it gives same behaviour.

We tried with -w option, as like following command.

sudo jailhouse cell linux configs/jetson-tx2-linux-demo.cell /boot/Image_jan -i 
rootfs.cpio -d inmate-jetson-tx2.dtb -c "console=ttyS0,115200" -w FILE 

but output shows

Modified device tree written. Start Linux with the following commands 
(adjusting paths as needed):

jailhouse cell create configs/jetson-tx2-linux-demo.cell
jailhouse cell load jetson-tx2-linux-demo linux-loader.bin -a 0x0 -s 
"kernel=0xe828 dtb=0xe800" -a 0x1000 /boot/Image_jan -a 0xe828
jailhouse cell start jetson-tx2-linux-demo

it seems related to virt.start address provided in config file can someone give 
me idea about how to calculate virtual-address and how that -w FILE option will 
work in jailhouse

Regards
Ashok

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-08 Thread Jan Kiszka

On 2018-01-08 19:55, Gustavo Lima Chaves wrote:
> * 'Lokesh Vutla' via Jailhouse  [2018-01-08 
> 18:33:29 +0530]:
> 
>>
>>
>> On Saturday 06 January 2018 03:05 PM, a.ku...@matellio.com wrote:
>>> Hi,
>>>
>>>
>>> We are able to run jailhouse on Tx2 platform using 4.14-rc14-kernel, we are 
>>> able to enable root-cell and we can run non-root cell demo application 
>>> which is provided by jailhouse(gic-demo.bin). 
>>>
>>> But we are stuck in the middle of booting while loading 4.14-rc14-kernel in 
>>> non-root cell, i have attached both root-cell and non-root cell config.
>>>
>>> This is the logs we are getting while loading non-root cell.
>>>
>>> Created cell "jetson-tx2-linux-demo"
>>> Page pool usage after cell creation: mem 117/16356, remap 101/131072
>>> [ 2059.007251] Created Jailhouse cell "jetson-tx2-linux-demo"
>>> Cell "jetson-tx2-linux-demo" can be loaded
>>> Started cell "jetson-tx2-linux-demo"
>>> [0.00] Booting Linux on physical CPU 0x102
>>> [0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version 
>>> 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
>>> [0.00] Boot CPU: AArch64 Processor [411fd073]
>>> [0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
>>> [0.00] efi: Getting EFI parameters from FDT:
>>> [0.00] efi: UEFI not found.
>>> [0.00] cma: Reserved 16 MiB at 0xff00
>>> [0.00] psci: probing for conduit method from DT.
>>> [0.00] psci: PSCIv0.2 detected in firmware.
>>> [0.00] psci: Using standard PSCI v0.2 function IDs
>>> [0.00] psci: MIGRATE_INFO_TYPE not supported.
>>> [0.00] Failed to find device node for boot cpu
>>> [0.00] missing boot CPU MPIDR, not enabling secondaries
>>> [0.00] percpu: Embedded 21 pages/cpu @800042cca000 s47128 r8192 
>>> d30696 u86016
>>> [0.00] Detected PIPT I-cache on CPU0
>>> [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 108092
>>> [0.00] Kernel command line: console=ttyS0,115200
>>
>> Can you try passing some valid root= option in bootargs?
>>
>> Thanks and regards,
>> Lokesh
> 
> I have also started to see these inmate boot stalls. They are random,
> though, if you try again you may see the boot pass. BTW, why the
> change "tools: Leave more space between kernel and initrd on x86"? I'm
> running with it reverted for a while, since it now takes too much
> space on inmates for typical 8MB kernels.

Look into next, and you will find both answers and (hopefully) some
solution.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-08 Thread Gustavo Lima Chaves

* 'Lokesh Vutla' via Jailhouse  [2018-01-08 
18:33:29 +0530]:

> 
> 
> On Saturday 06 January 2018 03:05 PM, a.ku...@matellio.com wrote:
> > Hi,
> > 
> > 
> > We are able to run jailhouse on Tx2 platform using 4.14-rc14-kernel, we are 
> > able to enable root-cell and we can run non-root cell demo application 
> > which is provided by jailhouse(gic-demo.bin). 
> > 
> > But we are stuck in the middle of booting while loading 4.14-rc14-kernel in 
> > non-root cell, i have attached both root-cell and non-root cell config.
> > 
> > This is the logs we are getting while loading non-root cell.
> > 
> > Created cell "jetson-tx2-linux-demo"
> > Page pool usage after cell creation: mem 117/16356, remap 101/131072
> > [ 2059.007251] Created Jailhouse cell "jetson-tx2-linux-demo"
> > Cell "jetson-tx2-linux-demo" can be loaded
> > Started cell "jetson-tx2-linux-demo"
> > [0.00] Booting Linux on physical CPU 0x102
> > [0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version 
> > 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
> > [0.00] Boot CPU: AArch64 Processor [411fd073]
> > [0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
> > [0.00] efi: Getting EFI parameters from FDT:
> > [0.00] efi: UEFI not found.
> > [0.00] cma: Reserved 16 MiB at 0xff00
> > [0.00] psci: probing for conduit method from DT.
> > [0.00] psci: PSCIv0.2 detected in firmware.
> > [0.00] psci: Using standard PSCI v0.2 function IDs
> > [0.00] psci: MIGRATE_INFO_TYPE not supported.
> > [0.00] Failed to find device node for boot cpu
> > [0.00] missing boot CPU MPIDR, not enabling secondaries
> > [0.00] percpu: Embedded 21 pages/cpu @800042cca000 s47128 r8192 
> > d30696 u86016
> > [0.00] Detected PIPT I-cache on CPU0
> > [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 108092
> > [0.00] Kernel command line: console=ttyS0,115200
> 
> Can you try passing some valid root= option in bootargs?
> 
> Thanks and regards,
> Lokesh

I have also started to see these inmate boot stalls. They are random,
though, if you try again you may see the boot pass. BTW, why the
change "tools: Leave more space between kernel and initrd on x86"? I'm
running with it reverted for a while, since it now takes too much
space on inmates for typical 8MB kernels.

Regards,

> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jailhouse" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jailhouse-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
Gustavo Lima Chaves
Intel - Open Source Technology Center

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-08 Thread 'Lokesh Vutla' via Jailhouse



On Saturday 06 January 2018 03:05 PM, a.ku...@matellio.com wrote:
> Hi,
> 
> 
> We are able to run jailhouse on Tx2 platform using 4.14-rc14-kernel, we are 
> able to enable root-cell and we can run non-root cell demo application which 
> is provided by jailhouse(gic-demo.bin). 
> 
> But we are stuck in the middle of booting while loading 4.14-rc14-kernel in 
> non-root cell, i have attached both root-cell and non-root cell config.
> 
> This is the logs we are getting while loading non-root cell.
> 
> Created cell "jetson-tx2-linux-demo"
> Page pool usage after cell creation: mem 117/16356, remap 101/131072
> [ 2059.007251] Created Jailhouse cell "jetson-tx2-linux-demo"
> Cell "jetson-tx2-linux-demo" can be loaded
> Started cell "jetson-tx2-linux-demo"
> [0.00] Booting Linux on physical CPU 0x102
> [0.00] Linux version 4.14.0-rc4 (root@tegra-ubuntu) (gcc version 
> 5.3.1 20160413 (Ubuntu/Linaro 5.3.1-14ubuntu2.1)) #2 SMP PREEMPT Wed 8
> [0.00] Boot CPU: AArch64 Processor [411fd073]
> [0.00] Machine model: Jailhouse cell on NVIDIA Jetson TX2
> [0.00] efi: Getting EFI parameters from FDT:
> [0.00] efi: UEFI not found.
> [0.00] cma: Reserved 16 MiB at 0xff00
> [0.00] psci: probing for conduit method from DT.
> [0.00] psci: PSCIv0.2 detected in firmware.
> [0.00] psci: Using standard PSCI v0.2 function IDs
> [0.00] psci: MIGRATE_INFO_TYPE not supported.
> [0.00] Failed to find device node for boot cpu
> [0.00] missing boot CPU MPIDR, not enabling secondaries
> [0.00] percpu: Embedded 21 pages/cpu @800042cca000 s47128 r8192 
> d30696 u86016
> [0.00] Detected PIPT I-cache on CPU0
> [0.00] Built 1 zonelists, mobility grouping on.  Total pages: 108092
> [0.00] Kernel command line: console=ttyS0,115200

Can you try passing some valid root= option in bootargs?

Thanks and regards,
Lokesh

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-08 Thread Jan Kiszka

On 2018-01-08 08:23, a.ku...@matellio.com wrote:
> Hi Jan,
>>> [0.100617] Unpacking initramfs...
>>> [0.262347] Initramfs unpacking failed: junk in compressed archive
>  
>> Something is wrong with the memory layout or size so that the initramfs
>> gets corrupted (I'm assuming you tested that it works fine natively).
>>
>  
>  I did some experiments with memory layout and size but problem is not 
> resolving. can you give me a hint which memory layout you are talking about?
>> Do you load kernel and initramfs via "jailhouse cell linux"? What
>> parameter does the script report when you call it with "-w ..."?
>>
>> Jan
> 
>   We build rootfs.cpio using buidroot it is working for Tx1, but stuck in Tx2.
> 
> We provided the following command to boot non-root cell.
> 
> sudo jailhouse cell linux configs/jetson-tx2-linux-demo.cell /boot/Image_jan 
> -i rootfs.cpio -d inmate-jetson-tx2.dtb -c "console=ttyS0,115200"
> 
> We have not provided any parameters with "-w ", suggest me that we have to 
> provide any extra parameters?

jailhouse cell linux --help
[...]
  --write-params FILE, -w FILE
only parse cell configuration, write out parameters
into the specified file and print required jailhouse
cell commands to boot Linux to the console

It also reports the commands you need to issue on the target. Those
reveal which addresses the images should be loaded to.

Note that I pushed some updates to the next branch that make the gap
between kernel and initrd configurable, and they also shrink it for
ARM64 (because that arch does not do any kernel compression). Maybe
worth a try.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-07 Thread a . kumar

Hi Jan,
> > [0.100617] Unpacking initramfs...
> > [0.262347] Initramfs unpacking failed: junk in compressed archive
 
> Something is wrong with the memory layout or size so that the initramfs
> gets corrupted (I'm assuming you tested that it works fine natively).
> 
 
 I did some experiments with memory layout and size but problem is not 
resolving. can you give me a hint which memory layout you are talking about?
> Do you load kernel and initramfs via "jailhouse cell linux"? What
> parameter does the script report when you call it with "-w ..."?
> 
> Jan

  We build rootfs.cpio using buidroot it is working for Tx1, but stuck in Tx2.

We provided the following command to boot non-root cell.

sudo jailhouse cell linux configs/jetson-tx2-linux-demo.cell /boot/Image_jan -i 
rootfs.cpio -d inmate-jetson-tx2.dtb -c "console=ttyS0,115200"

We have not provided any parameters with "-w ", suggest me that we have to 
provide any extra parameters?


Regards
Ashok



-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

2018-01-07 Thread a . kumar

Hi Jan,

> > [0.100617] Unpacking initramfs...
> > [0.262347] Initramfs unpacking failed: junk in compressed archive
 
> Something is wrong with the memory layout or size so that the initramfs
> gets corrupted (I'm assuming you tested that it works fine natively).
> 
 
 I did some experiments with memory layout and size but problem is not 
resolving. can you give me a hint which memory layout you are talking about?

> Do you load kernel and initramfs via "jailhouse cell linux"? What
> parameter does the script report when you call it with "-w ..."?
> 
> Jan


  We build rootfs.cpio using buidroot it is working for Tx1, but stuck in Tx2.

We provided the following command to boot non-root cell.

sudo jailhouse cell linux configs/jetson-tx2-linux-demo.cell /boot/Image_jan -i 
rootfs.cpio -d configs/jetson-tx2-linux-demo.cell -c "console=ttyS0,115200"

We have not provided any parameters with "-w ", suggest me that we have to 
provide any extra parameters? 


Regards
Ashok

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

Re: Loading kernel on Non-root cell in jetson-TX2.

11 matches

Site Navigation

Mail list logo

Footer information