All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinhard Schwillinsky <rsw@maxxio.at>
To: "Kári Davíðsson" <kd@medcare.is>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [linuxppc-embedded:] 8xx_io/enet.c
Date: Tue, 10 Dec 2002 11:42:59 +0100	[thread overview]
Message-ID: <3DF5C533.2050809@maxxio.at> (raw)
In-Reply-To: EADB10BAC266A14A85ECBF8686A73E31938190@kolkrabbi.flaga.is


Kári Davíðsson wrote:
> Hello,
>
> I am hitting the following code (i.e. the printk() is reached) in the interrupt handler for the ethernet on a custom 823e board in arch/ppc/8xx_io/enet.c
>
> 	/* Check for receive busy, i.e. packets coming but no place to
> 	 * put them.  This "can't happen" because the receive interrupt
> 	 * is tossing previous frames.
> 	 */
> 	if (int_events & SCCE_ENET_BSY) {
> 		cep->stats.rx_dropped++;
> 		printk("CPM ENET: BSY can't happen.\n");
> 	}
>
> Clearly this can happen, even though the comment sais otherwise.
> This happens for a "high" datarate sunrpc interface operating over TCP/IP.

As far as I remember "BSY" in an 8xx SCC means that no more receive
buffers are available. This happens when the driver software isn't fast
enough to return currently received buffers to the SCC. This can occur
when too few buffers are allocated or at very high data rates.


>
> Is it safe to ignore this "error" or is it a real bug that should be investigated?

I don't know the current version of the enet driver but I think it's
"save" to ignore that message but you should check why that occurs. You
can increase the number of buffers allocated for the rx part of that
particular SCC.

>
> I am a litle unclear on the ethernet operation in whole.

This has nothing to do with ethernet directly! Only a received ethernet
packet cannot be stored. Higher protocols (f.e. TCP) should resend the
missing data!


rgs Reinhard


--
----------------------------------------------------
Reinhard Schwillinsky        Tel.: ++43/1/205 255/210
Maxxio technologies GmbH     Fax.: ++43/1/205 255/900
Prinz Eugen Strasse 8        A-1040 Vienna/Austria


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

  reply	other threads:[~2002-12-10 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 10:19 8xx_io/enet.c Kári Davíðsson
2002-12-10 10:42 ` Reinhard Schwillinsky [this message]
2002-12-10 10:46 ` 8xx_io/enet.c Joakim Tjernlund
  -- strict thread matches above, loose matches on Subject: below --
2002-12-10 12:05 [linuxppc-embedded:] 8xx_io/enet.c Kári Davíðsson

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=3DF5C533.2050809@maxxio.at \
    --to=rsw@maxxio.at \
    --cc=kd@medcare.is \
    --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 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.