So looks like I figured it out .. I came across this bug reference https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728692 and thought of checking out my problem with ACPI turned off. And with ACPI turned off, the problem doesnt happen. So theres something that the igb driver is not happy about when acpi is on .. Any thoughts ?
Rgds, Gopa. On Fri, Apr 15, 2016 at 10:38 AM, Gopakumar Choorakkot Edakkunni < gopakumar.c.e at gmail.com> wrote: > Nothing in dmesg .. The ethtool was just a side-observation, the biggest > problem was that after unbinding from igb_uio and rebinding to igb, if I > follow it up with an /etc/init.d/network restart, that completely hoses the > linux system - anyone trying to open a socket (ifconfig for example) just > hangs. Thats how I started troubleshooting this and happened to see this > ethtool thing along with it, not sure if its related. Also the issue > doesn't happen with one or two interfaces, there needs to be at least five > or six interfaces for this to happen. > > The other thing I noticed is that if I put some sleep (2 seconds) between > unbind igb_uio and re-bind igb, the network-restart-hosing-system doesnt > happen, but the ethtool issue still remains > > Rgds, > Gopa. > > On Fri, Apr 15, 2016 at 12:50 AM, Remy Horton <remy.horton at intel.com> > wrote: > >> On 14/04/2016 20:25, Gopakumar Choorakkot Edakkunni wrote: >> [..] >> >>> ge8-----> 06:00.0 Ethernet controller: Intel Corporation 82576 Gigabit >>> Network Connection (rev 01) >>> >>> root:~# ls /sys/class/net/ge8/device/driver/module/drivers/ >>> pci:igb >>> root:~# >>> >>> root:~# ethtool ge8 >>> Settings for ge8: >>> Cannot get device settings: No such device >>> Cannot get wake-on-lan settings: No such device >>> Cannot get message level: No such device >>> Cannot get link status: No such device >>> No data available >>> >> >> Seems a little odd. Does dmesg show anything related to igb/ixgbe when >> you try this? >> >> ..Remy >> > >
