From: Ben Greear <greearb@candelatech.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] 5.10.0 kernel regression for 2.5Gbps link negotiation?
Date: Fri, 18 Dec 2020 11:41:48 -0800 [thread overview]
Message-ID: <638c7cb6-9aaa-1365-a99a-9551c9d985b5@candelatech.com> (raw)
In-Reply-To: <BYAPR11MB3606E48BA821185142354D67EFC30@BYAPR11MB3606.namprd11.prod.outlook.com>
That is going to be a bit painful to implement.
Any chance we can get a compile time option to enable 2.5 and 5Ghz by default,
with user option to disable those rates in case they find problems?
Thanks,
Ben
On 12/18/20 11:27 AM, Fujinaka, Todd wrote:
> Yes, and I'm plugging the hole in the README right now. Here's the proposed text:
>
> Advertisements for 2.5G and 5G on the x550 were turned off by default due to
> interoperability issues with certain switches. To turn them back on, use
>
> ethtool -s <ethX> advertise N
>
> where N is a combination of the following.
>
> 100baseTFull 0x008
> 1000baseTFull 0x020
> 2500baseTFull 0x800000000000
> 5000baseTFull 0x1000000000000
> 10000baseTFull 0x1000
>
> For example, to turn on all modes:
> ethtool -s <ethX> advertise 0x1800000001028
>
> For more details please see the ethtool man page.
>
> Todd Fujinaka
> Software Application Engineer
> Data Center Group
> Intel Corporation
> todd.fujinaka at intel.com
>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of Ben Greear
> Sent: Friday, December 18, 2020 10:08 AM
> To: intel-wired-lan <intel-wired-lan@lists.osuosl.org>
> Subject: [Intel-wired-lan] 5.10.0 kernel regression for 2.5Gbps link negotiation?
>
> Hello,
>
> One of our users reports that our 5.10 kernel negotiates the 1/2.5/5/10g NIC to 1Gbps instead of 2.5Gbps. Booting the 5.4 kernel shows 2.5Gbps as expected.
>
> I have not yet tried to bisect this...is it a known issue?
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb@candelatech.com>
> Candela Technologies Inc http://www.candelatech.com _______________________________________________
> Intel-wired-lan mailing list
> Intel-wired-lan at osuosl.org
> https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2020-12-18 19:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 18:08 [Intel-wired-lan] 5.10.0 kernel regression for 2.5Gbps link negotiation? Ben Greear
2020-12-18 19:27 ` Fujinaka, Todd
2020-12-18 19:41 ` Ben Greear [this message]
2020-12-18 19:43 ` Paul Menzel
2020-12-18 23:07 ` Ben Greear
2020-12-18 23:19 ` Paul Menzel
2020-12-19 0:09 ` Fujinaka, Todd
2020-12-19 0:47 ` Ben Greear
2020-12-19 16:19 ` Fujinaka, Todd
2020-12-19 16:48 ` Ben Greear
2020-12-21 15:20 ` Fujinaka, Todd
2020-12-21 15:52 ` Ben Greear
2020-12-21 15:58 ` Fujinaka, Todd
2020-12-21 16:04 ` Ben Greear
2020-12-22 8:59 ` Greg KH
2020-12-21 15:09 ` [Intel-wired-lan] ixgbe: " Paul Menzel
2020-12-21 15:16 ` Fujinaka, Todd
2020-12-21 15:31 ` Hisashi T Fujinaka
2020-12-19 7:54 ` Paul Menzel
2020-12-19 16:07 ` Fujinaka, Todd
2020-12-19 20:59 ` Linus Torvalds
2020-12-21 15:12 ` Fujinaka, Todd
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=638c7cb6-9aaa-1365-a99a-9551c9d985b5@candelatech.com \
--to=greearb@candelatech.com \
--cc=intel-wired-lan@osuosl.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