I've tried a few things.  I did a blacklist ipv6, which seems to make it
harder to trigger the condition with MythTV traffic (I was able to
successfully watch a number of shows without the client locking up), but
this didn't stop the case where any NFS transfers to my Slackware server
locked up the client.

On a lark, I swapped the network card from the new e1000 to an old e100 card I 
had in a drawer.  It locks up identically under NFS load:
[  341.152000] NETDEV WATCHDOG: eth0: transmit timed out
[  341.172000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
[  346.168000] NETDEV WATCHDOG: eth0: transmit timed out
[  346.188000] e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex


I suspect a deeper bug in the kernel, perhaps relating to interrupts, or the 
networking parts common to both code paths (where the skbs are transmitted).

-- 
e1000 locks up under load in Feisty.
https://bugs.launchpad.net/bugs/106869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to