summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorMikulas Patocka <mpatocka@redhat.com>2009-10-21 08:55:28 +0000
committerDavid S. Miller <davem@davemloft.net>2009-10-29 03:02:06 -0700
commit9bd7496f5dd488e109e91d9d5743915fb4dfbfde (patch)
treec6f33d133a6062e9521240e55ed20eebdc65f2a2 /.gitignore
parent032665a26f5fe230509c4d35bd53f69fb6aa45b0 (diff)
downloadlinux-3.10-9bd7496f5dd488e109e91d9d5743915fb4dfbfde.tar.gz
linux-3.10-9bd7496f5dd488e109e91d9d5743915fb4dfbfde.tar.bz2
linux-3.10-9bd7496f5dd488e109e91d9d5743915fb4dfbfde.zip
ide: Serialize CMD643 and CMD646 to fix a hardware bug with SSD
CMD646 corrupts data on concurrent transfers on both channels when IDE SSD is connected to one of the channels. Setup that demonstrates this hardware bug: Ultra 5, onboard CMD646, rev 3. /dev/hda is 8GB Seagate ST38410A in MWDMA2 /dev/hdd is 32GB SSD SiliconHardDisk in MWDMA2 - When reading /dev/hdd (for example with dd or fsck), reads from /dev/hda are corrupted, there are twiddled single bits 1->0 and some full 32-bit words corrupted, sometimes commands fail (which switches /dev/hda to PIO mode but the corruptions happen even in PIO). - Reads from /dev/hdd don't seem to be corrupted (i.e. fsck passes fine). - When I connected normal rotating harddisk to /dev/hdd, there was no corruption, so the corruption is something specific to SSD. - I tried the same setup on a PCI card with CMD649 and saw no corruption. This patch serializes the operation for CMD646 and 643 (I didn't test CMD643 but it may have the same hw bug too because it's earlier design). CMD649 is good. I don't know anything about CMD 648. Signed-off-by: Mikulas Patocka <mpatocka@redhat.com> Tested-by: Frans Pop <elendil@planet.nl> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions