Re: [PATCH] nvme: log when APST skips a state due to latency cap
From: Michael Bommarito
Date: Tue May 26 2026 - 10:01:33 EST
On Tue, May 26, 2026 at 9:47 AM Keith Busch <kbusch@xxxxxxxxxx> wrote:
> The "_once" is not actually once for each controller; it's just once.
> Some people have found other similar debug prints to be confusing when
> they have multiple controllers since it looks like the seemingly
> problematic controller is not consistent across reboots.
Maybe it makes sense to move this back to print every time, but gate
it behind a boot-time parameter so it doesn't spam normal users?
My use case has been debugging bad suspend/hibernate/PM across
different laptops to figure out which device is bad or needs a quirk.
It would be easy enough to boot with verbose=1 or print_apst_skip=1 or
something like that, collect the details needed to fix the hw, then
reboot.
Thanks,
Mike