Re: [Intel-wired-lan] [PATCH] igb: use igb_adapter->io_addr instead of e1000_hw->hw_addr

On Nov 10 05:48, Hisashi T Fujinaka wrote:

On Thu, 10 Nov 2016, Corinna Vinschen wrote:

quoted

On Nov  8 11:33, Alexander Duyck wrote:

...

quoted

quoted

The question I would have is what is reading the device when it is in
this state.  The watchdog and any other functions that would read the
device should be disabled.

One possibility could be a race between a call to igb_close and the
igb_suspend function.  We have seen some of those pop up recently on
ixgbe and it looks like igb has the same bug.  We should probably be
using the rtnl_lock to guarantee that netif_device_detach and the call
to __igb_close are completed before igb_close could possibly be called
by the network stack.

Do you have a pointer to the related ixgbe patch, by any chance?

...
Here's the initial patch for igb I have, but it's on hold awaiting more
changes in ixgbe regarding AER.

Thanks a lot!


Corinna