Comment 18 for bug 469837

Hi again~ Is it possible that a problem with the hardware could be related?

I've had this error continuously happen every few seconds for as long as I can tell (since Jaunty), but didn't do anything because it didn't affect anything that I could see...

I'm not sure, but I'm guessing it's an error about something wrong with my HDD?

From dmesg:
[11752.144071] ata3.00: qc timeout (cmd 0xa0)
[11752.144112] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[11752.144122] ata3.00: irq_stat 0x40000001
[11752.144147] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[11752.144151] cdb 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[11752.144154] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[11752.144163] ata3.00: status: { DRDY ERR }
[11752.144178] ata3: hard resetting link
[11752.628060] ata3: softreset failed (device not ready)
[11752.628073] ata3: applying SB600 PMP SRST workaround and retrying
[11752.792065] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[11752.806957] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[11752.822474] ata3.00: SB600 AHCI: limiting to 255 sectors per cmd
[11752.822487] ata3.00: configured for PIO0
[11752.824540] ata3: EH complete

I hope it isn't harmful to my HDD...

Thanks and have a good day~! ^^