NVMe suspend failure
Keith Busch
kbusch at kernel.org
Mon Feb 5 09:58:14 PST 2024
On Sat, Feb 03, 2024 at 05:44:03PM -0800, Bart Van Assche wrote:
> On 2/3/24 17:18, Keith Busch wrote:
> > And this is happening during a suspend? What kind of suspend? Like an
> > S3/S4, or idle suspend?
>
> I'm not sure how to determine this? This is what I found in the logs:
>
> Feb 03 09:02:20 asus systemd-logind[1208]: The system will suspend now!
> Feb 03 09:02:20 asus systemd-logind[1208]: Unit suspend.target is masked,
> refusing operation.
I am not sure what the "suspend now!" message means to the driver. Your
initial report with the "CSTS=0xfffffff" comes from the nvme request
timeout handler, so I'd want to confirm what command is timing out, and
what path dispatched it: was the command dispatched from nvme_suspend()
path, or is this coming from somewhere else? If somewhere else, was it
dispatched before or after the nvme_suspend?
More information about the Linux-nvme
mailing list