From: "Will Simoneau" <simoneau@ele.uri.edu>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Belisko Marek <marek.belisko@gmail.com>,
Trond.Myklebust@netapp.com, broonie@opensource.wolfsonmicro.com,
bdowning@lavos.net, linux-nfs@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [bisect] kernel 2.6.38 regression with root nfs mounting
Date: Tue, 29 Mar 2011 16:24:08 -0400 [thread overview]
Message-ID: <20110329202408.GM1966@ele.uri.edu> (raw)
In-Reply-To: <4AD2FFC1-E777-4C29-8718-4E1717EFCD86@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On 09:26 Fri 25 Mar , Chuck Lever wrote:
>
> According to the trace, the mount succeeds, and NFS requests are working. However, the server's replies to READ requests are not being seen by the client. Something on the client host or in the network is dropping them. I see successful 16KB reads, but 32KB reads do not work. Check your client for packet filtering (either intentional filtering, or accidental filtering due to configuration issues).
>
> I'll revisit the mount option defaults for NFSROOT again.
I have encountered the same problem as Belisko, using an FPGA board I am
working on (CPU is a mipsel r4k clone). 2.6.38-rc8 nfsroot works fine,
2.6.38 hangs while starting init. I can see read replies going out from
the NFS server but the client does not seem to receive them.
Interestingly, we are both using DM9000 network chips. I wonder if there
is a UDP-related problem on the DM9000. I will play with my
configuration a little more (in particular testing proto=tcp and revert
of 53d4737580535e073963b91ce87d4216e434fab5) but my guess is the DM9000
driver/chip is to blame. The DM9000A on my board has 16K of on-chip SRAM
used for its RX/TX buffers which may be playing a part in the problem.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-03-29 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimjmdi8sFTTjSPerOVgHQ+pjjwwMvCUX3AJ16At@mail.gmail.com>
[not found] ` <43F07477-9075-444D-9BBB-368650538EA8@oracle.com>
2011-03-23 6:30 ` [bisect] kernel 2.6.38 regression with root nfs mounting Belisko Marek
2011-03-23 13:44 ` Chuck Lever
2011-03-23 13:46 ` Belisko Marek
2011-03-23 14:06 ` Chuck Lever
[not found] ` <AANLkTik0UgB+k2i=E5t9XcF50SoSr_iXaFYrhctDx0FJ@mail.gmail.com>
2011-03-23 14:54 ` Chuck Lever
2011-03-25 7:24 ` Belisko Marek
2011-03-25 13:26 ` Chuck Lever
2011-03-29 20:24 ` Will Simoneau [this message]
2011-03-29 21:22 ` Mark Brown
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=20110329202408.GM1966@ele.uri.edu \
--to=simoneau@ele.uri.edu \
--cc=Trond.Myklebust@netapp.com \
--cc=bdowning@lavos.net \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=marek.belisko@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).