Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp2223739imd; Sun, 28 Oct 2018 05:44:15 -0700 (PDT) X-Google-Smtp-Source: AJdET5f65J6nyRtwWO44/FKIBtYEcjycJc2jsRoXevOwzjJ+43Q+At84QOI1z290UGfnQATep/uy X-Received: by 2002:a17:902:7108:: with SMTP id a8-v6mr2187686pll.290.1540730655700; Sun, 28 Oct 2018 05:44:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540730655; cv=none; d=google.com; s=arc-20160816; b=p9pB6BVZgv1s4sLAlrya37ahjMN0gSVzvWCZkiuPl2BZDE2g3iYGbJVqozCyIlk2Lk eD1x2B1mbgVmYQfC+3RFISBNGc8VxCCSPmLshwt/x1efQJ2qGC8wEzmhIL45a+S4Yny3 xOMXZBwnsWidzwESVKYoeXTw4CD25JHsnrRdXBpXWweHfcFrmxDkjTJt3JrUdYSpBZj3 MDnV/c7b6Tw013HlXhmCc+RQrc1YODqoKoFoXEkUexhdTOLG9dmq01BWMm2M3jxLt7Q0 7rk42nHt5i17ippQycaXRMJNmY8szPy8vieXszbWyWncwwskYhTT5ruUZRG8UsC8l2E3 R4xQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=mvWfHfJBZwvGtnu+XYX6yhLYvwzquy04EJDa09e+OAw=; b=zNubjoBz35rZY7whHSVJn/acs6si6kvf92AmxIgk8R889IbmRda/4m4AsWyQ3leWSy 3aBsQDN8Pzf5Zw45hpwR6vf45UrQVu7zqeltqb/0m4bKisVi7xDxX4eGCfDxitN5a+xK Mrp2GDe2+gS5xz3lr0megSa1+jbyUBt8ZD/sFoZ9E3rjYE05E2Yi11Yrl3d2K0Ujmh4q ap7LyOr1VJ+L3yZQQ8YMVgtl9xBaiRCh0kxxlVK+spQ/EYlsGC3GRMIMTryj9dxxWLtq hPLwNyO4CKSdtOIqdZ50qFh5rBGzb9MPyUo8/i7zyisUb7otWztexrHCZKYtJFwqCV1T XcWA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qqpuT2l+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f19-v6si17293278pgj.334.2018.10.28.05.43.58; Sun, 28 Oct 2018 05:44:15 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=qqpuT2l+; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727008AbeJ1V2H (ORCPT + 99 others); Sun, 28 Oct 2018 17:28:07 -0400 Received: from mail-yw1-f67.google.com ([209.85.161.67]:37214 "EHLO mail-yw1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726379AbeJ1V2G (ORCPT ); Sun, 28 Oct 2018 17:28:06 -0400 Received: by mail-yw1-f67.google.com with SMTP id v77-v6so2293220ywc.4; Sun, 28 Oct 2018 05:43:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=mvWfHfJBZwvGtnu+XYX6yhLYvwzquy04EJDa09e+OAw=; b=qqpuT2l+3E+1bd3GPzdflJ9fqSZlQKcI+yzRm8IGCICsf34xsImwEuZezqbKEbtT7J nJ8+HoGRSS32D0I2Jj7Ozwi9z4rL9Dw1ukxDnVl5/vF4O3qDs1aYxDmr8UTW9tO1Vi1L 2LB8cCZ4aVcQNDYmiaHRMxoxYVVZJcjcH7FIcP/+Z3z5CIve0yr/svpcX7Ag1CrlGtnD PF3uqXJW7aJN6SEiF1yqNgiYNA7NFuUhS+AqVEN+SlXAnnthJwejptLCRXvh6rp0eml5 E2CrP+VQqAIg9qCXfH4iuH4vON9ZYgz3NoDeQOWg4twB3Tc5Z8ctj8EIHxYGcrH0y84l LWcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=mvWfHfJBZwvGtnu+XYX6yhLYvwzquy04EJDa09e+OAw=; b=U9DykvSDyP3W5tmP/Z796xmHO/lNX4ZGIvpV//gzFqHVxxcp8z+O3wQ2yMTIkMqmbV yCXaBbFHhQ0EUd4HvHdcaO/vPBrycdRHMOuj5B2oCQ5xlS6inCOqhGnasBwG/4B9V/dO 3samn1jNQj8g2b4Le0P5cjoweUP98bGZfKxTm0DYNRSVZ9iajFnrWooui+Xv5+cPHpe3 ZSEwqoAijqyx5jPhp6REUpROXL24zrBhJ3vMvku0fw4qqLKic0i/CdsEHXfhaiQ0OJre Ak+v8VcMaeY2oA//YMuLWkV1MWAZ/0AuvZMgG14+5BatUL2EBM6X5VWPSQrlxUm1Lxse LZgQ== X-Gm-Message-State: AGRZ1gINEzs1LlG4ibd6ikLuobMEFKonYfb5ZYEN95llavd/67qHIgjg iruXCLA8Haa2rx1Hdh7rPkobnYH+pQ/nnSK3sak= X-Received: by 2002:a81:2a83:: with SMTP id q125-v6mr1259913ywq.480.1540730613138; Sun, 28 Oct 2018 05:43:33 -0700 (PDT) MIME-Version: 1.0 References: <20181026134516.1234-1-diego.viola@gmail.com> <3d9dd60b-7bfe-bc1c-b971-0935a84dcf45@kernel.dk> <539a21b1-7d09-4f30-0421-d083d1c48ee4@redhat.com> In-Reply-To: <539a21b1-7d09-4f30-0421-d083d1c48ee4@redhat.com> From: Diego Viola Date: Sun, 28 Oct 2018 09:43:21 -0300 Message-ID: Subject: Re: [PATCH v3] libata: Apply NOLPM quirk for SAMSUNG MZ7TD256HAFV-000L9 To: hdegoede@redhat.com Cc: axboe@kernel.dk, tj@kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Hans, On Sun, Oct 28, 2018 at 7:48 AM Hans de Goede wrote: > > Hi, > > On 28-10-18 05:13, Diego Viola wrote: > > On Fri, Oct 26, 2018 at 5:36 PM Diego Viola wrote: > >> > >> On Fri, Oct 26, 2018 at 11:21 AM Jens Axboe 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 I've just got another freeze with the latest firmware while I was watching some YouTube videos. I think it's safe to assume this drive is borked and won't get better, I'll send another patch. Thanks, Diego