From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Patrick McLean <chutzpah@gentoo.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: libata-core: Disable READ LOG DMA EXT for Samsung MZ7LH
Date: Tue, 14 Feb 2023 10:33:23 +0900 [thread overview]
Message-ID: <b7626a3c-cf6b-45a2-0342-3bafa8090dcf@opensource.wdc.com> (raw)
In-Reply-To: <20230213121745.2847a9ff@moya.linuxfreak.ca>
On 2/14/23 05:17, Patrick McLean wrote:
> On Sat, 11 Feb 2023 12:11:48 +0900
> Damien Le Moal <damien.lemoal@opensource.wdc.com> wrote:
>
>> On 2/11/23 06:51, Patrick McLean wrote:
>>> Samsung MZ7LH drives are spewing messages like this in to dmesg with AMD
>>> SATA controllers:
>>>
>>> ata1.00: exception Emask 0x0 SAct 0x7e0000 SErr 0x0 action 0x6 frozen
>>> ata1.00: failed command: SEND FPDMA QUEUED
>>> ata1.00: cmd 64/01:88:00:00:00/00:00:00:00:00/a0 tag 17 ncq dma 512 out
>>> res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask
>>> 0x4 (timeout)
>>>
>>> Since this was seen previously with SSD 840 EVO drives in
>>> https://bugzilla.kernel.org/show_bug.cgi?id=203475 let's add the same
>>> fix for these drives as the EVOs have, since they likely have very
>>> similar firmwares.
>>>
>>> Signed-off-by: Patrick McLean <chutzpah@gentoo.org>
>>> ---
>>> drivers/ata/libata-core.c | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
>>> index 2ea572628b1c..c4c89d24f84c 100644
>>> --- a/drivers/ata/libata-core.c
>>> +++ b/drivers/ata/libata-core.c
>>> @@ -4045,6 +4045,9 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
>>> { "Samsung SSD 870*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
>>> ATA_HORKAGE_ZERO_AFTER_TRIM |
>>> ATA_HORKAGE_NO_NCQ_ON_ATI },
>>> + { "SAMSUNG*MZ7LH*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
>>> + ATA_HORKAGE_ZERO_AFTER_TRIM |
>>> + ATA_HORKAGE_NO_NCQ_ON_ATI, },
>>> { "FCCT*M500*", NULL, ATA_HORKAGE_NO_NCQ_TRIM |
>>> ATA_HORKAGE_ZERO_AFTER_TRIM },
>>>
>>
>> Looks OK, but ATA_HORKAGE_NO_NCQ_ON_ATI is for PCI vendor ID 1002h. AMD
>> also has vendor ID 1022h. Did you check you adapter vendor ID & tested
>> this patch ?
>
> We tested this patch, and it resolves the problem for us (we have been
> using it for several months).
OK. Thanks for confirming. Will apply in a little while. Thanks !
>
>> --
>> Damien Le Moal
>> Western Digital Research
>>
>
>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-02-14 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 21:51 Patrick McLean
2023-02-11 3:11 ` Damien Le Moal
2023-02-13 20:17 ` Patrick McLean
2023-02-14 1:33 ` Damien Le Moal [this message]
2023-02-11 3:12 ` Damien Le Moal
2023-02-13 20:16 ` Patrick McLean
2023-02-14 3:27 ` Damien Le Moal
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=b7626a3c-cf6b-45a2-0342-3bafa8090dcf@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=chutzpah@gentoo.org \
--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
all inboxes | Powered by JetHome®