iwlwifi: mvm: avoid dumping assert log when device is stopped
authorSara Sharon <sara.sharon@intel.com>
Mon, 20 Nov 2017 16:02:05 +0000 (18:02 +0200)
committerLuca Coelho <luciano.coelho@intel.com>
Tue, 5 Dec 2017 19:01:40 +0000 (21:01 +0200)
We might erroneously get to error dumping code when the
device is already stopped.

In that case the driver will detect a defective value and will try to
reset the HW, assuming it is only a bus issue.  The driver than
proceeds with the dumping.

The result has two side effects:

1. The device won't be stopped again, since the transport status is
already stopped, so the device remains powered on while it actually
should be stopped.

2. The dump in that case is completely garbaged and useless.

Detect and avoid this.  It will also make debugging such issues
easier.

Signed-off-by: Sara Sharon <sara.sharon@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
drivers/net/wireless/intel/iwlwifi/mvm/utils.c

index d46115e2d69e1d6de1fcc3126e3f1af8a59da99c..79acb13f203aae97c95ffb96d6e865501661398d 100644 (file)
@@ -595,6 +595,12 @@ static void iwl_mvm_dump_lmac_error_log(struct iwl_mvm *mvm, u32 base)
 
 void iwl_mvm_dump_nic_error_log(struct iwl_mvm *mvm)
 {
+       if (!test_bit(STATUS_DEVICE_ENABLED, &mvm->trans->status)) {
+               IWL_ERR(mvm,
+                       "DEVICE_ENABLED bit is not set. Aborting dump.\n");
+               return;
+       }
+
        iwl_mvm_dump_lmac_error_log(mvm, mvm->error_event_table[0]);
 
        if (mvm->error_event_table[1])