Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: jesse.brandeburg@intel.com, anthony.l.nguyen@intel.com
Cc: intel-wired-lan@lists.osuosl.org
Subject: [Intel-wired-lan] Fw: [Bug 216261] New: Ethernet adapter i225_LM probe fail, return -1
Date: Tue, 19 Jul 2022 18:48:08 -0700	[thread overview]
Message-ID: <20220719184808.7ba1d6e1@hermes.local> (raw)



Begin forwarded message:

Date: Wed, 20 Jul 2022 01:19:08 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 216261] New: Ethernet adapter i225_LM probe fail, return -1


https://bugzilla.kernel.org/show_bug.cgi?id=216261

            Bug ID: 216261
           Summary: Ethernet adapter i225_LM probe fail, return -1
           Product: Networking
           Version: 2.5
    Kernel Version: 5.4.y
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: IPV4
          Assignee: stephen@networkplumber.org
          Reporter: joseph.bao@intel.com
        Regression: No

Created attachment 301461
  --> https://bugzilla.kernel.org/attachment.cgi?id=301461&action=edit  
This patch is based on 5.4.206, fix the i225 probe issue caused by unnecessary
point check.

Running kernel 5.4 with intel CPU alderlake-s and Ethernet adapter i225-LM,
encounter probe failure, return err code -2. 

The root cause is that i225 devices have only one PHY vendor. There is no point
checking _I_PHY_ID during the link establishment and auto-negotiation process.

Refer to the link below.   

https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git/commit/drivers/net/ethernet/intel/igc?h=dev-queue&id=7c496de538eebd8212dc2a3c9a468386b264d0d4

Attach the patch to clean up these pointless checkings.

I tried another branch 5.15.y, it fixes this issue but has another issue
related to PCIe switch & nvme SSD, so I have to stay kernel 5.4.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

                 reply	other threads:[~2022-07-20  1:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220719184808.7ba1d6e1@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.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