[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <79a41832-12e2-2ed-f3af-da3bac90d941@panix.com>
Date: Mon, 7 Feb 2022 10:20:32 -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:
> I think it's more likely that something changed in BIOS settings or
> other configuration, which means other people may trip over it even if
> you don't see it. Do you remember any BIOS updates, BIOS setup
> tweaks, hardware changes, kernel parameter changes, etc?
I thought about that Saturday morning, and yeah, it's been over a year, and
Dell has released at least two BIOS updates since then.
> 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.
-Kenny
--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
Powered by blists - more mailing lists