AnsweredAssumed Answered

[LS1046A] Slow boot caused by ethernets

Question asked by Łukasz Łaguna on Aug 21, 2019
Latest reply on Aug 22, 2019 by Yiping Wang

Hello. We are bringing up the custom board based on the NXP LS1046A and we have a problem with slow boot caused by ethernets probably. Below we share some logs:

```
[    0.000000] Linux version 4.14.53-rt34+g1fc9948fb7f4 (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP PREEMPT RT Fri Jul 19 11:18:57 UTC 2019
```

```
[    3.044007] libphy: Fixed MDIO Bus: probed
[    3.048100] tun: Universal TUN/TAP device driver, 1.6
[    3.054101] libphy: Freescale XGMAC MDIO Bus: probed
[    3.060539] libphy: Freescale XGMAC MDIO Bus: probed
[    3.065574] libphy: Freescale XGMAC MDIO Bus: probed
[    3.070726] libphy: Freescale XGMAC MDIO Bus: probed
[    3.075877] libphy: Freescale XGMAC MDIO Bus: probed
[    3.081029] libphy: Freescale XGMAC MDIO Bus: probed
[    3.086183] libphy: Freescale XGMAC MDIO Bus: probed
[    3.091328] libphy: Freescale XGMAC MDIO Bus: probed
[    3.096478] libphy: Freescale XGMAC MDIO Bus: probed
[    3.101625] libphy: Freescale XGMAC MDIO Bus: probed
[    3.116777] Freescale FM module, FMD API version 21.1.0
[    3.125341] Freescale FM Ports module
[    3.129000] fsl_mac: fsl_mac: FSL FMan MAC API based driver
[    3.135095] fsl_mac 1ae0000.ethernet: FMan MEMAC
[    3.139713] fsl_mac 1ae0000.ethernet: FMan MAC address: 00:04:9f:05:00:11
[    3.146736] fsl_mac 1ae2000.ethernet: FMan MEMAC
[    3.151352] fsl_mac 1ae2000.ethernet: FMan MAC address: 00:04:9f:05:00:12
[    3.158330] fsl_mac 1ae4000.ethernet: FMan MEMAC
[    3.162946] fsl_mac 1ae4000.ethernet: FMan MAC address: 00:04:9f:05:00:13
[    3.169945] fsl_mac 1ae6000.ethernet: FMan MEMAC
[    3.174562] fsl_mac 1ae6000.ethernet: FMan MAC address: 00:04:9f:05:00:14
[    3.181746] fsl_mac 1ae8000.ethernet: FMan MEMAC
[    3.186361] fsl_mac 1ae8000.ethernet: FMan MAC address: 00:04:9f:05:00:15
[    3.193551] fsl_mac 1aea000.ethernet: FMan MEMAC
[    3.198167] fsl_mac 1aea000.ethernet: FMan MAC address: 00:04:9f:05:00:16
[    3.205215] fsl_mac 1af0000.ethernet: FMan MEMAC
[    3.209832] fsl_mac 1af0000.ethernet: FMan MAC address: 00:04:9f:05:00:17
[    3.217030] fsl_mac 1af2000.ethernet: FMan MEMAC
[    3.221646] fsl_mac 1af2000.ethernet: FMan MAC address: 00:04:9f:05:00:18
[    3.228475] fsl_dpa: FSL DPAA Ethernet driver
[    3.236830] fsl_dpa: fsl_dpa: Probed interface eth0
[    3.245565] fsl_dpa: fsl_dpa: Probed interface eth1
[    3.254385] fsl_dpa: fsl_dpa: Probed interface eth2
[    3.263491] fsl_dpa: fsl_dpa: Probed interface eth3
[    3.272563] fsl_dpa: fsl_dpa: Probed interface eth4
[    3.282117] fsl_dpa: fsl_dpa: Probed interface eth5
[    3.291717] fsl_dpa: fsl_dpa: Probed interface eth6
[    3.301808] fsl_dpa: fsl_dpa: Probed interface eth7
[    3.306740] fsl_advanced: FSL DPAA Advanced drivers:
[    3.311703] fsl_proxy: FSL DPAA Proxy initialization driver
[    3.317512] fsl_oh: FSL FMan Offline Parsing port driver
```

