Comment 14 for bug 761176

Tiago's new kernel does fix the slow problem. However, I got a new problem with the new kernel.

System hang for a while when login, and I got the following error messages in the syslog. It looks like a bug in the new kernel. Once I roll back to the old kernel, it disappeared.

kernel: [ 75.020013] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x40000 action 0x6 frozen
kernel: [ 75.020089] ata1: SError: { CommWake }
kernel: [ 75.020129] ata1.00: failed command: READ FPDMA QUEUED
kernel: [ 75.020168] ata1.00: cmd 60/08:00:20:bc:f1/00:00:36:00:00/40 tag 0 ncq 4096 in
kernel: [ 75.020168] res 40/00:01:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
kernel: [ 75.020227] ata1.00: status: { DRDY }
kernel: [ 75.020245] ata1.00: failed command: READ FPDMA QUEUED
kernel: [ 75.020269] ata1.00: cmd 60/08:08:88:bb:f1/00:00:37:00:00/40 tag 1 ncq 4096 in
kernel: [ 75.020270] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: [ 75.020326] ata1.00: status: { DRDY }
kernel: [ 75.020347] ata1: hard resetting link
kernel: [ 75.369277] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [ 75.681488] ata1.00: both IDENTIFYs aborted, assuming NODEV
kernel: [ 75.681492] ata1.00: revalidation failed (errno=-2)
kernel: [ 80.359207] ata1: hard resetting link
kernel: [ 80.708571] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
kernel: [ 80.711202] ata1.00: configured for UDMA/133
kernel: [ 80.711453] ata1.00: device reported invalid CHS sector 0
kernel: [ 80.711458] ata1.00: device reported invalid CHS sector 0
kernel: [ 80.711469] ata1: EH complete
kernel: [ 80.781582] ppdev: user-space parallel port driver
kernel: [ 80.790844] type=1400 audit(1305127912.864:18): apparmor="STATUS"