From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Stefan Behte <s.behte@babiel.com>
Cc: netdev@vger.kernel.org, "Skidmore,
Donald C" <donald.c.skidmore@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Tantilov, Emil S" <emil.s.tantilov@intel.com>,
"Keller, Jacob E" <jacob.e.keller@intel.com>
Subject: Re: ixgbe: Regression, unsupported SFP+ modules on 10Gbit/s X520 NIC no longer work with allow_unsupported_sfp=1
Date: Thu, 14 Feb 2013 16:28:56 -0800 [thread overview]
Message-ID: <1360888136.26020.4.camel@jtkirshe-mobl> (raw)
In-Reply-To: <D76AF9B3DDF5FF49833AC0A1396549060333A1C5@s554.babiel.com>
[-- Attachment #1: Type: text/plain, Size: 6115 bytes --]
On Fri, 2013-02-15 at 01:10 +0100, Stefan Behte wrote:
> Hello,
>
> I was told to send a mail, even though I had already opened
> https://bugzilla.kernel.org/show_bug.cgi?id=53901.
>
> Someone patched the ixgbe driver, and now non-intel SFPs do not work
> anymore, again. The issue of intel "lock-in" was discussed before
> here:
> http://marc.info/?l=e1000-devel&m=132697406314730&w=2
>
> A tested patch is attached.
>
> Here is what I do:
>
> # modinfo ixgbe | grep parm
> parm: max_vfs:Maximum number of virtual functions to
> allocate per physical function - default is zero and maximum value is
> 63 (uint)
> parm: allow_unsupported_sfp:Allow unsupported and untested
> SFP+ modules on 82599-based adapters (uint)
> parm: debug:Debug level (0=none,...,16=all) (int)
>
> # modprobe -r ixgbe
> # modprobe ixgbe allow_unsupported_sfp=0
> # dmesg | grep ixgbe
> [13690.355090] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version 3.9.15-k
> [13690.355092] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
> [13690.373128] ixgbe 0000:02:00.0: failed to load because an
> unsupported SFP+ module type was detected.
> [13690.373177] ixgbe 0000:02:00.0: Reload the driver after installing
> a supported module.
> [13690.390987] ixgbe 0000:02:00.1: failed to load because an
> unsupported SFP+ module type was detected.
> [13690.391036] ixgbe 0000:02:00.1: Reload the driver after installing
> a supported module.
>
> # modprobe -r ixgbe
> # modprobe ixgbe allow_unsupported_sfp=1
> # dmesg | grep ixgbe
> [13679.088849] dca service started, version 1.12.1
> [13679.091174] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version 3.9.15-k
> [13679.091177] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
> [13679.109194] ixgbe 0000:02:00.0: failed to load because an
> unsupported SFP+ module type was detected.
> [13679.109243] ixgbe 0000:02:00.0: Reload the driver after installing
> a supported module.
> [13679.127399] ixgbe 0000:02:00.1: failed to load because an
> unsupported SFP+ module type was detected.
> [13679.127450] ixgbe 0000:02:00.1: Reload the driver after installing
> a supported module.
> [13690.352712] dca service started, version 1.12.1
>
>
> With the patch:
>
> # modprobe -r ixgbe
> # modprobe ixgbe allow_unsupported_sfp=0
> # dmesg | grep ixgbe
> [13907.870087] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version 3.9.15-k
> [13907.870089] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
> [13907.888106] ixgbe 0000:02:00.0: failed to load because an
> unsupported SFP+ module type was detected.
> [13907.888155] ixgbe 0000:02:00.0: Reload the driver after installing
> a supported module.
> [13907.906187] ixgbe 0000:02:00.1: failed to load because an
> unsupported SFP+ module type was detected.
> [13907.906237] ixgbe 0000:02:00.1: Reload the driver after installing
> a supported module.
>
>
> # modprobe -r ixgbe
> # modprobe ixgbe allow_unsupported_sfp=1
> # dmesg | grep ixgbe
> [13914.534758] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver -
> version3.9.15-k
> [13914.534761] ixgbe: Copyright (c) 1999-2012 Intel Corporation.
> [13914.552820] ixgbe 0000:02:00.0 (unregistered net_device): WARNING:
> Intel (R) Network Connections are quality tested using Intel (R)
> Ethernet Optics. Using untested modules is not supported and may
> cause unstable operation or damage to
> the module or the adapter. Intel Corporation is not responsible for
> any harm caused by using untested modules.
> [13917.741931] ixgbe 0000:02:00.0: irq 50 for MSI/MSI-X
> [13917.741938] ixgbe 0000:02:00.0: irq 51 for MSI/MSI-X
> [13917.741942] ixgbe 0000:02:00.0: irq 52 for MSI/MSI-X
> [13917.741951] ixgbe 0000:02:00.0: irq 53 for MSI/MSI-X
> [13917.741955] ixgbe 0000:02:00.0: irq 54 for MSI/MSI-X
> [13917.741960] ixgbe 0000:02:00.0: irq 55 for MSI/MSI-X
> [13917.741965] ixgbe 0000:02:00.0: irq 56 for MSI/MSI-X
> [13917.741969] ixgbe 0000:02:00.0: irq 57 for MSI/MSI-X
> [13917.741973] ixgbe 0000:02:00.0: irq 58 for MSI/MSI-X
> [13917.742002] ixgbe 0000:02:00.0: Multiqueue Enabled: Rx Queue count
> = 8, Tx Queue count = 8
> [13917.742126] ixgbe 0000:02:00.0: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:37:3b:18
> [13917.742207] ixgbe 0000:02:00.0: MAC: 2, PHY: 14, SFP+: 65535, PBA
> No: E68793-005
> [13917.743461] ixgbe 0000:02:00.0: Intel(R) 10 Gigabit Network
> Connection
> [13917.761578] ixgbe 0000:02:00.1 (unregistered net_device): WARNING:
> Intel (R) Network Connections are quality tested using Intel (R)
> Ethernet Optics. Using untested modules is not supported and may
> cause unstable operation or damage to the module or the adapter.
> Intel Corporation is not responsible for any harm caused by using
> untested modules.
> [13920.948726] ixgbe 0000:02:00.1: irq 59 for MSI/MSI-X
> [13920.948737] ixgbe 0000:02:00.1: irq 60 for MSI/MSI-X
> [13920.948742] ixgbe 0000:02:00.1: irq 61 for MSI/MSI-X
> [13920.948746] ixgbe 0000:02:00.1: irq 62 for MSI/MSI-X
> [13920.948751] ixgbe 0000:02:00.1: irq 63 for MSI/MSI-X
> [13920.948757] ixgbe 0000:02:00.1: irq 64 for MSI/MSI-X
> [13920.948761] ixgbe 0000:02:00.1: irq 65 for MSI/MSI-X
> [13920.948767] ixgbe 0000:02:00.1: irq 66 for MSI/MSI-X
> [13920.948774] ixgbe 0000:02:00.1: irq 67 for MSI/MSI-X
> [13920.948803] ixgbe 0000:02:00.1: Multiqueue Enabled: Rx Queue count
> = 8, Tx Queue count = 8
> [13920.948927] ixgbe 0000:02:00.1: (PCI Express:5.0GT/s:Width x8)
> 90:e2:ba:37:3b:19
> [13920.949008] ixgbe 0000:02:00.1: MAC: 2, PHY: 14, SFP+: 65535, PBA
> No: E68793-005
> [13920.950237] ixgbe 0000:02:00.1: Intel(R) 10 Gigabit Network
> Connection
>
> And then I get two nice Interfaces. Please apply. :)
>
>
> Best regards,
>
> Stefan Behte
>
> Babiel GmbH
> Moskauer Strasse 27
> D-40227 Düsseldorf
>
> Tel: 0211-179349 0
> Fax: 0211-179349 29
> E-Mail: S.Behte@babiel.com
> Internet: http://www.babiel.com
>
Thanks Stefan, I will make sure that we take a look at the bugzilla.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next parent reply other threads:[~2013-02-15 0:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D76AF9B3DDF5FF49833AC0A1396549060333A1C5@s554.babiel.com>
2013-02-15 0:28 ` Jeff Kirsher [this message]
2013-02-15 0:58 ixgbe: Regression, unsupported SFP+ modules on 10Gbit/s X520 NIC no longer work with allow_unsupported_sfp=1 Stefan Behte
2013-02-15 20:14 ` Tantilov, Emil S
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=1360888136.26020.4.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=emil.s.tantilov@intel.com \
--cc=jacob.e.keller@intel.com \
--cc=netdev@vger.kernel.org \
--cc=s.behte@babiel.com \
/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;
as well as URLs for NNTP newsgroup(s).