Compact Flash IDE driver error

lzyking1439

Hello 各位大侠,

我最近的CF卡访问出现了一个访问失败的问题，请路过的各位帮忙分析一下，抛一块砖也行，只要不是臭鸡蛋。
使用环境：
CPU:MP8378
Local bus :Nor flash on CS0, Nand flash on CS1, CPLD on CS2 and Compact flash on CS3, CS3 is in UPM mode.. the Linux kernel: 2.6.30, ext3 fs， ture IDE mode.
现象：
在实验室比较稳定运行了2个多月后有很多的CF卡访问失败，
（1）有一些卡的某些分区挂接不上，分区似乎被损坏了，我用fdisk可以看到该分区，e2fsck可以修复它，但修复后分区里的文件就丢了。
（2）第二种现象是软件开始运行好好的突然出现irq timeout， 然后就变成了只读文件系统。软复位单板可以恢复正常。现象如下：
many Compact flash has error when it's accessed, (1)some of them failed to mount some partition, this lost partition can can be recovered with e2fsck although some files in it dispeared forever.(2)some of them encounter access time-out sudenly, but it can be recoverd when warm/cold reset the system.
the following is the error information:
hda: irq timeout: status=0xd0 { Busy }
hda: possibly failed opcode: 0x30
ide0: reset timed-out, status=0xd0
hda: status timeout: status=0xd0 { Busy }
hda: possibly failed opcode: 0x30
hda: drive not ready for command
ide0: reset timed-out, status=0xd0
end_request: I/O error, dev hda, sector 4225651
end_request: I/O error, dev hda, sector 4225653
Aborting journal on device hda4.
end_request: I/O error, dev hda, sector 4865089
Buffer I/O error on device hda4, logical block 335873
lost page write due to I/O error on hda4
end_request: I/O error, dev hda, sector 4868453
Buffer I/O error on device hda4, logical block 337555
lost page write due to I/O error on hda4
end_request: I/O error, dev hda, sector 4193927
Buffer I/O error on device hda4, logical block 292
lost page write due to I/O error on hda4
journal commit I/O error
ext3_abort called.
EXT3-fs error (device hda4): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only

目前为止还不知道是硬件问题（硬件设计隐患？CF卡bug?）还是IDE驱动的问题。
我尝试在出错时去硬复位CF卡，似乎能够解决一些问题，但如果反复出现错误和反复复位CF卡十几次之后，CF卡又会彻底检测不到，除非掉电复位单板。

以下是e2fsck 的检测结果：
# e2fsck  -n /dev/hda4
e2fsck 1.40.4 (31-Dec-2007)
Warning: skipping journal recovery because doing a read-only filesystem check.
Superblock last mount time is in the future.  Fix? no

Superblock last write time is in the future.  Fix? no

/common contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1315462, counted=1267862).
Fix? no

Free inodes count wrong (16233, counted=15722).
Fix? no


/common: ********** WARNING: Filesystem still has errors **********

/common: 375/16608 files (23.5% non-contiguous), 99234/1414696 blocks
[nemi:/boot] #
Thank you very much.