Oops--trying again with address fixed. On Thu, Jan 07, 2010 at 09:35:58AM -0500, J. Bruce Fields wrote: > On Wed, Jan 06, 2010 at 08:02:14PM -0500, Scott Sturdivant wrote: > > On Wed, 6 Jan 2010, J. Bruce Fields wrote: > >> On a quick skim I don't see an obvious reason; one approach (if you're > >> *positive* there weren't also any software changes) might be just to try > >> swapping the hardware back (starting with the LAN?) and see if you can > >> reliably turn the problem on/off with just one hardware change. > >> > >> --b. > > > > Thank you for the good suggestion! I have done this and have verified > > that indeed the onboard LAN is the root of the problem. > > Woo-hoo! > > > However, as the > > onboard LAN is able to handle Samba / scp but fails with NFS, I'm curious > > if this is an actual hardware problem or a driver issue? Does anyone > > know where the appropriate place for this problem would be? Is there an > > atl1c list? > > Adding netdev@xxxxxxxxxxxxxxxxxxx Could you repeat any details about > the exact models of the network interfaces? > > --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
