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 15:45:32 -0300	[thread overview]
Message-ID: <48B843CC.1050805@yahoo.com.ar> (raw)

(sorry, my english, again, very BAD!)

(not in mailing-list, please CC to me)


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

>> 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.
>
>See my original bug report, which included experiences with
>memaper. Unofrtunately they didn't help:
>
>    REF: http://article.gmane.org/gmane.linux.kernel/725293 (thread >start)
>
>but I'll try that once more with this 2.6.26 kernel to double check.

No your options are bad,

You have mixed options for "swiotlb" and "amd gart", see the
Documentation/x86_64/boot-options.txt

iommu=soft,memaper=3 swiotlb=65536 BAD.

memaper=3 don't have any effects here, memaper is only for "AMD GART"

The noagp option in this motherboard is redundant.

iommu=noagp,noaperture,off swiotlb=512M BAD combination options!
OFF, OFF, OFF, ON: The result are unknown.

You need to use the IOMMU (from AMD GART) that with your options: you
never used.

When you boot with no iommu options, kernels uses the AMD GART in this
system, with an aperture of 64MB (too small) to fix, you need only one
option: iommu=memaper=3

¡Buena suerte!



>
>> 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)
>
>Interestingly 'noaperture' together with 'noagp' has been the best
>option so far. It gives workign system for about week, but eventually
>the "out of IOMMU space" messages start appear.

>The system has always seen the full 8 GB memory without problems.


-- 
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 18:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-29 18:45 Gerardo Exequiel Pozzi [this message]
2008-08-29 21:31 ` 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory Jari Aalto
2008-12-05  9:07   ` 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory (SOLVED) Jari Aalto
  -- strict thread matches above, loose matches on Subject: below --
2008-08-29  3:41 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory Gerardo Exequiel Pozzi
2008-08-29  6:20 ` Jari Aalto
2008-08-29  7:49 ` Jari Aalto
2008-08-29  8:08   ` Yinghai Lu
     [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=48B843CC.1050805@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