2024-05-21 08:07:51

by Gia

[permalink] [raw]
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7

Thank you Mika,

Here you have the output of sudo journalctl -k without enabling the
kernel option "pcie_aspm=off": https://codeshare.io/7JPgpE. Without
"pcie_aspm=off", "thunderbolt.host_reset=false" is not needed, my
thunderbolt dock does work. I also connected a 4k monitor to the
thunderbolt dock thinking it could provide more data.

I'm almost sure I used this option when I set up this system because
it solved some issues with system suspending, but it happened many
months ago.



On Tue, May 21, 2024 at 7:15 AM Mika Westerberg
<[email protected]> wrote:
>
> Hi,
>
> On Mon, May 20, 2024 at 05:57:42PM +0200, Gia wrote:
> > Hi Mario,
> >
> > In my case in both cases the value for:
> >
> > $ cat /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection
> >
> > is 0.
> >
> > Output of sudo journalctl -k with kernel option thunderbolt.dyndbg=+p:
> > https://codeshare.io/qAXLoj
> >
> > Output of sudo dmesg with kernel option thunderbolt.dyndbg=+p:
> > https://codeshare.io/zlPgRb
>
> I see you have "pcie_aspm=off" in the kernel command line. That kind of
> affects things. Can you drop that and see if it changes anything? And
> also provide a new full dmesg with "thunderbolt.dyndbg=+p" in the
> command line (dropping pcie_aspm_off)?
>
> Also is there any particular reason you have it there?


2024-05-21 13:42:30

by Mika Westerberg

[permalink] [raw]
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7

Hi,

On Tue, May 21, 2024 at 10:07:23AM +0200, Gia wrote:
> Thank you Mika,
>
> Here you have the output of sudo journalctl -k without enabling the
> kernel option "pcie_aspm=off": https://codeshare.io/7JPgpE. Without
> "pcie_aspm=off", "thunderbolt.host_reset=false" is not needed, my
> thunderbolt dock does work. I also connected a 4k monitor to the
> thunderbolt dock thinking it could provide more data.
>
> I'm almost sure I used this option when I set up this system because
> it solved some issues with system suspending, but it happened many
> months ago.

Okay. I recommend not to use it. The defaults should always be the best
option (unless you really know what you are doing or working around some
issue).

The dmesg you shared looks good, there are few oddities but they should
not matter from functional perspective (unless you are planning to have
a second monitor connected).

First is this:

May 21 09:59:40 um773arch kernel: thunderbolt 0000:36:00.5: IOMMU DMA protection is disabled

It should really be enabled but I'm not familiar with AMD hardware to
tell more so hoping Mario can comment on that.

The second thing is the USB4 link that seems to be degraded to 2x10G =
20G even though you say it is a Thunderbolt cable. I'll comment more on
that in the other email.