```
[    6.228064] fsl_dpa soc:fsl,dpaa:ethernet@8 fm1-eth3: renamed from eth6
[   25.003560] fsl_dpa soc:fsl,dpaa:ethernet@5 fm1-eth5: renamed from eth5
[   56.543109] fsl_dpa soc:fsl,dpaa:ethernet@9 fm1-eth8: renamed from eth7
[   68.562379] udevd[2826]: worker [2833] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@9/net/eth7 is taking a long time
[   68.573953] udevd[2826]: worker [2837] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@3/net/eth3 is taking a long time
[   68.585526] udevd[2826]: worker [2838] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@0/net/eth0 is taking a long time
[   68.597099] udevd[2826]: worker [2835] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@1/net/eth1 is taking a long time
[   68.608672] udevd[2826]: worker [2841] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@2/net/eth2 is taking a long time
[   68.620244] udevd[2826]: worker [2836] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@4/net/eth4 is taking a long time
[   88.086953] fsl_dpa soc:fsl,dpaa:ethernet@4 fm1-eth6: renamed from eth4
[  109.118941] fsl_dpa soc:fsl,dpaa:ethernet@1 fm1-eth4: renamed from eth1
```
```
Configuring network interfaces... [  172.211162] fsl_dpa soc:fsl,dpaa:ethernet@2 fm1-eth1: renamed from eth2
[  187.233122] udevd[2826]: worker [2838] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@0/net/eth0 timeout; kill it
[  187.244720] udevd[2826]: seq 2888 '/devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@0/net/eth0' killed
[  187.254821] udevd[2826]: worker [2841] /devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@2/net/eth2 timeout; kill it
[  187.266024] udevd[2826]: seq 2892 '/devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@2/net/eth2' killed
[  193.242989] fsl_dpa soc:fsl,dpaa:ethernet@0 fm1-eth7: renamed from eth0
[  193.246866] udevd[2826]: worker [2841] terminated by signal 9 (Killed)
[  193.246871] udevd[2826]: worker [2841] failed while handling '/devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@2/net/eth2'
[  214.271436] udevd[2826]: worker [2838] terminated by signal 9 (Killed)
[  214.277985] udevd[2826]: worker [2838] failed while handling '/devices/platform/soc/soc:fsl,dpaa/soc:fsl,dpaa:ethernet@0/net/eth0'
```
```
[  245.816079] IPv6: ADDRCONF(NETDEV_CHANGE): fm1-eth7: link becomes ready
[  245.826110] IPv6: ADDRCONF(NETDEV_UP): fm1-eth4: link is not ready
[  245.835716] IPv6: ADDRCONF(NETDEV_UP): fm1-eth1: link is not ready
[  245.843211] IPv6: ADDRCONF(NETDEV_UP): fm1-eth2: link is not ready
```

 

At this moment login prompt shows up, but the system works slowly. After some additional time next interfaces show up.

 

```
[  424.583678] IPv6: ADDRCONF(NETDEV_UP): fm1-eth6: link is not ready
[  445.603218] net fm1-eth5: PHY already attached
[  445.607991] fsl_dpa soc:fsl,dpaa:ethernet@5 fm1-eth5: Could not connect to PHY /soc/fman@1a00000/mdio@fc000/ethernet-phy@4
[  445.619141] fsl_dpa soc:fsl,dpaa:ethernet@5 fm1-eth5: init_phy() = -19
[  445.627707] IPv6: ADDRCONF(NETDEV_UP): fm1-eth3: link is not ready
[  466.632640] IPv6: ADDRCONF(NETDEV_UP): fm1-eth8: link is not ready
```

 

We have the same image with different device tree for the reference platform LS1046ARDB and we didn't notice such problem on this platform. Maybe you have an idea what can be wrong? Can it be caused by a device tree?

 

Thanks.

Outcomes