ARMADAXP MV78260 CPU-1:failed to come online

ARMADAXP MV78260 CPU-1:failed to come online

[raghu MG]

Hi,
This mail is regarding Linux smp boot on ARMADA-XP MV2860
.

CPU-1 doesnt boot/go through the boot sequence & it fails to come
online & dumps this message

CPU1:failed to come online .

The CPU-1 boot register is programmed with physical address of
-->armada_xp_secondary_startup function & then cpu-0 deasserts the CPU-1.

I am using armada-xp-gp.dts ,I included armada-xp-mv78260.dts in it.

Any help would be appreciated.
Regards

ARMADAXP MV78260 CPU-1:failed to come online

[Andrew Lunn]

Hi Thomas, Gregory

On Tue, May 19, 2015 at 01:17:26AM +0530, raghu MG wrote:
> Hi,
> This mail is regarding Linux smp boot on ARMADA-XP MV2860
> .
> 
> CPU-1 doesnt boot/go through the boot sequence & it fails to come
> online & dumps this message
> 
> CPU1:failed to come online .
> 
> The CPU-1 boot register is programmed with physical address of
> -->armada_xp_secondary_startup function & then cpu-0 deasserts the CPU-1.
> 
> I am using armada-xp-gp.dts ,I included armada-xp-mv78260.dts in it.

Does this ring any bells? I have vague recollections of a u-boot
issue?

     Andrew

ARMADAXP MV78260 CPU-1:failed to come online

[Thomas Petazzoni]

Hello,

On Mon, 18 May 2015 22:20:33 +0200, Andrew Lunn wrote:

> On Tue, May 19, 2015 at 01:17:26AM +0530, raghu MG wrote:
> > Hi,
> > This mail is regarding Linux smp boot on ARMADA-XP MV2860
> > .
> > 
> > CPU-1 doesnt boot/go through the boot sequence & it fails to come
> > online & dumps this message
> > 
> > CPU1:failed to come online .
> > 
> > The CPU-1 boot register is programmed with physical address of
> > -->armada_xp_secondary_startup function & then cpu-0 deasserts the CPU-1.
> > 
> > I am using armada-xp-gp.dts ,I included armada-xp-mv78260.dts in it.
> 
> Does this ring any bells? I have vague recollections of a u-boot
> issue?

On Armada 375/38x yes. On Armada XP, I don't remember.

Raghu, can you make a more specific bug report, that includes:

 * The kernel version you tested
 * The U-Boot version you're using
 * The kernel configuration you're using
 * The complete boot log

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

ARMADAXP MV78260 CPU-1:failed to come online

[Thomas Petazzoni]

Raghu,

On Tue, 19 May 2015 14:15:49 +0530, raghu MG wrote:

> I am trying latest stable release from kernel.org -->linux-4.0.3.
> 
> I have seen this issue in linux-3.10.39 & linux-3.10.32 for which
> Marvell has provided lsp.
> 
> This issue doesnt crop up in older version like linux-3.2.40 &
> linux-3.2.52 with uImage
> 
> Not sure but I think this is something do with zImage & device tree combination.

Can you please try to boot with appended DTB? Some versions of the
Marvell bootloader tend to do horrible modifications to the FDT, making
assumptions that might be true with their Linux LSP, but not with the
mainline kernel. Using appended DTB is a way of making sure that their
bootloader will not touch the kernel DTB.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

ARMADAXP MV78260 CPU-1:failed to come online

[raghu MG]

Hi Thomas
That was quick.....Yes the append works fine..
I have to port drivers for the board now.

Thanks for the help..Will post queries if I  get into trouble on
ARMADAXP platform.

Anyways thanks  a ton :)

On Tue, May 19, 2015 at 2:19 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Raghu,
>
> On Tue, 19 May 2015 14:15:49 +0530, raghu MG wrote:
>
>> I am trying latest stable release from kernel.org -->linux-4.0.3.
>>
>> I have seen this issue in linux-3.10.39 & linux-3.10.32 for which
>> Marvell has provided lsp.
>>
>> This issue doesnt crop up in older version like linux-3.2.40 &
>> linux-3.2.52 with uImage
>>
>> Not sure but I think this is something do with zImage & device tree combination.
>
> Can you please try to boot with appended DTB? Some versions of the
> Marvell bootloader tend to do horrible modifications to the FDT, making
> assumptions that might be true with their Linux LSP, but not with the
> mainline kernel. Using appended DTB is a way of making sure that their
> bootloader will not touch the kernel DTB.
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com