public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: Jari Aalto <jari.aalto@cante.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory
Date: Sun, 24 Aug 2008 15:52:44 -0600	[thread overview]
Message-ID: <48B1D82C.5000107@shaw.ca> (raw)
In-Reply-To: <fa.XwRqZTkk0olSp3UUnbSFZahR4TI@ifi.uio.no>

Jari Aalto wrote:
> Krzysztof Halasa <khc@pm.waw.pl> writes:
> 
>> Jari Aalto <jari.aalto@cante.net> writes:
>>
>>> >From Debian stock kernel:
>>>
>>> $ grep -Ei 'iommu|agp' /boot/config-2.6.25-2-amd64
>>> CONFIG_GART_IOMMU=y
>>> CONFIG_CALGARY_IOMMU=y
>>> CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
>>> CONFIG_IOMMU_HELPER=y
>>> CONFIG_AGP=y
>>> CONFIG_AGP_AMD64=y
>>> CONFIG_AGP_INTEL=m
>>> CONFIG_AGP_SIS=m
>>> CONFIG_AGP_VIA=m
>> Should be fine. SWIOTLB is there for a backup, most (?) Intel machines
>> don't have IOMMU (even the newest desktop boards).
>>
>>> Are these the correct boot options, without swiotlb?
>>>
>>>    iommu=noagp,noaperture,off
>>>
>>> Or just:
>>>
>>>    iommu=off
>> Do you have problems without "iommu=XXX"?
> 
> 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?

No, you can't use iommu=off. If you have memory located over 4GB and 
devices which can only do 32-bit DMA then you need some kind of IOMMU 
support, otherwise things will just blow up.

If you use no options and it's enabled in the kernel config it should be 
using the GART IOMMU built into the CPU on this machine..

       reply	other threads:[~2008-08-24 21:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2008-08-24 22:16             ` 2.6.25 DMA: Out of SW-IOMMU space - Asus M2N32 AMD 8GB memory 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-29 18:45 Gerardo Exequiel Pozzi
2008-08-29 21:31 ` Jari Aalto
  -- strict thread matches above, loose matches on Subject: below --
2008-08-29  3:41 Gerardo Exequiel Pozzi
2008-08-29  6:20 ` Jari Aalto
2008-08-29  7:49 ` Jari Aalto
2008-08-29  8:08   ` 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=48B1D82C.5000107@shaw.ca \
    --to=hancockr@shaw.ca \
    --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