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.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
