Comment 48 for bug 569680

Bad news everyone... My assumptions about kernel 2.6.32-24 may be wrong... It just failed with the same kind of errors.
I will need to start again my research. Meanwhile... this is today's error report:

Dec 12 13:25:12 kernel: [16294.040083] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 12 13:25:12 kernel: [16294.040095] ata3.00: failed command: READ DMA
Dec 12 13:25:12 kernel: [16294.040108] ata3.00: cmd c8/00:08:df:01:20/00:00:00:00:00/e0 tag 0 dma 4096 in
Dec 12 13:25:12 kernel: [16294.040111] res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Dec 12 13:25:12 kernel: [16294.040117] ata3.00: status: { DRDY }
Dec 12 13:25:17 kernel: [16299.410040] ata3: link is slow to respond, please be patient (ready=0)
Dec 12 13:25:22 kernel: [16304.090043] ata3: device not ready (errno=-16), forcing hardreset
Dec 12 13:25:22 kernel: [16304.090057] ata3: soft resetting link
Dec 12 13:25:27 kernel: [16309.271751] ata3: link is slow to respond, please be patient (ready=0)
Dec 12 13:25:32 kernel: [16314.140114] ata3: SRST failed (errno=-16)
Dec 12 13:25:32 kernel: [16314.140383] ata3: soft resetting link
Dec 12 13:25:37 kernel: [16319.340133] ata3: link is slow to respond, please be patient (ready=0)
Dec 12 13:25:42 kernel: [16324.200032] ata3: SRST failed (errno=-16)
Dec 12 13:25:42 kernel: [16324.200301] ata3: soft resetting link