linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Graham Stoney <greyham@research.canon.com.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: FEC ERROR 41200000 on CLLF-860T
Date: Tue, 07 Dec 1999 01:54:19 -0500	[thread overview]
Message-ID: <384CAF1B.1C6CFE3@netx4.com> (raw)
In-Reply-To: 19991207064156.5D9DF118D3@elph.research.canon.com.au


Graham Stoney wrote:


>     FEC ERROR 41200000
>     FEC ENET: rcv is not +last
> 
> Is this something I should be worried about?


Oh yes.....I don't have the FEC driver updated for that board
yet.  Although my instructions tell you how to download through
that port and get the CLLF utility program to initialize it
because I have been too lazy, something still isn't quite
right.

If it appears to be working, then just keep smiling and go
on about your business.  Don't try any performance tests.......

That particular error looks legitimate.  Probably some kind
of a hard network error.  Since the buffer wasn't marked as +last,
it looks like someone is jumping on the bus with late collisions
or something.  How often does it occur?


	-- Dan

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~1999-12-07  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07  6:41 FEC ERROR 41200000 on CLLF-860T Graham Stoney
1999-12-07  6:54 ` Dan Malek [this message]
1999-12-07  7:05   ` Graham Stoney
1999-12-07 17:23     ` Dan Malek
1999-12-09  0:24       ` Graham Stoney
1999-12-09 11:18         ` Marcus Sundberg
1999-12-09 18:11           ` Dan Malek
1999-12-10 12:39             ` Marcus Sundberg
1999-12-12 23:56               ` Graham Stoney
1999-12-13  1:25                 ` Dan Malek
1999-12-15 16:20                 ` Marcus Sundberg

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=384CAF1B.1C6CFE3@netx4.com \
    --to=dan@netx4.com \
    --cc=greyham@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).