Received-SPF: pass (google.com: domain of linux-kernel+bounces-184617-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
References: <CAHe5sWavQcUTg2zTYaryRsMywSBgBgETG=R1jRexg4qDqwCfdw@mail.gmail.com>
 <38de0776-3adf-4223-b8e0-cedb5a5ebf4d@leemhuis.info> <lqdpk7lopqq4jn22mycxgg6ps4yfs7hcca33tqb2oy6jxc2y7p@rhjjbzs6wigu>
 <611f8200-8e0e-40e4-aff4-cc2c55dc6354@amd.com> <CAHe5sWY_YJsyiuwf2TsfRTS9AoGoYh4+UxkkZZ0G9z2pXfbnzg@mail.gmail.com>
 <20240521051525.GL1421138@black.fi.intel.com>
In-Reply-To: <20240521051525.GL1421138@black.fi.intel.com>
From: Gia <giacomo.gio@gmail.com>
Date: Tue, 21 May 2024 10:07:23 +0200
Message-ID: <CAHe5sWY3P7AopLqwaeXSO7n-SFwEZom+MfWpLKGmbuA7L=VdmA@mail.gmail.com>
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding,
 assume dead" on stable kernel > 6.8.7
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>, Christian Heusel <christian@heusel.eu>, 
	Linux regressions mailing list <regressions@lists.linux.dev>, 
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, 
	"stable@vger.kernel.org" <stable@vger.kernel.org>, "kernel@micha.zone" <kernel@micha.zone>, 
	Andreas Noever <andreas.noever@gmail.com>, Michael Jamet <michael.jamet@intel.com>, 
	Yehezkel Bernat <YehezkelShB@gmail.com>, 
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>, =?UTF-8?Q?Benjamin_B=C3=B6hmke?= <benjamin@boehmke.net>, 
	"S, Sanath" <Sanath.S@amd.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thank you Mika,

Here you have the output of sudo journalctl -k without enabling the
kernel option "pcie_aspm=3Doff": https://codeshare.io/7JPgpE. Without
"pcie_aspm=3Doff", "thunderbolt.host_reset=3Dfalse" 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=E2=80=AFAM Mika Westerberg
<mika.westerberg@linux.intel.com> 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=3D+p=
:
> > https://codeshare.io/qAXLoj
> >
> > Output of sudo dmesg with kernel option thunderbolt.dyndbg=3D+p:
> > https://codeshare.io/zlPgRb
>
> I see you have "pcie_aspm=3Doff" 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=3D+p" in the
> command line (dropping pcie_aspm_off)?
>
> Also is there any particular reason you have it there?