Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "jeffrey.tseng (曾弘)" <jeffrey.tseng@gigabyte.com>
To: Bjorn Helgaas <helgaas@kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: "gary.liu (劉家良)" <gary.liu@gigabyte.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"arthur.chen (陳善康)" <arthur.chen@gigabyte.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"tony.ku (谷瑞麟)" <tony.ku@gigabyte.com>
Subject: Re: [Intel-wired-lan] [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10)
Date: Tue, 18 Oct 2022 06:59:37 +0000	[thread overview]
Message-ID: <ed063410b22b4c14881640ed30539dfd@gigabyte.com> (raw)
In-Reply-To: <20221017170820.GA3712555@bhelgaas>


[-- Attachment #1.1.1: Type: text/plain, Size: 5517 bytes --]

Hi Bjorn , Jesse and Tony



I already updated my status on Bugzilla and the issue is still there.(P1)

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



Platform : imx8mm

Linux version : 5.10



My kernel log :

[    2.764994] pci 0000:01:00.0: BAR 0: assigned [mem 0x18100000-0x1817ffff]

[    2.771801] pci 0000:01:00.0: BAR 3: assigned [mem 0x18180000-0x18183fff]

[    2.778620] pci 0000:01:00.0: BAR 2: assigned [io  0x1000-0x101f]





The log of kernel issue.

  BAR 0: 0x40000000 (32-bit, non-prefetchable) [size=1M]

  BAR 3: 0x40200000 (32-bit, non-prefetchable) [size=16K]

  ROM:   0x40200000 (disabled) [size=1M]



I try to modify the PCIE driver of kernel to Expansion ROM but it seem to show not thing and work not well. (P2)





Dear Jesse and Anthony

Is this a igb driver issue or i210 defective ? If it already fixed, you can give me a suggestion to download the fixed version check it out.

Please kindly give me a hand.



Jeffrey











P1 :

[cid:image001.png@01D8E300.51031010]









P2:

[cid:image002.png@01D8E302.2D0EE420]





Best Regards,

Jeffrey Tseng 曾弘

技嘉科技 GIGABYTE

新北市新店區北新路三段213號11樓

電話: 02-89787668 ext. 556

Mobile : 0952432332

line : 0952432332

E-mail: jeffrey.tseng@gigabyte.com







-----Original Message-----
From: Bjorn Helgaas <helgaas@kernel.org>
Sent: Tuesday, October 18, 2022 1:08 AM
To: Jesse Brandeburg <jesse.brandeburg@intel.com>; Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: jeffrey.tseng (曾弘) <jeffrey.tseng@gigabyte.com>; netdev@vger.kernel.org; linux-pci@vger.kernel.org; intel-wired-lan@lists.osuosl.org; linux-kernel@vger.kernel.org
Subject: Re: [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10)



Caution: This is an external email and has a suspicious subject or content. Please take care when clicking link or opening attachments. When in doubt, contact your MIS Department.







On Mon, Oct 17, 2022 at 11:09:20AM +0000, bugzilla-daemon@kernel.org<mailto:bugzilla-daemon@kernel.org> wrote:

> https://urldefense.com/v3/__https://bugzilla.kernel.org/show_bug.cgi?i<https://urldefense.com/v3/__https:/bugzilla.kernel.org/show_bug.cgi?i>

> d=216599__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2

> VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM6vnLuWnY$

>

>             Bug ID: 216599

>            Summary: i210 doesn't work and triggers netdev watchdog (Linux

>                     5.10)



> Created attachment 303021

>   -->

> https://urldefense.com/v3/__https://bugzilla.kernel.org/attachment.cgi<https://urldefense.com/v3/__https:/bugzilla.kernel.org/attachment.cgi>

> ?id=303021&action=edit__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU

> 2nPJVoN03EYlj2VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM6e138Wjg$

> This is the complete dmesg log and "sudo lspci -vv" output.

