public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Christian Heusel <christian@heusel.eu>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Gia <giacomo.gio@gmail.com>,
	"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>,
	"Mika Westerberg" <mika.westerberg@linux.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: Mon, 20 May 2024 09:41:43 -0500	[thread overview]
Message-ID: <611f8200-8e0e-40e4-aff4-cc2c55dc6354@amd.com> (raw)
In-Reply-To: <lqdpk7lopqq4jn22mycxgg6ps4yfs7hcca33tqb2oy6jxc2y7p@rhjjbzs6wigu>

On 5/20/2024 09:39, Christian Heusel wrote:
> On 24/05/06 02:53PM, Linux regression tracking (Thorsten Leemhuis) wrote:
>> [CCing Mario, who asked for the two suspected commits to be backported]
>>
>> On 06.05.24 14:24, Gia wrote:
>>> Hello, from 6.8.7=>6.8.8 I run into a similar problem with my Caldigit
>>> TS3 Plus Thunderbolt 3 dock.
>>>
>>> After the update I see this message on boot "xHCI host controller not
>>> responding, assume dead" and the dock is not working anymore. Kernel
>>> 6.8.7 works great.
> 
> We now have some further information on the matter as somebody was kind
> enough to bisect the issue in the [Arch Linux Forums][0]:
> 
>      cc4c94a5f6c4 ("thunderbolt: Reset topology created by the boot firmware")
> 
> This is a stable commit id, the relevant mainline commit is:
> 
>      59a54c5f3dbd ("thunderbolt: Reset topology created by the boot firmware")
> 
> The other reporter created [a issue][1] in our bugtracker, which I'll
> leave here just for completeness sake.
> 
> Reported-by: Benjamin Böhmke <benjamin@boehmke.net>
> Reported-by: Gia <giacomo.gio@gmail.com>
> Bisected-by: Benjamin Böhmke <benjamin@boehmke.net>
> 
> The person doing the bisection also offered to chime in here if further
> debugging is needed!
> 
> Also CC'ing the Commitauthors & Subsystem Maintainers for this report.
> 
> Cheers,
> Christian
> 
> [0]: https://bbs.archlinux.org/viewtopic.php?pid=2172526
> [1]: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/48
> 
> #regzbot introduced: 59a54c5f3dbd
> #regzbot link: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/issues/48

As I mentioned in my other email I would like to collate logs onto a 
kernel Bugzilla.  With these two cases:

thunderbolt.dyndbg=+p
thunderbolt.dyndbg=+p thunderbolt.host_reset=false

Also what is the value for:

$ cat /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection

  reply	other threads:[~2024-05-20 14:41 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 [this message]
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

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=611f8200-8e0e-40e4-aff4-cc2c55dc6354@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