netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Anthony DeRobertis <asd@suespammers.org>
Cc: Stephen Hemminger <shemminger@osdl.org>,
	Martin Michlmayr <tbm@cyrius.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kevin@sysexperts.com
Subject: Re: skge error; hangs w/ hardware memory hole
Date: Tue, 25 Jul 2006 04:35:05 +0200	[thread overview]
Message-ID: <200607250435.05557.ak@suse.de> (raw)
In-Reply-To: <44C317FF.8030705@suespammers.org>

On Sunday 23 July 2006 08:32, Anthony DeRobertis wrote:
> Andreas Kleen wrote:
> 
> > 
> > You need to use iommu=soft swiotlb=force
> > 
> > The standard IOMMU is also broken on VIA, but forced swiotlb should
> > work.
> 
> Didn't work :-(

swiotlb=force is unfortunately broken right now. 

But which this patch it should work. Does it?

-Andi

Test patch only: disable DMA over 4GB

Index: linux-2.6.17-work/arch/x86_64/kernel/pci-dma.c
===================================================================
--- linux-2.6.17-work.orig/arch/x86_64/kernel/pci-dma.c
+++ linux-2.6.17-work/arch/x86_64/kernel/pci-dma.c
@@ -202,7 +202,7 @@ int dma_set_mask(struct device *dev, u64
 {
 	if (!dev->dma_mask || !dma_supported(dev, mask))
 		return -EIO;
-	*dev->dma_mask = mask;
+	*dev->dma_mask = mask & 0xffffffff;
 	return 0;
 }
 EXPORT_SYMBOL(dma_set_mask);


      parent reply	other threads:[~2006-07-25  2:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-03 20:52 skge error; hangs w/ hardware memory hole Martin Michlmayr
2006-07-07 21:18 ` Stephen Hemminger
2006-07-07 21:28   ` Andi Kleen
2006-07-08  8:50     ` Martin Michlmayr
2006-07-09 15:24     ` Anthony DeRobertis
2006-07-12  2:46     ` Anthony DeRobertis
2006-07-12  2:54       ` Andreas Kleen
2006-07-12  4:09         ` Kevin Brown
2006-07-12 13:37           ` Andi Kleen
2006-07-23  6:32         ` Anthony DeRobertis
2006-07-24  2:12           ` Stephen Hemminger
2006-07-25  2:35           ` Andi Kleen [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=200607250435.05557.ak@suse.de \
    --to=ak@suse.de \
    --cc=asd@suespammers.org \
    --cc=kevin@sysexperts.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@osdl.org \
    --cc=tbm@cyrius.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;
as well as URLs for NNTP newsgroup(s).