From: Sascha Hauer <s.hauer@pengutronix.de>
To: Holger Hans Peter Freyther <holger@freyther.de>
Cc: barebox@lists.infradead.org
Subject: Re: Activating network during start
Date: Fri, 21 Nov 2014 10:20:00 +0100 [thread overview]
Message-ID: <20141121092000.GW30369@pengutronix.de> (raw)
In-Reply-To: <20141121084001.GO4921@xiaoyu.lan>
On Fri, Nov 21, 2014 at 09:40:01AM +0100, Holger Hans Peter Freyther wrote:
> On Fri, Nov 21, 2014 at 08:11:16AM +0100, Sascha Hauer wrote:
>
> Good Morning,
>
> > I don't understand what the exact problem is. So your command generally
> > works, only when it's called from the start script it doesn't work. Did
> > I get that correctly? Also a second invocation of the command then
> > works, right?
> > This sounds like the phy is not yet ready. I often get the impression
> > that the very first packet sent to the network is lost, even though the
> > phy registers tell us the phy is ready. I never found out what the
> > problem is here.
>
> lldp
> sleep 2s
> lldp
>
> With the first "lldp" invocation the network is activated and then I
> need to sleep a bit (I don't know if 1s or less is working but with
> no wait it certainly doesn't work).
>
> With checking the phy you refer to the call of eth_carrier_check that
> is used by eth_send?
Yes.
You could try if one of the other network commands like 'ping' work
right after startup.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-11-21 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 20:50 Holger Freyther
2014-11-21 7:11 ` Sascha Hauer
2014-11-21 8:40 ` Holger Hans Peter Freyther
2014-11-21 9:18 ` Sascha Hauer
2014-11-21 9:20 ` Sascha Hauer [this message]
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=20141121092000.GW30369@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=holger@freyther.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