[Macchiato] macchiatobin problem

[Baruch Siach]

Hi Steve, Team,

On Tue, Oct 30, 2018 at 09:22:52PM +0000, Steve McIntyre wrote:
> On Mon, Oct 29, 2018 at 06:09:17PM -0400, Team of Confiared wrote:
> >We have problem with our macchiatobin, the vanilla kernel not work:
> >
> >[ 58.364030] mvpp2 f2000000.ethernet eth0: could not attach PHY (-19)
> >[ 58.381763] mvpp2 f2000000.ethernet eth0: could not attach PHY (-19)
> >[ 67.443146] mvpp2 f4000000.ethernet eth1: could not attach PHY (-19)
> >[ 67.460872] mvpp2 f4000000.ethernet eth1: could not attach PHY (-19)

>From the kernel log below I infer that you are running the Macchiatobin 
SingleShot. Is that correct?

If this is the case, what DT are you using? Note that mainline kernel 
armada-8040-mcbin.dts is meant for the DoubleShot, which has 88x3310 PHYs on 
eth0 and eth1 (marked U2 and U3 on the PCB). These PHYs are not assembled on 
the SingleShot. Instead, both interfaces are directly connected to SFP cages. 
So the error message (-19 == -ENODEV) is correct. You need to remove the PHYs 
description from the DT for the SingleShot.

> >the constructor kernel not work too:
> >
> >[ 28.051705] NMI watchdog: BUG: soft lockup – CPU#2 stuck for 23s!
> >[swapper/0:1]
> >[ 28.059043] Modules linked in:
> >[ 28.062119]
> >[ 28.063616] CPU: 2 PID: 1 Comm: swapper/0 Not tainted
> >4.4.120-armada-18.09.2 #5
> >[ 28.070953] Hardware name: Marvell 8040 MACHIATOBin SingleShot (DT)
> >[ 28.077245] task: ffff80013b088000 ti: ffff80013b06c000 task.ti:
> >ffff80013b06c000
> >[ 28.084765] PC is at smp_call_function_many+0x24c/0x2b0
> >[ 28.090010] LR is at smp_call_function_many+0x21c/0x2b0
> >[ 28.095256] pc : [<ffff80000012344c>] lr : [<ffff80000012341c>] pstate:
> >80000145
> >[ 28.102681] sp : ffff80013b06f840
> >[ 28.106008] x29: ffff80013b06f840 x28: ffff800000c6a000
> >[ 28.111363] x27: ffff800000c6ab74 x26: 0000000000000040
> >[ 28.116717] x25: ffff800000ce1300 x24: ffff8000001566f0
> >[ 28.122070] x23: 0000000000000001 x22: ffff800000c47d80
> >[ 28.127424] x21: ffff80013ff8ae08 x20: ffff800000c6ad78
> >[ 28.132778] x19: ffff80013ff8ae00 x18: ffff800080cef12f
> >[ 28.138132] x17: 000000000000677f x16: ffff800000ce1400
> >[ 28.143485] x15: 0000000000000005 x14: 0000000000000050
> >[ 28.148838] x13: 0000000000000001 x12: ffff800000ce1780
> >[ 28.154192] x11: ffff800000ce1780 x10: ffff7bffc2c04020
> >[ 28.159546] x9 : 0000000000000140 x8 : 0000000000000008
> >[ 28.164899] x7 : 000000013f343000 x6 : 0000000000000000
> >[ 28.170253] x5 : 000000000000000b x4 : 0000000000000000
> >[ 28.175605] x3 : 0000000000000000 x2 : 0000000000000000
> >[ 28.180959] x1 : ffff80013ff6e120 x0 : ffff80013ff6e13
> >
> >More details at: http://macchiatobin.net/forums/topic/kernel-vanilla/
> 
> I've seen similar to that with vanilla 4.19. So I dropped back to 4.18
> and that works great.

What is you kernel .config? Are you using U-Boot? I can try to reproduce it 
here.

Thanks,
baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -