From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gabriele Mazzotta Subject: Re: SATA link power management issues Date: Mon, 12 Jan 2015 18:15:52 +0100 Message-ID: <1606112.gp6iaYBghU@xps13> References: <3352987.ugV1Ipy7Z5@xps13> <3361938.rq9uq9yRiO@xps13> <20150112170734.GA22156@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: Received: from mail-wi0-f181.google.com ([209.85.212.181]:52986 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750963AbbALRPz (ORCPT ); Mon, 12 Jan 2015 12:15:55 -0500 In-Reply-To: <20150112170734.GA22156@htj.dyndns.org> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org On Monday 12 January 2015 12:07:34 Tejun Heo wrote: > Hello, Gabriele. > > On Mon, Jan 12, 2015 at 06:03:41PM +0100, Gabriele Mazzotta wrote: > > I tried it and got the same result: > > > > [ 451.077463] ahci 0000:00:1f.2: port does not support device sleep > > [ 452.162451] ata3.00: exception Emask 0x10 SAct 0x400 SErr 0x50000 action 0xe frozen > > [ 452.162461] ata3.00: irq_stat 0x00400008, PHY RDY changed > > [ 452.162467] ata3: SError: { PHYRdyChg CommWake } > > [ 452.162473] ata3.00: failed command: WRITE FPDMA QUEUED > > [ 452.162484] ata3.00: cmd 61/58:50:98:7c:4b/00:00:17:00:00/40 tag 10 ncq 45056 out > > res 40/00:54:98:7c:4b/00:00:17:00:00/40 Emask 0x10 (ATA bus error) > > [ 452.162489] ata3.00: status: { DRDY } > > [ 452.162497] ata3: hard resetting link > > [ 452.886958] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) > > [ 452.890384] ata3.00: configured for UDMA/133 > > [ 452.902976] ahci 0000:00:1f.2: port does not support device sleep > > [ 452.903002] ata3: EH complete > > Hah, that's weird. Can you please double check that you're actually > running the patched kernel by throwing in a printk around the > commented out section? If leaving phy irqs turned off doesn't make > the problem go away, I'm not sure there's much we can do. Hmmm... one > option could be holding off speed-down verdict after LPM state > transition, but it looks like the ssd in question is misbehaving > pretty badly. > > Thanks. Done: [ 168.515793] ahci 0000:00:1f.2: port does not support device sleep [ 168.515800] Skip turn PHYRDY IRQ back on [ 168.515802] turn PHYRDY IRQ back on skipped [ 168.523793] ata3.00: exception Emask 0x10 SAct 0x40 SErr 0x50000 action 0xe frozen [ 168.523798] ata3.00: irq_stat 0x00400008, PHY RDY changed [ 168.523801] ata3: SError: { PHYRdyChg CommWake } [ 168.523805] ata3.00: failed command: WRITE FPDMA QUEUED [ 168.523811] ata3.00: cmd 61/28:30:68:60:4b/00:00:17:00:00/40 tag 6 ncq 20480 out res 40/00:34:68:60:4b/00:00:17:00:00/40 Emask 0x10 (ATA bus error) [ 168.523814] ata3.00: status: { DRDY } [ 168.523819] ata3: hard resetting link [ 169.248384] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 169.251661] ata3.00: configured for UDMA/133 [ 169.264293] ahci 0000:00:1f.2: port does not support device sleep [ 169.264299] Skip turn PHYRDY IRQ back on [ 169.264301] turn PHYRDY IRQ back on skipped [ 169.264315] ata3: EH complete