Re: data corruption with nvidia chipsets and IDE/SATA drives // memory hole mapping related bug?!

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 can confirm this,...
booting with mem=2G => works fine,...

(all of the following tests were made with memory hole mapping=hardware
in the BIOS,.. so I could access my full ram):
booting with iommu=soft => works fine
booting with iommu=noagp => DOESN'T solve the error
booting with iommu=off => the system doesn't even boot and panics

When I set IOMMU to disabled in the BIOS the error is not solved-
I tried to set bigger space for the IOMMU in the BIOS (256MB instead of
64MB),.. but it does not solve the problem.

Any ideas why iommu=disabled in the bios does not solve the issue?

I.e. on these systems the data corruption only happens if the hw-iommu
(PCI-GART) of the Opteron CPUs is in use.

1) And does this now mean that there's an error in the hardware (chipset
or CPU/memcontroller)?


Christoph, Erik, Chris: I would appreciate if you would test and hopefully
confirm this workaround, too.

Yes I can absolutely confirm this...
Do my additional tests help you?



Do you have any ideas why the issue doesn't occur (even with memhole
mapping=hardware in the bios and no iommu=soft at kernel command line)
when dma is disabled for the disks (or a slower dma mode is used)?


Chris.
begin:vcard
fn:Mitterer, Christoph Anton
n:Mitterer;Christoph Anton
email;internet:calestyo@xxxxxxxxxxxx
x-mozilla-html:TRUE
version:2.1
end:vcard

Relevant Pages

  • Re: Suggestions for PII 400 boot failure
    ... I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. ... burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. ... It just don't like booting to that OS." ... The first thing your PC does after being powered on or when rebooting is the motherboard BIOS ROM chip gets control and it interrogates all the hardware ports on the motherboard to determine what I/O devices are attached. ...
    (freebsd-questions)
  • Re: Windows server 2003 service pack 1 problems
    ... You can get through part of the boot, ... Booting in safe mode ends with the same effect. ... So I went to the BIOS and configured the BIOS with the setting saying ...
    (microsoft.public.windowsupdate)
  • Re: Bios chip update suggestions
    ... It's bio's do not allow booting from a usb memory stick. ... bios doesn't know anything about operating system. ... Just boot from ...
    (freebsd-questions)
  • Re: S-ATA & P-ATA booting
    ... Not too familiar with the 945 chipset but my Nvidea chipset mobo Bios allows me to set either PATA or SATA drive to boot from as well as drive boot order...1st choice. ... If you are contemplating adding the 1TB HD to the new system and just dual booting in that manner you would need to enter the BIOS each time to chose which HD to boot from. ... With a HD from another older system installed in this manner all of the drivers required would be missing/different...a repair install of XP would be necessary. ...
    (microsoft.public.windowsxp.hardware)
  • Re: 2 wondows versions detected on pc startup?
    ... if not put there by the BIOS? ... BIOS examines the very first sector of the disk for a Master Boot Record ... table which describes the layout of the fixed disk and the partition loader ... This is where Windows and NTLDR comes in, ...
    (microsoft.public.windowsxp.setup_deployment)