netdev - Re: secondary CPU port facing switch does not come up/online

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8f29251c-d572-f37f-3678-85b68889fd61@gmail.com>
Date:   Sun, 21 Jun 2020 14:08:36 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     vtol@....net, netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>, marek.behun@....cz
Subject: Re: secondary CPU port facing switch does not come up/online

Le 2020-06-21 à 13:24, ѽ҉ᶬḳ℠ a écrit :
> {"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.

There can only be one CPU port at a time active right now, so I am not
sure why it even worked with kernel 4.14. Could you please share kernel
logs and the output of ip link show in both working/non-working cases?

> 
> ____
> DT
> 
> cpu_port5: ports@5 {
>     reg = <5>;
>     label = "cpu";
>     ethernet = <&eth1>;
> 
>     fixed-link {
>         speed = <1000>;
>         full-duplex;
>     };
> };
> 
> cpu_port6: ports@6 {
>     reg = <6>;
>     label = "cpu";
>     ethernet = <&eth0>;
> 
>     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


-- 
Florian