#19085: nanostation m5 loco xw "loses" interface
------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Resolution: | Keywords:
------------------------+------------------------
Comment (by devel@…):
We tried to set a fixed ethernet link speed with ethtool on some devices
that are affected by this bug:
{{{
ethtool -s eth0 autoneg off
ethtool -s eth0 speed 100
ethtool -s eth0 duplex full
}}}
One of these devices went down from an average of 5 failures per day down
to zero failures (27 hours up to now). Its kernel log shows a lot of
renegotiation events (ca. 100 per day). They all end up with the fixed
link speed (100Mbps/Full duplex) after exactly one or two seconds delay:
{{{
[90171.670000] eth0: link up (1000Mbps/Full duplex)
[90173.670000] eth0: link up (100Mbps/Full duplex)
[92611.690000] eth0: link up (10Mbps/Half duplex)
[92613.690000] eth0: link up (100Mbps/Full duplex)
[93047.690000] eth0: link down
[93048.690000] eth0: link up (100Mbps/Full duplex)
[93340.690000] eth0: link down
[93341.690000] eth0: link up (100Mbps/Full duplex)
[93789.690000] eth0: link down
[93790.690000] eth0: link up (100Mbps/Full duplex)
[94240.690000] eth0: link up (1000Mbps/Full duplex)
[94242.690000] eth0: link up (100Mbps/Full duplex)
[95298.710000] eth0: link up (10Mbps/Half duplex)
[95300.710000] eth0: link up (100Mbps/Full duplex)
}}}
Thus the negotiation some works (with hiccups) for one device.
Sadly two other loco XW devices with the same fixed link speed setup still
expose the known failure.
--
Ticket URL: <https://dev.openwrt.org/ticket/19085#comment:5>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
