From: Peter Buckingham <peter@pantasys.com>
To: Sean Bruno <sean.bruno@dsl-only.net>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE)
Date: Fri, 19 Aug 2005 08:38:25 -0700 [thread overview]
Message-ID: <4305FCF1.6020905@pantasys.com> (raw)
In-Reply-To: <1124410753.14825.32.camel@home-lap>
Hi Sean,
Sean Bruno wrote:
> Well, I do have IOMMU enabled in my kernel .config. I have attached it
> to this message as well. I would appreciate any guidance as I pretty
> much have no idea what 99% of the items in here are for. This is
> the .config that I used to build the kernel from the dmesg output that
> is attached to this email.
the error that you see is because you haven't set a big enough size in
the BIOS for the IOMMU. The error message is just saying that the kernel
is enabling the IOMMU anyway. It used to be that it would enable 64MB,
it looks like it's defaulting now to 256MB. When you enable a big enough
size in the bios this error will go away (assuming that your bios fills
in the registers correctly).
peter
next prev parent reply other threads:[~2005-08-19 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124401950.14825.13.camel@home-lap.suse.lists.linux.kernel>
2005-08-18 21:59 ` 2.6.13-rc6-git10 test report [x86_64] Andi Kleen
[not found] ` <1124405533.14825.24.camel@home-lap>
2005-08-18 23:03 ` Andi Kleen
2005-08-18 23:26 ` Sean Bruno
2005-08-19 0:19 ` 2.6.13-rc6-git10 test report [x86_64](WITHOUT NVIDIA MODULE) Sean Bruno
2005-08-19 15:38 ` Peter Buckingham [this message]
2005-08-19 15:46 ` Andi Kleen
2005-08-19 15:52 ` Peter Buckingham
2005-08-19 15:53 ` Andi Kleen
2005-08-19 15:59 ` Peter Buckingham
2005-08-19 16:11 ` Sean Bruno
2005-08-19 16:22 ` Peter Buckingham
2005-08-20 21:35 ` Joseph Fannin
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=4305FCF1.6020905@pantasys.com \
--to=peter@pantasys.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.bruno@dsl-only.net \
/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