From: Andi Kleen <ak@suse.de>
To: Michael Madore <michael.madore@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI-DMA: high address but no IOMMU
Date: 28 Oct 2005 00:16:51 +0200 [thread overview]
Message-ID: <p73slum38rw.fsf@verdi.suse.de> (raw)
In-Reply-To: <d4b6d3ea0510271047t413e9ea8l333a532c1a5f3d77@mail.gmail.com>
Michael Madore <michael.madore@gmail.com> writes:
> 2.6.14-rc5 on a dual Opteron nforce4 motherboard with 8GB of RAM:
>
> Checking aperture...
> CPU 0: aperture @ be8c000000 size 32 MB
> Aperture from northbridge cpu 0 too small (32 MB)
> No AGP bridge found
> Your BIOS doesn't leave a aperture memory hole
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM
> Mapping aperture over 65536 KB of RAM @ 8000000
>
> ...
>
> PCI-DMA: Disabling AGP.
> PCI-DMA: More than 4GB of RAM and no IOMMU
> PCI-DMA: 32bit PCI IO may malfunction.<6>PCI-DMA: Disabling IOMMU.
>
> ...
>
> Attached scsi disk sda at scsi2, channel 0, id 0, lun 0
> Kernel panic - not syncing: PCI-DMA: high address but no IOMMU.
>
> With 2.6.13, the systems boots OK with these messages in the log:
>
> Checking aperture...
> CPU 0: aperture @ 8000000 size 32 MB
> Aperture from northbridge cpu 0 too small (32 MB)
> No AGP bridge found
> Your BIOS doesn't leave a aperture memory hole
> Please enable the IOMMU option in the BIOS setup
> This costs you 64 MB of RAM
> Mapping aperture over 65536 KB of RAM @ 8000000
>
> ...
>
> PCI-DMA: Disabling AGP.
> PCI-DMA: aperture base @ 8000000 size 65536 KB
> PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
Can you post the full boot log?
> Using git bisect, I narrowed the problem down to the following commit:
>
> 6142891a0c0209c91aa4a98f725de0d6e2ed4918 is first bad commit
> diff-tree 6142891a0c0209c91aa4a98f725de0d6e2ed4918 (from
> 357e11d4cbbbb959a88a9bdbbf33a10f160b0823)
> Author: Andi Kleen <ak@suse.de>
> Date: Mon Sep 12 18:49:24 2005 +0200
>
> [PATCH] x86-64: Avoid unnecessary double bouncing for swiotlb
>
> PCI_DMA_BUS_IS_PHYS has to be zero even when the GART IOMMU is disabled
> and the swiotlb is used. Otherwise the block layer does unnecessary
> double bouncing.
Your system shouldn't be using swiotlb anyways.
-Andi
next prev parent reply other threads:[~2005-10-27 22:16 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 [this message]
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 ` PCI-DMA: high address but no IOMMU (still there) Alex Bligh - linux-kernel
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=p73slum38rw.fsf@verdi.suse.de \
--to=ak@suse.de \
--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