On Wed, 13 Dec 2006, Erik Andersen wrote:
> On Mon Dec 11, 2006 at 10:24:02AM +0100, Karsten Weiss wrote:
> > Last week we did some more testing with the following result:
> >
> > We could not reproduce the data corruption anymore if we boot the machines
> > with the kernel parameter "iommu=soft" i.e. if we use software bounce
> > buffering instead of the hw-iommu. (As mentioned before, booting with
> > mem=2g works fine, too, because this disables the iommu altogether.)
> >
> > I.e. on these systems the data corruption only happens if the hw-iommu
> > (PCI-GART) of the Opteron CPUs is in use.
> >
> > Christoph, Erik, Chris: I would appreciate if you would test and hopefully
> > confirm this workaround, too.
>
> What did you set the BIOS to when testing this setting?
> Memory Hole enabled? IOMMU enabled?
"Memory hole mapping" was set to "hardware". With "disabled" we only
see 3 of our 4 GB memory.
Best regards,
Karsten
--
__________________________________________creating IT solutions
Dipl.-Inf. Karsten Weiss science + computing ag
phone: +49 7071 9457 452 Hagellocher Weg 73
teamline: +49 7071 9457 681 72070 Tuebingen, Germany
email: [email protected] www.science-computing.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
