No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

[Oliver Smith]

Hi,

on a SolidRun LX2160A Clearfog CX machine I've upgraded from 6.12.101 to
6.12.113 in Debian 13, and with that kernel there is no eth0 after boot.
When downgrading to 6.12.101, it is there again.

I suspect this is a regression from dts changes in
arch/arm64/boot/dts/freescale as there were a few for lx2160a:

* 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/arch/arm64/boot/dts/freescale?h=v6.12.113
* 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/arch/arm64/boot/dts/freescale?h=v6.12.101

imx@lists.linux.dev is listed in MAINTAINERS for that path and Vincent
authored the related patches, therefore sending this to you. If this is
the wrong place then let me know where to report this instead.

Thank you!

Best regards,
Oliver

-- 
- Oliver Smith <osmith@sysmocom.de>            https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Siemensstr. 26a
* 10551 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte

Re: No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

[Fabio Estevam]

Hi Oliver,

On Fri, Oct 30, 2026 at 8:48 AM Oliver Smith <osmith@sysmocom.de> wrote:
>
> Hi,
>
> on a SolidRun LX2160A Clearfog CX machine I've upgraded from 6.12.101 to
> 6.12.113 in Debian 13, and with that kernel there is no eth0 after boot.
> When downgrading to 6.12.101, it is there again.
>
> I suspect this is a regression from dts changes in
> arch/arm64/boot/dts/freescale as there were a few for lx2160a:

Run git bisect between 6.12.101 and 6.12.113 to find the exact commit
that caused the regression.

Re: No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

[Vincent Jardin]

Hi Oliver,

Le 30/10/26 11:32, Fabio Estevam a écrit :
> Hi Oliver,
> 
> On Fri, Oct 30, 2026 at 8:48 AM Oliver Smith <osmith@sysmocom.de> wrote:
> >
> > Hi,
> >
> > on a SolidRun LX2160A Clearfog CX machine I've upgraded from 6.12.101 to
> > 6.12.113 in Debian 13, and with that kernel there is no eth0 after boot.
> > When downgrading to 6.12.101, it is there again.
> >
> > I suspect this is a regression from dts changes in
> > arch/arm64/boot/dts/freescale as there were a few for lx2160a:
> 
> Run git bisect between 6.12.101 and 6.12.113 to find the exact commit
> that caused the regression.

then, on the board, check, analyze and provide the outputs if needed of:

uname -r; cat /proc/device-tree/model; echo
ip -br link
dmesg | grep -i -e fsl-mc -e dpaa2 -e dpmac -e dprc
cat /sys/kernel/debug/devices_deferred
ls /sys/bus/fsl-mc/devices/
busybox devmem 0x08340008 32 # or equivalent for your Debian

From U-Boot, before it boots Linux:

md.l 0x08340008 1
printenv mcinitcmd bootcmd

0x08340008 is the General Status Register (GSR) of the MC

my 2 cents,
  Vincent

Re: No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

[Oliver Smith]

Hi Fabio,
Hi Vincent,

thank you for the replies!

On 10/30/26 15:37, Vincent Jardin wrote:
> Le 30/10/26 11:32, Fabio Estevam a écrit :
>> Run git bisect between 6.12.101 and 6.12.113 to find the exact commit
>> that caused the regression.

Sorry, but this is not a development machine and I don't have physical
access to it, only a serial console. I can run some checks, but building
multiple kernels for bisect and booting them sounds too risky and time
intense unfortunately.

On 10/30/26 15:37, Vincent Jardin wrote:
> then, on the board, check, analyze and provide the outputs if needed of:
> 
> uname -r; cat /proc/device-tree/model; echo
> ip -br link
> dmesg | grep -i -e fsl-mc -e dpaa2 -e dpmac -e dprc
> cat /sys/kernel/debug/devices_deferred
> ls /sys/bus/fsl-mc/devices/
> busybox devmem 0x08340008 32 # or equivalent for your Debian

