[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240521112915.GQ1421138@black.fi.intel.com>
Date: Tue, 21 May 2024 14:29:15 +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
On Tue, May 21, 2024 at 11:24:56AM +0200, Gia wrote:
> Thank you for your suggestion Mika, as a general rule I totally agree
> with you and I do not mess with kernel default parameters, but I
> remember "pcie_aspm=off" was necessary at the time I set up the
> system. Probably a kernel or a BIOS update makes it unnecessary today.
Okay, thanks.
> I see it removes these messages from my logs but I trust you when you
> say they have not an impact on functionality:
>
> May 21 11:01:36 um773arch kernel: pcieport 0000:05:04.0: Unable to
> change power state from D3hot to D0, device inaccessible
> May 21 11:01:36 um773arch kernel: igb 0000:09:00.0 eth0: PCIe link lost
> May 21 11:01:36 um773arch kernel: xhci_hcd 0000:08:00.0: xHCI host
> controller not responding, assume dead
> May 21 11:01:36 um773arch kernel: xhci_hcd 0000:07:00.0: xHCI host
> controller not responding, assume dead
Correct these are side-effect of the USB4 topology reset we do. As
explained earlier the tunnels get re-established and the devices will
come back soon after this.
Powered by blists - more mailing lists