linux-kernel - Re: [REGRESSION][BISECTED] "xHCI host controller not responding, assume dead" on stable kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 21 May 2024 08:15:25 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Gia <giacomo.gio@...il.com>
Cc: Mario Limonciello <mario.limonciello@....com>,
	Christian Heusel <christian@...sel.eu>,
	Linux regressions mailing list <regressions@...ts.linux.dev>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"stable@...r.kernel.org" <stable@...r.kernel.org>,
	"kernel@...ha.zone" <kernel@...ha.zone>,
	Andreas Noever <andreas.noever@...il.com>,
	Michael Jamet <michael.jamet@...el.com>,
	Yehezkel Bernat <YehezkelShB@...il.com>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
	Benjamin Böhmke <benjamin@...hmke.net>,
	"S, Sanath" <Sanath.S@....com>
Subject: Re: [REGRESSION][BISECTED] "xHCI host controller not responding,
 assume dead" on stable kernel > 6.8.7

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?