From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: Christoph Hellwig <hch@lst.de>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Jian-Hong Pan <jhp@endlessos.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: RE: Bug 215742 - The NVME storage quirked as SIMPLE SUSPEND makes system resume failed after suspend (Regression)
Date: Fri, 1 Apr 2022 16:32:20 +0000 [thread overview]
Message-ID: <BL1PR12MB51571269CB0F40E4257D2232E2E09@BL1PR12MB5157.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220401112649.GA14810@lst.de>
[Public]
> -----Original Message-----
> From: Christoph Hellwig <hch@lst.de>
> Sent: Friday, April 1, 2022 06:27
> To: Thorsten Leemhuis <regressions@leemhuis.info>
> Cc: Limonciello, Mario <Mario.Limonciello@amd.com>; Jian-Hong Pan
> <jhp@endlessos.org>; regressions@lists.linux.dev; Christoph Hellwig
> <hch@lst.de>; linux-kernel@vger.kernel.org; linux-
> nvme@lists.infradead.org; Rafael J . Wysocki <rjw@rjwysocki.net>; ACPI
> Devel Maling List <linux-acpi@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.
prev parent reply other threads:[~2022-04-01 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 7:55 Bug 215742 - The NVME storage quirked as SIMPLE SUSPEND makes system resume failed after suspend (Regression) Thorsten Leemhuis
2022-04-01 11:26 ` Christoph Hellwig
2022-04-01 16:32 ` Limonciello, Mario [this message]
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=BL1PR12MB51571269CB0F40E4257D2232E2E09@BL1PR12MB5157.namprd12.prod.outlook.com \
--to=mario.limonciello@amd.com \
--cc=hch@lst.de \
--cc=jhp@endlessos.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).