public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Gia <giacomo.gio@gmail.com>
Cc: "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>,
	"Benjamin Böhmke" <benjamin@boehmke.net>,
	"S, Sanath" <Sanath.S@amd.com>
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7
Date: Tue, 21 May 2024 05:50:23 -0500	[thread overview]
Message-ID: <b04e04bc-a0dc-434f-b7cb-7df2cd3abab1@amd.com> (raw)
In-Reply-To: <20240521085501.GN1421138@black.fi.intel.com>



On 5/21/2024 3:55 AM, Mika Westerberg wrote:
> 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).

Windows and Linux handle port pm differently at suspend.  I've had a few 
patch series attempts to allow unifying them with some "smaller" pieces 
landing as well as a quirk for one of the root ports.

But the specific issue that was happening was a platform bug that 
occurred due to this.  It's since then been fixed, and I guess you have 
a new BIOS Gia.

Completely agree with Mika the default policy for Linux is generally 
right though.

> 
> 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.

This is controlled by OEM BIOS policy.
You should try to turn it on if you can as it's a more secure setup.
Some of the Linux stack (for example bolt) will automatically authorize 
PCIe and TBT3 devices when it's deemed secure.

I'm not familiar with the OEM for your machine, but some strings you can 
look for that might point you in that direction to enable it:

1) "Kernel DMA protection"
2) "Security levels"

I know some OEMs also only enable it when you "load optimized defaults".

> 
> 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.

      parent reply	other threads:[~2024-05-21 10:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHe5sWavQcUTg2zTYaryRsMywSBgBgETG=R1jRexg4qDqwCfdw@mail.gmail.com>
2024-05-06 12:53 ` [REGRESSION] Thunderbolt Host Reset Change Causes eGPU Disconnection from 6.8.7=>6.8.8 Linux regression tracking (Thorsten Leemhuis)
2024-05-20  9:19   ` Gia
2024-05-20 13:43     ` Mario Limonciello
2024-05-20 14:39   ` [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel > 6.8.7 Christian Heusel
2024-05-20 14:41     ` Mario Limonciello
2024-05-20 15:12       ` Benjamin Böhmke
2024-05-20 16:21         ` Mika Westerberg
2024-05-20 16:53           ` Benjamin Böhmke
2024-05-20 17:30             ` Gia
2024-05-21  5:11               ` Mika Westerberg
2024-05-21  8:15                 ` Gia
2024-05-21  8:59                   ` Mika Westerberg
2024-05-21  9:12                     ` Gia
2024-05-21 11:26                       ` Mika Westerberg
2024-05-22 14:41                         ` Gia
2024-05-22 15:19                           ` Mario Limonciello
2024-05-23  4:45                             ` Mika Westerberg
2024-05-21  4:59             ` Mika Westerberg
2024-05-21 10:52               ` Limonciello, Mario
2024-05-20 15:57       ` Gia
2024-05-21  5:15         ` Mika Westerberg
2024-05-21  8:07           ` Gia
2024-05-21  8:55             ` Mika Westerberg
2024-05-21  9:24               ` Gia
2024-05-21 11:29                 ` Mika Westerberg
2024-05-21 10:50               ` Limonciello, Mario [this message]

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=b04e04bc-a0dc-434f-b7cb-7df2cd3abab1@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=Sanath.S@amd.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=benjamin@boehmke.net \
    --cc=christian@heusel.eu \
    --cc=giacomo.gio@gmail.com \
    --cc=kernel@micha.zone \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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