Ok, there's no way this is a hardware issue. I have on my desk two idenical Eee 900's. Both have exhibited this issue under Jaunty and both exhibit the issue under Karmic. If I roll them back to karmic and wipe the SSD along the way, the error goes away.
I have now installed 9.10 UNR on one, and have added the 2.6.32 kernel from the links in comment #47.
Ok, there's no way this is a hardware issue. I have on my desk two idenical Eee 900's. Both have exhibited this issue under Jaunty and both exhibit the issue under Karmic. If I roll them back to karmic and wipe the SSD along the way, the error goes away.
I have now installed 9.10 UNR on one, and have added the 2.6.32 kernel from the links in comment #47.
[ 113.816054] ata2: lost interrupt (Status 0x58) a7:8f:09/ 00:00:00: 00:00/e0 tag 0 dma 16384 in a7:8f:09/ 00:00:00: 00:00/e0 Emask 0x2 (HSM violation)
[ 113.820008] ata2: drained 8192 bytes to clear DRQ.
[ 113.835302] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 113.835310] ata2.00: BMDMA stat 0x64
[ 113.835317] ata2.00: failed command: READ DMA
[ 113.835332] ata2.00: cmd c8/00:20:
[ 113.835335] res 58/00:20:
[ 113.835343] ata2.00: status: { DRDY DRQ }
[ 113.835393] ata2: soft resetting link