All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] igb initialization time after powerup
@ 2018-03-20 15:45 Ran Shalit
  2018-03-20 16:36 ` Peter Korsgaard
       [not found] ` <CALURroQg1Scf+i-_Y9_NgKa4UgFJBSLQzBZEcOgpKtNo7BihbA@mail.gmail.com>
  0 siblings, 2 replies; 3+ messages in thread
From: Ran Shalit @ 2018-03-20 15:45 UTC (permalink / raw)
  To: buildroot

Hello,

This is not specific buildroot issue, yet I hope someone here will have an idea.
I have long ethernet boot time till receiving ping after powerup.
I use igb driver.

I tried plenty of things, but nothing worked.
I have printed the function which are called in igb driver.

This is the relevant log in dmesg:

[    2.538089] igb: Intel(R) Gigabit Ethernet Network Driver network 5
- version 5.4.0-k
[    2.549736] network igb_reset
[    2.561629] network igb_phy_sw_reset
[    2.561902] network igb_setup_copper_link
[    2.561902] network igb_setup_copper_link... in autoneg
[    2.561903] network igb_copper_link_autoneg
[    2.561904] network igb_phy_setup_autoneg
[    2.562311] network igb_phy_has_link
[    2.563896] network igb_power_down_link
[    2.563900] network igb_power_down_phy_copper
[    2.566079] network igb_phy_has_link
[    3.696797] network igb_set_spd_dplx
[    3.699341] network ping    <<---   trying to ping host from init.d script
[    3.710493] network gpio 5
[    3.975110] network igb_open
[    3.975113] network __igb_open
[    3.975197] network igb_phy_hw_reset
[    3.977192] network igb_power_up_link
[    3.977198] network igb_power_up_phy_copper
[    3.977487] network igb_phy_sw_reset
[    3.977760] network igb_setup_copper_link
[    3.977901] network igb_phy_sw_reset
[    3.978038] network igb_phy_has_link
[    4.020261] network igb_phy_has_link
[    5.216208] network igb_phy_has_link
[    7.881180] network igb_phy_has_link

Is there any idea how to minimize igb boot time ?

Regards,
ranran

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] igb initialization time after powerup
  2018-03-20 15:45 [Buildroot] igb initialization time after powerup Ran Shalit
@ 2018-03-20 16:36 ` Peter Korsgaard
       [not found] ` <CALURroQg1Scf+i-_Y9_NgKa4UgFJBSLQzBZEcOgpKtNo7BihbA@mail.gmail.com>
  1 sibling, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2018-03-20 16:36 UTC (permalink / raw)
  To: buildroot

>>>>> "Ran" == Ran Shalit <ranshalit@gmail.com> writes:

 > Hello,
 > This is not specific buildroot issue, yet I hope someone here will have an idea.
 > I have long ethernet boot time till receiving ping after powerup.
 > I use igb driver.

Sorry, no idea. You may have more luck if you ask on the kernel netdev
mailing list:

http://vger.kernel.org/vger-lists.html#netdev

-- 
Bye, Peter Korsgaard

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Buildroot] igb initialization time after powerup
       [not found]   ` <CALURroToHgZk4i22gs2rRaPNZPF3T9jXZqbLpaDYFvZYZvkLXA@mail.gmail.com>
@ 2018-03-20 20:03     ` Christopher McCrory
  0 siblings, 0 replies; 3+ messages in thread
From: Christopher McCrory @ 2018-03-20 20:03 UTC (permalink / raw)
  To: buildroot

On Mar 20, 2018 8:45 AM, "Ran Shalit" <ranshalit@gmail.com> wrote:

Hello,

This is not specific buildroot issue, yet I hope someone here will have an
idea.
I have long ethernet boot time till receiving ping after powerup.
I use igb driver.


Spanning tree protocol on the connected switch might be causing it.



I tried plenty of things, but nothing worked.
I have printed the function which are called in igb driver.

This is the relevant log in dmesg:

[    2.538089] igb: Intel(R) Gigabit Ethernet Network Driver network 5
- version 5.4.0-k
[    2.549736] network igb_reset
[    2.561629] network igb_phy_sw_reset
[    2.561902] network igb_setup_copper_link
[    2.561902] network igb_setup_copper_link... in autoneg
[    2.561903] network igb_copper_link_autoneg
[    2.561904] network igb_phy_setup_autoneg
[    2.562311] network igb_phy_has_link
[    2.563896] network igb_power_down_link
[    2.563900] network igb_power_down_phy_copper
[    2.566079] network igb_phy_has_link
[    3.696797] network igb_set_spd_dplx
[    3.699341] network ping    <<---   trying to ping host from init.d
script
[    3.710493] network gpio 5
[    3.975110] network igb_open
[    3.975113] network __igb_open
[    3.975197] network igb_phy_hw_reset
[    3.977192] network igb_power_up_link
[    3.977198] network igb_power_up_phy_copper
[    3.977487] network igb_phy_sw_reset
[    3.977760] network igb_setup_copper_link
[    3.977901] network igb_phy_sw_reset
[    3.978038] network igb_phy_has_link
[    4.020261] network igb_phy_has_link
[    5.216208] network igb_phy_has_link
[    7.881180] network igb_phy_has_link

Is there any idea how to minimize igb boot time ?

Regards,
ranran
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180320/ed641729/attachment.html>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2018-03-20 20:03 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-03-20 15:45 [Buildroot] igb initialization time after powerup Ran Shalit
2018-03-20 16:36 ` Peter Korsgaard
     [not found] ` <CALURroQg1Scf+i-_Y9_NgKa4UgFJBSLQzBZEcOgpKtNo7BihbA@mail.gmail.com>
     [not found]   ` <CALURroToHgZk4i22gs2rRaPNZPF3T9jXZqbLpaDYFvZYZvkLXA@mail.gmail.com>
2018-03-20 20:03     ` Christopher McCrory

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.