[lkml]   [2015]   [May]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/3] libata: Add firmware_default LPM policy
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 |

 \ /
  Last update: 2015-05-11 22:41    [W:0.040 / U:7.548 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site