Return-Path: Received: from mail-qt0-f193.google.com ([209.85.216.193]:43772 "EHLO mail-qt0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751407AbeBRN2e (ORCPT ); Sun, 18 Feb 2018 08:28:34 -0500 Date: Sun, 18 Feb 2018 05:28:30 -0800 From: Tejun Heo To: Hans de Goede Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH] libata: Apply NOLPM quirk to Crucial MX100 512GB SSDs Message-ID: <20180218132830.GG695913@devbig577.frc2.facebook.com> References: <20180216094820.3587-1-hdegoede@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180216094820.3587-1-hdegoede@redhat.com> Sender: stable-owner@vger.kernel.org List-ID: On Fri, Feb 16, 2018 at 10:48:20AM +0100, Hans de Goede wrote: > Various people have reported the Crucial MX100 512GB model not working > with LPM set to min_power. I've now received a report that it also does > not work with the new med_power_with_dipm level. > > It does work with medium_power, but that has no measurable power-savings > and given the amount of people being bitten by the other levels not > working, this commit just disables LPM altogether. > > Note all reporters of this have either the 512GB model (max capacity), or > are not specifying their SSD's size. So for now this quirk assumes this is > a problem with the 512GB model only. > > Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=89261 > Buglink: https://github.com/linrunner/TLP/issues/84 > Cc: stable@vger.kernel.org > Signed-off-by: Hans de Goede Applied to libata/for-4.16-fixes. Thanks. -- tejun