From mboxrd@z Thu Jan 1 00:00:00 1970 From: "J. Bruce Fields" Subject: Re: NFS Server Not Responding after hw change (svc: transport busy, not enqueued) Date: Thu, 7 Jan 2010 09:35:58 -0500 Message-ID: <20100107143557.GA24418@fieldses.org> References: <20100106204017.GN6612@fieldses.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org To: Scott Sturdivant Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org 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-u79uwXL29TaiAVqoAR/hOOOyGI2DFzLe@public.gmane.org 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html