Bug#627140: Fixed with unstable kernel

Using kernel 2.6.39-1 from unstable fixed this problem, I can now access my esata drives again.

Bug#627140: linux-image-2.6.38-2-amd64: No longer able to use esata drives

Package: linux-2.6 Version: 2.6.38-5 Severity: important After recent update to kernel 2.6.38-2-amd64 I can no longer use my esata drives, they have worked flawlessly until recent update. This is what always appears in dmesg ata1: exception Emask 0x10 SAct 0x0 SErr 0x405 action 0xe frozen [1

Bug#605395: Follow up

Sorry, strike the info I gave earlier, I got confused. The express cards I tried earlier were both dual port cards, it's just that one was xpress54 and one 34, they both have the same id. and both exhibit the same problem I guess because they are basically the same card. The single port card

Bug#605395: linux-image-2.6.32-5-amd64: JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot

Package: linux-2.6 Version: 2.6.32-28 Severity: important dmesg becomes completely filled with this message with only a couple of hours uptime, the messages start to appear immediately after boot, sometimes whilst booting. If booting to a command prompt, the messages just keep filling up the termi