summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBen Hutchings <bhutchings@solarflare.com>2012-07-27 20:48:36 +0100
committerBen Hutchings <bhutchings@solarflare.com>2012-08-24 20:10:21 +0100
commitb812f8b7a9b657367eaacab8c34e6711a657a48b (patch)
tree6d3da71309bb03e02b957a0416fa861c166e954c
parent8b7325b4e29256881117aff8a162e829c79b47e9 (diff)
downloadop-kernel-dev-b812f8b7a9b657367eaacab8c34e6711a657a48b.zip
op-kernel-dev-b812f8b7a9b657367eaacab8c34e6711a657a48b.tar.gz
sfc: Improve log messages in case we abort probe due to a pending reset
The current informational message doesn't properly explain what happens, and could also appear if we defer a reset during suspend/resume. Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
-rw-r--r--drivers/net/ethernet/sfc/efx.c7
1 files changed, 3 insertions, 4 deletions
diff --git a/drivers/net/ethernet/sfc/efx.c b/drivers/net/ethernet/sfc/efx.c
index 977fc3a..5555e9f 100644
--- a/drivers/net/ethernet/sfc/efx.c
+++ b/drivers/net/ethernet/sfc/efx.c
@@ -2311,11 +2311,8 @@ static void efx_reset_work(struct work_struct *data)
/* If we're not READY then don't reset. Leave the reset_pending
* flags set so that efx_pci_probe_main will be retried */
- if (efx->state != STATE_READY) {
- netif_info(efx, drv, efx->net_dev,
- "scheduled reset quenched; NIC not ready\n");
+ if (efx->state != STATE_READY)
return;
- }
rtnl_lock();
(void)efx_reset(efx, fls(pending) - 1);
@@ -2703,6 +2700,8 @@ static int __devinit efx_pci_probe(struct pci_dev *pci_dev,
* probably hosed anyway.
*/
if (efx->reset_pending) {
+ netif_err(efx, probe, efx->net_dev,
+ "aborting probe due to scheduled reset\n");
rc = -EIO;
goto fail4;
}
OpenPOWER on IntegriCloud