Tejun Heo writes:
Please give a shot at the attached patch on top of 2.6.22. Thanks.
Patch applied, but still getting the corruption.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Andi Kleen writes:
If it has 2GB or so it might be worth trying booting it with mem=2G
Nope, only 1GB of RAM.
Most likely it is some sort of hardware bug that we might
not be able to do much about. Have you tried contacting SIL or VIA?
No, I haven't. Like I mentioned above, the OpenBSD
Alan Cox writes:
Not suprised to be honest. We have a large number of reports that are all
of the following form
Nvidia chipset, Silicon Image SATA, corruption
and several reports that BIOS updates fixed it. Unfortunately we don't
know what the BIOS updates do (or indeed if what they do
Greetings,
I have been troubleshooting a problem for over a year now, and to make a
long story short, I think the sata_sil driver has a bug during writing when
there are multiple cards that are using different models of SiI chips in the
system.
I will be watching the list, although cc'ing me
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel parameter.
--
tejun
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel parameter.
--
tejun
[EMAIL PROTECTED] writes:
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel
Apologies for the chain-replying to myself, just replying as I think of
things to try.
[EMAIL PROTECTED] writes:
Here's an odd data point.
I just broke that array, formatted all three of those partitions
seperately, mounted and did my ISO copy test.
All three drives, run one at a
