Opened 4 years ago

Last modified 2 years ago

#15511 new defect

lantiq/xrx200 switch - Ethernet-Frames are forwarded to all ports (on TD 8970)

Reported by: spam@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: lantiq xrx200 Cc:


This problem is already reported in /ticket/14439.html, but this ticket seems to be dead.
On this device (maybe only this) the switch driver seems not to work correct - all packets are forwarded to all switch ports (tested with wireshark)
If I comment out the

#define SW_PORTMAP

in lantiq_xrx200.c it works OK - but I get a lot of

tx ring full

messages under load and I think, that is because this feature is missing.

Attachments (0)

Change History (6)

comment:1 Changed 4 years ago by anonymous

Test with current trunk, there is a new driver

comment:2 Changed 4 years ago by anonymous

It tried using latest trunk (rev. 40565) but its not working either. I thought that this is maybe related to bad initialization through uboot - because nobody else seems to have this problem.
When I read the code lately, I saw a "TODO"-part where the switch should be resetted completly when driver get loaded. Is this done in the meantime?
If you need any futher information for debugging purposes - let me know ....

comment:3 Changed 3 years ago by anonymous

This applies to Barrier Breaker to.

comment:4 Changed 3 years ago by hitech95

I have just compiled a version of trunk, looks like that without

#define SW_PORTMAP

the switch not is working as a hub. All frames are sent to the correct port.
Someone should find the mistake in the driver and fix it...

comment:5 Changed 2 years ago by anonymous

I can't confirm this. I compiled 15.05 without "#define SW_PORTMAP" but I still get a lot of ring full messages (kern.err kernel: eth0: tx ring full).

comment:6 Changed 2 years ago by ikebanat

r47953 same situation, nothing has changed

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.