iavf: wait longer for close to complete

On some hardware/driver/architecture combinations, it may take longer
than 200msec for all close operations to be completed, causing a
spurious error message to be logged.

Increase the timeout value to 500msec to avoid this erroneous error.

Signed-off-by: Mitch Williams <mitch.a.williams@intel.com>
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
index 36f17d0c7a2e17a2e2d918cef4ad3180ac719375..9ce04a8c0d0ff4fa502758079546cb63996c1999 100644 (file)
--- a/drivers/net/ethernet/intel/iavf/iavf_main.c
+++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
@@ -3021,7 +3021,7 @@ static int iavf_close(struct net_device *netdev)
 
        status = wait_event_timeout(adapter->down_waitqueue,
                                    adapter->state == __IAVF_DOWN,
-                                   msecs_to_jiffies(200));
+                                   msecs_to_jiffies(500));
        if (!status)
                netdev_warn(netdev, "Device resources not yet released\n");
        return 0;