RE: [Xen-devel] DMA trouble with current xen-sparse

WARNING - OLD ARCHIVES

http://lists.xen.org/

To:	"Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject:	RE: [Xen-devel] DMA trouble with current xen-sparse
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Wed, 2 Nov 2005 15:32:58 -0000
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Wed, 02 Nov 2005 15:30:08 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcXcZ7ujFcsGlwrlQjC/T/t8Rj/bNwDWtiEg
Thread-topic:	[Xen-devel] DMA trouble with current xen-sparse

> On 28 Oct 2005, at 20:21, Stephen C. Tweedie wrote:
> 
> > The trouble is that this is a 1G box, so its memory is not large 
> > enough to automatically enable the swiotlb.  
> > (arch/xen/i386/kernel/swiotlb.c enables swiotlb 
> automatically for dom0 
> > only if there's at least 2G of
> > memory.)  And the first time we get a pci_dma_single() 
> request for a 
> > dom0-contiguous region which crosses a page boundary, we hit the 
> > BUG_ON at arch/xen/i386/kernel/pci_dma.c:270 due to 
> dma_map_single() checking:

Does your card support TSO? What revision e1000 is it?

Please can you try turning it off with: 
  ethtool -K eth0 tso off

If TSO is the problem we'll come up with a better fix than using
swiotlb.


Thanks,
Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [Xen-devel] Re: DomU panic in net_rx_action *initiated by another DomU*; 7503:20d1a79ebe31, Keir Fraser

Next by Date:

Re: [Xen-devel] "xm save" trouble -- deadlock?, Gerd Knorr

Previous by Thread:

[Xen-devel] Re: DomU panic in net_rx_action *initiated by another DomU*; 7503:20d1a79ebe31, Charles Duffy

Next by Thread:

Re: [Xen-devel] DMA trouble with current xen-sparse, Stephen Tweedie

Indexes:

[Date] [Thread] [Top] [All Lists]