>

> Here is my question.

> My platform : imx8mm

> Ethernet Control : Intel I210

> Linux version 5.10.72-lts-5.10.y+g22ec7e8cbace (oe-user@oe-host)

> (aarch64-poky-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2. UTC

> 2011

>

> I follow this

> https://urldefense.com/v3/__https://git.kernel.org/linus/500b55b05d0a_<https://urldefense.com/v3/__https:/git.kernel.org/linus/500b55b05d0a_>

> _;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2VYD6tGeXT

> lmGOoLhpX-vPc9_1P3_LsEz9r7zM65IqfTIk$

> to add the patch in my platform.

>

> The issue and problem is still there. Anyone can give me a hand ?



Note this is an old v5.10 kernel on ARM64.  No indication of whether the problem occurs on a recent kernel.



We had an earlier issue with i210 when the disabled ROM BAR overlapped BAR 3 [1] and the watchdog triggered:



  BAR 0: 0x40000000 (32-bit, non-prefetchable) [size=1M]

  BAR 3: 0x40200000 (32-bit, non-prefetchable) [size=16K]

  ROM:   0x40200000 (disabled) [size=1M]

  ...

  NETDEV WATCHDOG: enP2p1s0 (igb): transmit queue 0 timed out

  Hardware name: Kontron SMARC-sAL28 (Single PHY) on SMARC Eval 2.0 carrier (DT)

  igb 0002:01:00.0 enP2p1s0: Reset adapter



But this case looks different because there is no ROM BAR at all.

From the dmesg attached at [2]:



  pci 0000:01:00.0: BAR 0: assigned [mem 0x18100000-0x1817ffff]

  pci 0000:01:00.0: BAR 3: assigned [mem 0x18180000-0x18183fff]

  pci 0000:01:00.0: BAR 2: assigned [io  0x1000-0x101f]

  ...

  igb 0000:01:00.0: Detected Tx Unit Hang

  NETDEV WATCHDOG: eth1 (igb): transmit queue 1 timed out



I'm assuming this is a driver issue, not a PCI core issue.  But please ping me if you think otherwise.



Bjorn



[1] https://urldefense.com/v3/__https://git.kernel.org/linus/500b55b05d0a__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM65IqfTIk$<https://urldefense.com/v3/__https:/git.kernel.org/linus/500b55b05d0a__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM65IqfTIk$>

[2] https://urldefense.com/v3/__https://bugzilla.kernel.org/show_bug.cgi?id=216599__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM6vnLuWnY$<https://urldefense.com/v3/__https:/bugzilla.kernel.org/show_bug.cgi?id=216599__;!!DaQGe0nW977OPw!nRfCuRVCLM4YW4T8lrmKHPy7gHiU2nPJVoN03EYlj2VYD6tGeXTlmGOoLhpX-vPc9_1P3_LsEz9r7zM6vnLuWnY$>

[-- Attachment #1.1.2: Type: text/html, Size: 17601 bytes --]

[-- Attachment #1.2: image001.png --]
[-- Type: image/png, Size: 99488 bytes --]

[-- Attachment #1.3: image002.png --]
[-- Type: image/png, Size: 230333 bytes --]

[-- Attachment #2: Type: text/plain, Size: 162 bytes --]

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  reply	other threads:[~2022-10-19 14:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-216599-41252@https.bugzilla.kernel.org/>
2022-10-17 17:08 ` [Intel-wired-lan] [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10) Bjorn Helgaas
2022-10-18  6:59   ` jeffrey.tseng (曾弘) [this message]
2022-10-18  9:05   ` jeffrey.tseng (曾弘)

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=ed063410b22b4c14881640ed30539dfd@gigabyte.com \
    --to=jeffrey.tseng@gigabyte.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arthur.chen@gigabyte.com \
    --cc=gary.liu@gigabyte.com \
    --cc=helgaas@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tony.ku@gigabyte.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