From: Andi Kleen <ak@suse.de>
To: Maurice Volaski <mvolaski@aecom.yu.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: The "Out of IOMMU space" error and the "Please enable the IOMMU option" option
Date: Fri, 16 Jun 2006 10:31:16 +0200 [thread overview]
Message-ID: <200606161031.16554.ak@suse.de> (raw)
In-Reply-To: <a0623094bc0b77aaeba9a@[129.98.90.227]>
On Thursday 15 June 2006 23:17, Maurice Volaski wrote:
> Occasionally, we get errors like these:
>
> Jun 9 00:56:35 [kernel] [18020.416620] PCI-DMA: Out of IOMMU space
> for 12288 bytes at device 0000:03:01.0
> and it looks like it might have something to do with these messages
> (after updating and setting BIOS as below):
>
> Jun 15 16:38:54 [kernel] [ 0.000000] Checking aperture...
> Jun 15 16:38:54 [kernel] [ 0.000000] CPU 0: aperture @ 0 size 256 MB
> Jun 15 16:38:54 [kernel] [ 0.000000] No AGP bridge found
> Jun 15 16:38:54 [kernel] [ 0.000000] Your BIOS doesn't leave a
> aperture memory hole
> Jun 15 16:38:54 [kernel] [ 0.000000] Please enable the IOMMU
> option in the BIOS setup
> Jun 15 16:38:54 [kernel] [ 0.000000] This costs you 64 MB of RAM
> Jun 15 16:38:54 [kernel] [ 0.000000] Mapping aperture over 65536
> KB of RAM @ 8000000
>
> The box is a dual Opteron 250 with an Arima HDAMA Rev. D motherboard.
Not directly - the kernel will create a fallback aperture if it can't
find one provided by the BIOS. The default is 64MB, but it can be
enlarged with iommu=memaper=4
There was also a bug that might have caused this over longer uptimes.
If you still see it with latest 2.6.16.stable (19 or so).
If it still happens with those two changes then something is likely
leaking mappings or your have a extreme workload that needs
a lot of mappings.
> First, am I correct to assume that I'm not getting the 256 MB?
Yes you'll get 64MB fallback likely.
>
> Second, is the the case the BIOS is lying?
Probably yes.
-Andi
next prev parent reply other threads:[~2006-06-16 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 21:17 The "Out of IOMMU space" error and the "Please enable the IOMMU option" option Maurice Volaski
2006-06-16 8:31 ` Andi Kleen [this message]
2006-06-19 20:09 ` Maurice Volaski
2006-06-19 20:35 ` Andi Kleen
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=200606161031.16554.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mvolaski@aecom.yu.edu \
/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