netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Lilly <brian@crystalfontz.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	Jim Baxter <jim_baxter@mentor.com>,
	Frank Li <Frank.Li@freescale.com>,
	Fugang Duan <B38611@freescale.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: i.MX28 based system losing eth0 on boot
Date: Tue, 6 May 2014 09:44:34 -0700	[thread overview]
Message-ID: <CAOk88BLR=nwNGdT++39vLdOt=TwZmemF-trSQPY8AdMN9tKtKQ@mail.gmail.com> (raw)

Uwe:

With commit a264b981f2c76e281ef27e7232774bf6c54ec865 we're having eth0
come up, then brought right back down with an MDIO rx timeout moments
after.  Adding back in the removed code keeps the interface alive and
it's working afterward without trouble.  I've tested the re-inserted
code in 3.12, 3.14 without issue on our boards.

Is there something else that can be done to prevent the MDIO timeouts?
We are using basically the same schematic for networking as the
imx28evk.

Any thoughts on how to resolve this?

Thanks,
Brian Lilly

             reply	other threads:[~2014-05-06 16:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 16:44 Brian Lilly [this message]
2014-05-06 18:11 ` i.MX28 based system losing eth0 on boot Uwe Kleine-König
2014-05-06 18:39   ` Florian Fainelli
2014-05-06 19:12   ` Brian Lilly
2014-05-06 19:24     ` Florian Fainelli
2014-05-06 21:40       ` Brian Lilly
2014-05-06 22:06         ` Florian Fainelli
2014-05-06 22:27           ` Brian Lilly
2014-05-07  3:07             ` Florian Fainelli
2014-05-07 19:16               ` Brian Lilly
2014-05-07 19:34                 ` Florian Fainelli
2014-05-07 19:51                   ` Brian Lilly
2014-05-08  1:47                     ` fugang.duan
2014-05-07  3:17 ` Fabio Estevam
2014-05-07 19:00   ` Brian Lilly

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='CAOk88BLR=nwNGdT++39vLdOt=TwZmemF-trSQPY8AdMN9tKtKQ@mail.gmail.com' \
    --to=brian@crystalfontz.com \
    --cc=B38611@freescale.com \
    --cc=Frank.Li@freescale.com \
    --cc=davem@davemloft.net \
    --cc=fabio.estevam@freescale.com \
    --cc=jim_baxter@mentor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).