From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Simon Arlott <simon@octiron.net>, linux-ide@vger.kernel.org
Cc: Jens Axboe <axboe@kernel.dk>,
open list <linux-kernel@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] ata: Disable queued TRIM for Samsung 860 SSDs
Date: Thu, 16 Jul 2020 02:37:22 +0900 [thread overview]
Message-ID: <CAD14+f0CVzRCJUJBBM=+jQ=UtOhxVJu9naQ9SpgqMqbbaeamiQ@mail.gmail.com> (raw)
In-Reply-To: <9324ef33-eedd-b965-37e8-b82e06778aab@0882a8b5-c6c3-11e9-b005-00805fc181fe>
Hi Simon,
On Wed, Jul 15, 2020 at 8:13 PM Simon Arlott <simon@octiron.net> wrote:
> the original justification for
> enabling appears to be based on marketing material with no explanation
> of what has been changed to make the 860 work properly when the earlier
> 840 and 850 both have the same issue.
Yes, this was why I sent out the patch.
With that said though, I've tested 860 EVO at that time(on i5-6200U,
so it's an Intel SATA controller) for a few weeks both with
asynchronous trim via f2fs and manual synchronous trim via fstrim.
(Since I was also using TLP, the SATA controller and the SSD was
constantly switching between LPM mode and non-LPM.)
My unit did not have any problem whereas both my previous 850 PRO and
850 EVO suffered from issues.
My 860 EVO was just fine with no problem for about 1.5 year until
later I switched to NVMe.
Given how late the bug reports were made after my patch went into
mainline, I wonder if this is firmware-specific.
Thanks.
>
> Signed-off-by: Simon Arlott <simon@octiron.net>
> Cc: Park Ju Hyung <qkrwngud825@gmail.com>
> Cc: stable@vger.kernel.org
> Fixes: ca6bfcb2f6d9 ("libata: Enable queued TRIM for Samsung SSD 860")
> ---
> drivers/ata/libata-core.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index b1cd4d97bc2a..02e861aac5ec 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -3951,6 +3951,8 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> ATA_HORKAGE_ZERO_AFTER_TRIM, },
> { "Samsung SSD 850*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
> ATA_HORKAGE_ZERO_AFTER_TRIM, },
> + { "Samsung SSD 860*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
> + ATA_HORKAGE_ZERO_AFTER_TRIM, },
> { "FCCT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
> ATA_HORKAGE_ZERO_AFTER_TRIM, },
>
> --
> 2.17.1
>
> --
> Simon Arlott
next prev parent reply other threads:[~2020-07-15 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 11:13 [PATCH] ata: Disable queued TRIM for Samsung 860 SSDs Simon Arlott
2020-07-15 17:37 ` Ju Hyung Park [this message]
2020-07-15 20:53 ` Martin K. Petersen
2020-07-15 21:12 ` Simon Arlott
2020-07-15 22:03 ` Ju Hyung Park
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD14+f0CVzRCJUJBBM=+jQ=UtOhxVJu9naQ9SpgqMqbbaeamiQ@mail.gmail.com' \
--to=qkrwngud825@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=simon@octiron.net \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).