From: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
To: Michael Madore <michael.madore@gmail.com>, linux-kernel@vger.kernel.org
Cc: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: PCI-DMA: high address but no IOMMU (still there)
Date: Sun, 18 Dec 2005 20:07:08 +0000 [thread overview]
Message-ID: <92C54DAE01BADE27ACF9C370@[192.168.100.25]> (raw)
In-Reply-To: <d4b6d3ea0510271047t413e9ea8l333a532c1a5f3d77@mail.gmail.com>
--On 27 October 2005 10:47 -0700 Michael Madore <michael.madore@gmail.com>
wrote:
> Hi,
>
> I am seeing the following errors in /var/log/messages when booting
> 2.6.14-rc5 on a dual Opteron nforce4 motherboard with 8GB of RAM:
For the record, I was seeing the same problem with 2.6.15-rc5 (it
wasn't there on 2.6.12), but the thread I'm replying to isolated the
problem patch.
A workaround here (Phoenix BIOS, Dual Opteron 275, 8GB RAM, 1.02.2895,
Tyan Thunder K8WE (S2895)) is to set the following in BIOS:
* Set Operating System to "Linux"
* Hammer Configuration->Memory Hole->IOMMU set to Enable
* Hammer Configuration->MTRR mapping set to "Discrete"
No idea why this fixes it, nor why it wasn't necessary before,
but it at least boots now.
It hangs in a pretty cryptic way on a default config kernel (well, Ubuntu
Dapper defaults) so it would be nice if this was resolved.
--
Alex Bligh
prev parent reply other threads:[~2005-12-18 20:07 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
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 ` Alex Bligh - linux-kernel [this message]
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='92C54DAE01BADE27ACF9C370@[192.168.100.25]' \
--to=linux-kernel@alex.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.madore@gmail.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 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®