From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Harry Wentland <harry.wentland@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: acpi: fix boot hang due to early incorrect 'tunneled' USB3 device links
Date: Thu, 24 Oct 2024 13:57:02 +0300 [thread overview]
Message-ID: <8c72a211-06aa-40f5-a478-aa2d2604143c@linux.intel.com> (raw)
In-Reply-To: <126c429f-7c55-4d7e-9d3a-1fa5c5ab1369@amd.com>
On 23.10.2024 21.07, Harry Wentland wrote:
>
>
> On 2024-10-23 12:50, Mario Limonciello wrote:
>> On 10/23/2024 07:12, Mathias Nyman wrote:
>>> On 22.10.2024 16.22, Mika Westerberg wrote:
>>>> The test case would be something like this:
>>>>
>>>> 1. Add "thunderbolt.host_reset=0" in the kernel command line.
>>>> 2. Boot with USB4 device connected (and so that it has USB 3.x device
>>>> connected such as USB 3 memory stick).
>>>> 3. Since there is no device link Thunderbolt/USB4 can runtime suspend
>>>> freely.
>>>> 4. Once that happens the tunnels are gone, including the USB 3.x tunnel
>>>> so the xHCI might see disconnect here.
>>>>
>>>> Also on resume path it will not be recreating the tunnel before xHCI
>>>> because there is no device link. I can try this on my side too if you
>>>> like.
>>>>
>>>
>>> You are right, I was able to reproduce it.
>>>
>>> Device link won't be created if BIOS created the tunnel, thunderbolt driver
>>> probes after this usb device is created, and "thunderbolt.host_reset=0" is set.
>>>
>>> Turning the device link "stateless" could possible help.
>>> It removes driver presence dependency but keeps correct suspend/resume and
>>> shutdown ordering.
>>> It should also help with boot hang/probe issues seen on the AMD platforms.
>>>
>>> Mario, Harry, does the following work for you?
>>
>> I didn't repro Harry's problem, but I did try on two OEM systems (Rembrandt and Phoenix based) with this change in place on a 6.12-rc4 base and didn't notice anything worse happening.
>
> Yeah, the following diff works for me.
>
> If you create a patch feel free to add my
> Tested-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
Thanks for testing, I'll turn this into a proper v2 patch
-Mathias
prev parent reply other threads:[~2024-10-24 10:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 12:37 [PATCH] usb: acpi: fix boot hang due to early incorrect 'tunneled' USB3 device links Mathias Nyman
2024-10-22 12:51 ` Mario Limonciello
2024-10-22 13:22 ` Mika Westerberg
2024-10-23 12:12 ` Mathias Nyman
2024-10-23 16:50 ` Mario Limonciello
2024-10-23 18:07 ` Harry Wentland
2024-10-24 10:57 ` Mathias Nyman [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=8c72a211-06aa-40f5-a478-aa2d2604143c@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=harry.wentland@amd.com \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.