Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jeffrey Tseng <jeffrey.tseng@gigabyte.com>
Subject: Re: [Intel-wired-lan] [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10)
Date: Mon, 17 Oct 2022 12:08:20 -0500	[thread overview]
Message-ID: <20221017170820.GA3712555@bhelgaas> (raw)
In-Reply-To: <bug-216599-41252@https.bugzilla.kernel.org/>

On Mon, Oct 17, 2022 at 11:09:20AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=216599
> 
>             Bug ID: 216599
>            Summary: i210 doesn't work and triggers netdev watchdog (Linux
>                     5.10)

> Created attachment 303021
>   --> https://bugzilla.kernel.org/attachment.cgi?id=303021&action=edit
> 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://git.kernel.org/linus/500b55b05d0a
> 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://git.kernel.org/linus/500b55b05d0a
[2] https://bugzilla.kernel.org/show_bug.cgi?id=216599
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

       reply	other threads:[~2022-10-17 17:08 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 ` Bjorn Helgaas [this message]
2022-10-18  6:59   ` [Intel-wired-lan] [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10) jeffrey.tseng (曾弘)
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=20221017170820.GA3712555@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.tseng@gigabyte.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=netdev@vger.kernel.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