From: Kenneth Crudup <kenny@panix.com>
To: ilpo.jarvinen@linux.intel.com
Cc: Me <kenny@panix.com>, "Bjorn Helgaas" <bhelgaas@google.com>,
"Jian-Hong Pan" <jhp@endlessos.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
"Cc: \"Ilpo Järvinen\"" <ilpo.jarvinen@linux.intel.com>,
"Niklāvs Koļesņikovs" <pinkflames.linux@gmail.com>
Subject: Re: PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac)
Date: Sat, 8 Feb 2025 12:56:35 -0800 [thread overview]
Message-ID: <04091f53-3c94-4533-ab48-e9296e6e2841@panix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
Guys, I don't think this commit is right; I've had 2 out of three resume
failures since this change went into Linus' master. I've attached a
pstore dump of the latest crash, and while it appears to be coming from
the Intel XE driver, 95% of my (s0ix) resumes worked previously[1]
before this change.
LMK if you need more information.
-Kenny
[1] - unless I forget to detach my NVMe USB4 external drive before
suspending, which is a breakage that appears to have gone in sometime
around the 6.10 series, but I haven't been able to bisect it
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange
County CA
[-- Attachment #2: kernel-crash.tar.gz --]
[-- Type: application/gzip, Size: 8617 bytes --]
next reply other threads:[~2025-02-08 21:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 20:56 Kenneth Crudup [this message]
2025-02-09 3:47 ` PCI/ASPM: Fix L1SS saving (linus/master commit 7507eb3e7bfac) Kenneth Crudup
2025-02-10 21:05 ` 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
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=04091f53-3c94-4533-ab48-e9296e6e2841@panix.com \
--to=kenny@panix.com \
--cc=bhelgaas@google.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jhp@endlessos.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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