PCIE SATA controller ASM1062 problems or software

[Nikolay_Po]

Emask=0x10 probably can be deciphered by an enumerator of current linux source torvalds/linux/include/linux/libata.h:

Code:

enum ata_completion_errors {
AC_ERR_DEV = (1 << 0), /* device reported error */
AC_ERR_HSM = (1 << 1), /* host state machine violation */
AC_ERR_TIMEOUT = (1 << 2), /* timeout */
AC_ERR_MEDIA = (1 << 3), /* media error */
AC_ERR_ATA_BUS = (1 << 4), /* ATA bus error */
AC_ERR_HOST_BUS = (1 << 5), /* host bus error */
AC_ERR_SYSTEM = (1 << 6), /* system error */
AC_ERR_INVALID = (1 << 7), /* invalid argument */
AC_ERR_OTHER = (1 << 8), /* unknown */
AC_ERR_NODEV_HINT = (1 << 9), /* polling device detection hint */
AC_ERR_NCQ = (1 << 10), /* marker for offending NCQ qc */
};

0x10 means 4-th bit is set, ATA bus error. Not a device reported error, not an SBC failure, not a drive media failure, not an SBC bus (PCIe) error, not an unknown error. Exactly ATA bus error. This is mean that the SATA controller itself has reported a bus error. Looking forward...

---

SErr=0x4040000 means two bits of SATA error register are set, 18-th and 26-th.
Intel's SATA AHCI standard draft available says that the problem is:

• A Comm Wake signal was detected by the Phy;
  
• A COMINIT signal was received.
  

Can't say the signals are abnormal themself. They are not an errors like CRC or protocol failures. But these signals are not expected right now by libata code.