[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ca14a7-b726-8430-fe61-a3ac183a1088@panix.com>
Date: Tue, 15 Feb 2022 05:10:48 -0800 (PST)
From: "Kenneth R. Crudup" <kenny@...ix.com>
To: Bjorn Helgaas <helgaas@...nel.org>
cc: Vidya Sagar <vidyas@...dia.com>, bhelgaas@...gle.com,
lorenzo.pieralisi@....com, hkallweit1@...il.com,
wangxiongfeng2@...wei.com, mika.westerberg@...ux.intel.com,
kai.heng.feng@...onical.com, chris.packham@...iedtelesis.co.nz,
yangyicong@...ilicon.com, treding@...dia.com, jonathanh@...dia.com,
abhsahu@...dia.com, sagupta@...dia.com, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, kthota@...dia.com,
mmaddireddy@...dia.com, sagar.tv@...il.com,
"Kenneth R. Crudup" <kenny@...ix.com>
Subject: Re: [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for
suspend/resume
> On Mon, 7 Feb 2022, Bjorn Helgaas wrote:
> > If the problem really was fixed by some change elsewhere, it *should*
> > still happen on v5.11-rc1. I think we should verify that and try to
> > figure out what the other change was.
> Yeah, not a bad idea. I'm a little busy now, but I'll cut a kernel at
> 4257f7e0, remake, and see what happens. Gimme a day or so.
So I did this- checked out a branch hard-reset to commit 4257f7e0, used my
current _defconfig on it, and built and tested it- NOW it doesn't exhibit the
NVMe-device-killing behavior I'd seen a year earlier; I'm assuming Dell must
have fixed something in the BIOS?
Anyway, I'd done an "lspci -vvvnn" before and after hibernation, if you're
interested, and a diff of same; I'll send those in subsequent E-mails.
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
View attachment "kernel-4257f7e00-pre-hibernate" of type "text/plain" (42582 bytes)
View attachment "kernel-4257f7e00-pre-post-diff" of type "text/plain" (3147 bytes)
Powered by blists - more mailing lists