public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
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 15:46:18 +0200	[thread overview]
Message-ID: <20250303134618.GX3713119@black.fi.intel.com> (raw)
In-Reply-To: <20250303132327.GW3713119@black.fi.intel.com>

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.

Okay I'm now trying with following.

0. "Forget" all devices from boltctl to make sure PCIe is not involved.

1. Boot the system, nothing connected.
2. Plug in TBT 4 dock.
3. Plug in DP monitor through DP to Type-C adapter to the TBT 4 dock.
4. Verify that there is picture on that monitor.
5. Enter system suspend (s2idle):

  # rtcwake -s 30 -mmem

6. Once it wakes up verify that the monitor display a picture.
7. Repeat steps 5. and 6. several times.

I did serveral iterations (will do more) but I did not see any issues.

Can you try this one first, when you have time. If you see the issue, try
to take full dmesg.

---------------------------------------------------------------------

Then I tried another flow.

0. "Forget" all devices from boltctl to make sure PCIe is not involved.

1. Boot the system, nothing connected.
2. Plug in TBT 4 dock.
3. Plug in DP monitor through DP to Type-C adapter to the TBT 4 dock.
4. Verify that there is picture on that monitor.
5. Enter system suspend (s2idle):

  # rtcwake -s 30 -mmem

6. Once the system is suspended, unplug the monitor.
7. Once system resumes it should stay responsive.
8. Repeat steps 3. - 7. several times.

Here too, I don't see any issues. Please try this too if you have not been
able to reproduce with the first flow.

---------------------------------------------------------------------

Then yet another flow

0. "Forget" all devices from boltctl to make sure PCIe is not involved.

1. Boot the system, nothing connected.
2. Plug in TBT 4 dock.
3. Plug in DP monitor through DP to Type-C adapter to the TBT 4 dock.
4. Verify that there is picture on that monitor.
5. Enter system suspend (s2idle):

  # rtcwake -s 30 -mmem

6. Once the system is suspended, unplug the monitor.
7. Plug it back while the system is still suspended. You can use different
   Type-C port too.
8. Once system resumes the monitor should come up and show picture.
9. Repeat steps 5. - 8. several times.

I was not able to trigger any issues with this flow either but I'll
continue with them. Please try this one too if you don't manage to
reproduce the issue with the above two.

  reply	other threads:[~2025-03-03 13:46 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 [this message]
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
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=20250303134618.GX3713119@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