Old kernel:
> root@lx2-1:~# uname -r; cat /proc/device-tree/model; echo
> 6.12.101+deb13-arm64
> SolidRun LX2160A Clearfog CX
> root@lx2-1:~# ip -br link
> lo               UNKNOWN        00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
> eth0             UP             d0:63:b4:03:b4:f7 <BROADCAST,MULTICAST,UP,LOWER_UP>
> br0              UP             52:a0:18:ae:7c:34 <BROADCAST,MULTICAST,UP,LOWER_UP>
> lxcbr0           DOWN           10:66:6a:00:00:00 <NO-CARRIER,BROADCAST,MULTICAST,UP>
> vethhEvvMx@if2   UP             fe:19:6b:c5:90:0e <BROADCAST,MULTICAST,UP,LOWER_UP>
> veth5HPqsX@if2   UP             fe:de:f1:c5:ae:3a <BROADCAST,MULTICAST,UP,LOWER_UP>
> vethFfnWAR@if2   UP             fe:ec:61:dc:5a:aa <BROADCAST,MULTICAST,UP,LOWER_UP>
> root@lx2-1:~# dmesg | grep -i -e fsl-mc -e dpaa2 -e dpmac -e dprc
> root@lx2-1:~# cat /sys/kernel/debug/devices_deferred
> root@lx2-1:~# ls /sys/bus/fsl-mc/devices/
> dpbp.0	  dpcon.12  dpcon.18  dpcon.23	dpcon.29  dpcon.6  dpio.10  dpio.2  dpio.8    dpmac.5  dpmcp.10  dpmcp.16  dpmcp.21  dpmcp.27  dpmcp.32  dpmcp.6  dprtc.0
> dpbp.1	  dpcon.13  dpcon.19  dpcon.24	dpcon.3   dpcon.7  dpio.11  dpio.3  dpio.9    dpmac.6  dpmcp.11  dpmcp.17  dpmcp.22  dpmcp.28  dpmcp.33  dpmcp.7  dpseci.0
> dpcon.0   dpcon.14  dpcon.2   dpcon.25	dpcon.30  dpcon.8  dpio.12  dpio.4  dpmac.10  dpmac.7  dpmcp.12  dpmcp.18  dpmcp.23  dpmcp.29  dpmcp.34  dpmcp.8
> dpcon.1   dpcon.15  dpcon.20  dpcon.26	dpcon.31  dpcon.9  dpio.13  dpio.5  dpmac.17  dpmac.8  dpmcp.13  dpmcp.19  dpmcp.24  dpmcp.3   dpmcp.35  dpmcp.9
> dpcon.10  dpcon.16  dpcon.21  dpcon.27	dpcon.4   dpio.0   dpio.14  dpio.6  dpmac.3   dpmac.9  dpmcp.14  dpmcp.2   dpmcp.25  dpmcp.30  dpmcp.4	 dpni.0
> dpcon.11  dpcon.17  dpcon.22  dpcon.28	dpcon.5   dpio.1   dpio.15  dpio.7  dpmac.4   dpmcp.1  dpmcp.15  dpmcp.20  dpmcp.26  dpmcp.31  dpmcp.5	 dprc.1
> root@lx2-1:~# busybox devmem 0x08340008 32
> 0x0000003F

