From: Greg KH <gregkh@linuxfoundation.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] 5.10.0 kernel regression for 2.5Gbps link negotiation?
Date: Tue, 22 Dec 2020 09:59:05 +0100 [thread overview]
Message-ID: <X+G1WVz0qorjegSa@kroah.com> (raw)
In-Reply-To: <1d9e12e5-56a5-7921-e4b6-b67bcc180942@candelatech.com>
On Mon, Dec 21, 2020 at 07:52:54AM -0800, Ben Greear wrote:
> On 12/21/20 7:20 AM, Fujinaka, Todd wrote:
> > Nope. The timing of the PHYs means the switch times out while we're trying 2.5G and 5G and the switch goes to its default lowest speed of 1G. Then we go to 1G and by that time bonding is broken in several of the cases we ran into.
> >
> > Basically, we can have that switch work, or we can have 2.5G and 5G on by default. Not both. And since we're selling a 10G device with other speeds as a bonus, we're prioritizing the highest speed. That plus the very high profile customers who wanted this solution.
> >
> > The solution for one camp or the other is to use the ethtool command at boot (I've forgotten exactly what that was) but the high profile customers refused to do that. Sounds like you're refusing as well?
>
> I'm not refusing, I just would rather patch my kernels than use ethtool, that way my older user-space
> would work fine on newer kernels.
>
> Would you accept a patch that makes this a module option, defaulted to disable 2.5/5, but which
> a user could enabled to enable 2.5/5 by default?
Module options are not ok, this is not the 1990's. Please use the
proper configuration methods instead that can work on a per-device
basis.
thanks,
greg k-h
next prev parent reply other threads:[~2020-12-22 8:59 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
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 [this message]
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=X+G1WVz0qorjegSa@kroah.com \
--to=gregkh@linuxfoundation.org \
--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