Hi! On 17/07/12 11:22, Florian Fainelli wrote: > Transmit timeouts are really a bad situation, I'd rather check where they do > come from, maybe your transmit path is locked for too long, or you are > loosing > transmit completion interrupts?
Ethernet generally works stable and well on all Rt3xxx boards I got here for testing. But all of them show the same behavior which I now managed to reproduce reliably: Step 1: change the ip interface of bridge interface which includes eth0.1 Step 2: /etc/init.d/network restart Step 3: upon the first few packages trying to cross the interface, I get the transmit timeout. This applies to all Rt3050, Rt3052F, Rt3350, ... systems. Any idea? I don't remember this was a problem half a year ago when I last built a firmware for an Rt3350 based device... Any idea what could have introduced this? Cheers Daniel _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
