From: Jeff Angielski <jangiels@speakeasy.net>
To: LinuxPPC Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: 8260 FCC buffer underrun
Date: 17 Aug 2004 08:24:26 -0400 [thread overview]
Message-ID: <1092745466.4190.14.camel@localhost.localdomain> (raw)
Does anybody know what conditions would cause the FCC to report a buffer
underrun transmit error when we are transmitting small ethernet
packets? Especially since the packets are so small they only use 1
buffer descriptor.
The wierd thing is that ARP packets gets transmitted fine. Anything
larger than that, however, generate the underrun errors.
The receive side appears to work fine. Pings come in, get processed,
and then we attempt to transmit the reply.
This is on an EP8260 H2, a couple weeks old u-boot cvs, and bk pull of
linuxppc-2.4.27.
The hardware works because PlanetCore with bk pull of linuxppc-2.4.27
works fine [although PlanetCore has it's own configuration issues...].
Jeff Angielski
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-08-17 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 12:24 Jeff Angielski [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-17 12:48 8260 FCC buffer underrun VanBaren, Gerald (AGRE)
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=1092745466.4190.14.camel@localhost.localdomain \
--to=jangiels@speakeasy.net \
--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).