All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
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: Sat, 25 Feb 2023 22:02:20 +0100	[thread overview]
Message-ID: <20230225210220.GA17261@wunner.de> (raw)
In-Reply-To: <9B577F97-4E03-4D1D-B6F2-909897F938CC.1@smtp-inbound1.duck.com>

On Sat, Feb 25, 2023 at 01:37:23PM -0500, fk1xdcio@duck.com 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.
> 
> The more load I put on the NIC the faster the system freezes. For example if
> I activate four 2.5Gbps fully saturated network connections then the system
> hard freezes almost immediately. When the system freezes it seems completely
> dead. SysRq doesn't work, serial consoles are dead, etc. so I haven't been
> able to get much debugging information. I have tested on various different
> physical systems, Xeon E5, Xeon E3, i7, and they all behave the same so it
> doesn't seem like a system hardware issue.
> 
> Disabling IOMMU makes it run for a little longer before crashing.
> 
> The tiny bit of error information I have been able to get under various
> conditions (eg. disabling ASPM, forcing D0, etc):
>   Test #1:
>   pcieport 0000:04:02.0: Unable to change power state from D3hot to D0,
> device inaccessible

Have you tried adding pcie_port_pm=off to the kernel command line?

Thanks,

Lukas

  reply	other threads:[~2023-02-25 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 18:37 ASMedia ASM1812 PCIe switch causes system to freeze hard fk1xdcio
2023-02-25 21:02 ` Lukas Wunner [this message]
     [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
     [not found] <8e7978f65c6606fb2d48483435c78bd3@cutk.com>
2023-02-25 18:47 ` fk1xdcio
2023-02-27  8:12   ` Oliver O'Halloran
     [not found]     ` <9C53F704-1C13-4191-8890-20B18A23E94B.1@smtp-inbound1.duck.com>
2023-02-27  9:17       ` 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=20230225210220.GA17261@wunner.de \
    --to=lukas@wunner.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.