Alright, so it is not related to MSI and Andrew proved that network in general is ok He seems to have a quite similar system as David, though the GA-EP45-DS5 string in lspci is likely a lie as it shows the same here and I got a EX58-UD3R. Both of you get 2 CPUs. From the logs David posted earlier this seems to be a dual-core Intel without hyper- threading enabled. Both got this quite low number on timer interrupts.
@Andrew, yes I guess mixing 32 and 64bit would probably only help if it does not work. In which case the potential breakage was between Jaunty and Karmic. If it works it may be only 64bit broke. Which is a hint but hm. The last log I saw from David was using 2.6.35-22-generic. Has one of you updated to -23 since then? Due to the silent hang I don't think there is much to be gained by traces on the client. I wonder whether there is much to be gained from gathering a tcpdump on the server. Generally is that "ghost traffic" immediate or starts after a while? Let me create some kernel packages which have a bunch of debugging code activated (especially lock checking and that stuff). Hopefully that could give any hint on the client side. I'll post here when I got something. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/661294 Title: System lock-up when receiving large files (big data amount) from NFS server -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
