Hi Jesse and Tony
I also download the driver which is provide from Intel.
From the README , I find out this one.
I also modified source code of igb_main.c and make sure it is MSI interrupt because of above description.
It can’t work well.
Jeffrey
Best Regards,
Jeffrey Tseng
曾弘
技嘉科技 GIGABYTE
新北市新店區北新路三段213號11樓
電話: 02-89787668 ext. 556
Mobile : 0952432332
line : 0952432332
E-mail: jeffrey.tseng@gigabyte.com
From: jeffrey.tseng (曾弘)
Sent: Tuesday, October 18, 2022 3:01 PM
To: 'Bjorn Helgaas' <helgaas@kernel.org>; Jesse Brandeburg <jesse.brandeburg@intel.com>; Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: netdev@vger.kernel.org; linux-pci@vger.kernel.org; intel-wired-lan@lists.osuosl.org; linux-kernel@vger.kernel.org; gary.liu (劉家良) <gary.liu@gigabyte.com>;
arthur.chen (陳善康) <arthur.chen@gigabyte.com>; tony.ku (谷瑞麟)
<tony.ku@gigabyte.com>
Subject: RE: [Bug 216599] New: i210 doesn't work and triggers netdev watchdog (Linux 5.10)
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 :
P2:
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 wrote:
>
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
> ?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_
> _;!!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