From: Hans Zhang <hans.zhang@cixtech.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: Fix system hang when ASPM L1 is enabled during suspend
Date: Sat, 3 May 2025 00:04:43 +0800 [thread overview]
Message-ID: <87820fb9-cfd4-4b7c-b015-9626d5253a5f@cixtech.com> (raw)
In-Reply-To: <zbjd6ee22eqdu2caajq5gcwfqmq3vzz4down5jhxx7tsryu2at@ywng3qn5bbas>
On 2025/5/2 23:45, Manivannan Sadhasivam wrote:
> On Fri, May 02, 2025 at 11:20:51AM +0800,hans.zhang@cixtech.com wrote:
>> From: Hans Zhang<hans.zhang@cixtech.com>
>>
>> When PCIe ASPM L1 is enabled (CONFIG_PCIEASPM_POWERSAVE=y), certain
>> NVMe controllers fail to release LPI MSI-X interrupts during system
>> suspend, leading to a system hang. This occurs because the driver's
>> existing power management path does not fully disable the device
>> when ASPM is active.
>>
> Why can't you add quirks for those NVMe devices instead?
>
Dear Mani,
static int nvme_init_identify(struct nvme_ctrl *ctrl)
if (!ctrl->identified) {
for (i = 0; i < ARRAY_SIZE(core_quirks); i++) {
if (quirk_matches(id, &core_quirks[i]))
ctrl->quirks |= core_quirks[i].quirks;
}
quirk_matches needs to match the vid of each NVMe SSD. At present, I
have added all the vid available on the market to the quirks table,
which seems very unreasonable.
Best regards,
Hans
prev parent reply other threads:[~2025-05-02 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 3:20 [PATCH] nvme-pci: Fix system hang when ASPM L1 is enabled during suspend hans.zhang
2025-05-02 15:00 ` Bjorn Helgaas
2025-05-02 15:49 ` Hans Zhang
2025-05-02 15:58 ` Manivannan Sadhasivam
2025-05-02 16:07 ` Hans Zhang
2025-05-02 16:20 ` Hans Zhang
2025-05-02 18:05 ` Manivannan Sadhasivam
2025-05-03 14:36 ` Hans Zhang
2025-05-02 15:45 ` Manivannan Sadhasivam
2025-05-02 16:04 ` Hans Zhang [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=87820fb9-cfd4-4b7c-b015-9626d5253a5f@cixtech.com \
--to=hans.zhang@cixtech.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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