Bug 215742 - The NVME storage quirked as SIMPLE SUSPEND makes system resume failed after suspend (Regression)

[Limonciello, Mario]

[Public]

> -----Original Message-----
> From: Christoph Hellwig <hch at lst.de>
> Sent: Friday, April 1, 2022 06:27
> To: Thorsten Leemhuis <regressions at leemhuis.info>
> Cc: Limonciello, Mario <Mario.Limonciello at amd.com>; Jian-Hong Pan
> <jhp at endlessos.org>; regressions at lists.linux.dev; Christoph Hellwig
> <hch at lst.de>; linux-kernel at vger.kernel.org; linux-
> nvme at lists.infradead.org; Rafael J . Wysocki <rjw at rjwysocki.net>; ACPI
> Devel Maling List <linux-acpi at vger.kernel.org>
> Subject: Re: Bug 215742 - The NVME storage quirked as SIMPLE SUSPEND
> makes system resume failed after suspend (Regression)
> 
> On Fri, Apr 01, 2022 at 09:55:14AM +0200, Thorsten Leemhuis wrote:
> > Hi, this is your Linux kernel regression tracker.
> >
> > I noticed a regression report in bugzilla.kernel.org that afaics nobody
> > acted upon since it was reported about a week ago, that's why I decided
> > to forward it to the lists and all people that seemed to be relevant
> > here. Mario, could you maybe take a look at this? Or is that something
> > for the NVM or ACPI people? Or was this discussed somewhere else
> > already? Or even fixed?
> 
> I've not seenthe report.  Looks like the BIOS sets the StorageD3 flag
> in the ACPI tables in this system but doesn't actually want it,
> which is really strange.  We could add some kind of quirk based on
> DMI matching, but this all seems weird.

I've added some comments into the report.  I would be suspect that this just
uncovered a wider problem and we need to dig into more of all of the
circumstances to confirm.