summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorEilon Greenstein <eilong@broadcom.com>2008-11-03 16:45:55 -0800
committerDavid S. Miller <davem@davemloft.net>2008-11-03 16:45:55 -0800
commit9a0354405feb0f8bd460349a93db05e4cca8d166 (patch)
tree497d96cc2f7c8c9e0d6b0d6bdc65a79c4200bcab
parentee04448d8871e71f55520d62cf6adbf5dd403c99 (diff)
downloadop-kernel-dev-9a0354405feb0f8bd460349a93db05e4cca8d166.zip
op-kernel-dev-9a0354405feb0f8bd460349a93db05e4cca8d166.tar.gz
bnx2x: Removing the PMF indication when unloading
When the PMF flag is set, the driver can access the HW freely. When the driver is unloaded, it should not access the HW. The problem caused fatal errors when "ethtool -i" was called after the calling instance was unloaded and another instance was already loaded Signed-off-by: Eilon Greenstein <eilong@broadcom.com> Signed-off-by: David S. Miller <davem@davemloft.net>
-rw-r--r--drivers/net/bnx2x_main.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/net/bnx2x_main.c b/drivers/net/bnx2x_main.c
index fce7451..61152e1 100644
--- a/drivers/net/bnx2x_main.c
+++ b/drivers/net/bnx2x_main.c
@@ -6481,6 +6481,7 @@ load_int_disable:
bnx2x_free_irq(bp);
load_error:
bnx2x_free_mem(bp);
+ bp->port.pmf = 0;
/* TBD we really need to reset the chip
if we want to recover from this */
@@ -6791,6 +6792,7 @@ unload_error:
/* Report UNLOAD_DONE to MCP */
if (!BP_NOMCP(bp))
bnx2x_fw_command(bp, DRV_MSG_CODE_UNLOAD_DONE);
+ bp->port.pmf = 0;
/* Free SKBs, SGEs, TPA pool and driver internals */
bnx2x_free_skbs(bp);
OpenPOWER on IntegriCloud