From: Bjorn Helgaas <helgaas@kernel.org>
To: Jeffrey <tzeng015@gmail.com>
Cc: bjorn@helgaas.com, Michael Walle <michael@walle.cc>,
linux-pci@vger.kernel.org
Subject: Re: [Bug 211105] i210 doesn't work and triggers netdev watchdog
Date: Sun, 16 Oct 2022 22:27:46 -0500 [thread overview]
Message-ID: <20221017032746.GA3668382@bhelgaas> (raw)
In-Reply-To: <bug-211105-41252-6XGmOSrDLX@https.bugzilla.kernel.org/>
On Mon, Oct 17, 2022 at 01:30:43AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=211105
>
> --- Comment #3 from jeffreytseng (tzeng015@gmail.com) ---
> 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://lore.kernel.org/linux-pci/20201230185317.30915-1-michael@walle.cc/
> to add the patch in my platform.
>
> The issue and problem is still there. Anyone can give me a hand ?
>
> thank you
>
> jeffrey
The patch actually merged was slightly different than the one you
mentioned. The patch 500b55b05d0a ("PCI: Work around Intel I210 ROM
BAR overlap defect") [1] appeared in v5.17.
The best thing (if possible) would be to use a current kernel, e.g.,
v6.0.
If you can't use a current kernel, backport 500b55b05d0a to your v5.10
kernel and test that.
If you still see the problem, there's likely something more going on
that might be a different issue, so please open a new bugzilla and
attach the complete dmesg log and "sudo lspci -vv" output.
Bjorn
[1] https://git.kernel.org/linus/500b55b05d0a
parent reply other threads:[~2022-10-17 3:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-211105-41252-6XGmOSrDLX@https.bugzilla.kernel.org/>]
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=20221017032746.GA3668382@bhelgaas \
--to=helgaas@kernel.org \
--cc=bjorn@helgaas.com \
--cc=linux-pci@vger.kernel.org \
--cc=michael@walle.cc \
--cc=tzeng015@gmail.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