> So, assuming the setting was picked up, there is no improvement. > > Currently, the system is faster up than the network device tries to configure > the link. Do you have any other suggestions? > > Aren’t there really any other options to easily debug/instrument the Linux > kernel module to be sure where the time is spent and to optimize it? > > Having systems reboot very quickly is important to have short down times. > > > Thanks, > > Paul > Hi Paul,
Auto-neg can take up to 4 seconds by spec. and that looks to be happening. Forcing the speed and duplex as Aaron suggested should speed up getting link though. The switch port (as Aaron pointed out) also need to be set to force the link. There is nothing wrong with the driver or the NIC HW. This _is_ host this works. You could also try turning off spanning tree on the switch but that might have other consequences for the other devices on the network. Cheers, John ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ 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
