[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e5badaa8-20e2-4160-be20-75e174d241bc@panix.com>
Date: Sun, 2 Mar 2025 08:13:51 -0800
From: Kenneth Crudup <kenny@...ix.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>,
Kenneth Crudup <kenny@...ix.com>
Cc: Bjorn Helgaas <helgaas@...nel.org>, ilpo.jarvinen@...ux.intel.com,
Bjorn Helgaas <bhelgaas@...gle.com>, Jian-Hong Pan <jhp@...lessos.org>,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
Niklāvs Koļesņikovs <pinkflames.linux@...il.com>,
Andreas Noever <andreas.noever@...il.com>,
Michael Jamet <michael.jamet@...el.com>, Lukas Wunner <lukas@...ner.de>,
Yehezkel Bernat <YehezkelShB@...il.com>, linux-usb@...r.kernel.org
Subject: Re: diagnosing resume failures after disconnected USB4 drives (Was:
Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac))
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
Powered by blists - more mailing lists