All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: Michael Madore <michael.madore@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: PCI-DMA: high address but no IOMMU
Date: Sun, 30 Oct 2005 15:59:15 +0100	[thread overview]
Message-ID: <200510301559.15423.ak@suse.de> (raw)
In-Reply-To: <20051030142924.GA30183@us.ibm.com>

On Sunday 30 October 2005 15:29, Nishanth Aravamudan wrote:

> 
> Ah, silly me, I set IOMMU_DEBUG to Y at some point without realizing.
> Taking that away removed the issues and I now only get:
> 
> [    0.000000] Checking aperture...
> [    0.000000] CPU 0: aperture @ 4000000 size 32 MB
> [    0.000000] Aperture from northbridge cpu 0 too small (32 MB)
> [    0.000000] No AGP bridge found
> 
> ...
> 
> [   47.737770] PCI-DMA: Disabling IOMMU.
> 
> Which makes a lot more sense.

And everything works when you disable IOMMU_DEBUG? Is that the case
with the other reporters of this problem too?

-Andi

  reply	other threads:[~2005-10-30 14:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-27 17:47 PCI-DMA: high address but no IOMMU Michael Madore
2005-10-27 17:57 ` Nish Aravamudan
2005-10-27 22:16 ` Andi Kleen
2005-10-27 22:39   ` Michael Madore
2005-10-28  1:59     ` Nishanth Aravamudan
2005-10-30 14:29       ` Nishanth Aravamudan
2005-10-30 14:59         ` Andi Kleen [this message]
2005-10-30 21:26           ` Nishanth Aravamudan
2005-10-30  0:27   ` PCI-DMA: high address but no IOMMU - nForce4 Matti Aarnio
2005-11-01  5:21     ` Marc Perkel
2005-11-02 15:38       ` Andreas Kleen
2005-11-06 12:35         ` Matti Aarnio
2005-11-01 16:35     ` Marc Perkel
2005-12-18 20:07 ` PCI-DMA: high address but no IOMMU (still there) Alex Bligh - linux-kernel

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=200510301559.15423.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.madore@gmail.com \
    --cc=nacc@us.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.