From: Kenneth Crudup <kenny@panix.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>, Me <kenny@panix.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: So, I had to revert d6d458d42e1 ("Handle DisplayPort tunnel activation asynchronously") too, to stop my resume crashes
Date: Mon, 3 Mar 2025 05:53:22 -0800 [thread overview]
Message-ID: <24ef839c-8fa5-4a19-b9c6-0a267aab84f5@panix.com> (raw)
In-Reply-To: <20250303134618.GX3713119@black.fi.intel.com>
No failures for you at all? OK. It'll take me a couple of days to do all
the steps, but I'll get on it and get back to you.
> "Forget" all devices from boltctl to make sure PCIe is not involved.
What's this do? And my system recognizes all new TB devices
automatically (no manual intervention required).
----
$ boltctl
<snip>
● Belkin Thunderbolt 3 Dock Core
├─ type: peripheral
├─ name: Thunderbolt 3 Dock Core
├─ vendor: Belkin
├─ uuid: c2010000-0072-7c1e-8310-72c784524a06
├─ generation: Thunderbolt 3
├─ status: authorized
│ ├─ domain: 60838780-4021-ceb2-ffff-ffffffffffff
│ ├─ rx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ ├─ tx speed: 40 Gb/s = 2 lanes * 20 Gb/s
│ └─ authflags: none
├─ authorized: Mon 03 Mar 2025 11:59:48 AM UTC
├─ connected: Mon 03 Mar 2025 11:59:48 AM UTC
└─ stored: Sat 29 Jun 2024 11:03:09 PM UTC
├─ policy: iommu
└─ key: no
---
On 3/3/25 05:46, Mika Westerberg wrote:
> On Mon, Mar 03, 2025 at 03:23:27PM +0200, Mika Westerberg wrote:
>> Since if it is happening over suspend resume, I suggest we stick with that
>> for repro because it involves simpler code paths.
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
next prev parent reply other threads:[~2025-03-03 13:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 4:57 So, I had to revert d6d458d42e1 ("Handle DisplayPort tunnel activation asynchronously") too, to stop my resume crashes Kenneth Crudup
2025-03-02 5:36 ` Kenneth Crudup
2025-03-02 16:26 ` Kenneth Crudup
2025-03-02 16:30 ` Kenneth Crudup
2025-03-03 10:46 ` Mika Westerberg
2025-03-03 11:02 ` Kenneth Crudup
2025-03-03 11:21 ` Mika Westerberg
2025-03-03 11:38 ` Kenneth Crudup
2025-03-03 11:45 ` Kenneth Crudup
2025-03-03 11:55 ` Mika Westerberg
2025-03-03 12:39 ` Kenneth Crudup
2025-03-03 12:51 ` Kenneth Crudup
2025-03-03 11:53 ` Mika Westerberg
2025-03-03 12:33 ` Kenneth Crudup
2025-03-03 13:13 ` Mika Westerberg
2025-03-03 13:19 ` Kenneth Crudup
2025-03-03 13:23 ` Mika Westerberg
2025-03-03 13:46 ` Mika Westerberg
2025-03-03 13:53 ` Kenneth Crudup [this message]
2025-03-03 14:01 ` Mika Westerberg
2025-03-03 14:10 ` Kenneth Crudup
2025-03-03 14:20 ` Mika Westerberg
2025-03-03 14:33 ` Kenneth Crudup
2025-03-03 17:58 ` Mika Westerberg
2025-03-03 18:20 ` Kenneth Crudup
2025-03-03 19:44 ` Kenneth Crudup
2025-03-04 8:27 ` Mika Westerberg
2025-03-04 12:52 ` Kenneth Crudup
2025-03-04 13:40 ` Mika Westerberg
2025-03-04 13:48 ` Kenneth Crudup
2025-03-04 13:51 ` Mika Westerberg
2025-03-04 17:29 ` Kenneth Crudup
2025-03-05 8:31 ` Mika Westerberg
2025-03-03 14:17 ` Kenneth Crudup
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=24ef839c-8fa5-4a19-b9c6-0a267aab84f5@panix.com \
--to=kenny@panix.com \
--cc=linux-usb@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox