Messages in this thread | | | Date | Tue, 25 Sep 2012 12:10:35 -0700 | From | Carlos Moffat <> | Subject | Re: Slow Resume with SSD |
| |
Hi
On 09/25/2012 12:07 PM, Srivatsa S. Bhat wrote: > On 09/26/2012 12:00 AM, Carlos Moffat wrote: >> Hi, >> >> (please let me know if this is the wrong list to ask this) >> >> I have a Crucial M4 512 GB SSD installed on my Thinkpad X220 (Ubuntu >> Precise). Overall this runs very nicely, but it takes 10+ seconds to >> resume from suspend, apparently because some issue with the hardrive. >> The only message I see while resuming is "COMRESET failed (errno=-16)". >> >> [52483.228615] ata1: link is slow to respond, please be patient (ready=0) >> [52487.870616] ata1: COMRESET failed (errno=-16) >> [52488.190222] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) >> [52488.190752] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) >> succeeded >> [52488.190754] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE >> LOCK) filtered out >> [52488.190755] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) >> filtered out >> [52488.191849] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) >> succeeded >> [52488.191855] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE >> LOCK) filtered out >> [52488.191860] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) >> filtered out >> [52488.192406] ata1.00: configured for UDMA/100 >> [52488.206298] sd 0:0:0:0: [sda] Starting disk >> [52488.207334] Extended CMOS year: 2000 >> [52488.208335] PM: resume of devices complete after 10376.896 msecs >> [52488.208552] PM: resume devices took 10.376 seconds >> >> The only relevant post I've found was in the crucial support site: >> >> http://forums.crucial.com/t5/Solid-State-Drives-SSD/SOLVED-M4-CT512M4SSD1-7mm-512Gb-SSD-too-slow-when-laptop-wakes/td-p/102666 >> >> >> which suggested adding libata.force=nohrst as a boot option to get rid >> of the problem. >> >> I tried that, but the laptop wouldn't suspend. >> >> Any ideas? >> > > (Adding relevant people to CC) > > I recall seeing a similar problem getting fixed in mainline quite a long > time ago (around v3.3 I think). Did you try the latest mainline kernel? > > Regards, > Srivatsa S. Bhat >
Yes, I'm using 3.5.4 (Ubuntu Mainline packages).
Carlos
| |