public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel•com>
To: Ferenc Fejes <fejes@inf•elte.hu>, netdev <netdev@vger•kernel.org>
Cc: "anthony.l.nguyen" <anthony.l.nguyen@intel•com>,
	Jesse Brandeburg <jesse.brandeburg@intel•com>,
	"Neftin, Sasha" <sasha.neftin@intel•com>
Subject: Re: BUG: igc: Unable to select 100 Mbps speed mode
Date: Fri, 01 Dec 2023 15:40:21 -0800	[thread overview]
Message-ID: <87zfytv6e2.fsf@intel.com> (raw)
In-Reply-To: <c40ebbf9c285b87fc64d6f10d2cdc8e07d29b8c6.camel@inf.elte.hu>

Hi,

Ferenc Fejes <fejes@inf•elte.hu> writes:

> Hi!
>
> I upgraded from Ubuntu 23.04 to 23.10, the default Linux version
> changed from 6.2 to 6.5.
>
> We immediately noticed that we cannot set 100 Mbps mode on i225 with
> the new kernel.
>
> E.g.:
> sudo ethtool -s enp4s0 speed 100 duplex full
> dmesg:
> [   60.304330] igc 0000:03:00.0 enp3s0: NIC Link is Down
> [   62.582764] igc 0000:03:00.0 enp3s0: NIC Link is Up 2500 Mbps Full
> Duplex, Flow Control: RX/TX
>

I wonder if this patch fixes it, and it is still not available in your
distro:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e7684d29efdf37304c62bb337ea55b3428ca118e

> I just switched back to 6.2 and with that it works correctly.
>
> Sorry if this has already been addressed, after a quick search in the
> lore I cannot find anything related.
>

I think it was discussed here:

https://lore.kernel.org/all/20230922163804.7DDBA2440449@us122.sjc.aristanetworks.com/

> Best,
> Ferenc
>


Cheers,
-- 
Vinicius

  reply	other threads:[~2023-12-01 23:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 12:59 BUG: igc: Unable to select 100 Mbps speed mode Ferenc Fejes
2023-12-01 23:40 ` Vinicius Costa Gomes [this message]
2023-12-02  9:55   ` Ferenc Fejes

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=87zfytv6e2.fsf@intel.com \
    --to=vinicius.gomes@intel$(echo .)com \
    --cc=anthony.l.nguyen@intel$(echo .)com \
    --cc=fejes@inf$(echo .)elte.hu \
    --cc=jesse.brandeburg@intel$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sasha.neftin@intel$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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