[ASRock Z97X Killer] Booting takes 90 seconds, ata2: COMRESET failed (errno=-16)

[uniphirios]

booting to linux with intel SSD takes a good 90 seconds, thanks to COMRESET failed error.

just like https://bugs.launchpad.net/ubuntu/+source/linux/+bug/991040

[ 6.088180] ata2: link is slow to respond, please be patient (ready=0)
[ 10.734832] ata2: COMRESET failed (errno=-16)
[ 16.093275] ata2: link is slow to respond, please be patient (ready=0)
[ 20.739926] ata2: COMRESET failed (errno=-16)
[ 26.098372] ata2: link is slow to respond, please be patient (ready=0)
[ 55.769754] ata2: COMRESET failed (errno=-16)
[ 55.769758] ata2: limiting SATA link speed to 1.5 Gbps
[ 56.089669] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.089951] ata2.00: ATA-7: INTEL SSDSA2MH160G1GC, 045C8820, max UDMA/133
[ 56.089952] ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31)
[ 56.090264] ata2.00: configured for UDMA/133
[ 56.090400] scsi 1:0:0:0: Direct-Access ATA INTEL SSDSA2MH16 8820 PQ: 0 ANSI: 5
[ 56.090656] sd 1:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 56.090659] sd 1:0:0:0: Attached scsi generic sg2 type 0

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-24-generic 3.16.0-24.32
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: joo 2436 F.... pulseaudio
 /dev/snd/controlC0: joo 2436 F.... pulseaudio
CurrentDesktop: KDE
Date: Wed Nov 5 23:18:22 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-11-02 (3 days ago)
InstallationMedia: It
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=36386c27-b41b-4a9f-b01e-7ba413603f35 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-24-generic N/A
 linux-backports-modules-3.16.0-24-generic N/A
 linux-firmware 1.138
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/16/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: Z97X Killer
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/16/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97XKiller:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

uniphirios, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing in your release) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[uniphirios (jooel-nieminen)]

v3.18-rc2-utopic doesn't boot at all.

[penalvch (penalvch)]

uniphirios, the latest mainline kernel is 3.18-rc3, not rc2.

[uniphirios (jooel-nieminen)]

ok, sorry, will try that. I went with the latest utopic. and as that didn't boot at all, tried 3.17, which has the same issue:
[ 6.191346] ata2: link is slow to respond, please be patient (ready=0)
[ 10.838006] ata2: COMRESET failed (errno=-16)
[ 16.196441] ata2: link is slow to respond, please be patient (ready=0)
[ 20.843101] ata2: COMRESET failed (errno=-16)
[ 26.201536] ata2: link is slow to respond, please be patient (ready=0)
[ 55.872927] ata2: COMRESET failed (errno=-16)
[ 55.872940] ata2: limiting SATA link speed to 1.5 Gbps
[ 56.192830] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.193115] ata2.00: ATA-7: INTEL SSDSA2MH160G1GC, 045C8820, max UDMA/133
[ 56.193117] ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31)
[ 56.193429] ata2.00: configured for UDMA/133
[ 56.193533] scsi 1:0:0:0: Direct-Access ATA INTEL SSDSA2MH16 8820 PQ: 0 ANSI: 5

will try the 3.18.RC3 now.

[uniphirios (jooel-nieminen)]

with linux-image-3.18.0-031800rc3-generic I get the exact same.
am I wrong if I presume this is an intel firmware issue as all the issues this far I have seen have been with intel SSD's?

[ 2.548521] Switched to clocksource tsc
[ 6.211268] ata2: link is slow to respond, please be patient (ready=0)
[ 10.857917] ata2: COMRESET failed (errno=-16)
[ 16.216362] ata2: link is slow to respond, please be patient (ready=0)
[ 20.863013] ata2: COMRESET failed (errno=-16)
[ 26.221457] ata2: link is slow to respond, please be patient (ready=0)
[ 55.892841] ata2: COMRESET failed (errno=-16)
[ 55.892844] ata2: limiting SATA link speed to 1.5 Gbps
[ 56.212752] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 56.213137] ata2.00: ATA-7: INTEL SSDSA2MH160G1GC, 045C8820, max UDMA/133
[ 56.213139] ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31)
[ 56.213541] ata2.00: configured for UDMA/133
[ 56.213638] scsi 1:0:0:0: Direct-Access ATA INTEL SSDSA2MH16 8820 PQ: 0 ANSI: 5
[ 56.213735] sd 1:0:0:0: [sdc] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 56.213743] sd 1:0:0:0: [sdc] Write Protect is off
[ 56.213744] sd 1:0:0:0: [sdc] Mode Sense: 00 3a 00 00
[ 56.213756] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 56.213764] sd 1:0:0:0: Attached scsi generic sg2 type 0

[penalvch (penalvch)]

