This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] IVTV and Xen

To: Jason <xen@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] IVTV and Xen
From: Andy Clayton <xen.nospam@xxxxxxxxxx>
Date: Mon, 01 May 2006 00:20:19 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 30 Apr 2006 22:21:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.63.0604302226410.2431@localhost>
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>
References: <Pine.LNX.4.63.0604302226410.2431@localhost>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20060308)
Jason wrote:
Has anyone had any luck getting IVTV .61 working in xen (Im on 3.0 unstable changeset Fri Mar 31 00:26:07 2006 +0100 9494:8a8361994904 because of some unrelated driver issues with another device). I keep getting a DMA issue. If this is fixed in a later rev, I will upgrade but that will be a pretty major undertaking on this particular machine, so I thought I would ask for others experience first. This is what I get when the module inserts, this ia DomU kernel BTW.

It has been a while, but I think I had a similar error with ivtv that could be fixed by passing "swiotlb=force" to the kernel (extra in the configs). This was with an unstable changeset in between 3.0.1 and 3.0.2. When I changed over to 3.0.2 I believe it then started to panic with the setting, but booted fine without. Since I've been busy trying to get a FreeBSD domU to work and have it not panic every two seconds, I have yet to look into it further. Additionally when using that setting I could capture video initially, but after some time it would lock up. I don't know if that issue was related. Anyways it would seem as if something affecting the issue was changed in or around 3.0.2--assuming my memory is even partially correct. That setting may still be worth a try, though, if you do not want to try upgrading.

Sorry for the continuous stream of guessing and I thinks---Hopefully it helps,
Andy Clayton

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>