linux-kernel - Re: [PATCH v3] libata: Apply NOLPM quirk for SAMSUNG MZ7TD256HAFV-000L9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <539a21b1-7d09-4f30-0421-d083d1c48ee4@redhat.com>
Date:   Sun, 28 Oct 2018 11:48:42 +0100
From:   Hans de Goede <hdegoede@...hat.com>
To:     Diego Viola <diego.viola@...il.com>, axboe@...nel.dk
Cc:     tj@...nel.org, linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH v3] libata: Apply NOLPM quirk for SAMSUNG
 MZ7TD256HAFV-000L9

Hi,

On 28-10-18 05:13, Diego Viola wrote:
> On Fri, Oct 26, 2018 at 5:36 PM Diego Viola <diego.viola@...il.com> wrote:
>>
>> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe <axboe@...nel.dk> wrote:
>>>
>>> On 10/26/18 7:45 AM, Diego Viola wrote:
>>>> med_power_with_dipm causes my T450 to freeze with a SAMSUNG
>>>> MZ7TD256HAFV-000L9 SSD (firmware DXT02L5Q).
>>>>
>>>> Switching the LPM to max_performance fixes this issue.
>>>
>>> Applied, thanks.
>>>
>>> --
>>> Jens Axboe
>>>
>>
>> Jens, Hans,
>>
>> Thank you.
>>
>> Diego
> 
> Hi Hans and Jens,
> 
> I just wanted to give you guys an update about this problem.
> 
> I've managed to update my SSD firmware to the latest version[1].
> 
> For running the update, I've had to install Windows 10, ran the
> firmware update, remove Windows and reinstall Arch Linux.
> 
> The latest version of the firmware is DXT04L5Q, and it looks like
> there hasn't been a new update since 2015.
> 
> I'll be running with med_power_with_dipm and hope this firmware update
> fixes the problem, if it doesn't and I get another freeze, I'll send
> another patch blacklisting the drive completely. Is that OK?

Yes, if it still happens with the latest firmware then blacklisting
it completely is the right thing to do.

Unfortunately for reasons which I do not understand OEM SSDs often use
different (customized?) firmware compared to the model on which they
are based and often see less updates and seem to have more bugs :|

Regards,

Hans