netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Santwona.Behera@sun.com, Matheos Worku <Matheos.Worku@Sun.COM>
Subject: question about niu linux driver behaviour
Date: Wed, 16 Sep 2009 15:13:00 -0600	[thread overview]
Message-ID: <4AB154DC.7070305@nortel.com> (raw)

Hi all,

I've got a Sun 3320 ATCA "alonso" board with Neptune network devices.
I'm running basically 2.6.27.8, and I'm seeing some odd behaviour in the
niu driver.

My understanding is that there are four ports. 0 and 1 are XMAC links,
while 10, and 11 are BMAC links.  On our board these normally map to
eth4/5/6/7.

At boot time, if the other end for the XMAC links is not up, then we see
messages that look like:

niu 0000:08:00.0: niu: Port 0 signal bits [00000000] are not [30000000]
niu 0000:08:00.0: niu: Port 0 10G/1G SERDES Link Failed
niu 0000:08:00.1: niu: Port 1 signal bits [00000000] are not [0c000000]
niu 0000:08:00.1: niu: Port 1 10G/1G SERDES Link Failed

and the BMAC links come up as eth4/eth5.

This seems to be due to the fact that we're checking ESR_INT_SIGNALS for
ESR_INT_DET0_P0 and ESR_INT_DET0_P1, and then failing because they're
not set.  (The 10G initialization behaves similarly.)

Is this valid behaviour?  I seems fragile for successful serdes
initialization to depend on the other end of the link being up at driver
init time.

Chris

                 reply	other threads:[~2009-09-16 21:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AB154DC.7070305@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=Matheos.Worku@Sun.COM \
    --cc=Santwona.Behera@sun.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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).