linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Neil Brown <neilb@suse.de>,
	linux-nfs@vger.kernel.org
Subject: Re: NFS problem on Microblaze LE
Date: Wed, 2 Mar 2011 10:49:00 -0500	[thread overview]
Message-ID: <20110302154900.GA29136@fieldses.org> (raw)
In-Reply-To: <4D6E4052.7050201-pSz03upnqPeHXe+LvDLADg@public.gmane.org>

On Wed, Mar 02, 2011 at 02:04:18PM +0100, Michal Simek wrote:
> Hi,
> 
> I am getting some troubles to get nfs work on new Microblaze
> little-endian platform and I would like to ask you for some
> recommendations how to debug it.
> 
> First of all I need to write that Microblaze big-endian platforms have no problem.
> The problem only happen if I use mount without -o nolock option
> (mount -t nfs 192.168.0.101:/tftpboot/nfs /mnt)
> If I use -o nolock option I have no problem to use nfs.
> 
> I use xilinx emaclite and axi emac(it is not in the mainline now)
> driver and I have no problem to use dhcp, ftp, http, telnet and
> other internet protocols.
> 
> I compared debug logs on big and little endian platform(rootfs has
> the same setting) I found that little-endian got packet which is
> shorter than on big endian which I have added to the log below.
> The second thing, which I think is connected to the previous point,
> is that I am getting BADCRED in rpc_verify_headers.
> 
> Is there any option/macro/recommended debug technique how to see
> packets? I need to get some clue how to see packet and then how they
> are passed to rpc_verify_header function.

A good first step would be to look at the network traffic with
wireshark.

--b.

  parent reply	other threads:[~2011-03-02 15:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 13:04 NFS problem on Microblaze LE Michal Simek
     [not found] ` <4D6E4052.7050201-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2011-03-02 15:49   ` J. Bruce Fields [this message]
2011-03-02 16:11     ` Michal Simek
2011-03-02 17:34       ` J. Bruce Fields
2011-03-02 18:20         ` Michal Simek
2011-03-02 18:24           ` J. Bruce Fields
2011-03-03  9:29             ` Michal Simek
2011-03-03 14:55               ` J. Bruce Fields
2011-03-03 15:01               ` Chuck Lever
2011-03-03 15:08                 ` Michal Simek
2011-03-03 15:51                   ` Chuck Lever
2011-03-03 16:20                     ` Michal Simek

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=20110302154900.GA29136@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org \
    --cc=neilb@suse.de \
    /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).