Hi, > I forwarded your report to our Validation and we will try to reproduce > this issue in our labs. You may want to consider opening a bug on e1000.sf.net > which will make it easier for us to track. > > Also your description of the issue is very vague and lacking in detail which > can make it harder for us to reproduce. For example, information such as: > > 1. Type/model of the switch (link partner). > 2. SFP+ module and/or DA cable used in the setup. > 3. What is the offset of the PHY register you are referring to?
Yes, It's because tbh, I wasn't really focusing on what actually causes the phy to crash or need to be reset. What I was trying to get fixed here is the fact that even a reboot or poweroff or a reload of ixgbe was not actually triggering a reset of the PHY and that only physically unplugging the machine from the mains did the trick. (Presumably the PHY stays powered even if the machine is "off"). And that's quite annoying when the machine in question is in a remote datacenter with no operators around. And this is because of this : https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/intel/ixgbe/ixgbe_x550.c#L237 The 'magic' value written to IXGBE_CS4227_SCRATCH register survives a reboot / poweroff / reload of ixgbe ... > If you open a ticket on e1000.sf.net make sure to include that information, > and any other details that will allow us to get a better idea of your setup. Ok, I'll do that next week when I'm back at the office. Cheers, Sylvain ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ 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
