From: Kenneth Crudup <kenny@panix.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>,
Kenneth Crudup <kenny@panix.com>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
ilpo.jarvinen@linux.intel.com,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jian-Hong Pan" <jhp@endlessos.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Niklāvs Koļesņikovs" <pinkflames.linux@gmail.com>,
"Andreas Noever" <andreas.noever@gmail.com>,
"Michael Jamet" <michael.jamet@intel.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Yehezkel Bernat" <YehezkelShB@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: diagnosing resume failures after disconnected USB4 drives (Was: Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac))
Date: Sun, 2 Mar 2025 08:13:51 -0800 [thread overview]
Message-ID: <e5badaa8-20e2-4160-be20-75e174d241bc@panix.com> (raw)
In-Reply-To: <1f214d95-61c0-4be9-8b19-5aef76631c0e@panix.com>
On 2/28/25 08:04, Kenneth Crudup wrote:
> Don't worry about the printk()s WRT to the code; a couple of weeks ago
> I'd seen an NPE on resume in __tb_path_deactivate_hop so threw in a
> bunch of tb_port_info(port, "%s(): %d\n", __func__, __LINE__); so I
> could get an idea of where the crash was.
I've started a separate E-mail about this, but I'd determined those
crashes were due to d6d458d42e1 ("Handle DisplayPort tunnel activation
asynchronously").
Since reverting 9d573d1954 and d6d458d42e1 I've been testing several
resume scenarios (NVMe connected/disconnected and/or external
DP-tunneled monitor connected/disconnected and have yet to have a resume
or hibernate failure over several cycles.
Now, how do I help you guys go about fixing these commits?
-K
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
next prev parent reply other threads:[~2025-03-02 16:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b2abd254-d11f-4ef7-8664-b9e5a1409abc@panix.com>
2025-02-10 21:05 ` PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac) Bjorn Helgaas
2025-02-11 0:18 ` Kenneth Crudup
2025-02-11 5:57 ` Mika Westerberg
2025-02-11 6:17 ` diagnosing resume failures after disconnected USB4 drives (Was: Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac)) Kenneth Crudup
2025-02-13 13:59 ` Mika Westerberg
2025-02-13 19:19 ` Kenneth Crudup
2025-02-14 16:29 ` Mika Westerberg
2025-02-14 17:39 ` Kenneth Crudup
2025-02-26 8:44 ` Mika Westerberg
2025-02-26 9:10 ` Lukas Wunner
2025-02-26 9:19 ` Mika Westerberg
2025-03-03 20:00 ` Lukas Wunner
2025-03-03 20:57 ` Kenneth Crudup
2025-03-04 8:23 ` Mika Westerberg
2025-03-06 16:45 ` Lukas Wunner
2025-03-06 16:56 ` Kenneth Crudup
2025-03-06 18:18 ` Lukas Wunner
2025-03-06 20:38 ` Kenneth Crudup
2025-03-07 2:04 ` Kenneth Crudup
2025-03-07 10:34 ` Mika Westerberg
2025-02-26 15:31 ` Kenneth Crudup
2025-02-26 21:13 ` Kenneth Crudup
2025-02-26 21:14 ` Kenneth Crudup
2025-02-27 17:46 ` Kenneth Crudup
2025-02-28 10:49 ` Mika Westerberg
2025-02-28 16:04 ` Kenneth Crudup
2025-03-02 16:13 ` Kenneth Crudup [this message]
2025-03-03 10:48 ` Mika Westerberg
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=e5badaa8-20e2-4160-be20-75e174d241bc@panix.com \
--to=kenny@panix.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jhp@endlessos.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=pinkflames.linux@gmail.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