From: Jonathan Derrick <jonathan.derrick@linux.dev>
To: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>, Len Brown <lenb@kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
m.heingbecker@googlemail.com,
linux-nvme <linux-nvme@lists.infradead.org>,
Nirmal Patel <nirmal.patel@linux.intel.com>
Subject: Re: [Bug] nvme blocks PC10 since v5.15 - bisected
Date: Thu, 10 Feb 2022 11:54:24 -0700 [thread overview]
Message-ID: <79b15466-4fe5-ec2b-5530-e5dbfff52f2b@linux.dev> (raw)
In-Reply-To: <20220210182423.GB16171@lst.de>
On 2/10/2022 11:24 AM, Christoph Hellwig wrote:
> On Thu, Feb 10, 2022 at 06:56:35AM -0800, Keith Busch wrote:
>> Apparently it works fine when you disable VMD, so sounds like the
>> acpi_storage_d3 is set, but we fail to find the correct acpi companion
>> device when it's in a VMD domain.
>
> I guess the acpi_storage_d3 is set on the VMD device and we need
> to propagate that down the entire bus hanging off it.
This is all you needed to say
>
> Which kinda makes sense in the twisted world where vmd was invented,
> given that vmd is Intel's evil plot so that only their Windows driver
> can bind to these devices,
Is this relevant or necessary?
so the property also needs to be set on
> the vmd device.
>
> Nirmal and Jonathan, can you help to sort this mess out?
next prev parent reply other threads:[~2022-02-10 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 19:00 [Bug] nvme blocks PC10 since v5.15 - bisected Rafael J. Wysocki
2022-01-21 21:09 ` Keith Busch
2022-01-27 19:02 ` Rafael J. Wysocki
2022-01-27 19:30 ` Keith Busch
2022-01-27 19:41 ` Rafael J. Wysocki
2022-02-10 14:56 ` Keith Busch
2022-02-10 18:24 ` Christoph Hellwig
2022-02-10 18:54 ` Jonathan Derrick [this message]
2022-02-10 18:54 ` Keith Busch
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=79b15466-4fe5-ec2b-5530-e5dbfff52f2b@linux.dev \
--to=jonathan.derrick@linux.dev \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=m.heingbecker@googlemail.com \
--cc=nirmal.patel@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sagi@grimberg.me \
/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