On Mon, 2 Mar 2015, Daniel J Blueman wrote:

> Hi Todd,
>
> Following up on this, since the packet loss doesn't occur when using the 
> out-of-tree driver but does when using the mainline driver, it's more 
> plausible that there's a driver behavioural difference causing this.
>
> After instrumenting MDI activity, a bunch of differences come from 
> force_speed_duplex() being called when the hardware is first 
> initialised, wherein hw->mac.autoneg is 0 only with the mainline driver 
> along this path:
>
> igb_setup_copper_link+0x2a5/0x2c0
> igb_copper_link_setup_igp+0xb7/0x210
> igb_setup_copper_link_82575+0xd4/0x180
> igb_setup_link+0x36/0x1c0
> igb_init_hw_82575+0xba/0x330
> igb_reset+0x15f/0x5e0
> igb_sriov_reinit+0x88/0xc0
> igb_pci_enable_sriov+0x115/0x200
> igb_probe+0x4ae/0x11a0
> local_pci_probe+0x40/0xa0
>
> The same 6 setup_copper_link() calls occur (three per on-board adapter) 
> in the out-of-tree driver, however hw->mac.autoneg is always set; this 
> also fits with our findings that triggering autoneg prevent the packet loss.
>
> What's the expectation with value of hw->mac.autoneg?

If this is the case, it sounds like all your packets are being dropped
at boot time. Did you ever complete your bisecting of the kernel?

Also, do you have direct factory support? I'd suggest filing an IPS if
you want this issue tracked.

-- 
todd.fujin...@intel.com

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to