public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Mugunthan V N <mugunthanvnm@ti•com>
To: netdev <netdev@vger•kernel.org>
Cc: David Miller <davem@davemloft•net>
Subject: phy link status not stable
Date: Tue, 16 Sep 2014 21:56:56 +0530	[thread overview]
Message-ID: <541864D0.7080803@ti.com> (raw)

Hi

While doing ifdown/ifup test, phy link up status is very much delayed
and also link up/down comes alternatively without physical link changes
which leads to ifup failure. in v3.12 internal tree there is no failure.
Pasting the logs below.

root@am437x-evm:~# ifup eth0
[  652.633204] net eth0: initializing cpsw version 1.15 (0)
[  652.717428] net eth0: phy found : id is : 0x221622
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
[  658.717859] cpsw 4a100000.ethernet eth0: Link is Up - 1Gbps/Full -
flow control rx/tx
Sending discover...
[  660.717894] cpsw 4a100000.ethernet eth0: Link is Down
[  661.717937] cpsw 4a100000.ethernet eth0: Link is Up - 1Gbps/Full -
flow control rx/tx
No lease, failing
root@am437x-evm:~# udhcpc
udhcpc (v1.20.2) started
Sending discover...
Sending select for 172.24.190.6...
Lease of 172.24.190.6 obtained, lease time 3600
/etc/udhcpc.d/50default: Adding DNS 192.0.2.2
/etc/udhcpc.d/50default: Adding DNS 192.0.2.3
root@am437x-evm:~#

Is this a known issue or any pointers where to look for clues?

Setup: TI-AM437x EVM
Phy: Micrel KSZ9031 Gigabit PHY

Thanks,
Mugunthan V N

             reply	other threads:[~2014-09-16 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-16 16:26 Mugunthan V N [this message]
2014-09-16 17:09 ` phy link status not stable Florian Fainelli

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=541864D0.7080803@ti.com \
    --to=mugunthanvnm@ti$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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