uniphirios, so we have the information. could you please execute the following in a terminal, and post the results here:
sudo hdparm -I /dev/sda

[uniphirios (jooel-nieminen)]

you sure you want that as it's not the same SSD?

[uniphirios (jooel-nieminen)]

/dev/sdc:

ATA device, with non-removable media
        Model Number: INTEL SSDSA2MH160G1GC
        Serial Number: CVEM9385013G160PGN
        Firmware Revision: 045C8820
        Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6
Standards:
        Used: ATA/ATAPI-7 T13 1532D revision 1
        Supported: 7 6 5 4
Configuration:
        Logical max current
        cylinders 16383 16383
        heads 16 16
        sectors/track 63 63
        --
        CHS current addressable sectors: 16514064
        LBA user addressable sectors: 268435455
        LBA48 user addressable sectors: 312581808
        Logical Sector size: 512 bytes
        Physical Sector size: 512 bytes
        device size with M = 1024*1024: 152627 MBytes
        device size with M = 1000*1000: 160041 MBytes (160 GB)
        cache/buffer size = unknown
        Nominal Media Rotation Rate: Solid State Device
Capabilities:
        LBA, IORDY(can be disabled)
        Queue depth: 31
        Standby timer values: spec'd by Standard, no device specific minimum
        R/W multiple sector transfer: Max = 16 Current = 16
        DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
             Cycle time: min=120ns recommended=120ns
        PIO: pio0 pio1 pio2 pio3 pio4
             Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
        Enabled Supported:
           * SMART feature set
                Security Mode feature set
           * Power Management feature set
           * Write cache
           * Look-ahead
           * Host Protected Area feature set
           * WRITE_BUFFER command
           * READ_BUFFER command
           * NOP cmd
           * DOWNLOAD_MICROCODE
           * 48-bit Address feature set
           * Device Configuration Overlay feature set
           * Mandatory FLUSH_CACHE
           * FLUSH_CACHE_EXT
           * SMART error logging
           * SMART self-test
           * General Purpose Logging feature set
           * 64-bit World wide name
           * IDLE_IMMEDIATE with UNLOAD
           * WRITE_UNCORRECTABLE_EXT command
           * {READ,WRITE}_DMA_EXT_GPL commands
           * Segmented DOWNLOAD_MICROCODE
           * Gen1 signaling speed (1.5Gb/s)
           * Gen2 signaling speed (3.0Gb/s)
           * Native Command Queueing (NCQ)
                Device-initiated interface power management
           * Software settings preservation
Security:
        Master password revision code = 65534
                supported
        not enabled
        not locked
                frozen
        not expired: security count
                supported: enhanced erase
        2min for SECURITY ERASE UNIT. 2min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50015179590925fe
        NAA : 5
        IEEE OUI : 001517
        Unique ID : 9590925fe
Checksum: correct

[uniphirios (jooel-nieminen)]

related https://communities.intel.com/thread/53851

[penalvch (penalvch)]

uniphirios, just to clarify, the scope of this report is only going to be with the initial hardware you originally reported with, not every permutation of hardware, disk you may have. Hence, is the information you provided in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389958/comments/10 the drive this issue is reproducible with?

[uniphirios (jooel-nieminen)]

seriously?
if you read the initial bug report, you will see that this is exactly the same drive.

no hardware changes have taken place, which is why sdc was reported and not sda, which is a kingston ssd.

[penalvch (penalvch)]

uniphirios, your previous comments were vague in meaning, in that it appeared you were posting the results of a different SSD drive, not the same one you initially reported against.

Despite this, have you checked for a firmware update for your SSD drive yet?

[uniphirios (jooel-nieminen)]

yes.

[penalvch (penalvch)]

uniphirios, and the results were?

[uniphirios (jooel-nieminen)]

that there is no newer firmware available. this is also why I linked the intel communities.
it is a current issue, if you cared to read.

https://communities.intel.com/thread/53851

[penalvch (penalvch)]

uniphirios, as you may have noticed, it asks to file a Web Ticket with Intel. Were you given a case number when you filed this previously with Intel?

[uniphirios (jooel-nieminen)]

I never said I filed this with intel.
I said there is a related discussion on intel site. and on a later comment I pointed it out again as it PROVES this is the latest firmware.
I have not discussed this with intel and I never promised to do so.

the web is full of these issues if you just care to search for them.

[penalvch (penalvch)]

uniphirios, please file a report with Intel as you were already advised to do. You are welcome to put the case number here for tracking.

However, unless there is an extreme circumstance, the linux community wouldn't investigate coding a WORKAROUND to poorly written firmware, if it's even technically possible -> Won't Fix.

[uniphirios (jooel-nieminen)]

seriously?
I was not adviced to do it. again it wasn't me. some people seem to have issues understanding what they are reading