From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev@lists.ozlabs.org
Subject: NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel
Date: Mon, 29 Oct 2018 10:56:03 +0100 [thread overview]
Message-ID: <99266ac6-640c-b2a9-eef3-4e89ee1e0ad5@xenosoft.de> (raw)
In-Reply-To: <6bcb4b23-bb78-d1a5-7fd0-5f892115d302@xenosoft.de>
Hello,
I have figured out that the commit 'devicetree-for-4.20' [1] is
responsible for the SMP problem. I was able to revert this commit with
'git revert b27186abb37b7bd19e0ca434f4f425c807dbd708 -m 1' today.
[master ec81438] Revert "Merge tag 'devicetree-for-4.20' of
git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux"
138 files changed, 931 insertions(+), 1538 deletions(-)
rename Documentation/devicetree/bindings/arm/{atmel-sysregs.txt =>
atmel-at91.txt} (67%)
delete mode 100644
Documentation/devicetree/bindings/arm/freescale/fsl,layerscape-dcfg.txt
delete mode 100644
Documentation/devicetree/bindings/arm/freescale/fsl,layerscape-scfg.txt
rename Documentation/devicetree/bindings/arm/{zte,sysctrl.txt =>
zte.txt} (62%)
delete mode 100644 Documentation/devicetree/bindings/misc/lwn-bk4.txt
create mode 100644 arch/c6x/boot/dts/linked_dtb.S
delete mode 100644 arch/nios2/boot/dts/Makefile
create mode 100644 arch/nios2/boot/linked_dtb.S
delete mode 100644 arch/powerpc/boot/dts/Makefile
delete mode 100644 arch/powerpc/boot/dts/fsl/Makefile
delete mode 100644 scripts/dtc/yamltree.c
It solves the SMP problem! SMP works again on my P5020 board and on
virtual e5500 QEMU machines.
QEMU command: ./qemu-system-ppc64 -M ppce500 -cpu e5500 -m 2048 -kernel
/home/christian/Downloads/uImage-4.20-alpha5 -drive
format=raw,file=/home/christian/Dokumente/ubuntu_MATE_16.04.3_LTS_PowerPC_QEMU/ubuntu_MATE_16.04_PowerPC.img,index=0,if=virtio
-nic user,model=e1000 -append "rw root=/dev/vda3" -device virtio-vga
-device virtio-mouse-pci -device virtio-keyboard-pci -soundhw es1370 -smp 4
Screenshot:
https://plus.google.com/u/0/photos/photo/115515624056477014971/6617705776207990082
Do we need a new dtb file or is it a bug?
Thanks,
Christian
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b27186abb37b7bd19e0ca434f4f425c807dbd708
On 28 October 2018 at 5:35PM, Christian Zigotzky wrote:
> Hello,
>
> SMP doesn't work anymore with the latest Git kernel (28/10/18 11:12AM
> GMT) on my P5020 board and on virtual e5500 QEMU machines.
>
> Board with P5020 dual core CPU:
>
> [ 0.000000] -----------------------------------------------------
> [ 0.000000] phys_mem_size = 0x200000000
> [ 0.000000] dcache_bsize = 0x40
> [ 0.000000] icache_bsize = 0x40
> [ 0.000000] cpu_features = 0x00000003008003b4
> [ 0.000000] possible = 0x00000003009003b4
> [ 0.000000] always = 0x00000003008003b4
> [ 0.000000] cpu_user_features = 0xcc008000 0x08000000
> [ 0.000000] mmu_features = 0x000a0010
> [ 0.000000] firmware_features = 0x0000000000000000
> [ 0.000000] -----------------------------------------------------
> [ 0.000000] CoreNet Generic board
>
> ...
>
> [ 0.002161] smp: Bringing up secondary CPUs ...
> [ 0.002339] No cpu-release-addr for cpu 1
> [ 0.002347] smp: failed starting cpu 1 (rc -2)
> [ 0.002401] smp: Brought up 1 node, 1 CPU
>
> Virtual e5500 quad core QEMU machine:
>
> [ 0.026394] smp: Bringing up secondary CPUs ...
> [ 0.027831] No cpu-release-addr for cpu 1
> [ 0.027989] smp: failed starting cpu 1 (rc -2)
> [ 0.030143] No cpu-release-addr for cpu 2
> [ 0.030304] smp: failed starting cpu 2 (rc -2)
> [ 0.032400] No cpu-release-addr for cpu 3
> [ 0.032533] smp: failed starting cpu 3 (rc -2)
> [ 0.033117] smp: Brought up 1 node, 1 CPU
>
> QEMU command: ./qemu-system-ppc64 -M ppce500 -cpu e5500 -m 2048
> -kernel
> /home/christian/Downloads/vmlinux-4.20-alpha4-AmigaOne_X1000_X5000/X5000_and_QEMU_e5500/uImage-4.20
> -drive
> format=raw,file=/home/christian/Downloads/MATE_PowerPC_Remix_2017_0.9.img,index=0,if=virtio
> -nic user,model=e1000 -append "rw root=/dev/vda" -device virtio-vga
> -device virtio-mouse-pci -device virtio-keyboard-pci -usb -soundhw
> es1370 -smp 4
>
> .config:
>
> ...
> CONFIG_SMP=y
> CONFIG_NR_CPUS=4
> ...
>
> Please test the latest Git kernel on your NXP P50XX boards.
>
> Thanks,
> Christian
>
next prev parent reply other threads:[~2018-10-29 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 16:35 NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel Christian Zigotzky
2018-10-29 9:56 ` Christian Zigotzky [this message]
2018-10-29 10:22 ` arch/powerpc/kvm/trace.h:9:0: error: "TRACE_INCLUDE_PATH" redefined Christian Zigotzky
2018-10-31 10:09 ` Christian Zigotzky
2018-11-05 7:09 ` Christian Zigotzky
2018-10-29 17:00 ` NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel Christian Zigotzky
2018-10-29 18:13 ` LEROY Christophe
2018-10-29 20:12 ` Christian Zigotzky
2018-10-29 23:04 ` Scott Wood
2018-10-30 0:41 ` Christian Zigotzky
2018-10-30 1:42 ` Christian Zigotzky
2018-10-30 1:59 ` Benjamin Herrenschmidt
2018-10-30 7:27 ` Christian Zigotzky
2018-10-30 15:05 ` Christian Zigotzky
2018-10-29 22:24 ` Christian Zigotzky
2018-10-31 13:20 ` Michael Ellerman
2018-10-31 13:38 ` Christian Zigotzky
2018-11-07 2:11 ` Scott Wood
2018-11-07 6:46 ` Christian Zigotzky
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=99266ac6-640c-b2a9-eef3-4e89ee1e0ad5@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).