From: Pete Popov <ppopov@embeddedalley.com>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: Michael Kelly <mike@cogcomp.com>,
"'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: AMD Au1100 problems (USB & Ethernet)
Date: Fri, 05 Aug 2005 14:14:34 -0700 [thread overview]
Message-ID: <1123276474.23193.6.camel@localhost.localdomain> (raw)
In-Reply-To: <42F3D4B7.6040905@246tNt.com>
> The PHY is on the CPU module itself, it's a BCM5221.
I see.
> >>If you could determine the actual errors (such as CRC, collision, etc) then we
> >>can try to determine where the errors are coming from. It may very well be
> >>HW, but it is a bit too early to make such a broad statement without more
> >>information.
> >
> >
> > Well, could be just a cable issue, hub, etc, but I'll put that in the HW
> > bucket as well :)
>
> The RX errors are reported as "rx miss" (RX_MISSED_FRAME set) which is
> described as "Internal FIFO overrun". Maybe those are just OK and it's
> just that it can't wistand full 100Mbps (the module is connected on a
> 10/100/1000 switch and the server is gigabit).
No, I don't think that's normal.
> The TX errors are time-out, how can I find more details about that ?
If possible, eliminate the gig switch by replacing it with a small
10/100 switch. If the problems go away, then that's a big clue.
Take a look at what the bcm phy is auto-negotiating and make sure it
matches what the switch thinks it has negotiated. Although, the tx
timeouts should have nothing to do with mismatched auto negotiation...
but I see there are a bunch of "carrier" errors.
You of course tried a different cable, just in case?
Pete
next prev parent reply other threads:[~2005-08-05 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:39 AMD Au1100 problems (USB & Ethernet) Sylvain Munaut
2005-08-05 19:47 ` Pete Popov
[not found] ` <6.2.0.14.2.20050805155414.044a0f00@mail.cogcomp.com>
2005-08-05 20:10 ` Pete Popov
2005-08-05 21:05 ` Sylvain Munaut
2005-08-05 21:14 ` Pete Popov [this message]
2005-08-06 10:42 ` Sylvain Munaut
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=1123276474.23193.6.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=linux-mips@linux-mips.org \
--cc=mike@cogcomp.com \
--cc=tnt@246tNt.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox