public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: Kenneth Crudup <kenny@panix.com>,
	Bjorn Helgaas <helgaas@kernel.org>,
	ilpo.jarvinen@linux.intel.com,
	Bjorn Helgaas <bhelgaas@google.com>,
	Jian-Hong Pan <jhp@endlessos.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Nikl??vs Ko??es??ikovs <pinkflames.linux@gmail.com>,
	Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	linux-usb@vger.kernel.org
Subject: Re: diagnosing resume failures after disconnected USB4 drives (Was: Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac))
Date: Tue, 4 Mar 2025 10:23:14 +0200	[thread overview]
Message-ID: <20250304082314.GE3713119@black.fi.intel.com> (raw)
In-Reply-To: <Z8YKXC1IXYXctQrZ@wunner.de>

On Mon, Mar 03, 2025 at 09:00:28PM +0100, Lukas Wunner wrote:
> On Wed, Feb 26, 2025 at 11:19:58AM +0200, Mika Westerberg wrote:
> > On Wed, Feb 26, 2025 at 10:10:43AM +0100, Lukas Wunner wrote:
> > > On Wed, Feb 26, 2025 at 10:44:04AM +0200, Mika Westerberg wrote:
> > > >   [Meteor Lake host] <--> [TB 4 dock] <--> [TB 3 NVMe]
> > > [...]
> > > > I added "no_console_suspend" to the command line and the did sysrq-w to
> > > > get list of blocked tasks. I've attached it just in case it is needed.
> > > 
> > > This looks like the deadlock we've had for years when hot-removing
> > > nested hotplug ports.
> > > 
> > > If you attach only a single device to the host, I guess the issue
> > > does not occur, right?
> > 
> > Yes.
> > 
> > > Previous attempts to fix this:
> > > 
> > > https://lore.kernel.org/all/4c882e25194ba8282b78fe963fec8faae7cf23eb.1529173804.git.lukas@wunner.de/
> > > 
> > > https://lore.kernel.org/all/20240612181625.3604512-1-kbusch@meta.com/
> > 
> > Well, it does not happen if I revert the commit so isn't that a
> > regresssion?
> 
> Does the below fix the issue?

Unfortunately I still see the same hang. I double checked, with revert the
problem goes a way and with this patch I still see it.

Steps:

1. Boot the system, nothing connected.
2. Connect TBT 4 dock to the host.
3. Connect TBT 3 NVMe to the TBT4 doc.
4. Authorize both PCIe tunnels, verify devices are there.
5. Enter s2idle.
6. Unplug the TBT 4 dock from the host.
7. Exit s2idle.

  parent reply	other threads:[~2025-03-04  8:23 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b2abd254-d11f-4ef7-8664-b9e5a1409abc@panix.com>
2025-02-10 21:05 ` PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac) Bjorn Helgaas
2025-02-11  0:18   ` Kenneth Crudup
2025-02-11  5:57     ` Mika Westerberg
2025-02-11  6:17       ` diagnosing resume failures after disconnected USB4 drives (Was: Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac)) Kenneth Crudup
2025-02-13 13:59         ` Mika Westerberg
2025-02-13 19:19           ` Kenneth Crudup
2025-02-14 16:29             ` Mika Westerberg
2025-02-14 17:39               ` Kenneth Crudup
2025-02-26  8:44                 ` Mika Westerberg
2025-02-26  9:10                   ` Lukas Wunner
2025-02-26  9:19                     ` Mika Westerberg
2025-03-03 20:00                       ` Lukas Wunner
2025-03-03 20:57                         ` Kenneth Crudup
2025-03-04  8:23                         ` Mika Westerberg [this message]
2025-03-06 16:45                           ` Lukas Wunner
2025-03-06 16:56                             ` Kenneth Crudup
2025-03-06 18:18                               ` Lukas Wunner
2025-03-06 20:38                             ` Kenneth Crudup
2025-03-07  2:04                             ` Kenneth Crudup
2025-03-07 10:34                             ` Mika Westerberg
2025-02-26 15:31                   ` Kenneth Crudup
2025-02-26 21:13                   ` Kenneth Crudup
2025-02-26 21:14                   ` Kenneth Crudup
2025-02-27 17:46                     ` Kenneth Crudup
2025-02-28 10:49                       ` Mika Westerberg
2025-02-28 16:04                         ` Kenneth Crudup
2025-03-02 16:13                           ` Kenneth Crudup
2025-03-03 10:48                             ` Mika Westerberg

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=20250304082314.GE3713119@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=helgaas@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jhp@endlessos.org \
    --cc=kenny@panix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=pinkflames.linux@gmail.com \
    /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