From: Tor Vic <torvic9@mailbox.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@redhat.com" <hpa@redhat.com>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"hdegoede@redhat.com" <hdegoede@redhat.com>
Subject: Re: [PATCH v4] libata: Add ATA_HORKAGE_NO_NCQ_ON_AMD for Samsung 860 and 870 SSD.
Date: Wed, 1 Sep 2021 17:56:57 +0000 [thread overview]
Message-ID: <1e52352c-05e3-700a-58e7-462e1c0adbd1@mailbox.org> (raw)
In-Reply-To: <DM6PR04MB708115B43C231444AFB22DC2E7CD9@DM6PR04MB7081.namprd04.prod.outlook.com>
On 01.09.21 08:13, Damien Le Moal wrote:
> On 2021/09/01 16:38, torvic9@mailbox.org wrote:
>> (Sorry for not doing a proper reply)
>>
>> Hello,
>> Noob here.
>> I have a Samsung 860 Pro connected to a AMD X570 chipset mainboard and
>> it just works flawlessly on 5.13 and 5.14.
>> Are you sure that *every* 860/870 is concerned by this problem on
>> *every* AMD controller? Isn't this too restrictive?
>> Or am I simply missing something?
>
> Is you drive being initialized with NCQ enabled ?
>
> cat /sys/block/sdX/device/queue_depth ?
Samsung 860 Pro:
$ cat /sys/block/sda/device/queue_depth
32
Samsung 860 Evo:
$ cat /sys/block/sdb/device/queue_depth
32
>
>>
>> Thanks,
>> Tor
>>
>
>
next prev parent reply other threads:[~2021-09-01 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 7:37 [PATCH v4] libata: Add ATA_HORKAGE_NO_NCQ_ON_AMD for Samsung 860 and 870 SSD torvic9
2021-09-01 8:13 ` Damien Le Moal
2021-09-01 17:56 ` Tor Vic [this message]
2021-09-01 18:58 ` Martin K. Petersen
2021-09-02 7:44 ` torvic9
2021-09-02 18:41 ` Martin K. Petersen
2021-09-01 8:55 ` Hans de Goede
2021-09-01 9:38 ` Hans de Goede
2021-09-01 11:11 ` torvic9
2021-09-01 17:59 ` Tor Vic
-- strict thread matches above, loose matches on Subject: below --
2021-09-01 4:52 Kate Hsuan
2021-09-01 5:47 ` Damien Le Moal
2021-09-01 6:32 ` Christoph Hellwig
2021-09-01 9:01 ` Hans de Goede
2021-09-01 9:09 ` Kate Hsuan
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=1e52352c-05e3-700a-58e7-462e1c0adbd1@mailbox.org \
--to=torvic9@mailbox.org \
--cc=Damien.LeMoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=hdegoede@redhat.com \
--cc=hpa@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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).