Bug 67721

Summary: SATA driver spew a lot of "hard resetting link" message after suspend cycle on macbook air 6,2
Product: IO/Storage Reporter: Lionel Landwerlin (llandwerlin)
Component: Serial ATAAssignee: Tejun Heo (tj)
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 3.12.3 Subsystem:
Regression: No Bisected commit-id:

Description Lionel Landwerlin 2013-12-25 20:44:19 UTC
Hi,

Just noticed a lot of messages in my logs, though the system seems to be working fine.

Dec 25 20:40:44 airy kernel: ata1.00: unexpected _GTF length (8)
Dec 25 20:40:44 airy kernel: ata1.00: unexpected _GTF length (8)
Dec 25 20:40:44 airy kernel: ata1.00: configured for UDMA/33
Dec 25 20:40:44 airy kernel: ata1: EH complete
Dec 25 20:40:44 airy kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
Dec 25 20:40:44 airy kernel: ata1: irq_stat 0x00400000, PHY RDY changed
Dec 25 20:40:44 airy kernel: ata1: SError: { PHYRdyChg }
Dec 25 20:40:44 airy kernel: ata1: hard resetting link
Dec 25 20:40:44 airy kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Dec 25 20:40:44 airy kernel: ata1.00: unexpected _GTF length (8)
Dec 25 20:40:44 airy kernel: ata1.00: unexpected _GTF length (8)
Dec 25 20:40:44 airy kernel: ata1.00: configured for UDMA/33
Dec 25 20:40:44 airy kernel: ata1: EH complete
Dec 25 20:40:45 airy kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x10000 action 0xe frozen
Dec 25 20:40:45 airy kernel: ata1: irq_stat 0x00400000, PHY RDY changed
Dec 25 20:40:45 airy kernel: ata1: SError: { PHYRdyChg }
Dec 25 20:40:45 airy kernel: ata1: hard resetting link

This is what I get about every second after a suspend cycle on my macbook air 6,2.

Here are the references for the SATA phy :

04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9183 (rev 14)
04:00.0 0106: 1b4b:9183 (rev 14)

I tried fixing this problem by adding libata.force=1:noncq to the command line, it didn't help.

Any idea?
Comment 1 Lionel Landwerlin 2013-12-26 14:29:09 UTC

*** This bug has been marked as a duplicate of bug 62351 ***