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: Tue, 4 Mar 2025 15:40:17 +0200 [thread overview]
Message-ID: <20250304134017.GL3713119@black.fi.intel.com> (raw)
In-Reply-To: <14351945-fcde-4088-b7b3-542c6e4b7d0e@panix.com>
On Tue, Mar 04, 2025 at 04:52:19AM -0800, Kenneth Crudup wrote:
>
> On 3/4/25 00:27, Mika Westerberg wrote:
>
> > If possible add "thunderbolt.dyndbg=+p" now to your kernel command line so
> > if this happens again, we hopefully have full dmesg to investigate.
>
> I've not seen any further instances of weird behavior, but I've added that
> to the command line going further.
Okay thanks!
> But I have been doing a fair amount of testing of the kernel with your patch
> and Lucas' NVMe adaptor (etc.) patch and am concerned that you're still
> seeing his issue, as it (at least as of now) hasn't occurred here since
> applying it.
It only happens if you have TBT dock and the NVMe connected and you
disconnect them while the system is suspended.
I suggest trying that a couple times and see if that happens. For me it
happened pretty much on first suspend cycle.
next prev parent reply other threads:[~2025-03-04 13:40 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
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 [this message]
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=20250304134017.GL3713119@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 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.