public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Gia <giacomo.gio@gmail.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>,
	"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 14:29:15 +0300	[thread overview]
Message-ID: <20240521112915.GQ1421138@black.fi.intel.com> (raw)
In-Reply-To: <CAHe5sWaABJi0Xo4ygFK4Oa3LdNUiQJSLidGPdAE=gwmy=b+ycw@mail.gmail.com>

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.

  reply	other threads:[~2024-05-21 11:29 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 [this message]
2024-05-21 10:50               ` Limonciello, Mario

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=20240521112915.GQ1421138@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.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=mario.limonciello@amd.com \
    --cc=michael.jamet@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