New kernel:
> root@lx2-1:~# uname -r; cat /proc/device-tree/model; echo
> 6.12.113+deb13-arm64
> SolidRun LX2160A Clearfog CX
> root@lx2-1:~# ip -br link
> lo               UNKNOWN        00:00:00:00:00:00 <LOOPBACK,UP,LOWER_UP>
> br0              UP             52:a0:18:ae:7c:34 <BROADCAST,MULTICAST,UP,LOWER_UP>
> lxcbr0           DOWN           10:66:6a:00:00:00 <NO-CARRIER,BROADCAST,MULTICAST,UP>
> vethXFQUqu@if2   UP             fe:0a:7b:88:52:cd <BROADCAST,MULTICAST,UP,LOWER_UP>
> vethUG8N9y@if2   UP             fe:ff:eb:09:16:a5 <BROADCAST,MULTICAST,UP,LOWER_UP>
> vethoesNCY@if2   UP             fe:8e:29:91:43:6b <BROADCAST,MULTICAST,UP,LOWER_UP>
> root@lx2-1:~# dmesg | grep -i -e fsl-mc -e dpaa2 -e dpmac -e dprc
> [    0.008101] fsl-mc MSI: msi-controller@6020000 domain created
> [    0.107175] fsl_mc_bus 80c000000.fsl-mc: fsl-mc: MC boot completed with error 0x3f
> [    0.114747] fsl_mc_bus 80c000000.fsl-mc: probe with driver fsl_mc_bus failed with error -22
> root@lx2-1:~# cat /sys/kernel/debug/devices_deferred
> 8000000.crypto
> root@lx2-1:~# ls /sys/bus/fsl-mc/devices/
> root@lx2-1:~# busybox devmem 0x08340008 32
> 0x0000003F

On 10/30/26 15:37, Vincent Jardin wrote:
> 
>  From U-Boot, before it boots Linux:
> 
> md.l 0x08340008 1
> printenv mcinitcmd bootcmd
> 
> 0x08340008 is the General Status Register (GSR) of the MC

uboot:
> => md.l 0x08340008 1
> 08340008: 00000001                               ....
> => printenv mcinitcmd bootcmd
> mcinitcmd=mmc dev 1; mmc read 0x80a00000 0x5000 0x1200;mmc read 0x80e00000 0x7000 0x800;env exists secureboot && mmc read 0x80640000 0x3200 0x20 && mmc read 0x80680000 0x3400 0x20 && esbc_validate 0x80640000 && esbc_validate 0x80680000 ;fsl_mc start mc 0x80a00000 0x80e00000
> bootcmd=mmc dev 1; env exists mcinitcmd && mmcinfo; mmc read 0x80d00000 0x6800 0x800; env exists mcinitcmd && env exists secureboot  && mmc read 0x806C0000 0x3600 0x20 && esbc_validate 0x806C0000;env exists mcinitcmd && fsl_mc lazyapply dpl 0x80d00000;run distro_bootcmd;run sd2_bootcmd;env exists secureboot && esbc_halt;
> =>

Best regards,
Oliver

-- 
- Oliver Smith <osmith@sysmocom.de>            https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Siemensstr. 26a
* 10551 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte

Re: No network for SolidRun LX2160A Clearfog CX with kernel 6.12.113

[Fabio Estevam]

Hi Oliver,

On Fri, Oct 30, 2026 at 1:30 PM Oliver Smith <osmith@sysmocom.de> wrote:

> Sorry, but this is not a development machine and I don't have physical
> access to it, only a serial console. I can run some checks, but building
> multiple kernels for bisect and booting them sounds too risky and time
> intense unfortunately.

I suggest reverting the 6.12 commit below:

commit 9a884fefd537e6a54aaaaa6d180d1f03f42baa8e
Author: Ioana Ciornei <ioana.ciornei@nxp.com>
Date:   Wed Apr 1 17:45:08 2026 +0300

    bus: fsl-mc: wait for the MC firmware to complete its boot

    [ Upstream commit 208858b1b48eba83d073542372329cf8ed606526 ]

    There are use cases in which the Management Complex firmware boot
    process is started by the bootloader which does not wait for the boot to
    complete. This is mainly done in order to reduce the overall boot time
    of a DPAA2 based SoC.

    In this kind of circumstance, the fsl-mc bus driver needs to make sure
    that the MC firmware boot process is finished before proceeding to the
    usual operations such as interrogating the firmware to gather all
    existent DPAA2 objects, creating the fsl-mc devices on the bus etc.

    Add this kind of check early in the boot process of the fsl-mc bus and
    defer the probe in case the firmware is still in its boot process.

    Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
    Link: https://lore.kernel.org/r/20260401144508.3062019-1-ioana.ciornei@nxp.com
    Signed-off-by: Christophe Leroy (CS GROUP) <chleroy@kernel.org>
    Signed-off-by: Sasha Levin <sashal@kernel.org>