From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Kenneth Crudup <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 16:20:58 +0200 [thread overview]
Message-ID: <20250303142058.GA3713119@black.fi.intel.com> (raw)
In-Reply-To: <567725a5-f984-4ea1-bd38-8815825c1211@panix.com>
On Mon, Mar 03, 2025 at 06:10:09AM -0800, Kenneth Crudup wrote:
>
> > > And my system recognizes all new TB devices automatically
> > > (no manual intervention required).
>
> On 3/3/25 06:01, Mika Westerberg wrote:
>
> > Right it does that if you have screen unlocked.
>
> I'm running Kubuntu (24.10); AFAIK it just allows them anyway. The "System
> Settings" dialog is just an Enable/Disable toggle.
Ah okay then nevermind.
> > If you "forget" them then it should in theory at least keep from creating
> > PCIe tunnels, so keeping them out of the equation (we just want to
> > concentrate on the TB/DP side here).
>
> But what I can try is just connecting the monitors directly; the portable
> monitor directly to one of the laptop's USB-Cs, and the Odyssey's
> USB-C-to-DP w/o using the dock.
Actually just managed to reproduce this with hibernate \o/ so debugging
now.
My steps:
(I run buildroot based distro on my test systems so there is nothing
authorizing PCIe tunnels by default)
1. Boot the system up, nothing connected.
2. Connect TBT 4 dock to the host.
3. Connect monitor to the TBT 4 dock.
4. Verify picture on screen.
5. Enter hibernate
# rtcwake -s 60 -m disk
6. Once booted up and resumed from disk verify that the monitor displays
correctly.
next prev parent reply other threads:[~2025-03-03 14:21 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
2025-03-03 14:01 ` Mika Westerberg
2025-03-03 14:10 ` Kenneth Crudup
2025-03-03 14:20 ` Mika Westerberg [this message]
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=20250303142058.GA3713119@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=kenny@panix.com \
--cc=linux-usb@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