public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: "Katiyar, Pooja" <pooja.katiyar@linux.intel.com>
To: Kenneth Crudup <kenny@panix.com>
Cc: "open list:THUNDERBOLT DRIVER" <linux-usb@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Andreas Noever <andreas.noever@gmail.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Pooja Katiyar <pooja.katiyar@intel.com>,
	Rene Sapiens <rene.sapiens@linux.intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Mario Limonciello <superm1@kernel.org>
Subject: Re: [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities
Date: Tue, 3 Feb 2026 16:50:28 -0800	[thread overview]
Message-ID: <0819af50-d19c-4169-b3be-74cde9388802@linux.intel.com> (raw)
In-Reply-To: <31ec74be-13b6-4d74-8643-6bd68659299b@panix.com>

Hi Kenny,

On Thu, Jan 29, 2026 at 05:42:43PM -0800, Kenneth Crudup wrote:
> 
> BTW, I had no TB connectivity until I'd unplugged/replugged.
> 
> -Kenny

Thanks for testing the patch series!

To help diagnose the warning/issue, can you share your TB dock/setup
information and the steps that you are following? Also it would be
helpful if you can provide logs with dynamic debugging enabled for
thunderbolt. I am not able to reproduce the issue at my end, so the
above information would be really helpful to look into the issue while
I continue checking on my end. From the warning it appears that the tunnels
are invalid from the stack trace in the logs.

> 
> On 1/29/26 17:39, Kenneth Crudup wrote:
>>
>>>> The issue I'm trying to chase down (and not sure if any of this will
>>>> help with this, I wonder if it's really BIOS/EC related) is often times
>>>> that after a suspend (or hibernate, but I use "suspend then hibernate",
>>>> which I think does both and chooses which to use upon resume) and then
>>>> connect to a different dock (or setup) from the one I'd suspended with,
>>>> sometimes I have to unplug/replug my TB cable, otherwise I either get no
>>>> recognition of my new display setup (and sometimes TB devices) or it'll
>>>> try and use the same monitor resolution of the previously-connected
>>>> monitor (as if the TB subsystem doesn't recognize things have changed).
>>
>> On 1/29/26 15:13, Katiyar, Pooja wrote:
>>
>>> Below is the patch series that addresses mentioned issue. There are two
>>> patches in this series. The series takes care of releasing the DP resources
>>> as part of freeze call before the hibernation image is created. You can test
>>> it for your issues and let us know if it helps.
>>>
>>> Please note that these changes are still under internal review and are
>>> subject to change.
>>
>> I tested this against Linus' master (4d310797262) and while the jury is still out on my issue (a few tests against different monitors looked good, the big test is when I get back home later), I did see this on the 3rd resume from hibernate (full dmesg attached):
>>
>> ----

Thanks and Regards,
Pooja


      reply	other threads:[~2026-02-04  0:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  5:37 [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities Mario Limonciello (AMD)
2026-01-06  5:37 ` [PATCH v2 1/2] thunderbolt: Move nhi_reset before pmops declaration Mario Limonciello (AMD)
2026-01-06  5:37 ` [PATCH v2 2/2] thunderbolt: Reset NHI during S4 restore_noirq() callback Mario Limonciello (AMD)
2026-01-07  9:33 ` [PATCH v2 0/2] thunderbolt: Fix S4 resume incongruities Mika Westerberg
2026-01-07 20:50   ` Mario Limonciello
2026-01-08 11:42     ` Mika Westerberg
2026-01-08 19:18       ` Mario Limonciello
2026-01-09  7:23         ` Mika Westerberg
2026-01-09 15:38           ` Mario Limonciello
2026-01-10  0:42           ` Katiyar, Pooja
2026-01-13 18:44             ` Mario Limonciello (AMD) (kernel.org)
2026-01-17 16:57               ` Katiyar, Pooja
2026-01-19 19:59                 ` Mario Limonciello (AMD) (kernel.org)
2026-01-19 22:13                   ` Kenneth Crudup
2026-01-29 23:13                     ` Katiyar, Pooja
2026-01-30  1:39                       ` Kenneth Crudup
2026-01-30  1:42                         ` Kenneth Crudup
2026-02-04  0:50                           ` Katiyar, Pooja [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=0819af50-d19c-4169-b3be-74cde9388802@linux.intel.com \
    --to=pooja.katiyar@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=kenny@panix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=pooja.katiyar@intel.com \
    --cc=rene.sapiens@linux.intel.com \
    --cc=superm1@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