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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Fri, 1 Apr 2022 16:32:20 +0000
From:   "Limonciello, Mario" <Mario.Limonciello@....com>
To:     Christoph Hellwig <hch@....de>,
        Thorsten Leemhuis <regressions@...mhuis.info>
CC:     Jian-Hong Pan <jhp@...lessos.org>,
        "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
        "Rafael J . Wysocki" <rjw@...ysocki.net>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: RE: Bug 215742 - The NVME storage quirked as SIMPLE SUSPEND makes
 system resume failed after suspend (Regression)

[Public]

> -----Original Message-----
> From: Christoph Hellwig <hch@....de>
> Sent: Friday, April 1, 2022 06:27
> To: Thorsten Leemhuis <regressions@...mhuis.info>
> Cc: Limonciello, Mario <Mario.Limonciello@....com>; Jian-Hong Pan
> <jhp@...lessos.org>; regressions@...ts.linux.dev; Christoph Hellwig
> <hch@....de>; linux-kernel@...r.kernel.org; linux-
> nvme@...ts.infradead.org; Rafael J . Wysocki <rjw@...ysocki.net>; ACPI
> Devel Maling List <linux-acpi@...r.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.