[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9pwz4q0m-pSUy7ReWu4nNzxySNcYZrqyDZiTuGxHN=1NQ@mail.gmail.com>
Date: Thu, 9 Jun 2022 10:20:33 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Yi Zhang <yi.zhang@...hat.com>, alan.adamson@...cle.com
Cc: "open list:NVM EXPRESS DRIVER" <linux-nvme@...ts.infradead.org>,
Sagi Grimberg <sagi@...mberg.me>,
LKML <linux-kernel@...r.kernel.org>
Subject: 2 second nvme initialization delay regression in 5.18 [Was: Re: [bug
report]nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) MORE DNR observed
during blktests]
Hi folks,
On Tue, Apr 5, 2022 at 10:00 PM Jason A. Donenfeld <Jason@...c4.com> wrote:
> Using a Samsung SSD 970 EVO Plus 2TB, firmware version 2B2QEXM7, in case
> that's useful info.
>
> I also noticed a ~2 second boot delay on 5.18-rc1:
Just FYI, I am still seeing this delay in 5.19-rc1.
Boot lines from 5.17:
[ 0.882680] nvme nvme1: missing or invalid SUBNQN field.
[ 0.882719] nvme nvme1: Shutdown timeout set to 10 seconds
[ 0.885227] nvme nvme1: 8/0/0 default/read/poll queues
[ 0.887910] nvme1n1: p1 p2 p3
[ 0.888317] nvme nvme0: missing or invalid SUBNQN field.
[ 0.888361] nvme nvme0: Shutdown timeout set to 8 seconds
[ 0.906301] nvme nvme0: 16/0/0 default/read/poll queues
[ 0.910087] nvme0n1: p1 p2
Boot lines from 5.18 & 5.19:
[ 0.846827] nvme nvme1: missing or invalid SUBNQN field.
[ 0.846857] nvme nvme1: Shutdown timeout set to 10 seconds
[ 0.849043] nvme nvme1: 8/0/0 default/read/poll queues
[ 0.851595] nvme1n1: p1 p2 p3
[ 3.226962] nvme nvme0: Shutdown timeout set to 8 seconds
[ 3.253890] nvme nvme0: 16/0/0 default/read/poll queues
[ 3.263778] nvme0n1: p1 p2
The Samsung 970 EVO Plus has a ~2 second delay that wasn't there in 5.17.
Any idea what's going on?
Thanks,
Jason
Powered by blists - more mailing lists