public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
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 06:33:06 -0800	[thread overview]
Message-ID: <402bcee8-030a-45bf-834b-ea4baf5eed3c@panix.com> (raw)
In-Reply-To: <20250303142058.GA3713119@black.fi.intel.com>


On 3/3/25 06:20, Mika Westerberg wrote:

> Actually just managed to reproduce this with hibernate \o/ so debugging
> now.

OK, this is good ... but now you've got me wondering if I indeed saw it 
during suspend cycles as well (I usually suspend only, then systemd will 
initiate a hibernation after 4H so just going back/forth to the office 
shouldn't trigger this).

Waiting to see what you find,

-Kenny

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange 
County CA


  reply	other threads:[~2025-03-03 14:33 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
2025-03-03 14:33                                   ` Kenneth Crudup [this message]
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=402bcee8-030a-45bf-834b-ea4baf5eed3c@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