linux-kernel - Re: [PATCH 2/3] libata: Add firmware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAPeXnHtVZ-fuzxYiCFBTn_5g_z+mbLHGnD5yQpam_3Ypjfv0HQ@mail.gmail.com>
Date:	Mon, 11 May 2015 13:34:40 -0700
From:	Matthew Garrett <matthew.garrett@...eos.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Matthew Garrett <mjg59@...eos.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, kristen@...ux.intel.com,
	sgunderson@...foot.com
Subject: Re: [PATCH 2/3] libata: Add firmware_default LPM policy

On Mon, May 11, 2015 at 1:28 PM, Tejun Heo <tj@...nel.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@...eos.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/