WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] xen and mythbackend?

To: "Gordon McLellan" <gordonthree@xxxxxxxxx>
Subject: Re: [Xen-users] xen and mythbackend?
From: "Ben Holt" <beanjammin@xxxxxxxxx>
Date: Wed, 26 Mar 2008 22:03:49 -0700
Cc: James Harper <james.harper@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 26 Mar 2008 22:04:19 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=Pv76V4IeOVkJGM1vEwa8+HTyyCa3QiG43qIVdx+Y5mQ=; b=TX38Bv1joCqOWBVNqfGwxPRIUoqzm0Ki1MvpNSoEdx156qM8tpoNB8iiMmGbat8uUep5pVVww/Mxd7fEORbvKTu9J5eh81Yc0il+WCDHBQYzIPOw8HbFgbzehWQBOzA+gb++lXwLBnZW7rOj2FGbkENVQZJHPEZfuvNJsLWGh8A=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=piu9TeWpagIeuDNdBFwWsIPiJRq+yVSlW2blmj9LWL6h4F8nLIzmzq9O13zddMlq7XMWIj5EGnZqkh2JSWfUknr4Mbaux30vao36FZgbHaZzFSdpPJTvbRUAGIG5XB9pJSO18Q3a0daSoCxZYvfDBbpKT9gDoqZ0mSfau3FpaPU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <f64d94760803251706u639f2261v92b947c866838a94@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <f64d94760803250621g2c0e6682nd154666dcd3d415@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D013DC15D@trantor> <f64d94760803251706u639f2261v92b947c866838a94@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 25/03/2008, Gordon McLellan <gordonthree@xxxxxxxxx> wrote:

>  The card (pvr500) is actually two codecs sharing one pci interface ...
>  both will be capturing video, and then the capture output stops,
>  usually on the second codec only (ivtv1).  All that is reported in the
>  logs is DMA timeout ivtv1.

If you're not running ivtv 0.10.6 grab yourself the most recent ivtv
driver (ivtvdriver.org).  If you are already using 0.10.6 you should
consider a newer kernel and the most recent 1.0.x ivtv driver.  Yes,
building your own kernels can be a drag, but not nearly as much an
unstable box.

You should also look into what IRQs your PVR-500 is using (lspci -v)
and whether it is sharing any with something that requires a lot of
interrupts (like a NIC).  I expect you will find that your second
encoder is sharing an IRQ with something else.  Try to get it so that
both encoders are not sharing IRQs.

Unfortunately underlying hardware issues like what you are
experiencing don't go away when you switch to xen, though often you
can get away with merely restarting the domU that is having problems,
sometimes it'll take down the whole box and/or whatever other piece of
hardware it is conflicting with.  You'll be adding a layer of
complexity to your current set-up.

- Ben

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

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