From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221319] Certain operations via PCIe tunneling between an AMD USB4 host and a Thunderbolt-5 peripherals cause an instant reboot
Date: Mon, 06 Apr 2026 02:31:28 +0000 [thread overview]
Message-ID: <bug-221319-208809-8watC74938@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221319-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221319
--- Comment #6 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
Here's the message that I was looking for:
> [ 1.657766] x86/amd: Previous system reset reason [0x08000800]: an
> uncorrected error caused a data fabric sync flood event
I suspect that there are some PCIe errors occurring either internal to the SoC
or (more likely) between the SoC and your new device. These are causing a
flood of problems, and then the BIOS eventually triggers an internal watchdog
that reboots the system.
Try adding this to your kernel command line and we'll see if there is anything
new from the PCI core about the issue:
> pcie_ports=native pcie_ecrc=on
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-04-06 2:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 15:24 [Bug 221319] New: Certain operations via PCIe tunneling between an AMD USB4 host and a Thunderbolt-5 peripherals cause an instant reboot bugzilla-daemon
2026-04-04 15:25 ` [Bug 221319] " bugzilla-daemon
2026-04-05 11:58 ` bugzilla-daemon
2026-04-06 0:40 ` bugzilla-daemon
2026-04-06 0:41 ` bugzilla-daemon
2026-04-06 0:52 ` bugzilla-daemon
2026-04-06 2:31 ` bugzilla-daemon [this message]
2026-04-06 2:31 ` bugzilla-daemon
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=bug-221319-208809-8watC74938@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@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