linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: NXP P50XX/e5500: SMP doesn't work anymore with the latest Git kernel
Date: Wed, 7 Nov 2018 07:46:34 +0100	[thread overview]
Message-ID: <31eab5a0-3e24-2e65-8a9d-704dbfcc3319@xenosoft.de> (raw)
In-Reply-To: <6d196807270630668eb91f1448a043bddd43d291.camel@buserror.net>

On 07 November 2018 at 03:11AM, Scott Wood wrote:
> On Sun, 2018-10-28 at 17:35 +0100, 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,in
>> dex=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.
> I wasn't able to reproduce this with top-of-tree (commit 8053e5b93eca9b) with
> either qemu (e5500 on ppce500) or a hardware t4240.
>
> -Scott
>
>
Hi Scott,


Thanks for testing but your test was too late because Rob Herring fixed 
this issue last week. [1]


Cheers,

Christian


[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c961cb3be9064d1097ccc019390f8b5739daafc6


      reply	other threads:[~2018-11-07  6:49 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
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 [this message]

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=31eab5a0-3e24-2e65-8a9d-704dbfcc3319@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).