From: Andi Kleen <ak@suse.de>
To: c-otto@gmx.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: X86_64 + VIA + 4g problems
Date: 02 Jan 2006 20:01:08 +0100 [thread overview]
Message-ID: <p73bqyufo97.fsf@verdi.suse.de> (raw)
In-Reply-To: <20060102165231.GA23834@carsten-otto.halifax.rwth-aachen.de>
Carsten Otto <c-otto@gmx.de> writes:
[please don't strip cc lists like this - your email got nearly lost]
> On Mon, Jan 02, 2006 at 05:22:12PM +0100, Andi Kleen wrote:
> > When you not compile in the SKGE network driver does everything else work?
> > skge supports 64bit DMA, so it shouldn't use any IOMMU. But I'm somewhat
> > suspicious of the >4GB support in the VIA chipset. We had problems with
> > that before. It's possible that it's just not supported in the hardware
> > or that the BIOS sets up the MTRRs wrong.
>
> How can I find that out? Can I provide any useful material? VIA KT800Pro
> and 4GB RAM here..
What was unclear with my first question? Can you try that?
To repeat it again:
%% When you not compile in the SKGE network driver does everything else work?
%% skge supports 64bit DMA, so it shouldn't use any IOMMU.
Alternatively you can try with the appended patch. If that helps
then the chipset or the BIOS likely has some fundamental issue with >4GB.
-Andi
Index: linux-2.6.15rc7-work/arch/x86_64/kernel/pci-gart.c
===================================================================
--- linux-2.6.15rc7-work.orig/arch/x86_64/kernel/pci-gart.c
+++ linux-2.6.15rc7-work/arch/x86_64/kernel/pci-gart.c
@@ -630,6 +630,13 @@ void dma_unmap_sg(struct device *dev, st
int dma_supported(struct device *dev, u64 mask)
{
+#if 1
+ /* test patch for VIA quirk */
+ if (mask > 0xffffffff)
+ return 0;
+#endif
+
+
/* Copied from i386. Doesn't make much sense, because it will
only work for pci_alloc_coherent.
The caller just has to use GFP_DMA in this case. */
next prev parent reply other threads:[~2006-01-02 19:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 11:09 X86_64 + VIA + 4g problems Dieter Stüken
2006-01-02 12:26 ` Carsten Otto
2006-01-02 16:22 ` Andi Kleen
2006-01-02 16:52 ` Carsten Otto
2006-01-02 17:46 ` Carsten Otto
2006-01-02 19:01 ` Andi Kleen [this message]
2006-01-03 22:54 ` Carsten Otto
2006-01-03 10:04 ` Dieter Stüken
2006-01-03 13:58 ` Andi Kleen
2006-01-03 19:56 ` Dieter Stüken
2006-01-03 21:08 ` Dieter Stüken
2006-01-03 21:26 ` Andi Kleen
2006-01-04 10:27 ` Dieter Stüken
2006-01-04 10:57 ` Andi Kleen
2006-01-04 10:57 ` Dieter Stüken
[not found] <5qvTv-8f-17@gated-at.bofh.it>
[not found] ` <5qAKf-7n4-19@gated-at.bofh.it>
2006-01-02 19:18 ` Robert Hancock
2006-01-02 19:53 ` Andi Kleen
2006-01-02 20:15 ` Robert Hancock
2006-01-02 20:39 ` Andi Kleen
[not found] ` <5qBcJ-7ZZ-5@gated-at.bofh.it>
[not found] ` <5qDez-2Qf-19@gated-at.bofh.it>
[not found] ` <5r2nz-63n-233@gated-at.bofh.it>
2006-01-04 3:03 ` Robert Hancock
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=p73bqyufo97.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=c-otto@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.