From: Michal Pecio <michal.pecio@gmail.com>
To: Ben <benstaples10@gmail.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-usb@vger.kernel.org, andreas.noever@gmail.com,
westeri@kernel.org, YehezkelShB@gmail.com
Subject: Re: xhci_hcd 0000:0c:00.0 dies with "Abort failed to stop command ring: -110" exactly 24s post-init, tunneled USB4 xHCI behind Goshen Ridge (ASUS ThunderboltEX 4) + CalDigit TS4
Date: Fri, 25 Sep 2026 10:40:13 +0200 [thread overview]
Message-ID: <20260925104013.1c8e21cb.michal.pecio@gmail.com> (raw)
In-Reply-To: <20260925102746.25e87ef0.michal.pecio@gmail.com>
On Fri, 25 Sep 2026 10:27:46 +0200, Michal Pecio wrote:
> Broken 64 bit support usually shows as IOMMU faults logged in dmesg,
> because the chip tries to access different addresses than intended.
> Here, it looks like this chip doesn't attempt DMA at all.
But wait a moment, are you sure that you have removed all the weird
boot options as requested, and particularly iommu=soft?
This option being present could explain why the chip is set up with
addresses >4GB, which is otherwise a little unusual thing to see.
Using iommu=soft is 100% asking for trouble and it makes debugging
harder too.
Regards,
Michal
next prev parent reply other threads:[~2026-09-25 8:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 4:04 xhci_hcd 0000:0c:00.0 dies with "Abort failed to stop command ring: -110" exactly 24s post-init, tunneled USB4 xHCI behind Goshen Ridge (ASUS ThunderboltEX 4) + CalDigit TS4 Ben
2026-09-15 4:19 ` Mika Westerberg
2026-09-15 4:27 ` Ben
2026-09-15 4:38 ` Mika Westerberg
2026-09-15 4:46 ` Ben
2026-09-15 5:05 ` Mika Westerberg
2026-09-16 3:01 ` Ben
2026-09-16 7:51 ` Mika Westerberg
2026-09-17 2:18 ` Ben
2026-09-17 2:40 ` Ben
2026-09-17 4:38 ` Mika Westerberg
2026-09-19 0:28 ` Ben
2026-09-21 4:44 ` Mika Westerberg
2026-09-21 23:25 ` Ben
2026-09-22 4:26 ` Mika Westerberg
2026-09-22 11:28 ` Mathias Nyman
2026-09-24 3:02 ` Ben
2026-09-24 15:49 ` [WARNING: UNSCANNABLE EXTRACTION FAILED]Re: " Mathias Nyman
2026-09-24 22:18 ` Ben
2026-09-25 8:27 ` Michal Pecio
2026-09-25 8:40 ` Michal Pecio [this message]
2026-09-26 0:28 ` Ben
2026-09-26 8:37 ` Michal Pecio
2026-09-26 13:59 ` Ben
2026-09-26 17:41 ` Michal Pecio
2026-09-29 23:50 ` Ben
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=20260925104013.1c8e21cb.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=benstaples10@gmail.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@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.