linux-kernel - Re: "controller is down; will reset" on SK Hynix NVMe drive in Lenovo IdeaPad Pro 5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACbz5yE1RNmJkg-RSBe2u60Y5yd1zxkEZ=pVy_gTa2JLh9d5xQ@mail.gmail.com>
Date: Thu, 20 Nov 2025 14:52:22 +0100
From: Thomas ten Cate <ttencate@...il.com>
To: Keith Busch <kbusch@...nel.org>
Cc: Jens Axboe <axboe@...com>, Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>, 
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: "controller is down; will reset" on SK Hynix NVMe drive in Lenovo
 IdeaPad Pro 5

On Tue, Nov 18, 2025 at 9:49 PM Keith Busch <kbusch@...nel.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.

Still, it's odd that the problem manifested differently, and much less
severely, on an older kernel. ¯\_(ツ)_/¯

I've linked to this thread on the Arch wiki [1] to let others chime
in, in case a single report is not enough evidence to add a quirk to
the driver.

[1] https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Controller_failure_due_to_broken_APST_support