Slow resume because of SATA (COMRESET failed) after harddisk upgrade (Seagate Momentus 7200.3) on Thinkpad T61

[Karl Martin]

Binary package hint: linux-source

Hi,

I would like to report a problem that occurred after upgrading the hard disk of my Thinkpad T61 to a Seagate Momentus 7200.3. Although the system suspends without problems it needs quite long for resuming. The message "COMRESET failed" is displayed after several seconds of inactivity. Thereafter, resuming continues normally. Dmesg displays the following error message: "kernel: [ 3.647374] ata3: port is slow to respond, please be patient (Status 0x80)". Resuming in Windows Vista works fine without delay. The problem does also not occur in Ubuntu when the SATA controller is set to "Compatibility Mode" (BIOS).

I had a similar problem some time ago with the old hard disk when resuming with activated SATA power management, However, the current problem also occurs when SATA power management is disabled.

I suspect that the hard drive might not be properly recognized by the kernel as dmesg shows only SATA I speed (1.5 GB/s) although to my knowledge both T61 and the Seagate hard disk should support SATA II. NCQ seems to be properly activated. Deactivating it by "echo 1 > /sys/block/sda/device/queue_depth" did not help.

I would be very happy if somebody could give me a hint how to solve the problem. Many thanks in advance!

Karl Martin

[Karl Martin (klein-km)]

Luckily, using a self-compiled kernel (2.6.26.3) this problem does not occur.

[mlissner (mlissner-michaeljaylissner)]

Do you know what is different in the self-compiled? I am having this same problem, though if I could avoid compiling a kernel, that would be nice.

Thanks.

[Karl Martin (klein-km)]

I suppose that the problem has been fixed in the newer kernel versions. Therefore, the Intrepid kernel should not have this bug.

[Leann Ogasawara (leannogasawara)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue. Thanks.

[Leann Ogasawara (leannogasawara)]

Closing per comment 7 from Karl, the original bug reporter. Thanks.

https://bugs.edge.launchpad.net/ubuntu/+bug/258736/comments/7