[PATCH v0 00/10] Convert Netgear WNR854T to devicetree
Jamie Lentin
jm at lentin.co.uk
Sun Jul 17 05:52:15 PDT 2016
On Sat, 16 Jul 2016, Andrew Lunn wrote:
>> There's one major flaw; unicast traffic is never received on any port.
>> Broadcast traffic is received however, and on the correct port. Thus
>> an external machine can make an ARP request and get a response, for
>> example. With a manually-entered ARP entry, the router can send pings
>> out to a remote machine which responds, and the response is lost in the
>> DSA switch. "ethtool -S" reports pings received on "in_unicast" but
>> nothing makes it through the switch. This thread[0] seems very similar.
>> I've run out of ideas here and can't find any switch datasheets to give
>> me pointers so any suggestions greatly appreciated.
>
> Hi Jamie
>
> So it is 6131? So part of the 6185 family.
Yes, that's what's detected and the OpenWRT page says 88E6131-LAR1. And my
test setup looks like:
88e6131
|- lan1:10.100.1.55 <-- switch --> eth0:10.100.1.41 -|
|- lan4:10.100.4.55 <-- cable --> enp0:10.100.4.41 -|
laptop
enp0 is a 100M USB network card, the switch is gigabit and on the rest of
my network here, so there's assorted background broadcast chatter. If the
noise is confusing matters then can disconnect it.
Firstly I've tried to to rebase against net-next[0], but after adding 6131
to mv88e6xxx_of_match, &chip->ppu_work seems to be causing a NULL pointer
ooops. I'll assume it's not done yet and ignore net-next for now.
> I see you have NET_TAG_DSA, but not NET_TAG_EDSA in your
> configuration. Try swapping to EDSA. I even removed support for
> TAG_DSA in one of the recent patches.
Okay, back to my original wnr854t-support-v0a branch based on 4.6,
switched to .tag_protocol = DSA_TAG_PROTO_EDSA and reconfig'ed to
add support, but there's no traffic in/out of any port. tcpdump on the
underlying ethernet port shows encapsulated broadcast traffic, e.g. this
ARP request from enp0:10.100.4.41:
00:15:31.173399 1a:ff:0f:fe:10:22 (oui Unknown) > Broadcast, ethertype
Unknown (0xc008), length 64:
0x0000: 0000 0806 0001 0800 0604 0001 1aff 0ffe ................
0x0010: 1022 0a64 0429 0000 0000 0000 0a64 0437 .".d.).......d.7
0x0020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0030: 0000 ..
...but no unicast traffic.
> Please also can you get https://github.com/vivien/linux.git commit
> 323321875671dfe95b6b91ce051a74d415c7158c which will give you some
> extra debug files /sys/kernel/debug/mv88e6xxx.
>
> The reg, stats, and atu would be interesting.
Okay, I rebased 4.7-rc7, ignoring my ropey attempts to configure the LEDs,
cherry-picked the above commit. Pushed the result if it's useful[1]. The
debugfs code wouldn't patch cleanly onto 4.6 or net-next.
On boot up I get:
mdio_bus f1072004.mdio-bu: switch 0x106 probed: Marvell 88E6131, revision 6
mv643xx_eth_port mv643xx_eth_port.0 eth0: [0]: detected a Marvell 88E6131 switch
libphy: dsa slave smi: probed
Marvell 88E1121R dsa-0:00:00: attached PHY driver [Marvell 88E1121R] (mii_bus:phy_addr=dsa-0:00:00, irq=-1)
Marvell 88E1121R dsa-0:00:01: attached PHY driver [Marvell 88E1121R] (mii_bus:phy_addr=dsa-0:00:01, irq=-1)
Marvell 88E1121R dsa-0:00:02: attached PHY driver [Marvell 88E1121R] (mii_bus:phy_addr=dsa-0:00:02, irq=-1)
Marvell 88E1112 dsa-0:00:05: attached PHY driver [Marvell 88E1112] (mii_bus:phy_addr=dsa-0:00:05, irq=-1)
Marvell 88E1112 dsa-0:00:07: attached PHY driver [Marvell 88E1112] (mii_bus:phy_addr=dsa-0:00:07, irq=-1)
Like above (since 4.7 seems to use DSA_TAG_PROTO_EDSA), there's no
traffic visible with tcpdump on lan1/4 (broadcast or unicast), only
broadcast traffic on the backing port, eth0.
# cat /sys/kernel/debug/mv88e6xxx.0/regs
GLOBAL GLOBAL2 SERDES 0 1 2 3 4 5 6 7
0: c800 0 0 7080 7d80 7080 6e88 6086 7e86 6086 7086
1: 1b 0 0 3 3 3 3e 403 403 403 403
2: 2fd5 0 0 0 0 0 0 0 0 0 0
3: 9df4 ffff 0 1066 1066 1066 1066 1066 1066 1066 1066
4: 4000 191 0 433 433 433 3533 433 433 433 433
5: 1000 ff 0 0 0 0 0 0 0 0 0
6: c000 1f0f 0 708 708 708 7f7 708 708 708 708
7: 0 70ff 0 0 0 0 0 0 0 0 0
8: 0 7800 0 83 83 83 c3 83 83 83 83
9: 0 0 0 1 1 1 1 1 1 1 1
a: f148 0 0 0 0 0 0 0 0 0 0
b: 400f 0 0 1 2 4 0 10 20 40 80
c: 0 0 0 0 0 0 0 0 0 0 0
d: ffff 0 0 0 0 0 0 0 0 0 0
e: ffff 0 0 0 0 0 0 0 0 0 0
f: ffff 77 0 0 0 0 0 0 0 0 0
10: 0 0 0 0 0 0 0 0 0 0 0
11: 0 0 0 0 0 0 0 0 0 0 0
12: 5555 0 0 0 0 0 12 0 0 0 0
13: 5555 0 0 0 0 0 0 0 0 0 0
14: aaaa 0 0 403 403 403 8403 403 403 403 403
15: aaaa 0 0 0 0 0 0 0 0 0 0
16: ffff 0 0 700 70d 700 700 f41 f0e f41 f02
17: ffff 0 0 0 0 0 0 0 0 0 0
18: fa41 0 0 3210 3210 3210 3210 3210 3210 3210 3210
19: 8100 0 0 7654 7654 7654 7654 7654 7654 7654 7654
1a: 3330 0 0 - - - - - - - -
1b: f4 0 0 - - - - - - - -
1c: f000 0 0 - - - - - - - -
1d: 5c07 0 0 - - - - - - - -
1e: 0 f0 0 - - - - - - - -
1f: 0 0 0 - - - - - - - -
# cat /sys/kernel/debug/mv88e6xxx.0/stats
(lan4) (cpu) (lan1)
Statistic Port 0 Port 1 Port 2 Port 3 Port 4 Port 5 Port 6 Port 7
in_good_octets: 0 1064 0 1152 0 112155 0 0
in_bad_octets: 0 0 0 0 0 0 0 0
in_unicast: 0 0 0 0 0 0 0 0
in_broadcasts: 0 6 0 18 0 335 0 0
in_multicasts: 0 8 0 0 0 490 0 0
in_pause: 0 0 0 0 0 0 0 0
in_undersize: 0 0 0 0 0 0 0 0
in_fragments: 0 0 0 0 0 0 0 0
in_oversize: 0 0 0 0 0 0 0 0
in_jabber: 0 0 0 0 0 0 0 0
in_rx_error: 0 0 0 0 0 0 0 0
in_fcs_error: 0 0 0 0 0 0 0 0
out_octets: 0 0 0 131331 0 0 0 0
out_unicast: 0 0 0 0 0 0 0 0
out_broadcasts: 0 0 0 558 0 0 0 0
out_multicasts: 0 0 0 498 0 0 0 0
out_pause: 0 0 0 0 0 0 0 0
excessive: 0 0 0 0 0 0 0 0
collisions: 0 0 0 0 0 0 0 0
deferred: 0 0 0 0 0 0 0 0
single: 0 0 0 0 0 0 0 0
multiple: 0 0 0 0 0 0 0 0
out_fcs_error: 0 0 0 0 0 0 0 0
late: 0 0 0 0 0 0 0 0
hist_64bytes: 0 6 0 18 0 188 0 0
hist_65_127bytes: 0 8 0 440 0 69 0 0
hist_128_255bytes: 0 0 0 376 0 376 0 0
hist_256_511bytes: 0 0 0 0 0 0 0 0
hist_512_1023bytes: 0 0 0 0 0 0 0 0
hist_1024_max_bytes: 0 0 0 0 0 0 0 0
sw_in_discards: 0 0 0 0 0 0 0 0
sw_in_filtered: 0 0 0 18 0 0 0 0
sw_out_filtered: 0 0 0 0 0 0 0 0
# cat /sys/kernel/debug/mv88e6xxx.0/atu
FID MAC Addr State Trunk? DPV/Trunk ID
0 (dhcp server) Age 6 n - - - - - 5 - -
0 (access point) Age 7 (newest) n - - - - - 5 - -
0 (laptop enp0) Age 4 n - 1 - - - - - -
0 (android phone) Age 2 n - - - - - 5 - -
0 (android phone) Age 5 n - - - - - 5 - -
0 (openelec box w/kodi) Age 7 (newest) n - - - - - 5 - -
0 (android phone) Age 7 (newest) n - - - - - 5 - -
0 (laptop eth0) Age 5 n - - - - - 5 - -
0 (android phone) Age 3 n - - - - - 5 - -
Apart from (laptop enp0), everything is on lan1/port 5. Let me know if
it's useful to shed the background noise and/or try something in
particular. Thanks for the help!
>
> Andrew
>
[0] https://github.com/lentinj/linux/tree/wnr854t-support-v0b-net-next-experiment
[1] https://github.com/lentinj/linux/tree/wnr854t-support-v0a-rebase-4.7-rc7
--
Jamie Lentin
More information about the linux-arm-kernel
mailing list