From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de
Subject: The "Out of IOMMU space" error and the "Please enable the IOMMU option" option
Date: Thu, 15 Jun 2006 17:17:32 -0400 [thread overview]
Message-ID: <a0623094bc0b77aaeba9a@[129.98.90.227]> (raw)
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.
The updated BIOS options are (with * for current setting)
MTRR mapping method [Continuous, Discrete*]
Memhole mapping [Software, Hardware*]
4 GB memory hole adjust [Disabled, Manual, Auto*]
4 GB memory hole size [128 MB]
IOMMU [Disabled, Enabled*]
Size [multiple sizes, 256 MB*]
Initially, I was booting kernel 2.6.16.1 with iommu=merge, but the
above message still occur when I booted without any iommu kernel
parameters.
First, am I correct to assume that I'm not getting the 256 MB?
Second, is the the case the BIOS is lying?
Third, what could be a workaround to get enough memory for the PCI
card that causes the out of space error (3Ware 8506)?
--
Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
next reply other threads:[~2006-06-15 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 21:17 Maurice Volaski [this message]
2006-06-16 8:31 ` Andi Kleen
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='a0623094bc0b77aaeba9a@[129.98.90.227]' \
--to=mvolaski@aecom.yu.edu \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®