From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: "Skyler Mäntysaari" <sm+lists@skym.fi>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] The difference between linux kernel driver and FreeBSD's with Intel X533
Date: Mon, 9 Oct 2023 08:33:23 -0700 [thread overview]
Message-ID: <6e48c3ba-8d17-41db-ca8d-0a7881d122c9@intel.com> (raw)
In-Reply-To: <c526d946-2779-434b-b8ec-423a48f71e36@skym.fi>
On 10/4/2023 10:08 AM, Skyler Mäntysaari wrote:
>>> Hi there,
>>>
>>> It seems that for reasons unknown to me, my Intel X533 based 10G SFP+
>>> doesn't want to work with kernel 6.1.55 in VyOS 1.4 nor Debian 12 but
>>> it does in OPNsense which is based on FreeBSD 13.2.
>>>
>>> How would I go about debugging this properly? Both sides see light,
>>> but no link unless I'm using FreeBSD.
> https://forum.vyos.io/t/10g-sfp-trouble-with-linking-intel-x553/12253/11?u=samip537
Hi Skyler,
Response from Intel team:
In the ethtool -m output pasted I see TX and RX optical power is fine.
Could you request fault status on both sides? Just want to check if link
is down because we are at local-fault or link partner is at local-fault.
rmmod ixgbe
modprobe ixgbe
ethtool -S eth0 | grep fault
Since it is 10G, if our side TX is ON (power level says it is) then we
should expect link partner RX to be locked so cannot be at Local Fault.
Skyler, please gather that ethtool -S data for us.
Jesse
next prev parent reply other threads:[~2023-10-09 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 23:25 The difference between linux kernel driver and FreeBSD's with Intel X533 Skyler Mäntysaari
2023-10-04 16:42 ` Jesse Brandeburg
[not found] ` <c526d946-2779-434b-b8ec-423a48f71e36@skym.fi>
2023-10-09 15:33 ` Jesse Brandeburg [this message]
2023-10-09 23:50 ` [Intel-wired-lan] " Skyler Mäntysaari
2023-10-10 0:39 ` Skyler Mäntysaari
2023-10-18 18:50 ` Skyler Mäntysaari
2023-11-28 2:20 ` Ivan Pang
2023-11-28 13:58 ` Skyler Mäntysaari
2023-11-28 14:01 ` Skyler Mäntysaari
2023-11-28 21:34 ` Paul Menzel
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=6e48c3ba-8d17-41db-ca8d-0a7881d122c9@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.org \
--cc=sm+lists@skym.fi \
/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).