Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753251AbbEKUer (ORCPT ); Mon, 11 May 2015 16:34:47 -0400 Received: from mail-ob0-f178.google.com ([209.85.214.178]:35765 "EHLO mail-ob0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753034AbbEKUel (ORCPT ); Mon, 11 May 2015 16:34:41 -0400 MIME-Version: 1.0 In-Reply-To: <20150511202830.GH11388@htj.duckdns.org> References: <1429370796-5881-1-git-send-email-mjg59@coreos.com> <1429370796-5881-3-git-send-email-mjg59@coreos.com> <20150422144812.GA10592@htj.duckdns.org> <20150511202830.GH11388@htj.duckdns.org> Date: Mon, 11 May 2015 13:34:40 -0700 Message-ID: Subject: Re: [PATCH 2/3] libata: Add firmware_default LPM policy From: Matthew Garrett To: Tejun Heo Cc: Matthew Garrett , Linux Kernel Mailing List , linux-ide@vger.kernel.org, kristen@linux.intel.com, sgunderson@bigfoot.com Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 886 Lines: 19 On Mon, May 11, 2015 at 1:28 PM, Tejun Heo wrote: > CommWake isn't the problem here. SError is being dumped just for > information. The disk is reporting failure on a write command which > is diagnosed as "device error" and thus the link is not reset. It's > really the device actively reporting command failure. Ok, that makes sense. Is there any practical way for us to identify why the device might be doing that? It seems to be limited to the LPM case, but this is (theoretically) in the same configuration that the firmware programmed, so it's a little surprising. -- Matthew Garrett | matthew.garrett@coreos.com -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/