linux-kernel - Re: [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20221017170820.GA3712555@bhelgaas>
Date:   Mon, 17 Oct 2022 12:08:20 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     Jesse Brandeburg <jesse.brandeburg@...el.com>,
        Tony Nguyen <anthony.l.nguyen@...el.com>
Cc:     Jeffrey Tseng <jeffrey.tseng@...abyte.com>, netdev@...r.kernel.org,
        linux-pci@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
        linux-kernel@...r.kernel.org
Subject: Re: [Bug 216599] New: i210 doesn't work and triggers netdev watchdog
 (Linux 5.10)

On Mon, Oct 17, 2022 at 11:09:20AM +0000, bugzilla-daemon@...nel.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@...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