From: Kenneth Crudup <kenny@panix.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>, Me <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>,
"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: Fri, 14 Feb 2025 09:39:33 -0800 [thread overview]
Message-ID: <661459dd-67d0-4e1c-bb28-9adf1417f660@panix.com> (raw)
In-Reply-To: <20250214162948.GJ3713119@black.fi.intel.com>
This is excellent news that you were able to reproduce it- I'd figured
this regression would have been caught already (as I do remember this
working before) and was worried it may have been specific to a
particular piece of hardware (or software setup) on my system.
I'll see what I can dig up on my end, but as I'm not expert in these
subsystems I may not be able to diagnose anything until your return.
I also saw some DRM/connected fixes posted to Linus' master so maybe one
of them corrects this new display-crash issue (I'm not home on my big
monitor to be able to test yet).
-Kenny
On 2/14/25 08:29, Mika Westerberg wrote:
> Hi,
>
> On Thu, Feb 13, 2025 at 11:19:35AM -0800, Kenneth Crudup wrote:
>>
>> On 2/13/25 05:59, Mika Westerberg wrote:
>>
>>> Hi,
>>
>> As Murphy's would have it, now my crashes are display-driver related (this
>> is Xe, but I've also seen it with i915).
>>
>> Attached here just for the heck of it, but I'll be better testing the NVMe
>> enclosure-related failures this weekend. Stay tuned!
>
> Okay, I checked quickly and no TB related crash there but I was actually
> able to reproduce hang when I unplug the device chain during suspend. I did
> not yet have time to look into it deeper. I'm sure this has been working
> fine in the past as we tested all kinds of topologies including similar to
> this.
>
> I will be out next week for vacation but will continue after that if the
> problem is not alraedy solved ;-)
>
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
next prev parent reply other threads:[~2025-02-14 17:39 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 [this message]
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
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=661459dd-67d0-4e1c-bb28-9adf1417f660@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=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