From: "Oliver O'Halloran" <oohall@gmail.com>
To: fk1xdcio@duck.com
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: ASMedia ASM1812 PCIe switch causes system to freeze hard
Date: Mon, 27 Feb 2023 19:12:14 +1100 [thread overview]
Message-ID: <CAOSf1CGoAVrzb7nrMgZ6tZP-Akx7DvGD5RBu9KjprP5r2DtQiA@mail.gmail.com> (raw)
In-Reply-To: <756173E3-354E-4AC4-89D7-9096B62E344C.1@smtp-inbound1.duck.com>
On Sun, Feb 26, 2023 at 6:20 AM <fk1xdcio@duck.com> wrote:
>
> On 2023-02-25 13:28, Chris wrote:
> > I'm testing a generic 4-port PCIe x4 2.5Gbps Ethernet NIC. It uses an
> > ASM1812 for the PCI packet switch to four RTL8125BG network
> > controllers.
>
> Sorry, I forget my attachment with the PCI device information.
Looks like your mail client is breaking threads.
Anyway, the only thing of interest I can see in the log is that AER is
reporting correctable errors on three of your four NICs:
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125
2.5GbE Controller (rev 05)
Capabilities: [100 v2] Advanced Error Reporting
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125
2.5GbE Controller (rev 05)
Capabilities: [100 v2] Advanced Error Reporting
CESta: RxErr+ BadTLP- BadDLLP+ Rollover- Timeout+ AdvNonFatalErr-
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125
2.5GbE Controller (rev 05)
Capabilities: [100 v2] Advanced Error Reporting
CESta: RxErr+ BadTLP- BadDLLP+ Rollover- Timeout+ AdvNonFatalErr-
0a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125
2.5GbE Controller (rev 05)
Capabilities: [100 v2] Advanced Error Reporting
CESta: RxErr+ BadTLP- BadDLLP+ Rollover- Timeout+ AdvNonFatalErr-
Bad Data Link Layer Packet errors suggest that specific card has
signal integrity issues. Assuming that's true, more traffic to the NIC
means more opportunities for uncorrectable errors which would explain
the hard lockups. I'm not sure why setting pci=nommconf seems to fix
the problem, but my guess it's just masking the issue. The AER
capability is in the extended config space which requires the memory
mapped config space to access so disabling that probably just stops
the kernel from noticing that errors are occuring. The network stack
is pretty forgiving of errors since it can just drop packets which
might also explain the lower throughput too.
next prev parent reply other threads:[~2023-02-27 8:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e7978f65c6606fb2d48483435c78bd3@cutk.com>
2023-02-25 18:47 ` ASMedia ASM1812 PCIe switch causes system to freeze hard fk1xdcio
2023-02-27 8:12 ` Oliver O'Halloran [this message]
[not found] ` <9C53F704-1C13-4191-8890-20B18A23E94B.1@smtp-inbound1.duck.com>
2023-02-27 9:17 ` fk1xdcio
2023-02-25 18:37 fk1xdcio
2023-02-25 21:02 ` Lukas Wunner
[not found] ` <FC4B5703-B454-4BEB-9E9C-6841FBD2CD60.1@smtp-inbound1.duck.com>
2023-02-25 21:58 ` fk1xdcio
2023-03-08 20:49 ` Bjorn Helgaas
2023-03-13 21:57 ` Bjorn Helgaas
[not found] ` <1BD0E6B9-0611-4879-BA26-DDA87E772512.1@smtp-inbound1.duck.com>
2023-03-14 8:28 ` fk1xdcio
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=CAOSf1CGoAVrzb7nrMgZ6tZP-Akx7DvGD5RBu9KjprP5r2DtQiA@mail.gmail.com \
--to=oohall@gmail.com \
--cc=fk1xdcio@duck.com \
--cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).