From: Keith Busch <kbusch@kernel.org>
To: Thomas ten Cate <ttencate@gmail.com>
Cc: Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: "controller is down; will reset" on SK Hynix NVMe drive in Lenovo IdeaPad Pro 5
Date: Thu, 20 Nov 2025 14:04:17 -0700 [thread overview]
Message-ID: <aR-CUUzWzQKIAfqx@kbusch-mbp> (raw)
In-Reply-To: <CACbz5yE1RNmJkg-RSBe2u60Y5yd1zxkEZ=pVy_gTa2JLh9d5xQ@mail.gmail.com>
On Thu, Nov 20, 2025 at 02:52:22PM +0100, Thomas ten Cate wrote:
> On Tue, Nov 18, 2025 at 9:49 PM Keith Busch <kbusch@kernel.org> wrote:
> >
> > The "report a bug" message was originally pointed at hardware vendors
> > rather than kernel. Something is wrong with the SSD, the PCIe slot, or
> > both if the power features cause the endpoint to drop off the bus. The
> > only recourse we have in the nvme driver is a quirk to disable APST for
> > the device. The driver doesn't control the PCIe ASPM settings though, so
> > that would have to be a different quirk if it's really necessary. Do you
> > need all three of those parameters, or is disabling the nvme driver's
> > apst sufficient on its own? These parameters do have a negative impact
> > on your machine's power consumption, so you'd usually want to hone in if
> > it's just the deepest power state or if every power saving feature
> > really needs to be disabled.
>
> Thanks for your reply!
>
> Just `nvme_core.default_ps_max_latency_us=0` appears to be sufficient,
> so presumably it's the drive, not the bus. I wouldn't even know where
> to begin reporting a bug to the manufacturer.
I assume vendor 0x1c5c for SK Hynix, but we also need the device id to
make a quirk. You can get that info from sysfs, for example if your
device is enumerated as "nvme0":
# cat /sys/class/nvme/nvme0/device/device
There's two quirks we can try: NVME_QUIRK_NO_DEEPEST_PS first, then
NVME_QUIRK_NO_APST if the first one wasn't successful.
next prev parent reply other threads:[~2025-11-20 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 13:39 "controller is down; will reset" on SK Hynix NVMe drive in Lenovo IdeaPad Pro 5 Thomas ten Cate
2025-11-18 20:49 ` Keith Busch
2025-11-20 13:52 ` Thomas ten Cate
2025-11-20 21:04 ` Keith Busch [this message]
2025-11-21 13:06 ` Thomas ten Cate
2025-11-24 19:52 ` Keith Busch
2025-12-15 12:15 ` Thomas ten Cate
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=aR-CUUzWzQKIAfqx@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=ttencate@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.