Messages in this thread | | | Date | Mon, 11 May 2015 13:34:40 -0700 | Subject | Re: [PATCH 2/3] libata: Add firmware_default LPM policy | From | Matthew Garrett <> |
| |
On Mon, May 11, 2015 at 1:28 PM, Tejun Heo <tj@kernel.org> 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
| |