From: "Raymond Lo" <lo@routefree.com>
To: "John Cagle" <jcagle@kernel.org>, <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 405GP network receive problem
Date: Wed, 4 Jul 2001 11:52:53 -0700 [thread overview]
Message-ID: <00ee01c104ba$882f1660$0400a8c0@earthlink.net> (raw)
In-Reply-To: 20010629104618.A22541@kernel.org
----- Original Message -----
From: "John Cagle" <jcagle@kernel.org>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, June 29, 2001 10:46 AM
Subject: 405GP network receive problem
>
> I am debugging a custom board design based on the 405GP and have a problem
> receiving lots of TCP/IP traffic (like FTP). We're using a 2.4 kernel
based
> on Monta Vista's CDK 1.2. UDP traffic (like TFTP) works very well, but it
> doesn't ever have back-to-back receives, typically. The problem occurs
> at both 10mbit and 100Mbit.
>
> I have narrowed the problem down (using ttcp) to the following:
>
> During back-to-back receives (within microseconds) of two large (1500
bytes)
> TCP packets, the second packet is usually dropped by the 405GP. When I
> check ifconfig statistics, it shows the 1 lost packet, but also shows 2
> framing errors.
>
> Has anyone else seen this type of problem with the 405GP or does anyone
> know what the problem might be?
>
> Thanks,
> John
> ------------------------------
> John Cagle <jcagle@kernel.org>
>
>
This can happen if the 405gp MAC is in full-duplex mode, but the other side
is in half-duplex. The second packet could be corrupted by 405gp sending
TCP acknowledgments without listening for traffic first.
The function in the ppc405_enet driver determines half/full duplex is
ppc405_phy_duplex. If reading PHY_BMCR does not give the correct duplex
setting, you can try the following.
-Raymond
static int
ppc405_phy_duplex(void)
{
int duplex = HALF; /* Assume HALF */
unsigned short anlpar = 0x0;
if (ppc405_phy_read(PHY_ANLPAR,&anlpar)) {
printk(KERN_ERR "phy duplex read failed \n\r");
ppc405_phy_dump(KERN_ERR);
}
if ((anlpar & (PHY_ANLPAR_10FD | PHY_ANLPAR_TXFD)) != 0)
duplex = FULL;
return (duplex);
}
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-07-04 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 12:43 Proper way to flush caches Justin (Gus) Hurwitz
2001-06-29 17:46 ` 405GP network receive problem John Cagle
2001-06-29 18:57 ` Armin Kuster
2001-07-04 18:52 ` Raymond Lo [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-04 20:31 Marti, Felix
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='00ee01c104ba$882f1660$0400a8c0@earthlink.net' \
--to=lo@routefree.com \
--cc=jcagle@kernel.org \
--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.