Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 9 Nov 2021 12:04:05 -0300
From:   Enzo Matsumiya <ematsumiya@suse.de>
To:     Christoph Hellwig <hch@lst.de>
Cc:     linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
        Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
        linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] nvme: add NO APST quirk for Kioxia device
Message-ID: <20211109150405.uv2he4quk4dlud6p@cyberdelia>
References: <20211106020858.18625-1-ematsumiya@suse.de>
 <20211109080634.GA28581@lst.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20211109080634.GA28581@lst.de>
Precedence: bulk

On 11/09, Christoph Hellwig wrote:
>On Fri, Nov 05, 2021 at 11:08:57PM -0300, Enzo Matsumiya wrote:
>> +	},
>> +	{
>> +		/*
>> +		 * This Kioxia device times out and aborts I/O during any load,
>> +		 * but more easily reproducible with discards (fstrim).
>> +		 *
>> +		 * Device is left in a state that is also not possible to use "nvme set-feature"
>> +		 * to disable APST, but booting with nvme_core.default_ps_max_latency=0 works.
>> +		 */
>
>Overly long lines here, but I can fix that up.

Missed that, sorry. Thanks.

>  Do you have a product
>name for this device or is just a nameless OEM controller?

I didn't, had to google. I see it listed on Kioxia's website as
CD6-V Series (6.4T model), but since customer was running on an
DL380 Gen10, I suspect it could also be HPE PE8030 (PN P19837-B21).


Cheers,

Enzo