Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 10:08:18 -0800	[thread overview]
Message-ID: <7bb485c3-9556-d9f1-e70f-a4b3a05909c9@candelatech.com> (raw)

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

             reply	other threads:[~2020-12-18 18:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 18:08 Ben Greear [this message]
2020-12-18 19:27 ` [Intel-wired-lan] 5.10.0 kernel regression for 2.5Gbps link negotiation? Fujinaka, Todd
2020-12-18 19:41   ` Ben Greear
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=7bb485c3-9556-d9f1-e70f-a4b3a05909c9@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