From: wsj20369 <wsj20369@163.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re:Re: [PATCH] Revert "ACPI: power: Turn off unused power resources unconditionally"
Date: Mon, 17 May 2021 17:45:50 +0800 (CST) [thread overview]
Message-ID: <52c748d4.5c2f.17979b7a960.Coremail.wsj20369@163.com> (raw)
In-Reply-To: <CAJZ5v0g--YTuzHiMTiVwuEH2Z87k+JCmynqqFshZ70yNXuUHew@mail.gmail.com>
At 2021-05-14 22:05:06, "Rafael J. Wysocki" <rafael@kernel.org> wrote:
>On Fri, Apr 30, 2021 at 2:43 PM Shujun Wang <wsj20369@163.com> wrote:
>>
>> This reverts commit 7e4fdeafa61f2b653fcf9678f09935e55756aed2.
>> It may cause some NVMe device probes to fail, and the system may get
>> stuck when using an NVMe device as the root filesystem.
>>
>> In the function nvme_pci_enable(struct nvme_dev *dev), as shown below,
>> readl(NVME_REG_CSTS) always returns -1 with the commit, which results in
>> the probe failed.
>>
>> if (readl(dev->bar + NVME_REG_CSTS) == -1) {
>> result = -ENODEV;
>> goto disable;
>> }
>>
>> dmesg:
>> [ 1.106280] nvme 0000:04:00.0: platform quirk: setting simple suspend
>> [ 1.109111] nvme nvme0: pci function 0000:04:00.0
>> [ 1.113066] nvme 0000:04:00.0: enabling device (0000 -> 0002)
>> [ 1.121040] nvme nvme0: Removing after probe failure status: -19
>>
>> lspci:
>> Non-Volatile memory controller: KIOXIA Corporation Device 0001
>>
>> device uevent:
>> DRIVER=nvme
>> PCI_CLASS=10802
>> PCI_ID=1E0F:0001
>> PCI_SUBSYS_ID=1E0F:0001
>> PCI_SLOT_NAME=0000:04:00.0
>> MODALIAS=pci:v00001E0Fd00000001sv00001E0Fsd00000001bc01sc08i02
>>
>> This patch was tested in Lenovo Thinkpad X1.
>
>Please send me the dmidecode output from this machine or (better)
>attach it at https://bugzilla.kernel.org/show_bug.cgi?id=213019
>
>Thanks!
Hi Rafael:
Sorry for late, I have attached the acpidump and dmidecode in the https://bugzilla.kernel.org/show_bug.cgi?id=213019
BR
Shujun Wang
prev parent reply other threads:[~2021-05-17 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 12:42 Shujun Wang
2021-04-30 13:31 ` Rafael J. Wysocki
2021-04-30 13:46 ` Rafael J. Wysocki
2021-05-10 6:37 ` Zhang, Rui
2021-05-10 12:13 ` Rafael J. Wysocki
2021-05-10 13:59 ` Zhang Rui
2021-05-17 9:48 ` wsj20369
2021-05-14 14:05 ` Rafael J. Wysocki
2021-05-17 9:45 ` wsj20369 [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=52c748d4.5c2f.17979b7a960.Coremail.wsj20369@163.com \
--to=wsj20369@163.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--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
all inboxes | Powered by JetHome®