All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Remi Lefevre <rlefevre@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1)
Date: Wed, 01 Oct 2008 10:14:46 -0500	[thread overview]
Message-ID: <48E393E6.7000505@freescale.com> (raw)
In-Reply-To: <4e0b9cb00810010636h10c0d1fw3385ecf1f0a27be5@mail.gmail.com>

Remi Lefevre wrote:
> Errors encountered are "Underrun" errors (from bd).

Try elevating the arbiter priority for the FCC.

> CPM clock-frequency is not defined in the DTS, neither filled by U-Boot,
> but it doesn't seem to be needed, does it ?

Not for ethernet.

> I'm a little confused, and find strange that the first UDP request completes
> correctly, as well as latter ARP ones.

If it's bus contention (as underrun implies), then it may happen only 
under load.

-Scott

  reply	other threads:[~2008-10-01 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 16:44 FS_ENET ERROR(s) 0x12 at second NFS RPC port lookup (100005/1) Remi Lefevre
2008-09-30 17:33 ` Scott Wood
2008-10-01 13:36   ` Remi Lefevre
2008-10-01 15:14     ` Scott Wood [this message]
2008-10-09 19:46       ` Remi Lefevre

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=48E393E6.7000505@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rlefevre@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.