netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Stefan Dimitrov <stefan.k.dimitrov@gmail.com>
Cc: <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: igb driver: i210 (8086:1533) very bad SNR performance
Date: Wed, 23 Oct 2024 15:38:11 +0200	[thread overview]
Message-ID: <66d96956-e393-41e6-952a-3f23ebcd3a79@intel.com> (raw)
In-Reply-To: <CAE8EbV3aruDHKrBezSLg_hy0XZG2Dr1pkzvXVVTj0QpNpH86nw@mail.gmail.com>

On 10/19/24 14:39, Stefan Dimitrov wrote:
> Hello All,
> 
> I am reporting the problem only, because the exact same
> environment/setup is working perfectly in Win7 with Intel driver
> version 12.13.27.0 from 7/8/2019 (I guess that is the latest driver
> version for Win7 as it is not supported for years, but it's the only
> Windows version I had during my tests).
> 
> So, in very short: the same 20-25m of UTP cable, works perfectly in
> Win7 and not at all in Linux with i210/igb driver and my best guess is
> PHY initialization in the Linux driver compared to the one in Win7
> drivers somehow reduces dramatically the Signal-to-Noise performance.



> P.S. it seems i217 (8086:153a and 8086:153b) is also affected, at
> least based on my very short and not extensive tests I did today.
> 
> thanks,
> stefan
> 

Thank your for the report, I will dispatch it within Intel, we will
communicate the progress here.

It will be beneficial for us to know the firmware version used both
on Linux and Windows setups.

For future reports, consider also CCing the IWL mailing list to get
faster responses.

Best Regards,
Przemek

  reply	other threads:[~2024-10-23 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 12:39 igb driver: i210 (8086:1533) very bad SNR performance Stefan Dimitrov
2024-10-23 13:38 ` Przemek Kitszel [this message]
2024-10-23 15:21   ` Stefan Dimitrov

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=66d96956-e393-41e6-952a-3f23ebcd3a79@intel.com \
    --to=przemyslaw.kitszel@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=netdev@vger.kernel.org \
    --cc=stefan.k.dimitrov@gmail.com \
    /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).