* [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time
@ 2016-02-29 12:47 Alexander Syring
2016-02-29 12:55 ` Gilles Chanteperdrix
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Syring @ 2016-02-29 12:47 UTC (permalink / raw)
To: xenomai
Hi
I patched the 4.1.15 from git.xenomai.org to compile it on the Cubietruck.
But it takes a long time to boot.
Here my dmesg:
root@Cubietruck:~# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.1.15-00126-g85a10db-dirty (root@Cubietruck)
(gcc version 5.3.1 20160205 (Debian 5.3.1-8) ) #9 SMP PREEMPT Thu Feb 25
21:33:38 CET 2016
[ 0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instruction cache
[ 0.000000] Machine model: Cubietech Cubietruck
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 523520
[ 0.000000] free_area_init_node: node 0, pgdat c0946cc0, node_mem_map
ee5f8000
[ 0.000000] Normal zone: 1710 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 194560 pages, LIFO batch:31
[ 0.000000] HighMem zone: 328960 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
[ 0.000000] PERCPU: Embedded 14 pages/cpu @ee5bd000 s27532 r8192 d21620
u57344
[ 0.000000] pcpu-alloc: s27532 r8192 d21620 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
pages: 521810
[ 0.000000] Kernel command line: console=ttyS0,115200 [earlyprintk]
root=/dev/mmcblk0p1 rootwait panic=10
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 2064612K/2094080K available (7101K kernel code, 247K
rwdata, 1776K rodata, 344K init, 467K bss, 29468K reserved, 0K cma-reserved,
1315840K highmem)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc08b36d0 (8878 kB)
.init : 0xc08b4000 - 0xc090a000 ( 344 kB)
.data : 0xc090a000 - 0xc0947df8 ( 248 kB)
.bss : 0xc094a000 - 0xc09befdc ( 468 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Additional per-CPU info printed with stalls.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
[ 0.000000] I-pipe, 24.000 MHz clocksource, wrap in 768614336404564 ms
[ 0.000000] clocksource ipipe_tsc: mask: 0xffffffffffffffff max_cycles:
0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff
max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[ 0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every
4398046511097ns
[ 0.000020] Switching to timer-based delay loop, resolution 41ns
[ 0.000381] clocksource timer: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 79635851949 ns
[ 0.000575] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff,
max_idle_ns: 12574081885 ns
[ 0.001104] Interrupt pipeline (release #1)
[ 8762.335587] Console: colour dummy device 80x30
[ 8762.335626] Calibrating delay loop (skipped), value calculated using timer
frequency.. 48.00 BogoMIPS (lpj=24000)
[ 8762.335645] pid_max: default: 32768 minimum: 301
[...]
has anyone a clue why it takes more than two hours to bring up the interrupt
pipeline?
Best
Alex
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time
2016-02-29 12:47 [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time Alexander Syring
@ 2016-02-29 12:55 ` Gilles Chanteperdrix
0 siblings, 0 replies; 4+ messages in thread
From: Gilles Chanteperdrix @ 2016-02-29 12:55 UTC (permalink / raw)
To: Alexander Syring; +Cc: xenomai
On Mon, Feb 29, 2016 at 01:47:17PM +0100, Alexander Syring wrote:
> Hi
> I patched the 4.1.15 from git.xenomai.org to compile it on the Cubietruck.
> But it takes a long time to boot.
>
> Here my dmesg:
>
> root@Cubietruck:~# dmesg
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Initializing cgroup subsys cpuacct
> [ 0.000000] Linux version 4.1.15-00126-g85a10db-dirty (root@Cubietruck)
> (gcc version 5.3.1 20160205 (Debian 5.3.1-8) ) #9 SMP PREEMPT Thu Feb 25
> 21:33:38 CET 2016
> [ 0.000000] CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
> [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
> instruction cache
> [ 0.000000] Machine model: Cubietech Cubietruck
> [ 0.000000] Memory policy: Data cache writealloc
> [ 0.000000] On node 0 totalpages: 523520
> [ 0.000000] free_area_init_node: node 0, pgdat c0946cc0, node_mem_map
> ee5f8000
> [ 0.000000] Normal zone: 1710 pages used for memmap
> [ 0.000000] Normal zone: 0 pages reserved
> [ 0.000000] Normal zone: 194560 pages, LIFO batch:31
> [ 0.000000] HighMem zone: 328960 pages, LIFO batch:31
> [ 0.000000] psci: probing for conduit method from DT.
> [ 0.000000] psci: Using PSCI v0.1 Function IDs from DT
> [ 0.000000] PERCPU: Embedded 14 pages/cpu @ee5bd000 s27532 r8192 d21620
> u57344
> [ 0.000000] pcpu-alloc: s27532 r8192 d21620 u57344 alloc=14*4096
> [ 0.000000] pcpu-alloc: [0] 0 [0] 1
> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total
> pages: 521810
> [ 0.000000] Kernel command line: console=ttyS0,115200 [earlyprintk]
> root=/dev/mmcblk0p1 rootwait panic=10
> [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
> [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
> bytes)
> [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
> [ 0.000000] Memory: 2064612K/2094080K available (7101K kernel code, 247K
> rwdata, 1776K rodata, 344K init, 467K bss, 29468K reserved, 0K cma-reserved,
> 1315840K highmem)
> [ 0.000000] Virtual kernel memory layout:
> vector : 0xffff0000 - 0xffff1000 ( 4 kB)
> fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
> vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
> lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
> pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
> modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
> .text : 0xc0008000 - 0xc08b36d0 (8878 kB)
> .init : 0xc08b4000 - 0xc090a000 ( 344 kB)
> .data : 0xc090a000 - 0xc0947df8 ( 248 kB)
> .bss : 0xc094a000 - 0xc09befdc ( 468 kB)
> [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
> [ 0.000000] Preemptible hierarchical RCU implementation.
> [ 0.000000] Additional per-CPU info printed with stalls.
> [ 0.000000] NR_IRQS:16 nr_irqs:16 16
> [ 0.000000] Architected cp15 timer(s) running at 24.00MHz (phys).
> [ 0.000000] I-pipe, 24.000 MHz clocksource, wrap in 768614336404564 ms
> [ 0.000000] clocksource ipipe_tsc: mask: 0xffffffffffffffff max_cycles:
> 0x588fe9dc0, max_idle_ns: 440795202592 ns
> [ 0.000000] clocksource arch_sys_counter: mask: 0xffffffffffffff
> max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
> [ 0.000006] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every
> 4398046511097ns
> [ 0.000020] Switching to timer-based delay loop, resolution 41ns
> [ 0.000381] clocksource timer: mask: 0xffffffff max_cycles: 0xffffffff,
> max_idle_ns: 79635851949 ns
> [ 0.000575] clocksource hstimer: mask: 0xffffffff max_cycles: 0xffffffff,
> max_idle_ns: 12574081885 ns
> [ 0.001104] Interrupt pipeline (release #1)
> [ 8762.335587] Console: colour dummy device 80x30
> [ 8762.335626] Calibrating delay loop (skipped), value calculated using timer
> frequency.. 48.00 BogoMIPS (lpj=24000)
> [ 8762.335645] pid_max: default: 32768 minimum: 301
>
> [...]
>
> has anyone a clue why it takes more than two hours to bring up the interrupt
> pipeline?
The problem is not the interrupt pipeline.
The Allwinner A20 is not among the processors supported by the
I-pipe patch, (see list here:
http://xenomai.org/embedded-hardware/)
Thus, before using this processor, you need to follow the porting
guide:
http://xenomai.org/2014/09/porting-xenomai-dual-kernel-to-a-new-arm-soc/
Also you do not tell us what version of the I-pipe patch you are
using, I guess not the latest, so you should try the latest to be
sure you get the latest fixes, notably:
https://git.xenomai.org/ipipe.git/commit/?h=ipipe-4.1.y&id=0a037e7db92fb0f0c4a1d77c6bac38814649ee26
Regards.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time
2016-02-29 18:39 Alexander Syring
@ 2016-02-29 19:16 ` Gilles Chanteperdrix
0 siblings, 0 replies; 4+ messages in thread
From: Gilles Chanteperdrix @ 2016-02-29 19:16 UTC (permalink / raw)
To: Alexander Syring; +Cc: xenomai
On Mon, Feb 29, 2016 at 07:39:56PM +0100, Alexander Syring wrote:
> On. On, Feb 29, 2016 at 13:55, Gilles Chanteperdrix
> wrote:
> >On Mon, Feb 29, 2016 at 01:47:17PM +0100, Alexander >Syring wrote:
> >> Hi
> >> I patched the 4.1.15 from git.xenomai.org to compile it on the Cubietruck.
> >> But it takes a long time to boot.
> > >
> > > [...]
> >>
> >> has anyone a clue why it takes more than two hours to bring up the interrupt
> >> pipeline?
> >
> >The problem is not the interrupt pipeline.
> >
> >The Allwinner A20 is not among the processors supported by the
> >I-pipe patch, (see list here:
> http://xenomai.org/embedded-hardware/)
> >
> >Thus, before using this processor, you need to follow the porting
> >guide:
> >http://xenomai.org/2014/09/porting-xenomai-dual-kernel-to-a-new-arm-soc/
> >
> >Also you do not tell us what version of the I-pipe patch >you are
> >using, I guess not the latest, so you should try the latest to be
> >sure you get the latest fixes, notably:
> >
> >https://git.xenomai.org/ipipe.git/commit/?h=ipipe-4.1.y&id=0a037e7db92fb0f0c4a1d77c6bac38814649ee26
>
> >Regards.
>
> I used the last version from yesterday of the ipipe.git
> ipipe-4.1.y
I doubt that, since you are talking about 4.1.15 whereas yesterday
version is for 4.1.18. But "yesterday" is a vague notion anyway,
with people living around the world in different time zones. A
git hash is more precise. Are you using
9920b05b219c09c2fa7036d9d7db1a9bcf04094e ?
Also, I pointed you to a precise patch, has the patch been applied
on the kernel you use or not?
>
> I tested 3.18.12 on Allwinner A20 before an here is the patch that I was using and the dmesg output.
> As you can see there is non delay of two hours.
>
> I don't know, why 4.1 is so different to 3.18.12.
If you follow the porting guide, you will find out. Since you are
using an unsupported processor, no effort has been made when porting
the I-pipe git from 3.18 to 4.1 to preserve anything about the
processor you use. If you want to avoid that, follow the porting
guide, them submit a patch to the I-pipe git for supporting the
processor you us, then, when your patch is merged, attempts will be
made to avoid breaking support for this processor in later versions.
--
Gilles.
https://click-hack.org
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time
@ 2016-02-29 18:39 Alexander Syring
2016-02-29 19:16 ` Gilles Chanteperdrix
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Syring @ 2016-02-29 18:39 UTC (permalink / raw)
To: xenomai
On. On, Feb 29, 2016 at 13:55, Gilles Chanteperdrix
wrote:
>On Mon, Feb 29, 2016 at 01:47:17PM +0100, Alexander >Syring wrote:
>> Hi
>> I patched the 4.1.15 from git.xenomai.org to compile it on the Cubietruck.
>> But it takes a long time to boot.
> >
> > [...]
>>
>> has anyone a clue why it takes more than two hours to bring up the interrupt
>> pipeline?
>
>The problem is not the interrupt pipeline.
>
>The Allwinner A20 is not among the processors supported by the
>I-pipe patch, (see list here:
http://xenomai.org/embedded-hardware/)
>
>Thus, before using this processor, you need to follow the porting
>guide:
>http://xenomai.org/2014/09/porting-xenomai-dual-kernel-to-a-new-arm-soc/
>
>Also you do not tell us what version of the I-pipe patch >you are
>using, I guess not the latest, so you should try the latest to be
>sure you get the latest fixes, notably:
>
>https://git.xenomai.org/ipipe.git/commit/?h=ipipe-4.1.y&id=0a037e7db92fb0f0c4a1d77c6bac38814649ee26
>Regards.
I used the last version from yesterday of the ipipe.git ipipe-4.1.y
I tested 3.18.12 on Allwinner A20 before an here is the patch that I was using and the dmesg output.
As you can see there is non delay of two hours.
I don't know, why 4.1 is so different to 3.18.12.
Regards
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.3.18.12
Type: application/octet-stream
Size: 25467 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20160229/34c2292f/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ipipe-allwinner-a20-3.18.12.patch
Type: application/octet-stream
Size: 2218 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20160229/34c2292f/attachment-0001.obj>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-02-29 19:16 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-02-29 12:47 [Xenomai] Ipipe 4.1 on Allwinner A20 (Cubietruck) takes a very long start time Alexander Syring
2016-02-29 12:55 ` Gilles Chanteperdrix
2016-02-29 18:39 Alexander Syring
2016-02-29 19:16 ` Gilles Chanteperdrix
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.