Monday, June 29, 2009, 4:53:49 PM, Alan Cox wrote:
> The only other thing I can see is the way it hangs around waiting a bit
> for the DMA to finish after the DMA completion event occurs - that might
> be your problem if they goofed and reported DMA complete too early.
Thank you very much for your advices. Reading from disk works fine now
but writing attempt results in a series of similar error messages.
What is the meaning of this error? Is there any documentation that may
be useful to understand libata error messages?
~ # cp /hdd/c/Test/test.dat /hdd/d
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x6
ata1.00: cmd 35/00:98:40:6f:fe/00:01:20:00:00/e0 tag 0 dma 208896 out
res 50/00:00:d7:70:fe/00:00:20:00:00/e0 Emask 0x20 (host bus error)
ata1.00: status: { DRDY }
jasper_set_piomode: devno = 0
jasper_tune_chipset: slave = 0 speed = 0x0c
jasper_set_dmamode: devno = 0
jasper_tune_chipset: slave = 0 speed = 0x22
ata1.00: configured for MWDMA2
ata1: EH complete
sd 0:0:0:0: [sda] 586070255 512-byte hardware sectors (300068 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata1.00: BMDMA stat 0x6
ata1.00: cmd 35/00:a0:b0:72:fe/00:01:20:00:00/e0 tag 0 dma 212992 out
res 50/00:00:4f:74:fe/00:00:20:00:00/e0 Emask 0x20 (host bus error)
ata1.00: status: { DRDY }
jasper_set_piomode: devno = 0
jasper_tune_chipset: slave = 0 speed = 0x0c
jasper_set_dmamode: devno = 0
jasper_tune_chipset: slave = 0 speed = 0x22
ata1.00: configured for MWDMA2
ata1: EH complete
--
Best regards,
Andrei mailto:andrei.martynov@xxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
