Thomas A. Oehser <[EMAIL PROTECTED]> : [...] > > I'll welcome a complete dmesg after you have recovered through > > ifconfig down/up though. > > _Nothing_ on dmesg.
Huh... Nothing appears when you issue 'dmesg' ? [...] > eth1 Link encap:Ethernet HWaddr 00:E0:4C:13:A9:56 > inet addr:192.168.99.99 Bcast:192.168.99.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:528416 errors:252 dropped:620 overruns:0 frame:966 > TX packets:243040 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > Interrupt:161 Base address:0xe000 How much long was the card under load ? A few seconds ? The same 1500 bytes mtu is used everywhere and the issue can not be reproduced with a simple ping -f -q -l 64 -s what_you_want aimed at the 8169, right ? [...] > What next? ethtool -d/-S before and after failure, .config and /proc/interrupts. -- Ueimor - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
