[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <d47ad9bb-280b-1c9c-a245-0aebd689ccf5@gmx.net>
Date: Sun, 21 Jun 2020 20:24:00 +0000
From: ѽ҉ᶬḳ℠ <vtol@....net>
To: netdev@...r.kernel.org
Subject: secondary CPU port facing switch does not come up/online
{"kernel":"5.4.46","hostname":"OpenWrt","system":"ARMv7 Processor rev 1
(v7l)","model":"Turris
Omnia","board_name":"cznic,turris-omnia","release":{"distribution":"OpenWrt","version":"SNAPSHOT","revision":"r13600-9a477b833a","target":"mvebu/cortexa9","description":"OpenWrt
SNAPSHOT r13600-9a477b833a"}}
_____
With the below cited DT both CPU ports facing the node's build-in switch
are brought online at boot time with kernel 4.14 but since having
switched to kernel 5.4 only one CPU port gets online. It is as if the
kernel discards the presence of the secondary CPU port. Kernel log only
prints for the offline port just a single entry:
mvneta f1070000.ethernet eth0: Using hardware mac address
Swapping eth1 to port6 and eth0 to port6 then eth0 is brought online but
eth1 is not. Removing port5 then the port6 listed port is brought up/online.
Once the node is booted the offline port can brought up with ip l set
up. This seems like a regression bug in between the kernel versions.
____
DT
cpu_port5: ports@5 {
reg = <5>;
label = "cpu";
ethernet = <ð1>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
cpu_port6: ports@6 {
reg = <6>;
label = "cpu";
ethernet = <ð0>;
fixed-link {
speed = <1000>;
full-duplex;
};
};
------------
kconf
CONFIG_MTD_NAND_MARVELL=y
# CONFIG_PATA_MARVELL is not set
CONFIG_NET_VENDOR_MARVELL=y
CONFIG_MARVELL_PHY=y
# CONFIG_MARVELL_10G_PHY is not set
# CONFIG_WLAN_VENDOR_MARVELL is not set
CONFIG_CRYPTO_DEV_MARVELL_CESA=y
Download attachment "OpenPGP_0xF4F735931F05C5CE.asc" of type "application/pgp-keys" (3112 bytes)
Download attachment "OpenPGP_signature" of type "application/pgp-signature" (841 bytes)
Powered by blists - more mailing lists