From: "J. Bruce Fields" <bfields@fieldses.org>
To: Scott Sturdivant <scott-ILTxhEaIe5LR7s880joybQ@public.gmane.org>
Cc: linux-nfs@vger.kernel.org, netdev@kernel.org
Subject: Re: NFS Server Not Responding after hw change (svc: transport busy, not enqueued)
Date: Thu, 7 Jan 2010 09:35:58 -0500 [thread overview]
Message-ID: <20100107143557.GA24418@fieldses.org> (raw)
In-Reply-To: <alpine.DEB.1.10.1001061958560.22025-GVPuzBPOE2JdLJ4KwZ+rgqxOck334EZe@public.gmane.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.
next prev parent reply other threads:[~2010-01-07 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 3:25 NFS Server Not Responding after hw change (svc: transport busy, not enqueued) Scott Sturdivant
[not found] ` <alpine.DEB.1.10.1001052221550.22025-GVPuzBPOE2JdLJ4KwZ+rgqxOck334EZe@public.gmane.org>
2010-01-06 20:40 ` J. Bruce Fields
2010-01-07 1:02 ` Scott Sturdivant
[not found] ` <alpine.DEB.1.10.1001061958560.22025-GVPuzBPOE2JdLJ4KwZ+rgqxOck334EZe@public.gmane.org>
2010-01-07 14:35 ` J. Bruce Fields [this message]
2010-01-07 14:41 ` J. Bruce Fields
2010-01-07 14:53 ` Scott Sturdivant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100107143557.GA24418@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@kernel.org \
--cc=scott-ILTxhEaIe5LR7s880joybQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox