From: Giorgio Dal Molin <giorgio.nicole@arcor.de>
To: barebox@lists.infradead.org
Subject: imx7d enable second core
Date: Wed, 18 Jul 2018 09:27:46 +0200 (CEST) [thread overview]
Message-ID: <461871869.117927.1531898866247@mail.vodafone.de> (raw)
Hi all,
I'm currently working with the imx7d sabre board from NXP.
I have now a running barebox bootloader and a booting kernel.
My problem is now that, apparently, only one core is active:
...
commandline: console=ttymxc0,115200n8 ip=11.0.0.4::11.0.0.2:255.0.0.0::eth0: root=/dev/mmcblk0p2 rootdelay=1
Starting kernel in secure mode
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.17.7 (giorgio@BV_blfs) (gcc version 8.1.0 (OSELAS.Toolchain-2018.02.0)) #1 SMP Wed Jul 18 07:44:41 CEST 2018
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Freescale i.MX7 SabreSD Board
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 64 MiB at 0xba000000
[ 0.000000] percpu: Embedded 14 pages/cpu @(ptrval) s36392 r0 d20952 u57344
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200n8 ip=11.0.0.4::11.0.0.2:255.0.0.0::eth0: root=/dev/mmcblk0p2 rootdelay=1
[ 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: 950804K/1048576K available (10240K kernel code, 450K rwdata, 2188K rodata, 1024K init, 7788K bss, 32236K reserved, 65536K cma-reserved, 196196K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] .text : 0x(ptrval) - 0x(ptrval) (11232 kB)
[ 0.000000] .init : 0x(ptrval) - 0x(ptrval) (1024 kB)
[ 0.000000] .data : 0x(ptrval) - 0x(ptrval) ( 451 kB)
[ 0.000000] .bss : 0x(ptrval) - 0x(ptrval) (7789 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Running RCU self tests
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU event tracing is enabled.
[ 0.000000] RCU lockdep checking is enabled.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] Offload RCU callbacks from CPUs: (none).
[ 0.000000] arch_timer: cp15 timer(s) running at 8.00MHz (virt).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x1d854df40, max_idle_ns: 440795202120 ns
[ 0.000009] sched_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns
[ 0.000033] Switching to timer-based delay loop, resolution 125ns
[ 0.000545] Switching to timer-based delay loop, resolution 41ns
[ 0.000574] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[ 0.000601] clocksource: mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[ 0.001981] Console: colour dummy device 80x30
[ 0.002013] Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar
[ 0.002032] ... MAX_LOCKDEP_SUBCLASSES: 8
[ 0.002050] ... MAX_LOCK_DEPTH: 48
[ 0.002068] ... MAX_LOCKDEP_KEYS: 8191
[ 0.002086] ... CLASSHASH_SIZE: 4096
[ 0.002104] ... MAX_LOCKDEP_ENTRIES: 32768
[ 0.002122] ... MAX_LOCKDEP_CHAINS: 65536
[ 0.002140] ... CHAINHASH_SIZE: 32768
[ 0.002158] memory used by lock dependency info: 4655 kB
[ 0.002176] per task-struct memory footprint: 1536 bytes
[ 0.002230] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[ 0.002264] pid_max: default: 32768 minimum: 301
[ 0.002590] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002622] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.004407] CPU: Testing write buffer coherency: ok
[ 0.005308] CPU0: update cpu_capacity 1024
[ 0.005335] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.006792] Setting up static identity map for 0x80100000 - 0x80100060
[ 0.007218] Hierarchical SRCU implementation.
[ 0.008853] smp: Bringing up secondary CPUs ...
[ 0.010740] smp: Brought up 1 node, 1 CPU
[ 0.010766] SMP: Total of 1 processors activated (48.00 BogoMIPS).
[ 0.010786] CPU: All CPU(s) started in SVC mode.
[ 0.012748] devtmpfs: initialized
...
I was expecting both cores to be enabled at least by the kernel.
Does anyone had the same problem ?
giorgio
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-07-18 7:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 7:27 Giorgio Dal Molin [this message]
2018-07-18 7:56 ` Oleksij Rempel
2018-07-18 16:54 ` Andrey Smirnov
2018-07-19 7:16 ` Giorgio Dal Molin
2018-07-19 16:02 ` Andrey Smirnov
2018-07-19 16:16 ` Giorgio Dal Molin
2018-07-19 15:52 ` Giorgio Dal Molin
2018-07-19 16:09 ` Andrey Smirnov
2018-07-19 16:18 ` Giorgio Dal Molin
2019-10-15 11:29 Giorgio Dal Molin
2019-10-15 11:37 ` Ahmad Fatoum
2019-10-15 11:51 ` Ahmad Fatoum
2019-10-15 12:11 ` Giorgio Dal Molin
2019-10-15 12:47 ` Ahmad Fatoum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=461871869.117927.1531898866247@mail.vodafone.de \
--to=giorgio.nicole@arcor.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox