public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar>
To: linux-kernel@vger.kernel.org, jari.aalto@cante.net
Subject: Re: 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory
Date: Fri, 29 Aug 2008 00:41:41 -0300	[thread overview]
Message-ID: <48B76FF5.6010507@yahoo.com.ar> (raw)

Hi 

(sorry my english)

When booted kernel with no iommu parameter, it uses the iommu gart (from amd) and the size of the aperture is 64MB
You can try to grow this size with iommu=memaper=2 for 128MB or 3 for 256MB. I don't have experience with this, but 
i read that this, solves the problem.

I have the similar hardware, but when boot in 64 bits, limit the memory with mem=4G (discarded 0.5G that are (remaped from pci space) beyond 4G)
and iommu=noaperture. (This is not option for you, will be discard 4G of RAM)


Asus M2N32-SLI DELUXE (BIOS Phoenix ver 1603 [12/17/2007])
4 x 1GB OCZ DDR2 PC2-6400 Platinum Rev2 ( OCZ2P800R21G )
AMD Athlon 64 X2 5200+ ( ADA5200IAA6CS ) (stepping F2)

I have realiced some test an posted here (sorry in spanish): http://www.pcmasmas.com/viewtopic.php?t=31445


Buena suerte.


Jari Aalto <jari.aalto <at> cante.net> writes:

> Initially when the PC was installed (and had no IOMMU) options, that
> cause the whole harddisk to corrupt and I had to reinstall everything.
> It might have been a little older kernel (2.6.23?), but I don't recall
> it exactly.

> According to messages in syslog I tried to track down similar incidents
> and found the iommu articles. But the information was like trial and
> error.

> Would you suggest that "immu=off" would be best option?


-- 
Gerardo Exequiel Pozzi ( djgera )
http://www.djgera.com.ar
KeyID: 0x1B8C330D
Key fingerprint = 0CAA D5D4 CD85 4434 A219  76ED 39AB 221B 1B8C 330D


             reply	other threads:[~2008-08-29  3:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29  3:41 Gerardo Exequiel Pozzi [this message]
2008-08-29  6:20 ` 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory Jari Aalto
2008-08-29  7:49 ` Jari Aalto
2008-08-29  8:08   ` Yinghai Lu
  -- strict thread matches above, loose matches on Subject: below --
2008-08-29 18:45 Gerardo Exequiel Pozzi
2008-08-29 21:31 ` Jari Aalto
     [not found] <fa.c8YPWdZHXAabbZwTVLAgq9ahOlE@ifi.uio.no>
     [not found] ` <fa.9B7J3O7801PlFtm4WwuBX/J0kU8@ifi.uio.no>
     [not found]   ` <fa.ES0QYHe349FfrOTaqTun1n3qaYk@ifi.uio.no>
     [not found]     ` <fa.8FK+C3lDiXBnZCV9FTofTkm6PJE@ifi.uio.no>
     [not found]       ` <fa.cN6j0N4TRlTlG7oLEhhT8Wj2N7A@ifi.uio.no>
     [not found]         ` <fa.XwRqZTkk0olSp3UUnbSFZahR4TI@ifi.uio.no>
2008-08-24 21:52           ` Robert Hancock
2008-08-24 22:16             ` Jari Aalto
2008-08-25  0:19               ` Krzysztof Halasa
2008-08-28 20:49                 ` Jari Aalto
2008-08-28 20:59                   ` Yinghai Lu
2008-08-23 10:49 Jari Aalto
2008-08-23 12:31 ` Krzysztof Halasa
2008-08-23 13:58   ` Alistair John Strachan
2008-08-23 15:23     ` Jari Aalto
2008-08-24  8:37     ` Jari Aalto
2008-08-24 13:42       ` Krzysztof Halasa
2008-08-24 15:08         ` Jari Aalto
2008-08-24  8:34   ` Jari Aalto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48B76FF5.6010507@yahoo.com.ar \
    --to=vmlinuz386@yahoo.com.ar \
    --cc=jari.aalto@cante.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox