mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andreas Kleen <ak@suse.de>
To: Marc Perkel <marc@perkel.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
	Michael Madore <michael.madore@gmail.com>,
	linux-kernel@vger.kernel.org, acurrid@nvidia.com
Subject: Re: PCI-DMA: high address but no IOMMU - nForce4
Date: Wed, 2 Nov 2005 16:38:20 +0100 (CET)	[thread overview]
Message-ID: <6079139.1130945900155.SLOX.WebMail.wwwrun@imap-dhs.suse.de> (raw)
In-Reply-To: <56702.69.50.231.10.1130822490.squirrel@mail.ctyme.com>

[full quote]
 
Am Di 01.11.2005 06:21 schrieb Marc Perkel <marc@perkel.com>:

> > On Fri, Oct 28, 2005 at 12:16:51AM +0200, Andi Kleen wrote:
> >
> > I will attach my own; A brand new Amd64 dual-core thing.
> > Works fine with mem=2500M, but blows up with mem=3G or
> > without any override and full 4G complement in use.
> >
> > This board (ASUS A8N-SLI) does use NVIDIA nForce4 chipset with
> > bios-option to map (hoist) "excess memory" out from first 4G to
> > higher physical addresses so that it can be accessed by the
> > processor.
> >
> > This board has no AGP at all in it, but it does have lots
> > of PCIE, and a bit of PCI-X thrown in for "legacy cards".
> > Somehow that detail breaks things when the machine really
> > should use bounce-buffering, or something similar -- I don't
> > know if Nvidia nForce4 chipset does have IOMMU, though...
> >
> > If Nvidia did omit such essential piece of hardware from
> > a modern chipset, I do find it amazingly short-sighted...
> > (Of course they don't yield documentation of the chips to
> > public so that I can't quickly verify this detail...)
>
>
> For what it's worth I have almost the exact same hardware and got the
> same
> error. Athlon X2 4400 with the same ASUS board. Reverting to 2.6.13.2
> kernel works.
>

 
This sounds like the PCI-X BIOS misconfiguration issue that Andy C.
recently
tracked down. Andy do you agree?
 
If yes it's a BIOS problem, but we can probably work around it with a
quirk.
 
-Andi


  reply	other threads:[~2005-11-02 15:38 UTC|newest]

Thread overview: 15+ 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 [this message]
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
2005-10-31 17:50 PCI-DMA: high address but no IOMMU - nForce4 Allen Martin

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=6079139.1130945900155.SLOX.WebMail.wwwrun@imap-dhs.suse.de \
    --to=ak@suse.de \
    --cc=acurrid@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc@perkel.com \
    --cc=matti.aarnio@zmailer.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®