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: Tue, 30 Sep 2008 12:33:51 -0500 [thread overview]
Message-ID: <48E262FF.9020108@freescale.com> (raw)
In-Reply-To: <4e0b9cb00809300944r2c2359dbx6df882705106c4d1@mail.gmail.com>
Remi Lefevre wrote:
> [ 5.573391] fs_enet: eth0 FS_ENET ERROR(s) 0x12
This is a transmit error; more detail can be found in the buffer descriptor.
Check your pin and clock configuration.
-Scott
next prev parent reply other threads:[~2008-09-30 17:36 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 [this message]
2008-10-01 13:36 ` Remi Lefevre
2008-10-01 15:14 ` Scott Wood
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=48E262FF.9020108@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.