From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, gospo@redhat.com,
Don Skidmore <donald.c.skidmore@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: [net-2.6 PATCH 3/4] ixgbe: fix inconsistent SFP/SFP+ failure results.
Date: Thu, 02 Jul 2009 15:50:52 -0700 [thread overview]
Message-ID: <20090702225051.22746.79159.stgit@localhost.localdomain> (raw)
In-Reply-To: <20090702225012.22746.57218.stgit@localhost.localdomain>
From: Don Skidmore <donald.c.skidmore@intel.com>
Currently if we loaded the driver, insert an unsupported module, and then
attempt to "ifconfig up" the device it will be brought down but the netdev
would not be unregistered. This behavior is different than all other
code paths. This patch corrects that by down'ing the device and then
scheduling the sfp_config_module_task tasklet. The tasklet will detect
this condition (like it does with other code paths) and do the
unregister_netdev().
I also removed the log message as this condition (an unsupported SFP+
module) will be logged in sfp_config_module_task.
Signed-off-by: Don Skidmore <donald.c.skidmore@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
---
drivers/net/ixgbe/ixgbe_main.c | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ixgbe/ixgbe_main.c b/drivers/net/ixgbe/ixgbe_main.c
index cf39f5a..a3061aa 100644
--- a/drivers/net/ixgbe/ixgbe_main.c
+++ b/drivers/net/ixgbe/ixgbe_main.c
@@ -2706,12 +2706,12 @@ static int ixgbe_up_complete(struct ixgbe_adapter *adapter)
if (hw->phy.type == ixgbe_phy_unknown) {
err = hw->phy.ops.identify(hw);
if (err == IXGBE_ERR_SFP_NOT_SUPPORTED) {
- dev_err(&adapter->pdev->dev, "failed to initialize "
- "because an unsupported SFP+ module type "
- "was detected.\n"
- "Reload the driver after installing a "
- "supported module.\n");
+ /*
+ * Take the device down and schedule the sfp tasklet
+ * which will unregister_netdev and log it.
+ */
ixgbe_down(adapter);
+ schedule_work(&adapter->sfp_config_module_task);
return err;
}
}
next prev parent reply other threads:[~2009-07-02 22:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 22:50 [net-2.6 PATCH 1/4] ixgbe: fix issues with failing to detect insert of unsupported module Jeff Kirsher
2009-07-02 22:50 ` [net-2.6 PATCH 2/4] ixgbe: fix regression on some 82598 adapters Jeff Kirsher
2009-07-04 2:12 ` David Miller
2009-07-02 22:50 ` Jeff Kirsher [this message]
2009-07-04 2:12 ` [net-2.6 PATCH 3/4] ixgbe: fix inconsistent SFP/SFP+ failure results David Miller
2009-07-02 22:51 ` [net-2.6 PATCH 4/4] ixgbe: Not allow 8259x unsupported wol options change from ethtool Jeff Kirsher
2009-07-04 2:12 ` David Miller
2009-07-04 2:12 ` [net-2.6 PATCH 1/4] ixgbe: fix issues with failing to detect insert of unsupported module David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090702225051.22746.79159.stgit@localhost.localdomain \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox