Thread (12 messages) 12 messages, 6 authors, 2026-03-02

Re: [PATCH net] net: dsa: b53: prevent standalone from trying to forward to other ports

From: Rafał Miłecki <zajec5@gmail.com>
Date: 2026-03-02 12:35:03
Also in: lkml

sob., 28 lut 2026 o 14:30 Jonas Gorski [off-list ref] napisał(a):
Does this affect all ports, or only the wan port?
Problem affects every standalone port (one that isn't part of a bridge).

Have you tried to check the hardware counters if they get sent out a
different (cpu) port? AFAIK they should be available as ethtool
counters via gmacs, though I'm not 100% sure.
With your patch:
1. "rx_packets" stays 0
2. "rx_bytes" stays 0
3. "RxDiscarded" goes higher than 0

Can you check the contents of the EAP Port config registers? Maybe
some extra mode is set there by default.
All my B53_EAP_PAGE / B53_PORT_EAP_CONF(port) registers are set to 0 by default.

I don't have NS(+) device, so I can only guess. Though I always
wondered if the setup which CPU port (5/8/both) to use is just a
software thing or actually a hardware thing ... .
Without your patch, 10 s after connecting cable to "wan" port:
NIC statistics:
     tx_packets: 13
     tx_bytes: 1998
     rx_packets: 2
     rx_bytes: 1180
     TxOctets: 2052
     TxDropPkts: 0
     TxBroadcastPkts: 2
     TxMulticastPkts: 11
     TxUnicastPkts: 0
     TxCollisions: 0
     TxSingleCollision: 0
     TxMultipleCollision: 0
     TxDeferredTransmit: 0
     TxLateCollision: 0
     TxExcessiveCollision: 0
     TxPausePkts: 0
     RxOctets: 1188
     RxUndersizePkts: 0
     RxPausePkts: 0
     Pkts64Octets: 0
     Pkts65to127Octets: 0
     Pkts128to255Octets: 0
     Pkts256to511Octets: 0
     Pkts512to1023Octets: 2
     Pkts1024to1522Octets: 0
     RxOversizePkts: 0
     RxJabbers: 0
     RxAlignmentErrors: 0
     RxFCSErrors: 0
     RxGoodOctets: 1188
     RxDropPkts: 0
     RxUnicastPkts: 2
     RxMulticastPkts: 0
     RxBroadcastPkts: 0
     RxSAChanges: 1
     RxFragments: 0
     RxJumboPkts: 0
     RxSymbolErrors: 0
     RxDiscarded: 0

With your patch, 10 s after connecting cable to "wan" port:
NIC statistics:
     tx_packets: 14
     tx_bytes: 2334
     rx_packets: 0
     rx_bytes: 0
     TxOctets: 2392
     TxDropPkts: 0
     TxBroadcastPkts: 3
     TxMulticastPkts: 11
     TxUnicastPkts: 0
     TxCollisions: 0
     TxSingleCollision: 0
     TxMultipleCollision: 0
     TxDeferredTransmit: 0
     TxLateCollision: 0
     TxExcessiveCollision: 0
     TxPausePkts: 0
     RxOctets: 1782
     RxUndersizePkts: 0
     RxPausePkts: 0
     Pkts64Octets: 0
     Pkts65to127Octets: 0
     Pkts128to255Octets: 0
     Pkts256to511Octets: 0
     Pkts512to1023Octets: 3
     Pkts1024to1522Octets: 0
     RxOversizePkts: 0
     RxJabbers: 0
     RxAlignmentErrors: 0
     RxFCSErrors: 0
     RxGoodOctets: 1782
     RxDropPkts: 0
     RxUnicastPkts: 3
     RxMulticastPkts: 0
     RxBroadcastPkts: 0
     RxSAChanges: 1
     RxFragments: 0
     RxJumboPkts: 0
     RxSymbolErrors: 0
     RxDiscarded: 3

-- 
Rafał
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help